Summary: | device in use - message received when beginning burn with K3b | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | summersons96-squareformat |
Component: | Burning/Hardware | Assignee: | k3b developers <k3b> |
Status: | CONFIRMED --- | ||
Severity: | grave | CC: | a.skembris, michalm, paka, pgnet.dev+kde, pip.kde, scroogie, simonandric5, tenlegger, trueg |
Priority: | NOR | ||
Version: | 2.0.3 | ||
Target Milestone: | --- | ||
Platform: | PCLinuxOS | ||
OS: | Linux | ||
URL: | http://www.pclinuxos.com/forum/index.php/topic,133018.0.html | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot showing what K3b wants to remove
screenshot of similar dialog; k3b-2.0.80+git on plasma5 |
Description
summersons96-squareformat
2015-06-30 22:09:12 UTC
Created attachment 93442 [details]
Screenshot showing what K3b wants to remove
I'm also having the exact same problem.
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
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? 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. [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 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). I have the same problem, device in user http://wahoo.no-ip.org/~paka/Screenshot_20180324_161145.png (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 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 lsof-4.91-1.1 solves this for me |