On March 24, 2018 6:26:31 PM MST, Patrick Shanahan <paka@opensuse.org> wrote:
* Peter Suetterlin <pit@astro.su.se> [03-24-18 17:50]:
Peter Suetterlin wrote:
Peter Suetterlin wrote:
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
* Patrick Shanahan <paka@opensuse.org> [03-24-18 18:31]: processes that
(only) refer to something in /dev:
And if I use the binary from a Leap 42.3 installation: lux:~ # ./lsof /var/log/Xorg.0.log COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME X 22801 root 4w REG 0,48 51757 113426 /var/log/Xorg.0.log
nothing else. This is lsof-4.89-6.3.x86_64 (leap) vs. lsof-4.90-1.1.x86_64 (TW)
Who opens the bug?
Someone already did, already in February when it was updated: boo#1082900
ok, will install lsof from 42.3 repo, and report
installed lsof-4.89-6.3.x86_64 from 42.3 and k3b works successfully. added comment to https://bugs.kde.org/show_bug.cgi?id=349764
thankyou
How do basic packages like laid drift so badly out of compliance with their documented functionality that long existing packages cease to function and nobody seems to notice? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org