I'm having a weird problem with the kde device notifier. when I connect a thumbdrive to a usb port, everything works as it should. whenever I put a dvd in the drive, nothing happens.
I've tried creating a new user and logging into that account with the same results. With the dvd in the drive, if I type
df -h /dev/sr0
in a console, then the device notifier pops up like it should. when I eject the dvd from the drive w/ the drive button, the device notifier doesn't know it's been ejected until I try to select one of the options from the menu.
This has been happening for quite a while, and the recent update to kde 4.10.5 hasn't fixed this. has anyone seen this before? I've been unable to find anything helpful so far. Thanks for any insight, this one has me puzzled.
would be curious to know how you installed kde. I emerge kde-meta and have it all and putting a dvd into the drive does have device notifier pop up and say so.
I tested it on two different kde machines with funtoo, kde and different hardware. Was no problem.
So something is funny with your system, could be a missing package or use flag. Hard to even guess without knowing if you installed your kde one package at a time, or if you used kde-meta for a one shot deal.
I just tested this on my kde desktop and can confirm the same problem. I do have kde-meta installed so I know it's not missing any packages. Never noticed before as i don't usually use the dvd drive. I don't have a solution but I'll look into it.
I will be happy to help debug.
I have heard of similar errors before, usually is something like dbus or consolekit not being started, or possibly one being started before the other, dbus should be started before consolekit.
But if anything I can help with, let me know.
I installed kde with emerge kde-meta as well. not sure that's much help. I've got 2 machines. this one, the one most up to date is the one that isn't working. I've been testing some ideas & run across this little item, but not sure how to proceed. I ran udevadm monitor, then put a dvd in and eject out and I get no messages. when I do the same on my other machine that does work I get messages like this:
# udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1373355274.604699] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) UDEV [1373355275.182830] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) KERNEL[1373355282.542860] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) UDEV [1373355283.340041] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) KERNEL[1373355292.599875] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) UDEV [1373355292.833338] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) KERNEL[1373355296.603546] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block) UDEV [1373355297.160455] change /devices/pci0000:00/0000:00:14.1/ata5/host4/target4:0:0/4:0:0:0/block/sr0 (block)
also, on the broken machine, when i enter in another shell
the udev monitor shell gives these messages:
KERNEL[1373357522.628691] change /devices/pci0000:00/0000:00:04.0/ata7/host6/target6:0:0/6:0:0:0/block/sr0 (block) UDEV [1373357526.035205] change /devices/pci0000:00/0000:00:04.0/ata7/host6/target6:0:0/6:0:0:0/block/sr0 (block)
I've re-emerged udev just to make sure there wasn't some corruption or something. any ideas?
Last edited by KirkyD (2013-07-09 08:15:19)
I get the same results though i noticed if i put a dvd in the drive before booting it get's found.
Since you have one machine that works and one that doesn't, try comparing kernel configs from them and see what's different.
certainly is madness, I am using gentoo-sources with genkernel on my machines. I just tried it again on a different system, I found a hard drive in desk drawer and it had funtoo/kde installed on it,
So it is 6 months out of date with kde4.9.3 installed and it works as well as latest kde.
My df /dev/sr0 is different though
funfool@funserver ~ $ df /dev/sr0 Filesystem 1K-blocks Used Available Use% Mounted on udev 10240 4 10236 1% /dev
I get the same when booting w/ a dvd in drive. I've used genkernel to build a new gentoo-sources-3.10.0 and no luck. I was using the sys-kernel/debian-sources-3.2.41 before. my other machine is using gentoo-sources-3.5.0.
here's my two configs if you want to have a look. I've got to go to work, but I'll try to compile a kernel on the broke machine with the .config from the working this evening and let you know what happened.
in that archive, "bigdaddy" is the working machine
haven't got my compile done, but I did find this interesting tidbit:
his solution was a little program that accesses the dvd drive every few seconds. not much of a solution. I've also noticed if I have k3b running in the background and put a dvd in, the device notifier works as expected. I assume it's checking the drive every so often like the program above does...
the kernel rebuild doesn't help. I did find the following pages that seem to speak to the problem:
that last one looks very familiar. anyway, their solution is to change "kernel polling" with this type of command
echo 5000 > /sys/module/block/parameters/events_dfl_poll_msecs
but I get a "cannot overwrite existing file" error when I try. changing the > to a >> does the trick though. and it works here sorta. putting a disk in is detected. mount/umount with device-notifier works, but if you eject disk with drive button, it's not detected. they mention a way to make this change survive a reboot, but it doesn't seem to be applicable to funtoo/gentoo. adding block.events_dfl_poll_msecs=5000 to the boot parameters in grub is supposed to do the trick.
Last edited by KirkyD (2013-07-10 09:09:03)
Just wanted to let you know , I played with this for a while, especially with kernel config but to no avail. When I have more time I may try again but for now, I don't have a solution other than the methods you already mentioned
thanks for having a look. on another weird note, if I leave k3b running in the background, ejecting with the drive button gets noticed properly by the device-notifier. I've noticed on my older machine, udisks is older (1.0.4-r3) and 2.0.0 on the broken machine. I'll post back if I find something else.