Closed sophie-h closed 2 years ago
The bug described in https://github.com/bus1/dbus-broker/issues/202#issuecomment-533310276 is still present (or a similar error) with installing the current Pika Backup Beta.
A beta tester posted the issue "Unable to launch from gnome-shell". The problem is reducible on a fresh install of Fedora 35 and 36. It can, for example, be fixed by one of these actions:
systemctl reload --user dbus-broker.service
If Pika was installed before, it will (partially) work after installing the new beta version.
This is blocking the planned release of Pika Backup. Therefore, I would also be grateful for a workaround, even if I'm not doing something wrong.
$ flatpak install --user https://flathub.org/beta-repo/appstream/org.gnome.World.PikaBackup.flatpakref -y
Try to start Pika Backup from GNOME Shell. Nothing happens. Try
$ busctl --user call org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus ListActivatableNames
and see that none of the three names containing PikaBackup is listed.
Sorry wrong issue tracker.
sophie-h
commented
2 years ago
The bug described in https://github.com/bus1/dbus-broker/issues/202#issuecomment-533310276 is still present (or a similar error) with installing the current Pika Backup Beta.
A beta tester posted the issue "Unable to launch from gnome-shell". The problem is reducible on a fresh install of Fedora 35 and 36. It can, for example, be fixed by one of these actions:
systemctl reload --user dbus-broker.serviceIf Pika was installed before, it will (partially) work after installing the new beta version.
This is blocking the planned release of Pika Backup. Therefore, I would also be grateful for a workaround, even if I'm not doing something wrong.
Way to reproduce
Try to start Pika Backup from GNOME Shell. Nothing happens. Try
and see that none of the three names containing PikaBackup is listed.