Community Packages

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!
Tasklist

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
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: 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.
Comment by Doug Newgard (Scimmia) - Wednesday, 02 December 2015, 03:34 GMT
Do you have dbus running in your user session?
Comment by Doug Newgard (Scimmia) - Friday, 04 December 2015, 00:08 GMT
Ping?
Comment by Ricardo Funke Ormieres (ricardofunke) - Friday, 04 December 2015, 02:21 GMT
[ricardofunke@funkenote ~]$ ps aux | grep dbus
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.
Comment by Christian Hesse (eworm) - Friday, 04 December 2015, 10:56 GMT
I do not think that things are in place for offline updates to work in Arch Linux, no?

Here is related information from Fedora:
https://fedoraproject.org/wiki/Features/OfflineSystemUpdates
Comment by Ricardo Funke Ormieres (ricardofunke) - Friday, 04 December 2015, 13:38 GMT
Well, I'm not the package maintainer, so I don't know, I'm only reporting the problem. Things used to work until last updates though.

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.

Comment by Remko (Malrak) - Monday, 07 December 2015, 13:22 GMT
It appears that this Process now needs plymouth to run. I have not found a way to use it without Plymouth.
I installed plymouth as described in the wiki. It works now (does not show me any progress anymore while updating ;( )
Comment by Christian Hesse (eworm) - Monday, 07 December 2015, 14:54 GMT
Here is a more general document about freedesktop's offline system updates:
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?
Comment by Jan Alexander Steffens (heftig) - Monday, 07 December 2015, 15:04 GMT
gnome-software is very unsupported; don't expect anything to work.

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.
Comment by Albert Gasset (albertgasset) - Monday, 07 December 2015, 15:12 GMT
Offline updates worked before: the system rebooted, it installed the updates (without starting the display manager) and it rebooted again.

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?
Comment by Christian Hesse (eworm) - Monday, 07 December 2015, 19:07 GMT
Oh, offline updates did work? I missed that point and it surprises me.
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).
Comment by Ricardo Funke Ormieres (ricardofunke) - Tuesday, 08 December 2015, 02:06 GMT
$ sudo pkcon update -d
$ sudo pkcon offline-trigger
$ reboot
Comment by Christian Hesse (eworm) - Tuesday, 08 December 2015, 09:11 GMT
Looks like this really works... (Me is surprised! :) Well, kind of... :-p

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
[...]
Comment by Ricardo Funke Ormieres (ricardofunke) - Tuesday, 08 December 2015, 13:53 GMT
Should we enable this service before this change?
Comment by Christian Hesse (eworm) - Tuesday, 08 December 2015, 13:58 GMT
It is already enabled for system-update.target (see symlink /usr/lib/systemd/system/system-update.target.wants/packagekit-offline-update.service).

So no, just edit the file, prepare and trigger the offline update and reboot.
Comment by Albert Gasset (albertgasset) - Tuesday, 08 December 2015, 14:04 GMT
I've tried adding "Requires=dbus.service" to packagekit-offline-update.service and it worked.
Comment by Jan Alexander Steffens (heftig) - Tuesday, 08 December 2015, 14:31 GMT
Requires=dbus.socket would be more appropriate. In any case, this is also an upstream problem.
Comment by Christian Hesse (eworm) - Tuesday, 08 December 2015, 14:35 GMT
Already sent upstream (with dbus.socket... ;)
https://github.com/hughsie/PackageKit/pull/99

Loading...