|
Bugzilla – Full Text Bug Listing |
| Summary: | PackageKit is restarted during update interrupting session | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Andrei Borzenkov <arvidjaar> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | badshah400, dimstar |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andrei Borzenkov
2016-01-23 07:29:52 UTC
And if you were updating via the offline-updates method (as I was), the same PK update simply hung the system in the non-gui installing-updates mode with the only way out being switching to a different VT and effecting a manual "shutdown". The reason I believe this is the same bug is because I got the same journal logs, notably with the message "scriptlet %postun(PackageKit-1.0.11-1.1.x86_64) failure: 2".* After effecting the manual shutdown and then booting in as usually, gnome-software shows "Updates failed to install". The only way to successfully install the update stack (20160120 I believe it was) was to use zypper. In the latter case, the update went swimmingly. Should be critical in my opinion, esp. for those using GNOME doing the update via the recommended way of offline installs. * Jan 21 13:53:12 linux-b3rv [RPM][16099]: scriptlet %postun(PackageKit-1.0.11-1.1.x86_64) failure: 2 (In reply to Atri Bhattacharya from comment #1) > * Jan 21 13:53:12 linux-b3rv [RPM][16099]: scriptlet > %postun(PackageKit-1.0.11-1.1.x86_64) failure: 2 grmbl... postun does not have ANY command that could potentially fail: postuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then if test -x /usr/bin/update-mime-database; then /usr/bin/update-mime-database "/usr/share/mime" || true fi fi # Do not restart PackageKit on upgrade - it kills the transaction export DISABLE_RESTART_ON_UPDATE=yes test -n "$FIRST_ARG" || FIRST_ARG="$1" if [ "$FIRST_ARG" -ge 1 ]; then # Package upgrade, not uninstall if [ -x /usr/bin/systemctl ]; then /usr/bin/systemctl daemon-reload || : ( test -f /etc/sysconfig/services && . /etc/sysconfig/services test "$YAST_IS_RUNNING" = instsys && exit 0 test "$DISABLE_RESTART_ON_UPDATE" = yes && exit 0 ^^^ Latest here, the script will be ended in an upgrade case anyway... so everything below won't ever run /usr/bin/systemctl try-restart packagekit.service || : ) fi else # package uninstall for service in packagekit.service ; do sysv_service="${service%.*}" rm -f "/var/lib/systemd/migrated/$sysv_service" || : done if [ -x /usr/bin/systemctl ]; then /usr/bin/systemctl daemon-reload || : fi fi test -n "$FIRST_ARG" || FIRST_ARG="$1" if [ "$FIRST_ARG" -ge 1 ]; then # Package upgrade, not uninstall if [ -x /usr/bin/systemctl ]; then /usr/bin/systemctl daemon-reload || : ( test -f /etc/sysconfig/services && . /etc/sysconfig/services test "$YAST_IS_RUNNING" = instsys && exit 0 test "$DISABLE_RESTART_ON_UPDATE" = yes && exit 0 /usr/bin/systemctl try-restart packagekit-offline-update.service || : ) fi else # package uninstall for service in packagekit-offline-update.service ; do sysv_service="${service%.*}" rm -f "/var/lib/systemd/migrated/$sysv_service" || : done if [ -x /usr/bin/systemctl ]; then /usr/bin/systemctl daemon-reload || : fi fi The recent resart of xdm during installation helped in uncovering the root for this issue as well: https://build.opensuse.org/package/rdiff/openSUSE:Factory/systemd-rpm-macros?linkrev=base&rev=14 That change made the variable, exported during the script execution, no longer have any effect. WEll, if the X-Team does not accept that this depends on the outcome of the other bug, then I mark is a DUP - the same root cause - the same broken systemd macros. *** This bug has been marked as a duplicate of bug 968405 *** |