Peter Suetterlin wrote:
Knurpht - Gertjan Lettink wrote:
Probably related to the removal of wodim from Tumbleweed.
Thought so too, first. But the message appears before cdrecord is even started, and it explicitely refers to k3b, so I think it must be some test k3b itself executes, that gets weird info back.
kernel? udev? lsof?
Clearly lsof is broken somehow. Try something like 'lsof /var/log/Xorg.0.log'. I get 1 process actually accessing it, and 140+ lines for other processes that (only) refer to something in /dev: lux:~ # lsof /var/log/Xorg.0.log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME X 22801 root 4w REG 0,48 51757 113426 /var/log/Xorg.0.log . . . bash 23484 pit 0u CHR 136,0 0t0 3 /dev/pts/0 bash 23484 pit 1u CHR 136,0 0t0 3 /dev/pts/0 bash 23484 pit 2u CHR 136,0 0t0 3 /dev/pts/0 bash 23484 pit 255u CHR 136,0 0t0 3 /dev/pts/0 and so on. And k3b uses lsof, as you can see if you start it from a terminal. Indeed, a 'lsof /dev/sr0' will list you tons of provesses accessing /dev/pts/* or /dev/nvidia*. /dev/sr0 does not show up in that list though... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org