Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47234 - [packagekit] Failed to get system bus connection: Could not connect: No such file or directory
Attached to Project:
Community Packages
Opened by Ricardo Funke Ormieres (ricardofunke) - Tuesday, 01 December 2015, 23:07 GMT
Last edited by Christian Hesse (eworm) - Thursday, 10 December 2015, 16:57 GMT
Opened by Ricardo Funke Ormieres (ricardofunke) - Tuesday, 01 December 2015, 23:07 GMT
Last edited by Christian Hesse (eworm) - Thursday, 10 December 2015, 16:57 GMT
|
DetailsDescription: When using gnome-software to update, it fails and show me the error "Failed to get system bus connection: Could not connect: No such file or directory" in the next login
gnome-software 3.18.3-1 packagekit 1.0.11-1 journalctl says: Dez 01 20:23:50 funkenote pk-offline-update[537]: failed to change mode for splash: Failed to execute child process "plymouth" (No such file or directory) Dez 01 20:23:50 funkenote pk-offline-update[537]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory) Dez 01 20:23:50 funkenote pk-offline-update[537]: Failed to get system bus connection: Could not connect: No such file or directory Dez 01 20:23:50 funkenote systemd[1]: packagekit-offline-update.service: Main process exited, code=exited, status=1/FAILURE Dez 01 20:23:50 funkenote systemd[1]: packagekit-offline-update.service: Unit entered failed state. Dez 01 20:23:50 funkenote systemd[1]: packagekit-offline-update.service: Triggering OnFailure= dependencies. Dez 01 20:23:50 funkenote systemd[1]: packagekit-offline-update.service: Failed with result 'exit-code'. Note: I don't have anything related to plymouth installed Steps to reproduce: Just try to do the offline update using gnome-software |
This task depends upon
Closed by Christian Hesse (eworm)
Thursday, 10 December 2015, 16:57 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed with packagekit 1.0.11-2.
Thursday, 10 December 2015, 16:57 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed with packagekit 1.0.11-2.
dbus 541 0.0 0.0 36328 5224 ? Ss Dez02 0:47 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
gdm 656 0.0 0.0 34828 3836 ? Ss Dez02 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
gdm 1316 0.0 0.0 34612 3656 ? S Dez02 0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
ricardo+ 1417 0.0 0.0 35792 4912 ? Ss Dez02 0:03 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
ricardo+ 1428 0.0 0.0 34744 3636 ? S Dez02 0:01 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
daemon 16420 0.0 0.0 76536 5320 ? S Dez03 0:00 /usr/lib/cups/notifier/dbus dbus://
ricardo+ 29848 0.0 0.0 10752 2192 pts/2 S+ 00:18 0:00 grep dbus
systemctl
{...}
dbus.service loaded active running D-Bus System Message Bus
{...}
dbus.socket loaded active running D-Bus System Message Bus Socket
{...}
I don't know what you're meaning, but this is what I could answer based on what I think you want to know.
Don't know the status of these during the update though.
Here is related information from Fedora:
https://fedoraproject.org/wiki/Features/OfflineSystemUpdates
I didn't find anything in this article that shows what or why it doesn't work in Arch or maybe I didn't understand your point.
I installed plymouth as described in the wiki. It works now (does not show me any progress anymore while updating ;( )
http://freedesktop.org/wiki/Software/systemd/SystemUpdates/
I still think that we do not support that. Probably gnome-software thinks we do... So two questions arise:
Why does it think we do support it?
How to prevent gnome-software from doing offline updates?
This isn't just a matter of bugs. The way it operates (automated offline upgrades) is contrary to how Arch upgrades, which may require user intervention before or after the upgrade in order to retain a usable system.
If I downgrade systemd to 227 offline updates work again, maybe there's a bug in systemd 228?
If gnome-software is very unsupported, why it's included in the official repositories?
Even more, I could not get it working myself. Can you give a step-by-step description what you do for an offline update? I do prefer pkcon (the packagekit console client, so no gnome-software, please - if possible).
$ sudo pkcon offline-trigger
$ reboot
Can you try to add "Requires=dbus.service" to packagekit-offline-update.service and test again, please? The file should look something like that:
[Unit]
Description=...
Requires=dbus.service
OnFailure=reboot.target
[...]
So no, just edit the file, prepare and trigger the offline update and reboot.
https://github.com/hughsie/PackageKit/pull/99