Patrick Shanahan wrote:

* Patrick Shanahan [03-24-18 15:17]:

...

don't use them much any more, but had occasion to need to burn a dvd and k3b puts up a window full of processes, mostly bash, that it says need to be closed to proceed. says those processess will interfer with burning. and closing those processes restarts the graphics.target.

not finding a quick solution, installed xfburn and burned iso to dvd w/o problem.

:)

...

just wondered if anyone else noticed a problem.

Have not used it in some time...

...

next step is to remove complete k3b and configurations and reinstall.

not thinking, Tumbleweed, k3b-17.12.3-76.1.x86_64

Where is it from? My TW repo says recent is k3b-17.12.2-1.1.x86_64 (just refreshed)... (I'd not expect it to be really related, but latest update replaced wodim with cdrecord - not sure if k3b makes use of any of those) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

...

...

...

next step is to remove complete k3b and configurations and reinstall.

not thinking, Tumbleweed, k3b-17.12.3-76.1.x86_64

Where is it from? My TW repo says recent is k3b-17.12.2-1.1.x86_64 (just refreshed)...

(I'd not expect it to be really related, but latest update replaced wodim with cdrecord - not sure if k3b makes use of any of those)

just reinstalled after wiping all config. app is from: http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Factory...

don't recall why I have this repo, but 190+ pkgs from there and /etc/repos.d/ shows I have had it since at least Sept 2015.

will retry present ver, and then, if necessary, install version from OSS.

Just tried a (simulate) burn using the TW k3b (with cdrecord backend). I also got a warning that my browser(!?) is 'acessing the drive', but I ignored it and pressed 'continue'. I checked with lsof, but couldn't see anything looking like my DVD drive being accessed by the browser... No issues with the 'burn'. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Patrick Shanahan [03-24-18 16:19]:

* Peter Suetterlin [03-24-18 16:08]:

...

Patrick Shanahan wrote:

...

...

...

...

next step is to remove complete k3b and configurations and reinstall.

not thinking, Tumbleweed, k3b-17.12.3-76.1.x86_64

Where is it from? My TW repo says recent is k3b-17.12.2-1.1.x86_64 (just refreshed)...

(I'd not expect it to be really related, but latest update replaced wodim with cdrecord - not sure if k3b makes use of any of those)

just reinstalled after wiping all config. app is from: http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Factory...

don't recall why I have this repo, but 190+ pkgs from there and /etc/repos.d/ shows I have had it since at least Sept 2015.

will retry present ver, and then, if necessary, install version from OSS.

Just tried a (simulate) burn using the TW k3b (with cdrecord backend).

I also got a warning that my browser(!?) is 'acessing the drive', but I ignored it and pressed 'continue'. I checked with lsof, but couldn't see anything looking like my DVD drive being accessed by the browser...

No issues with the 'burn'.

installed k3b-17.12.2-1.1.x86_64 from OSS with same result. screenshot of problem: http://wahoo.no-ip.org/~paka/Screenshot_20180324_161145.png

quitting the other applications, exits graphical target

is see it here: https://forum.kde.org/viewtopic.php?f=153&t=125732 and bug 394764 https://bugs.kde.org/show_bug.cgi?id=349764 has some age last report 2018-03-01 09:17:56 UTC no solution or work-a-round and I have no wodim installed added comment to kde bug report -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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 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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Peter Suetterlin [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 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 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On March 24, 2018 6:26:31 PM MST, Patrick Shanahan wrote:

...

* Peter Suetterlin [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 [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

* Felix Miata [03-24-18 16:19]:

Patrick Shanahan composed on 2018-03-24 15:16 (UTC-0400):

...

don't use them much any more, but had occasion to need to burn a dvd and k3b puts up a window full of processes, mostly bash, that it says need to be closed to proceed. says those processess will interfer with burning. and closing those processes restarts the graphics.target.

...

not finding a quick solution, installed xfburn and burned iso to dvd w/o problem.

...

just wondered if anyone else noticed a problem.

...

next step is to remove complete k3b and configurations and reinstall.

Different, but maybe related foundationally: https://bugzilla.opensuse.org/show_bug.cgi?id=1077190 RAM & swap exhaustion abend attempting to copy DVD with (kde3) K3B

I have no swap, but 32GIG memory. should not need swap.

free -m total used free shared buff/cache available Mem: 36189 8697 7617 589 19873 27462 Swap: 0 0 0

tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Fraser_Bell [03-24-18 19:22]:

On 03/24/2018 12:16 PM, Patrick Shanahan wrote:

...

don't use them much any more, but had occasion to need to burn a dvd and k3b puts up a window full of processes, mostly bash, that it says need to be closed to proceed. says those processess will interfer with burning. and closing those processes restarts the graphics.target.

not finding a quick solution, installed xfburn and burned iso to dvd w/o problem.

just wondered if anyone else noticed a problem.

next step is to remove complete k3b and configurations and reinstall.

In openSUSE Beta 15.0 (updated to latest at the time):

Just had it happen a couple days ago when I burned an Audio CD. Same result when closing the processes.

I reran it, ignored the warning, and had no issues burning the disk.

... but seeing that you have the same problem, you should register it as a bug.

it is on kde: https://bugs.kde.org/show_bug.cgi?id=349764 but it appears the problem is k3b calling lsof and tw version of lsof failing, ... suggestion is to use lsof from 42.3 repo and I am going to try. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org