[Bug 924346] New: Plasma5 install to openSUSE Tw, Hung during installation of kpackage
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 Bug ID: 924346 Summary: Plasma5 install to openSUSE Tw, Hung during installation of kpackage Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: pat@indy.rr.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- attempting to install plasma5 to my openSUSE Tw system hung during install of kpackage. Was not recoverable. After an extended period, reformatted and reinstalled Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 patrick shanahan <pat@indy.rr.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pat@indy.rr.com --- Comment #1 from patrick shanahan <pat@indy.rr.com> --- https://bugs.kde.org/show_bug.cgi?id=345528 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 Hrvoje Senjan <hrvoje.senjan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hrvoje.senjan@gmail.com, | |zypp-maintainers@forge.prov | |o.novell.com Flags| |needinfo?(zypp-maintainers@ | |forge.provo.novell.com) --- Comment #2 from Hrvoje Senjan <hrvoje.senjan@gmail.com> --- @zyppers, do you have some ideas what could have happened? This was also mentioned here: http://lists.opensuse.org/opensuse-factory/2015-03/msg00224.html The 5.8.0 kpackage update was mostly trivial (https://build.opensuse.org/request/show/290595) so i doubt the package alone had to do with this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 --- Comment #3 from patrick shanahan <pat@indy.rr.com> --- (In reply to Hrvoje Senjan from comment #2)
@zyppers, do you have some ideas what could have happened? This was also mentioned here: http://lists.opensuse.org/opensuse-factory/2015-03/msg00224.html
The 5.8.0 kpackage update was mostly trivial (https://build.opensuse.org/request/show/290595) so i doubt the package alone had to do with this issue.
No unfortunately. All I really know was provided in the msg thread you cite. I was the author of that post. Luca Beltrame requested testing and I obliged, but the Tw update provided many packages and zypper hung while installing kpackage. I could not coax zypper to recover, finally resorting to reinstall after waiting a week for help elicited in my posts in the thread you reference. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(zypp-maintainers@ | |forge.provo.novell.com) | --- Comment #6 from Michael Andres <ma@suse.com> --- I suspect that one of the plugins (/usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.py and/or /usr/lib/zypp/plugins/commit/snapper.py) cause some daemon to be started. The daemon does not close it's stdout (inherited from the plugin). This way the pipe is not closed and we hang trying to read the plugins final data. I'll check the zypp code to make sure we're always protected against such miss behaving deamons. The plugin code uses a slightly different code path than the rpm-install (where miss behaving deamons launched in %pre/%post scripts dont bit us). If you can identify the daemon (some snapper related stuff) and kill it, zypper should continue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 --- Comment #7 from patrick shanahan <pat@indy.rr.com> --- (In reply to Michael Andres from comment #6)
I suspect that one of the plugins (/usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.py and/or /usr/lib/zypp/plugins/commit/snapper.py) cause some daemon to be started.
The daemon does not close it's stdout (inherited from the plugin). This way the pipe is not closed and we hang trying to read the plugins final data. I'll check the zypp code to make sure we're always protected against such miss behaving deamons. The plugin code uses a slightly different code path than the rpm-install (where miss behaving deamons launched in %pre/%post scripts dont bit us).
If you can identify the daemon (some snapper related stuff) and kill it, zypper should continue.
I did kill it, but it do not continue and, if memory servers would not restart. And checked that instance was closed/killed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=924346 http://bugzilla.opensuse.org/show_bug.cgi?id=924346#c8 Libor Pechacek <lpechacek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |lpechacek@suse.com Resolution|--- |FIXED --- Comment #8 from Libor Pechacek <lpechacek@suse.com> --- I assume the issue is long gone. Reopen the bug if it's not the case. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com