Bug 349764 - device in use - message received when beginning burn with K3b
Summary: device in use - message received when beginning burn with K3b
Status: CONFIRMED
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 2.0.3
Platform: PCLinuxOS Linux
: NOR grave
Target Milestone: ---
Assignee: k3b developers
URL: http://www.pclinuxos.com/forum/index....
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-30 22:09 UTC by summersons96-squareformat
Modified: 2018-04-16 15:08 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing what K3b wants to remove (92.54 KB, image/png)
2015-07-01 07:52 UTC, RoadRunner
Details
screenshot of similar dialog; k3b-2.0.80+git on plasma5 (59.48 KB, image/png)
2015-08-22 15:43 UTC, pgnet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description summersons96-squareformat 2015-06-30 22:09:12 UTC
open K3b; select ISO; allow K3b to do what it needs to do (computing md5sum; click start (to begin the operation); warning message appears - pop up window

Reproducible: Always

Steps to Reproduce:
1.choose burn image from K3b
2.set options
3.click 'start'

Actual Results:  
warning message - short extract follows of what appears in the message/warning window.
 Link given to this message above:
Device 'ATAPI -iHAS524 B'  Already in use by other applications (gpg-agent, 4, dbus-launch, 3014, 3, 3015, ... lsof, 6)
It is highly recommended to quit those before continuing. Otherwise K3b might not be able to fully access the device.
Hint: Sometimes shutting down an application does not happen instantly. In that case you might have to use the 'Check again' button.
Buttons:
'Check again' 'Quit the other applications' 'Continue'

Expected Results:  
K3b should have proceeded with the burn after clicking the start button.

When you look at the thread link above where I posted about the bug please note that other users have noted seeing the same warning message as I do.

Experimentation shows that by, for example, choosing 'Quit the other applications' the unwary user has closed down their Desktop and is left at a black screen. It is easy to get out of this - but the user should not have to.
Comment 1 RoadRunner 2015-07-01 07:52:39 UTC
Created attachment 93442 [details]
Screenshot showing what K3b wants to remove

I'm also having the exact same problem.
Comment 2 pgnet 2015-08-22 15:43:28 UTC
Created attachment 94174 [details]
screenshot of similar dialog; k3b-2.0.80+git on plasma5

Similar screenshot; should mv this to -> confirmed

This is with

rpm -qa | egrep -i "k3b-2|plasma5-desktop-"
 k3b-2.0.80+git20150209.2250-1.5.x86_64
 plasma5-desktop-5.3.91git~20150821T120904~da2274c-135.1.x86_64
Comment 3 Andre Gemünd 2015-09-19 11:08:46 UTC
Same happens here on OpenSUSE Tumbleweed with k3b-2.0.80+git20150209.2250-1.10.x86_64 (didnt upgrade recently).
Should we provide some additional information?
Comment 4 Andre Gemünd 2015-09-19 12:51:44 UTC
Can't I edit a comment? 
However, to check if the device is in use k3b calls 

lsof -Fpc dev->blockDeviceName()

e.g. 

lsof -Fpc /dev/sr0

In my case, that indeed outputs all of the processes it shows in the dialog (k3blsofwrapperdialog).
The problem seems to be that lsof outputs pipes with these parameters, which you see when you omit the field selection parameter (-Fpc) :

$ lsof -w /dev/sr0 
COMMAND     PID    USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
dbus-laun  1451 gemuend    8r  FIFO   0,10      0t0  23646 pipe
gvfsd      1468 gemuend    6r  FIFO   0,10      0t0  21185 pipe
gvfsd      1468 gemuend    7w  FIFO   0,10      0t0  21185 pipe
at-spi-bu  1513 gemuend    4r  FIFO   0,10      0t0  21214 pipe
at-spi-bu  1513 gemuend    5w  FIFO   0,10      0t0  21214 pipe
start_kde  1577 gemuend    0r  FIFO   0,10      0t0  21277 pipe
start_kde  1577 gemuend    3r  FIFO   0,10      0t0  21278 pipe
kdeinit5   1578 gemuend    0r  FIFO   0,10      0t0  21277 pipe
kdeinit5   1578 gemuend    3r  FIFO   0,10      0t0  22707 pipe
kdeinit5   1578 gemuend    4w  FIFO   0,10      0t0  21278 pipe
kdeinit5   1578 gemuend    6w  FIFO   0,10      0t0  22707 pipe
klauncher  1579 gemuend    0r  FIFO   0,10      0t0  21277 pipe
klauncher  1579 gemuend    6r  FIFO   0,10      0t0  22716 pipe
klauncher  1579 gemuend    8w  FIFO   0,10      0t0  22716 pipe
klauncher  1579 gemuend   12r  FIFO   0,10      0t0  21295 pipe
klauncher  1579 gemuend   13w  FIFO   0,10      0t0  21295 pipe
kded5      1582 gemuend    0r  FIFO   0,10      0t0  21277 pipe
kded5      1582 gemuend    6r  FIFO   0,10      0t0  22121 pipe
kded5      1582 gemuend    8w  FIFO   0,10      0t0  22121 pipe
kded5      1582 gemuend   21w  FIFO   0,10      0t0  21324 pipe
kded5      1582 gemuend   22r  FIFO   0,10      0t0  21325 pipe
[...]

Does someone know by heart how to omit pipes and sockets with lsof? Otherwise I will try to investigate tomorrow and maybe provide a patch.
Comment 5 summersons96-squareformat 2015-09-21 02:20:59 UTC
[quote/]Does someone know by heart how to omit pipes and sockets with lsof?[/quote}

Hi Andre, I can only speak for myself and I have to say I do not know how to do what you suggest.

Thank you for keeping us udated,

Hugh
Comment 6 Angelos Skembris 2018-03-01 09:17:56 UTC
I am getting quite a lot of this as well after the latest update to k3b 17.12.2, KF5 5.43, I am trying to rip my CDs to audio files. 

Running openSUSE tumbleweed, kernel 4.15.5.

Before the update (kernel 14.4, KF5 5.40 or something) I was also getting this, but with much fewer applications, so "check again" would work. Currently check again does help much (the same applications are listed).

Also, every application with a tray icon is also listed (e.g. viber).
Comment 7 Patrick Shanahan 2018-03-24 20:26:07 UTC
I have the same problem, device in user
  http://wahoo.no-ip.org/~paka/Screenshot_20180324_161145.png
Comment 8 Patrick Shanahan 2018-03-24 20:26:56 UTC
(In reply to Patrick Shanahan from comment #7)
> I have the same problem, device in user
>   http://wahoo.no-ip.org/~paka/Screenshot_20180324_161145.png

openSUSE Tumbleweed
Comment 9 Patrick Shanahan 2018-03-25 00:54:36 UTC
on openSUSE Tumbleweed, reverting to lsof-4.89-6.3.x86_64 solves this problem for me.  

lsof-4.90-1.1.x86_64
lsof-4.90-50.3.x86_64

both cause k3b to fail for me
Comment 10 Patrick Shanahan 2018-04-16 15:08:37 UTC
lsof-4.91-1.1

solves this for me