[Bug 1020226] New: During update process stops at 'installing dbus' with network disconnected
http://bugzilla.opensuse.org/show_bug.cgi?id=1020226 Bug ID: 1020226 Summary: During update process stops at 'installing dbus' with network disconnected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dutchkind@txoriaskea.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- During update of Tumbleweed this morning the update stopped in the middle when dbus was being updated. I had to reboot via command line since nothing could be done to fix it. This left me with plasma workspace unusable and I had to use another desktop manager and install the remaining packages manually via yast. This afternoon my daughter called me with the same problem and she didn't have other desktop managers installed so she had to log in with icewm and connect via nmcli and then run yast When I had my own desktop up and running again I did a zypper verify which told me dbus-1 had to be uninstalled so I said 'yes', after which my system shut down. Maybe normal behavior, maybe related to this bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020226 http://bugzilla.opensuse.org/show_bug.cgi?id=1020226#c1 Bill Wayson <bill_wayson@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bill_wayson@yahoo.com --- Comment #1 from Bill Wayson <bill_wayson@yahoo.com> --- I believe bug 1020227 is related to this one. This issue struck me this week on two separate computers. The first time I saw it (Tuesday, January 17), I rebooted just as the bug reporter did, and now that installation of Tumbleweed is pretty messed up, and I will be reinstalling TW. On the second computer I experienced it on (Wednesday, January 18), I switched to a different virtual console (<Ctrl><Alt><F1>) while the updater GUI said "Installing dbus-1", logged on as root, and executed "zypper up". I let this complete, then rebooted from the virtual terminal. After a small amount of use of that computer, it seems to be running fine. One thing I noticed in the second instance is that the CPU fan, which was racing, indicated that CPU usage was very high. There was a zombie python process which had, as its parent, the HPLIP system tray applet. I killed HPLIP, which immediately reduced the fan noise. Unfortunately, it did not help in any other noticeable way. Both PCs multi-boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1020226 http://bugzilla.opensuse.org/show_bug.cgi?id=1020226#c3 --- Comment #3 from David Kerkhof <dutchkind@txoriaskea.org> --- Reading bug 1020227 I see it's the same bug, don't know what to do, continue here or there? Anyway, my wife started an update and when I got home saw the same dbus thing :( Since her desktop has a wired connection it apparently had still an internet connection so I run zypper dup --no-allow-vendor-change in a konsole and it updated all kinds of stuff. Because my laptop was pretty messed up I restored a partition image and did the update in a konsole without a problem, so it may have to do with the update app in Plasma. Reboot was fine except logging in gave lot's of difficulties. I logged in via ssh and saw in .xsession-errors-:0 errors with bluez, and since it doesn't have bluetooth I uninstalled bluez and after a reboot could log in. Next day same problem again, so did zypper verify which told me to remove dbus-1, which I did, and then it worked more or less fine. More or less, because since the 170117 update both pc's, mine and the desktop, have stability issues. Like now, my task bar is frozen here while I type, and 5 minutes ago had to restart the desktop via ssh because it had the same issue. Both with Plasma workspace. My laptop has Intel graphics and the desktop is older and has Radeon 2400 Graphics. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com