You are not logged in.
OK, so I'm having trouble with cdemu again. This time it's not about mounting an image, but getting rid of it ![]()
Essentially, when I load an image with the cdemu client, KDE Device Notifier immediately recognises it as an inserted optical media... which is cool.
However, when I try to unload it with cdemu, it stays "stuck" in KDE Device Notifier, and I can't access any other image which I mount via cdemu afterwards.
In other words, I do the following...
cdemu load 0 <name>.isoThe image appears to be successfully loaded, and I can access it's contents with no trouble at all. KDE Device Notifier sees it normally, can mount it and open it in Dolphin.
Then, when I'm done with it, I do the following...
cdemu unload 0This apparently unloads the image, as I can't open it in Dolphin anymore (or any other application within KDE), but KDE Device Notifier still sees it as if the "optical drive" is inserted, and it won't go away. If I try loading another image in cdemu, KDE will still see the previous one, and I won't be able to do anything with it.
I cannot mount or unmount it, I cannot open it in Dolphin or any other application (obviously, because the image isn't mounted anymore), but KDE Device Notifier still insists that it's there, and won't let me access any other image mounted via cdemu.
Since I have very little experience with cdemu and KDE's logs, I don't know what else I should post here, or where to find it...
Any advice or idea would be much appreciated. TIA! ![]()
Only the best is good enough.
Offline