Iiiintersting!
SilverWave, since the cdrom_id output looks so similar to jocko's, I assume that downgrading udev to -5 will fix the behaviour for you as well?
Since this problem does not reproduce on my hardware, I have to annoy you some more, I'm afraid. Can you please do
sudo strace -vvfo /tmp/cdrom_id_new.trace -s 1024 /lib/udev/cdrom_id /dev/sr0
with the current lucid udev version (151-8), then downgrade to 151-5, and do
sudo strace -vvfo /tmp/cdrom_id_old.trace -s 1024 /lib/udev/cdrom_id /dev/sr0
and then attach /tmp/cdrom_id_old.trace and /tmp/cdrom_id_new.trace ?
Alternatively, ssh access to an affected box would be the debugging luxury for me, of course. :-) (https://launchpad.net/~pitti/+sshkeys , martin@tick)
Thanks!
Iiiintersting!
SilverWave, since the cdrom_id output looks so similar to jocko's, I assume that downgrading udev to -5 will fix the behaviour for you as well?
Since this problem does not reproduce on my hardware, I have to annoy you some more, I'm afraid. Can you please do
sudo strace -vvfo /tmp/cdrom_ id_new. trace -s 1024 /lib/udev/cdrom_id /dev/sr0
with the current lucid udev version (151-8), then downgrade to 151-5, and do
sudo strace -vvfo /tmp/cdrom_ id_old. trace -s 1024 /lib/udev/cdrom_id /dev/sr0
and then attach /tmp/cdrom_ id_old. trace and /tmp/cdrom_ id_new. trace ?
Alternatively, ssh access to an affected box would be the debugging luxury for me, of course. :-) (https:/ /launchpad. net/~pitti/ +sshkeys , martin@tick)
Thanks!