when trying to burn a cd..
device is already in use by other applications: and it lists all core kde apps : dbus-launcher, tracker-miner, akonadi, and about 20 more....
If i quit the apps my desktop crashes..
I've look ed around for answers but coudn't find any. I have no idea where to start

as its not a KDE app I'd start with stopping tracker with

Code: Select all

 tracker-control --terminate=all

as I have no idea it might help to list the exact emessage with all the apps listed, could help someone else figure it out

the crash is caused by closing all the apps? is that an option when the "in use" message displays?

google01103 wrote:as its not a KDE app I'd start with stopping tracker with

Code: Select all

 tracker-control --terminate=all

as I have no idea it might help to list the exact emessage with all the apps listed, could help someone else figure it out

the crash is caused by closing all the apps? is that an option when the "in use" message displays?

here's a link to the dialogue image [img]https://lh6.googleusercontent.com/-RS9i5X8zRwc/VSIWmV4kzEI/AAAAAAAAAjg/xFrWFDRFNKI/w606-h390-no/snapshot1-K3b.png[/img]
yes, the crash happens when I hit the button to close the apps

If I continue regardless, Kb3 goes through the motions of burning the disk, hails it as successful but there is nothing on the disk and it still shows as a blank disk. On the same computer in mswindows7 it works.

Also the reason tracker is on my computer is because GNOME session is installed, but I don't know how to stop it from starting under KDE

sorry but I have never seen anything quite like that message

with all those processes "using" the disc just killing tracker probably won't help but just so you know running "tracker-control --terminate=all" in Konsole should stop it

does rebooting help?

for convenience here's an embedded copy of the error

Several people on the PCLinuxOS forum report seeing this error on multiple distros. See http://www.pclinuxos.com/forum/index.php/topic,133018.0/topicseen.html. If you look at the application list, it includes KDE processes by name and all other processes by PID, including "1" - which is init/systemd! Clearly, it's not just listing processes using the writer but all processes in the tree on which the one trying to access the writer (K3B itself, perhaps?) depend, or just the entire process table.

This would appear to be a bug, as most of these processes have nothing to do with accessing an optical drive, and are therefore being listed in error.

I've been seeing the same problem for a while now, if I select "Continue" (ie, ignore the 'in use' error) then the write proceeds without any problem.

There's mention of it on the openSUSE forums, https://forums.opensuse.org/showthread. ... in-use-K3b albeit with no solution

Just as a follow up... this has now been reported on bugzilla.
https://bugs.kde.org/show_bug.cgi?id=349764