jean-christophe-manciot
commented
6 years ago No such issue on Debian buster with: backintime-qt4 1.1.24-0.1 python3-pyqt4 4.12.1+dfsg-2+b1 python3-pyqt5 5.11.2+dfsg-1+b1
Closed jean-christophe-manciot closed 1 year ago
jean-christophe-manciot
commented
6 years ago No such issue on Debian buster with: backintime-qt4 1.1.24-0.1 python3-pyqt4 4.12.1+dfsg-2+b1 python3-pyqt5 5.11.2+dfsg-1+b1
kkaess
commented
6 years ago I get the same exact error messages on a fresh install of Fedora 29 -- Python version 3.7.0.
DRRDietrich
commented
6 years ago I have the same problem with Fedora Workstation 29 on three different devices and in a freshly installed VM.
glyndon
commented
6 years ago Same error here, started after upgrading to Ubuntu 18.10 from 18.4. Fixed by installing python3-dbus.mainloop.qt
7oxicshadow
commented
6 years ago +1 for problems with fedora 29.
Does anyone have a quick workaround for this? python3-dbus.mainloop.qt does not appear to exist within dnf on Fedora.
Thanks
jean-christophe-manciot
commented
5 years ago Same error here, started after upgrading to Ubuntu 18.10 from 18.4. Fixed by installing python3-dbus.mainloop.qt
I am now on Ubuntu 19.04 disco with python3-pyqt5 5.11.3+dfsg-1. This issue is still there & is NOT fixed/worked around by installing python3-dbus.mainloop.qt 4.12.1+dfsg-2build2.
kkaess
commented
5 years ago A "quick" workaround for this on Fedora is to reinstall Fedora 28, install backintime, then upgrade to Fedora 29. I've had success with this method.
j0hannes
commented
5 years ago Exact same issue on Arch.
Nicolarge
commented
5 years ago Hi everyone, I am currently having the same issue on a fresh install of Fedora 29. I've been using BIT for a while now and never had such issue on on previous versions of Fedora (currently running fine on different machines with Fedora 28). Any news on this issue?
jean-christophe-manciot
commented
5 years ago On Ubuntu disco 19.04, this issue is gone with the upgraded python3-pyqt5 5.11.3+dfsg-1build1.
# backintime-qt4
Back In Time
Version: 1.1.24
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
onmh
commented
5 years ago Hi everyone,
Issue occurred on Debian GNU/Linux bullseye/sid with python3-pyqt5 5.12.3+dfsg-2. Installing python3-dbus.mainloop.pyqt5 resolved it. python3-pyqt4 not required.
diego-betto
commented
5 years ago Sorry, but why backintime-qt4 requires python3-pyqt5?
xandark
commented
3 years ago I'm seeing this same problem in KDE neon 20.04 (essentially Ubuntu 20.04 with latest Qt + KDE packages)
These are installed:
Additionally, when I run journalctl -f before I run backintime-qt, I see this:
Apr 01 13:33:46 inspiron dbus-daemon[953]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.147' (uid=1000 pid=12254 comm="python3 -Es /usr/share/backintime/qt/app.py snapsh" label="unconfined") (using servicehelper)
Apr 01 13:33:46 inspiron net.launchpad.backintime.serviceHelper[12257]: Traceback (most recent call last):
Apr 01 13:33:46 inspiron net.launchpad.backintime.serviceHelper[12257]: File "/usr/share/backintime/qt/serviceHelper.py", line 75, in <module>
Apr 01 13:33:46 inspiron net.launchpad.backintime.serviceHelper[12257]: from PyQt5.QtCore import QCoreApplication
Apr 01 13:33:46 inspiron net.launchpad.backintime.serviceHelper[12257]: ImportError: /usr/local/lib/python3.8/dist-packages/PyQt5/QtCore.abi3.so: undefined symbol: _ZdlPvm, version Qt_5
Apr 01 13:33:46 inspiron dbus-daemon[953]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1So it seems that at on such a KDE neon system, that 5th line with the ImportError seems to be the issue:
ImportError: /usr/local/lib/python3.8/dist-packages/PyQt5/QtCore.abi3.so: undefined symbol: _ZdlPvm, version Qt_5
... which I don't understand. However, when I open a Python REPL shell and issue a:
>>> from PyQt5.QtCore import QCoreApplication
...I don't see any import error, such as Backintime is inducing.
Where should I look next to isolate this?
xandark
commented
3 years ago Another way to test this:
$ cd /usr/share/backintime/qt/
$ python3 serviceHelper.pyWhich immediately gives:
Traceback (most recent call last):
File "serviceHelper.py", line 75, in <module>
from PyQt5.QtCore import QCoreApplication
ImportError: /usr/local/lib/python3.8/dist-packages/PyQt5/QtCore.abi3.so: undefined symbol: _ZdlPvm, version Qt_5Is anyone else seeing this?
xandark
commented
3 years ago SOLUTION!
I found that the import order has an effect on inducing the ImportError crash.
In /usr/share/backintime/qt/serviceHelper.py, at line 75 we find this code block:
import dbus
import dbus.service
import dbus.mainloop.pyqt5
from PyQt5.QtCore import QCoreApplicationHowever, if the import order is changed to this, then there are no ImportError crashes!
from PyQt5.QtCore import QCoreApplication # must come before import dbus.mainloop.pyqt5 or will crash on ImportError
import dbus
import dbus.service
import dbus.mainloop.pyqt5I can now start and run backintime-qt!
JamesClarke7283
commented
2 years ago +1 Same error here on Trisquel Nabia, above solutions did not help. I get this error when running the service helper manually like above, "ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5'"
i am on python3.8 as my main system python.
Edit: My bad, i think this directory took precident /usr/local/lib/python3.8/dist-packages/ When i removed the dist-packages folder. it defaulted to /usr/lib/python3.8/ i think, and now it works.
aryoda
commented
2 years ago Related to #758: Mentions the same error message:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name
dwainsims
commented
2 years ago Same error on openSUSE 15.3 with a recently updated kernel. I have been using BIT for quite a while and this is annoying.
I may try moving back to an older kernel and see if that has any impact.
emtiu
commented
2 years ago Same error on openSUSE 15.3 with a recently updated kernel. I have been using BIT for quite a while and this is annoying.
I may try moving back to an older kernel and see if that has any impact.
I have installed a fresh OpenSUSE Leap 15.3 in a VM, updated to the latest packages, installed backintime and run it. The error does not occur. Can you tell me anything more?
emtiu
commented
2 years ago After closing many duplicate Issues opened in 2018, this is the main one concerning this problem now.
There are only three recent reports of this problem occurring:
It seems to me like the problem here isn't really with pyqt5, but rather an unsatisfied dbus dependency (in which case #1233 is likely a duplicate of this Issue). If true, this would be a packaging/distro problem more than a bug in backintime.
Please everyone, see if installing the python3-dbus (or similar) package solves your problem. (Installing stuff through pip might also help, but it's not how problems like this should be resolved.) If installing some python/dbus related package helps, please notify your distro's maintainers for backintime to include that dependency.
Kleysley
commented
2 years ago After installing the python dbus module from several different sources (using Arch package manager or pip as root and as normal user), the error still persists. In a Python 3.10 shell I can successfully import the module ("import dbus")
(when running Python as normal user and when running as root). So the package appears to be available.
Im running the newest Arch (kernel 5.19.13-arch1-1 with EXT4 as my filesystem.
aryoda
commented
2 years ago See also:
dwainsims
commented
2 years ago I am happy to run any diagnostics that you need. BIT was working just fine on my system. For months. Some suggested update from openSUSE for this release seemingly caused this to break. Nothing that I did specifically (that I am aware of).
Dwain
On Sun, Oct 9, 2022 at 8:35 PM aryoda @.***> wrote:
I think I do understand now how BiT uses this d-bus end point.
The reasons for "no such name" may be very different (missing rights, missing or incompatible library...) and IMHO the only way to diagnose the concrete reason on the specific computer is to start the d-bus end point manually.
I will prepare and publish a few diagnostic command here in a few days...
As first starter:
-
Is the d-bus end point running? sudo ps ax | grep -i serviceHelper.py
If no dbus end point is running and listening to d-bus (what is the reason): sudo python3 qt/serviceHelper.py You will the error messages then I hope - otherwise the serviceHelper needs to be started from the installation path so that the config files will be considered: /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
This is what I am trying to find out in the next days (how to start the end point manually + how to access the error logs)...
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1272667592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPYZ3GV63H2GKANESBS3WCNQEVANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
aryoda
commented
2 years ago OK, here's my (very long) summary...
BiT CLI as well as BiT qt (GUI) do not start anymore due to this unhandled primary exception:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name
The primary exception is always thrown together with one of the following secondary exceptions:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process net.launchpad.backintime.serviceHelper received signal 11
The traceback always contains this line of code (with varying line numbers depending on the BiT version) that threw the secondary exception when calling bus.get_object(...), eg.:
File "/usr/share/backintime/common/tools.py", line 1716, in __init__
conn = bus.get_object(SetupUdev.CONNECTION, SetupUdev.OBJECT)BiT cannot open a connection via D-Bus to a required system-bus-level service process named net.launchpad.backintime.serviceHelper' in the code line shown in the secondary traceback:
G_DBUS_ERROR_NAME_HAS_NO_OWNER (org.freedesktop.DBus.Error.NameHasNoOwner) The bus name you referenced doesn't exist (i.e. no application owns it). Taken from: https://www.freedesktop.org/software/gstreamer-sdk/data/docs/latest/gio/gio-GDBusError.html
BiT supports scheduling regular backups when a drive gets connected (triggered by Udev rules):
To install and manage these Udev rules BiT attaches a system-level background process to D-Bus (a interprocess communication system, kinda remote object invocation) which runs with root permissions since Udev rule changes require elevated (root) permissions.
This background process is implemented in Bit in the file qt/serviceHelper.py.
Normally it can be reached on the D-Bus via its service address net.launchpad.backintime.serviceHelper.
The background process is not started by BiT itself but automatically by the D-Bus service when the above service address is contacted for the first time.
Therefore the serviceHelper service must be installed ("registered") at the D-Bus which is done by copying the python script file and some descriptor files to distro-defined system folders.
This installation is done either by calling make install in the qt folder of the source code (when using the code from the Github repo) or by installing a distro-package (eg. for Ubuntu the service contained in the package backintime-qt).
There are multiple reasons why the serviceHelper is not available but a simple way to reproduce the bug is manipulating
the installed serviceHelper.py:
cd /usr/share/backintime/qt # or wherever `serviceHelper.py` was installed
# then edit the file with "sudo", go to the end of the file
# and insert "exit(1)" at the beginning of the main function (if __name__ == '__main__':)
# Then save the changed file and kill the running service process via its process id
ps ax | grep -i serviceHelper
kill <PID> # insert the process ID of the process found above (if it is not running you don't need to kill it ;-)
# Call BiT which should now immediately exit with the traceback described above:
backintimeStart BiT to trigger the start of the background service (provokes the error too)
backintime check-config or only backintime
To diagnose the problem it is important to find out if the serviceHelper process is running (but not reachable) or not running and why it did not start sucessfully.
serviceHelper background service running?# Should show the service process, otherwise it is not running
ps aux | grep -i serviceHelper
# Must show a line similar to this:
# root 16023 0.0 0.0 70552 22248 ? S Okt11 0:00 /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
# Alternative:
systemctl status dbus.service
# Must show a process in the `CGroup:` part looking similar to this:
# /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.pyAlternatively you could use the GUI tool qdbusviewer (eg. installed on Ubuntu with the package qttools5-dev-tools)
which can not only show running services but also show the callable methods of the remote object:
serviceHelper is not running:Is it installed at all? Search for the file serviceHelper.py in /usr/share/backintime/qt
Solution: Install the missing distro-package (eg. backintime-qt on Ubuntu) or do a
./configure and make install in the qt folder of the source code from Github
Note for Ubuntu: The serviceHelper is only contained in backintime-qt, not in backintime-common (even though it is required for both the BiT CLI and GUI but I think the package maintainer had no chance to recognize this dependency due to our lack of documentation of this).
Start the serviceHelper manually in the console to see the error messages:
cd /usr/share/backintime/qt # or wherever `serviceHelper.py` was installed
sudo python3 serviceHelper.pyThe error message you'll see can have different causes:
Wrong python version (eg. because you installed a different version manually).
# Should show: /usr/bin/python3 (on Ubuntu, may be different for other distros)
which python3Missing dependency like python package: Use your distro package manager to install the missing package as documented in the README.
python3-dbus, python3-dbus.mainloop.pyqt5Strange error messages (eg. installed python packages cannot be imported):
pip
-> uninstall via sudo -H pip3 uninstall <package name>sudo pip (never do this, it will overwrite the distro-packaged installations possibly causing incompatibilities)pip installations in the file path of the traceback (is no standard system path as used by the distro-packages)!find /usr/local/lib/python*/dist-packages -maxdepth 2 -name __init__.py | xargs realpath | LANG=en xargs dpkg -S 2>&1 | grep 'no path found'serviceHelper is running: Why does the connection fail?# Show only most recent D-Bus daemon logs after provoking the error
backintime
systemctl status dbus.service
# To view the complete log use the journalctl (scroll till the end!)
journalctl -b --unit=dbus # optionally with: | grep -i backintime@ All affected users: Please follow the above diagnosis steps and report here
Improve BiT documentation:
serviceHelper to the README (also important for package maintainers).
Mainly also a configure/make/install cycle is required for qt...Code changes:
D-bus exceptions in the startup code of BiT and throw + log only a warning (since 99 % of the users
do not use the Udev part of BiT I guess):
https://github.com/bit-team/backintime/blob/b4dd2d1737c5031d264d667c18f6987a1916762b/common/tools.py#L1884-L1894serviceHelper-related code and config files from the qt into the common folder (it is a backend thing and also required by the CLI - not only the GUI!). Requires also to move parts of the ./configure implementation from qt to common!
THIS IS A CRITICAL CHANGE SINCE IT AFFECTS DISTRO PACKAGING -> ASK PACKAGE MAINTAINERS FIRST!Why does BiT run from the Github source code on my computer without explicitly installing the serviceHelper?
A: Most developer I guess will install the distro-packages of BiT first to satisfy the dependencies
and do then a git clone. When you install the distro-packages the packaged serviceHelper
is installed and its API is still fully compatible to most-recent dev version of BiT
How can I use a dbus-send to check if the serviceHelper is running?
dbus-send --system --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedektop/DBus org.freedesktop.DBus.ListActivatableNames | grep -i backintime
# Output if the service is running:
# string "net.launchpad.backintime.serviceHelper"How can I query ("introspect") the available interface methods of serviceHelper via dbus-send?
dbus-send --system --dest=net.launchpad.backintime.serviceHelper --type=method_call --print-reply "/UdevRules" org.freedesktop.DBus.Introspectable.IntrospectThis is the raw output that you can see in a nicer form in the qdbusviewer GUI...
Kleysley
commented
2 years ago I have run the diagnostics and I think I might have found the reason why it fails: (can be found in the second to last line of the "systemctl status dbus" output": Connection \:x.xxx is not allowed to own the service [serviceHelper] due to security policies in the configuration file.
The serviceHelper is running:
-$ ps aux | grep -i serviceHelper
kleysley 4577 0.0 0.0 6564 2536 pts/1 S+ 07:44 0:00 grep --color=auto -i serviceHelper
-$ systemctl status dbus 1 (0.002s) < 07:47:18
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Wed 2022-10-12 07:39:12 CEST; 8min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 678 (dbus-daemon)
Tasks: 1 (limit: 18417)
Memory: 10.9M
CPU: 1.636s
CGroup: /system.slice/dbus.service
└─678 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: retval = bus.request_name(name, name_flags)
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.119" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in the configuration file
Oct 12 07:44:42 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1
-$ journalctl -b --unit=dbus 0 (01:58.931) < 07:51:54
Oct 12 07:39:12 kleysley-arch systemd[1]: Starting D-Bus System Message Bus...
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: dbus[678]: Unknown group "netdev" in message bus configuration file
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: dbus[678]: Unknown group "netdev" in message bus configuration file
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: dbus[678]: Unknown username "gdm" in message bus configuration file
Oct 12 07:39:12 kleysley-arch systemd[1]: Started D-Bus System Message Bus.
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/bin/cupsd -l")
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.5' (uid=0 pid=692 comm="/usr/bin/NetworkManager --no-daemon")
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=692 comm="/usr/bin/NetworkManager --no-daemon")
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 12 07:39:12 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='net.connman.iwd' unit='iwd.service' requested by ':1.5' (uid=0 pid=692 comm="/usr/bin/NetworkManager --no-daemon")
Oct 12 07:39:13 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'net.connman.iwd'
Oct 12 07:39:14 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.5' (uid=0 pid=692 comm="/usr/bin/NetworkManager --no-daemon")
Oct 12 07:39:14 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.19' (uid=973 pid=949 comm="/usr/lib/xdg-desktop-portal")
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.2' (uid=0 pid=681 comm="/usr/lib/systemd/systemd-logind")
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.23' (uid=973 pid=945 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-NedqAg")
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 12 07:39:15 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.23' (uid=973 pid=945 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-NedqAg")
Oct 12 07:39:16 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.UPower'
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.39' (uid=1000 pid=1180 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.39' (uid=1000 pid=1180 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='net.hadess.PowerProfiles' unit='power-profiles-daemon.service' requested by ':1.33' (uid=1000 pid=1072 comm="/usr/lib/xdg-desktop-portal")
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'power-profiles-daemon.service': Unit power-profiles-daemon.service not found.
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper'
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.39' (uid=1000 pid=1180 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.36' (uid=1000 pid=1113 comm="/usr/bin/kded5")
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.36' (uid=1000 pid=1113 comm="/usr/bin/kded5")
Oct 12 07:39:21 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='net.hadess.PowerProfiles' unit='power-profiles-daemon.service' requested by ':1.39' (uid=1000 pid=1180 comm="/usr/lib/org_kde_powerdevil")
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'power-profiles-daemon.service': Unit power-profiles-daemon.service not found.
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Activating service name='org.kde.kded.smart' requested by ':1.36' (uid=1000 pid=1113 comm="/usr/bin/kded5") (using servicehelper)
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.kde.kded.smart'
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.66' (uid=1000 pid=1427 comm="/usr/lib/DiscoverNotifier")
Oct 12 07:39:22 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Oct 12 07:39:23 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.72' (uid=1000 pid=1370 comm="/usr/bin/python /usr/bin/blueman-applet")
Oct 12 07:39:23 kleysley-arch dbus-daemon[678]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.79' (uid=1000 pid=1384 comm="python -Es /usr/share/backintime/common/backintime") (using servicehelper)
Oct 12 07:39:23 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.blueman.Mechanism'
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: Traceback (most recent call last):
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: retval = bus.request_name(name, name_flags)
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:39:23 kleysley-arch net.launchpad.backintime.serviceHelper[1844]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.82" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in >
Oct 12 07:39:23 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1
Oct 12 07:39:45 kleysley-arch dbus-daemon[678]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.39' (uid=1000 pid=1180 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 12 07:39:45 kleysley-arch dbus-daemon[678]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Oct 12 07:40:14 kleysley-arch dbus-daemon[678]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.106' (uid=1000 pid=3821 comm="python -Es /usr/share/backintime/common/backintime") (using servicehelper)
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: Traceback (most recent call last):
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: retval = bus.request_name(name, name_flags)
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:40:14 kleysley-arch net.launchpad.backintime.serviceHelper[3823]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.107" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in>
Oct 12 07:40:14 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1
Oct 12 07:41:23 kleysley-arch dbus-daemon[678]: [system] Activating via systemd: service name='net.hadess.PowerProfiles' unit='power-profiles-daemon.service' requested by ':1.62' (uid=1000 pid=1387 comm="/usr/lib/deja-dup/deja-dup-monitor")
Oct 12 07:41:23 kleysley-arch dbus-daemon[678]: [system] Activation via systemd failed for unit 'power-profiles-daemon.service': Unit power-profiles-daemon.service not found.
Oct 12 07:41:55 kleysley-arch dbus-daemon[678]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.110' (uid=1000 pid=4065 comm="python -Es /usr/share/backintime/common/backintime") (using servicehelper)
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: Traceback (most recent call last):
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: retval = bus.request_name(name, name_flags)
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:41:55 kleysley-arch net.launchpad.backintime.serviceHelper[4067]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.111" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in>
Oct 12 07:41:55 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1
Oct 12 07:43:41 kleysley-arch dbus-daemon[678]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.114' (uid=0 pid=4313 comm="python -Es /usr/share/backintime/common/backintime") (using servicehelper)
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: Traceback (most recent call last):
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: retval = bus.request_name(name, name_flags)
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:43:41 kleysley-arch net.launchpad.backintime.serviceHelper[4315]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.115" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in>
Oct 12 07:43:41 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1
Oct 12 07:44:42 kleysley-arch dbus-daemon[678]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.118' (uid=1000 pid=4546 comm="python -Es /usr/share/backintime/common/backintime") (using servicehelper)
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: Traceback (most recent call last):
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/share/backintime/qt/serviceHelper.py", line 331, in <module>
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: name = dbus.service.BusName("net.launchpad.backintime.serviceHelper", bus)
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/service.py", line 134, in __new__
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: retval = bus.request_name(name, name_flags)
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/bus.py", line 299, in request_name
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: File "/usr/lib/python3.10/site-packages/dbus/connection.py", line 634, in call_blocking
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: reply_message = self.send_message_with_reply_and_block(
Oct 12 07:44:42 kleysley-arch net.launchpad.backintime.serviceHelper[4548]: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.119" is not allowed to own the service "net.launchpad.backintime.serviceHelper" due to security policies in>
Oct 12 07:44:42 kleysley-arch dbus-daemon[678]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Launch helper exited with unknown return code 1`
aryoda
commented
2 years ago Connection :x.xxx is not allowed to own the service [serviceHelper] due to security policies in the configuration file.
THX for reporting this. The only configuration file that configures the D-Bus security for serviceHelper is this one here
and I think all AUR packages I saw (eg. https://aur.archlinux.org/packages/backintime-git) are using the standard ways of building and installation (configure+make+make install for both common and qt folders) - see the corresponding PKGBUILD.
I will set up a VM and try to reproduce this, perhaps the security configuration must be done differently on ARCH (or SELinux or another security tools is blocking by default and requires punching a whole).
aryoda
commented
2 years ago @Kleysley serviceHelper is running and working on my VM with kernel 5.19.13-arch1-1 #1 SMP and backintime check-config exits without an error (BiT version is 1.3.2).
I have installed AUR backintime-git but had to disable the make test line in PKGBUILD and install the missing dependency (was undocumented until recently at BiT side) sudo pacman -Sy python-packaging + sudo pacman -Sy python-pyfakefs but then makepkg -si did succeed.
From which source and how did you do the last installation of BiT (could you still reproduce the installation commands and post it here?).
Anyhow: The failing unit tests are an open issue (I saw you opened #1233)...
Edit: Can you please check if the file net.launchpad.backintime.serviceHelper.conf is installed in the folder /etc/dbus-1/system.d and that it has the same content like the one I have linked in the prev. post? Are the permissions set to 644 (rw-r--r--)? Use eg. stat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf for this...
Kleysley
commented
2 years ago Disabling the make test line in PKGBUILD does work and after installing the two undocumented dependencies it installs and runs fine on my system.
The serviceHelper.conf file is never present if installing without making changes to the make file. While the tests are running, that directory doesn't exist (which is probably also why they fail later).
It seems the file gets created AFTER the make tests are done but they themselves depend on that file.
If I remove the line from the PKGBUILD and then install using makepkg -si, it works and the file is created with the according permissions:
-$ ls -l /etc/dbus-1/system.d
.rw-r--r-- root root 899 B Thu Oct 13 TI:ME:STAMP 2022 ㅤnet.launchpad.backintime.serviceHelper.conf@Kleysley
The serviceHelper.conf file is never present if installing without making changes to the make file.
Which "make file" do you mean? the PKGBUILD or the real Makefile generated by .configure?
While the tests are running, that directory doesn't exist (which is probably also why they fail later).
Do you mean the /etc/dbus-1/system.d directory that does did not exist?
It seems the file gets created AFTER the make tests are done but they themselves depend on that file.
Do you mean the conf file in this location?
/etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf
If I remove the line from the PKGBUILD and then install using makepkg -si, it works
Could you run one more test please to help to me to get a holistic picture of the installation issue:
Make sure the serviceHelper is running now as daemon:
ps aux | grep -i serviceHelper
If 1. is true then enable the make test in your PKGBUILD again and repeat the installation with makepkg or makepkg -si.
Does this succeed or do you still get unit test errors? Which ones?
All in all the main reason for the bug in your case seems to be the chicken-egg-problem I have described in your other issue https://github.com/bit-team/backintime/issues/1233#issuecomment-1276913542 and I will discuss the options to fix this with the BiT team soon and extend the fix section of the analysis above with your case ("installation on arch from AUR"...).
Kleysley
commented
2 years ago Which "make file" do you mean? the PKGBUILD or the real Makefile generated by .configure?
The PKGBUILD file, sorry for the confusion.
Do you mean the /etc/dbus-1/system.d directory that does did not exist?
Exactly.
Do you mean the conf file in this location? /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf
Yes
- Make sure the serviceHelper is running now as daemon
It always is, even when BIT doesnt work. Its just not reachable by BIT.
If 1. is true then enable the make test in your PKGBUILD again and repeat the installation with makepkg or makepkg -si
This wouldnt change anything since the installation fails even though the serviceHelper is (and has always been) running. Ill try this as soon as Im able to but I dont think it will change anything.
aryoda
commented
2 years ago This wouldnt change anything since the installation fails even though the serviceHelper is (and has always been) running.
I am confused :face_in_clouds: So you still get an (permission or another) error when starting BiT despite the successful make test-less installation? Or do you expect the installation to fail?
At least according to the ps output of above comment (https://github.com/bit-team/backintime/issues/921#issuecomment-1275641499) serviceHelper was not running until you have installed make test-less.
-$ ps aux | grep -i serviceHelper
kleysley 4577 0.0 0.0 6564 2536 pts/1 S+ 07:44 0:00 grep --color=auto -i serviceHelpergrep did only find its own process, not the serviceHelper daemon.
If the daemon is running the output would look like:
root 16023 0.0 0.0 70552 22248 ? S Okt11 0:00 /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
bit 50785 0.0 0.0 9412 2728 pts/0 S+ 10:11 0:00 grep --color=auto -i serviceHelperThe 1st line is the daemon, not the 2nd (I should clarify this in my analysis summary)...
Kleysley
commented
2 years ago I am not very familar with ps, so I tgought the service was running looking at that output... If I disable the testing in the PKGBUILD, everything works fine and I can use BackInTime without any issues.
I now understand your request to enable "make test" again and retry the installation. I will try that as soon as I can.
dwainsims
commented
2 years ago I first noticed this on 5.3.18-150300.59.93-default (openSUSE Leap 15.3)
I just rolled back to
5.3.18-150300.59.90-default
and the problem persists. So my thought that it was related to a kernel update was incorrect. (I do believe it was some other update though. BIT had been working well for months.)
kanawha:~ # backintime
Back In Time Version: 1.2.1
Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details.
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 177, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 363, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 1165, in
Dwain
On Sat, Oct 8, 2022 at 5:32 PM Michael Büker @.***> wrote:
Same error on openSUSE 15.3 with a recently updated kernel. I have been using BIT for quite a while and this is annoying.
I may try moving back to an older kernel and see if that has any impact.
I have installed a fresh OpenSUSE Leap 15.3 in a VM, updated to the latest packages, installed backintime and run it. The error does not occur. Can you tell me anything more?
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1272400632, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPY5X6TNYK3CYNKV65VLWCHR57ANCNFSM4FRR5ZNQ . You are receiving this because you commented.Message ID: @.***>
Kleysley
commented
2 years ago @aryoda No that doesn't work, but it gives me a different error where other tests are failing. I don't think this is part of the current issue though:
ERROR: test_diagnostics_arg (test.test_backintime.TestBackInTime)
Traceback (most recent call last): File "/home/niklas/.cache/yay/backintime-git/src/backintime/common/test/test_backintime.py", line 181, in test_diagnostics_arg diagnostics = json.loads(output) File "/usr/lib/python3.10/json/init.py", line 346, in loads return _default_decoder.decode(s) File "/usr/lib/python3.10/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Ran 3 tests in 3.293s
FAILED (errors=1) make: *** [Makefile:570: unittest] Error 1 make: Leaving directory '/home/niklas/.cache/yay/backintime-git/src/backintime/common' ==> ERROR: A failure occurred in check(). Aborting... -> error making: backintime-git
aryoda
commented
2 years ago @Kleysley
[make test] gives me a different error where other tests are failing File "/home/niklas/.cache/yay/backintime-git/src/backintime/common/test/test_backintime.py", line 181, in
I get exactly the same error (but if I run the unit test alone it works).
This is definitely another issue, let's ignore it here. THX for back-testing!
aryoda
commented
2 years ago @dwainsims
I first noticed this on 5.3.18-150300.59.93-default (openSUSE Leap 15.3) I just rolled back to 5.3.18-150300.59.90-default and the problem persists.
Good to know!
It would be great if you could follow the "Diagnostics and Fixing" section of my above post https://github.com/bit-team/backintime/issues/921#issuecomment-1275364552 to help me narrow down the problem!
dwainsims
commented
2 years ago Sorry for the delay. This is on my work computer, so its kinda busy most of the time.
@.:~/Rancher2.6/Epinio> sudo ps ax | grep -i serviceHelper.py
24834 pts/3 S+ 0:00 grep --color=auto -i serviceHelper.py
@.:~/Rancher2.6/Epinio> /usr/bin/python3 -Es
/usr/share/backintime/qt/serviceHelper.py
Traceback (most recent call last):
File "/usr/share/backintime/qt/serviceHelper.py", line 331, in
On Sun, Oct 9, 2022 at 8:35 PM aryoda @.***> wrote:
I think I do understand now how BiT uses this d-bus end point.
The reasons for "no such name" may be very different (missing rights, missing or incompatible library...) and IMHO the only way to diagnose the concrete reason on the specific computer is to start the d-bus end point manually.
I will prepare and publish a few diagnostic command here in a few days...
As first starter:
-
Is the d-bus end point running? sudo ps ax | grep -i serviceHelper.py
If no dbus end point is running and listening to d-bus (what is the reason): sudo python3 qt/serviceHelper.py You will the error messages then I hope - otherwise the serviceHelper needs to be started from the installation path so that the config files will be considered: /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
This is what I am trying to find out in the next days (how to start the end point manually + how to access the error logs)...
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1272667592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPYZ3GV63H2GKANESBS3WCNQEVANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
dwainsims
commented
2 years ago More diagnostics....
@.***:~/Rancher2.6/Epinio> sudo ps ax | grep -i serviceHelper.py
25433 pts/3 S+ 0:00 grep --color=auto -i serviceHelper.py
@.:~/Rancher2.6/Epinio> /usr/bin/python3 -Es
/usr/share/backintime/qt/serviceHelper.py
Traceback (most recent call last):
File "/usr/share/backintime/qt/serviceHelper.py", line 331, in
● dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Fri 2022-10-14 08:48:36 EDT; 2h 44min ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 2058 (dbus-daemon) Tasks: 1 (limit: 4915) CGroup: /system.slice/dbus.service └─2058 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only @.:~/Rancher2.6/Epinio> sudo journalctl --unit=dbus -- Logs begin at Fri 2022-10-14 08:48:24 EDT, end at Fri 2022-10-14 11:32:49 EDT. -- Oct 14 08:48:36 kanawha systemd[1]: Started D-Bus System Message Bus. Oct 14 08:48:36 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.3' (uid=0 pid=2057 comm="/usr/sbin/cupsd -l ") Oct 14 08:48:36 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=2056 comm="/usr/lib/bluetooth/bluetoothd ") Oct 14 08:48:36 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.ColorManager' Oct 14 08:48:37 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.hostname1' Oct 14 08:48:37 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=2059 comm="/usr/sbin/NetworkManager --no-daemon ") Oct 14 08:48:37 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 14 08:48:37 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.7' (uid=0 pid=2059 comm="/usr/sbin/NetworkManager --no-daemon ") Oct 14 08:48:37 kanawha dbus-daemon[2058]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Oct 14 08:49:07 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.17' (uid=0 pid=2892 comm="localectl set-keymap us ") Oct 14 08:49:07 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.locale1' Oct 14 08:49:07 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=2059 comm="/usr/sbin/NetworkManager --no-daemon ") Oct 14 08:49:07 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 14 08:49:12 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.28' (uid=1000 pid=3311 comm="/usr/bin/baloo_file ") Oct 14 08:49:12 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=3347 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Oct 14 08:49:12 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Oct 14 08:49:13 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.26' (uid=1000 pid=3253 comm="kded5 ") Oct 14 08:49:13 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.UDisks2' Oct 14 08:49:14 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.UPower' Oct 14 08:49:14 kanawha dbus-daemon[2058]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.50' (uid=1000 pid=4002 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper) Oct 14 08:49:14 kanawha dbus-daemon[2058]: [system] Activated service 'org.kde.powerdevil.discretegpuhelper' failed: Failed to execute program org.kde.powerdevil.discretegpuhelper: Permission denied Oct 14 08:49:14 kanawha dbus-daemon[2058]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.50' (uid=1000 pid=4002 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper) Oct 14 08:49:14 kanawha dbus-daemon[2058]: [system] Activated service 'org.kde.powerdevil.backlighthelper' failed: Failed to execute program org.kde.powerdevil.backlighthelper: Permission denied Oct 14 08:49:15 kanawha dbus-daemon[2058]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.57' (uid=1000 pid=4007 comm="python3 -Es /usr/share/backintime/common/backintim") (using servicehelper) Oct 14 08:49:15 kanawha dbus-daemon[2058]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied Oct 14 08:49:15 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.56' (uid=1000 pid=3305 comm="/usr/bin/plasmashell ") Oct 14 08:49:15 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 14 08:53:36 kanawha dbus-daemon[2058]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.90' (uid=0 pid=6094 comm="python3 -Es /usr/share/backintime/qt/app.py ") (using servicehelper) Oct 14 08:53:36 kanawha dbus-daemon[2058]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied Oct 14 08:58:23 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.94' (uid=0 pid=7529 comm="/usr/lib/snapper/systemd-helper --cleanup ") Oct 14 08:58:23 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.opensuse.Snapper' Oct 14 09:49:16 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.56' (uid=1000 pid=3305 comm="/usr/bin/plasmashell ") Oct 14 09:49:16 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 14 10:00:02 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.102' (uid=0 pid=14395 comm="/usr/lib/snapper/systemd-helper --timeline ") Oct 14 10:00:02 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.opensuse.Snapper' Oct 14 10:22:59 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=2059 comm="/usr/sbin/NetworkManager --no-daemon ") Oct 14 10:22:59 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 14 10:49:16 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.56' (uid=1000 pid=3305 comm="/usr/bin/plasmashell ") Oct 14 10:49:16 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.PackageKit' Oct 14 11:00:02 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.108' (uid=0 pid=22048 comm="/usr/lib/snapper/systemd-helper --timeline ") Oct 14 11:00:02 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.opensuse.Snapper' Oct 14 11:01:49 kanawha dbus-daemon[2058]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.56' (uid=1000 pid=3305 comm="/usr/bin/plasmashell ") Oct 14 11:01:49 kanawha dbus-daemon[2058]: [system] Successfully activated service 'org.freedesktop.PackageKit' @.:~/Rancher2.6/Epinio> clear
On Tue, Oct 11, 2022 at 6:45 PM aryoda @.***> wrote:
OK, here's my (very long) summary... Symptoms
BiT CLI as well as BiT qt (GUI) do not start anymore due to this unhandled primary exception:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name
Observations
-
The problems occur in various distributions, BiT versions and installations from both distro packages as well from Github
The primary exception is always thrown together with one of the following secondary exceptions:
Launch helper exited with unknown return code 1
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
Permission denied:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
Process net.launchpad.backintime.serviceHelper received signal 11
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process net.launchpad.backintime.serviceHelper received signal 11
The traceback always contains this line of code (with varying line numbers depending on the BiT version) that threw the secondary exception when calling bus.get_object(...), eg.:
File "/usr/share/backintime/common/tools.py", line 1716, in init conn = bus.get_object(SetupUdev.CONNECTION, SetupUdev.OBJECT)
Reason
BiT cannot open a connection via D-Bus to a required system-bus-level service process named net.launchpad.backintime.serviceHelper' in the code line shown in the secondary traceback:
G_DBUS_ERROR_NAME_HAS_NO_OWNER (org.freedesktop.DBus.Error.NameHasNoOwner) The bus name you referenced doesn't exist (i.e. no application owns it). Taken from: https://www.freedesktop.org/software/gstreamer-sdk/data/docs/latest/gio/gio-GDBusError.html
Background
BiT supports scheduling regular backups when a drive gets connected (triggered by Udev rules):
[image: Udev_based_backup] https://user-images.githubusercontent.com/11374410/195189352-c0c2bdd3-4a79-4d15-859c-1ffcb88e2c0f.png
To install and manage these Udev rules BiT attaches a system-level background process to D-Bus (a interprocess communication system, kinda remote object invocation) which runs with root permissions since Udev rule changes require elevated (root) permissions.
This background process is implemented in Bit in the file qt/serviceHelper.py https://github.com/bit-team/backintime/blob/b4dd2d1737c5031d264d667c18f6987a1916762b/qt/serviceHelper.py .
Normally it can be reached on the D-Bus via its service address net.launchpad.backintime.serviceHelper https://github.com/bit-team/backintime/blob/b4dd2d1737c5031d264d667c18f6987a1916762b/qt/net.launchpad.backintime.serviceHelper.service#L2 .
The background process is not started by BiT itself but automatically by the D-Bus service when the above service address is contacted for the first time.
Therefore the serviceHelper service must be installed ("registered") at the D-Bus which is done by copying the python script file and some descriptor files to distro-defined system folders.
This installation is done either by calling make install in the qt folder of the source code (when using the code from the Github repo) or by installing a distro-package (eg. for Ubuntu the service contained in the package backintime-qt). Steps to reproduce the bug
There are multiple reasons why the serviceHelper is not available but a simple way to reproduce the bug is manipulating the installed serviceHelper.py:
cd /usr/share/backintime/qt # or wherever
serviceHelper.pywas installedthen edit the file with "sudo", go to the end of the file
and insert "exit(1)" at the beginning of the main function (if name == 'main':)
Then save the changed file and kill the running service process via its process id
ps ax | grep -i serviceHelper kill
# insert the process ID of the process found above (if it is not running you don't need to kill it ;-) Call BiT which should now immediately exit with the traceback described above:
backintime
Diagnostics and Fixing
1.
Start BiT to trigger the start of the background service (provokes the error too)
backintime check-config or only backintime
To diagnose the problem it is important to find out if the serviceHelper process is running (but not reachable) or not running and why it did not start sucessfully.
- Is the serviceHelper background service running?
Should show the service process, otherwise it is not running
ps ax | grep -i serviceHelper
Alternative:
systemctl status dbus.service
Alternatively you could use the GUI tool qdbusviewer (eg. installed on Ubuntu with the package qttools5-dev-tools) which can also show the callable methods of the remote object: [image: qdbusviewer] https://user-images.githubusercontent.com/11374410/195198963-aec1dab8-f50b-4c9a-b4ac-6f32f0e35e1b.png
If the serviceHelper is not running:
-
Is it installed at all? Search for the file serviceHelper.py in /usr/share/backintime/qt Solution: Install the missing distro-package (eg. backintime-qt on Ubuntu) or do a ./configure and make install in the qt folder of the source code from Github
Note for Ubuntu: The serviceHelper is only contained in backintime-qt, not in backintime-common (even though it is required for both the BiT CLI and GUI but I think the package maintainer had no chance to recognize this dependency due to our lack of documentation of this).
Start the serviceHelper manually in the console to see the error messages:
cd /usr/share/backintime/qt # or wherever
serviceHelper.pywas installed sudo python3 serviceHelper.pyThe error message you'll see can have different causes:
-
Wrong python version (eg. because you installed a different version manually).
Should show: /usr/bin/python3 (on Ubuntu, may be different for other distros)
which python3
-
Missing dependency like python package: Use your distro package manager to install the missing package as documented in the README https://github.com/bit-team/backintime#from-sources.
- eg. python3-dbus, python3-dbus.mainloop.pyqt5
Strange error messages (eg. installed python packages cannot be imported):
You may have installed incompatible python packages in parallel via pip -> uninstall via sudo -H pip3 uninstall
or even worse via sudo pip (never do this, it will overwrite the distro-packaged installations possibly causing incompatibilities)
- You can recognize pip installations in the file path of the traceback (is no standard system path as used by the distro-packages)!
You can find python packages which were not installed from (here: Ubuntu) repos via this (untested!) script:
find /usr/local/lib/python*/dist-packages -maxdepth 2 -name init.py | xargs realpath | LANG=en xargs dpkg -S 2>&1 | grep 'no path found'
- If the serviceHelper is running: Why does the connection fail?
Show only most recent D-Bus daemon logs after provoking the error
backintime systemctl status dbus.service
To view the complete log use the journalctl (scroll till the end!)
journalctl --unit=dbus
Next steps
1.
@ All affected users: Please follow the above diagnosis steps and report here
if you could solve the problem
- more information about currently unidentified reasons for the error 2.
Improve BiT documentation:
Add mandatory steps to install the serviceHelper to the README (also important for package maintainers). Mainly also a configure/make/install cycle is required for qt...
- Extract the generic parts from the above steps (helpful for other issues) as "1st aid self-diagnosis" into a new doc file
- Add reproducible end user documentation how to setup a Udev-based schedule (I did not succeed so far) 3.
Code changes:
Capture all D-bus exceptions in the startup code of BiT and throw + log only a warning (since 99 % of the users do not use the Udev part of BiT I guess):
- Move serviceHelper-related code and config files from the qt into the common folder (it is a backend thing and also required by the CLI - not only the GUI!) THIS IS A CRITICAL CHANGE SINCE IT AFFECTS DISTRO PACKAGING -> ASK PACKAGE MAINTAINERS FIRST!
Appendix
1.
Why does BiT run from source code on my computer without explicitly installing the serviceHelper?
A: Most developer I guess will install the distro-packages of BiT first to satisfy the dependencies and do then a git clone. When you install the distro-packages the packaged serviceHelper is installed and its API is still fully compatible to most-recent dev version of BiT 2.
How can I use a dbus-send to check if the serviceHelper is running?
dbus-send --system --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedektop/DBus org.freedesktop.DBus.ListActivatableNames | grep -i backintime
Output if the service is running:
string "net.launchpad.backintime.serviceHelper"
3.
How can I query ("introspect") the available interface methods of serviceHelper via dbus-send?
dbus-send --system --dest=net.launchpad.backintime.serviceHelper --type=method_call --print-reply "/UdevRules" org.freedesktop.DBus.Introspectable.Introspect
This is the raw output that you can see in a nicer form in the qdbusviewer GUI...
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1275364552, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPY5F5PWA5SF4IZKONWTWCXUY3ANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
aryoda
commented
2 years ago @dwainsims THX a lot, I can see the strange permission issue here:
dbus-daemon[2058]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
Just to be sure:
Did you call backintime once before the ps to trigger the serviceHelper daemon activation?
Then try again
# Should show the service process, otherwise it is not running
ps aux | grep -i serviceHelper
# Must show a line similar to this:
# root 16023 0.0 0.0 70552 22248 ? S Okt11 0:00 /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.pyCould you please start the serviceHelper daemon with sudo (otherwise registration at the system bus is not allowed):
Instead of
usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
use sudo /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
Please post the traceback here if any
Could you please check if this file exists and post the active permissions with
stat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf
(should be: `Access (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root)
If the file exists could please check if the content corresponds to the Github version of the conf file:
cat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf
vs.
https://github.com/bit-team/backintime/blob/b4dd2d1737c5031d264d667c18f6987a1916762b/qt/net.launchpad.backintime.serviceHelper.conf
aryoda
commented
2 years ago I first noticed this on 5.3.18-150300.59.93-default (openSUSE Leap 15.3) ~ # backintime Back In Time Version: 1.2.1
I have just the installation script of the Suse package and it looks OK (no unit testing issue like we have on Arch with AUR):
https://build.opensuse.org/package/view_file/openSUSE:Leap:15.3/backintime/backintime.spec?expand=1
dwainsims
commented
2 years ago Note: that once I was able to start the serviceHelper, I could not ctrl-C out of it. I had to ctrl-z and bg the process. That process seems to run.
@.:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.3" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.3" PRETTY_NAME="openSUSE Leap 15.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" @.:~> sudo -i kanawha:~ # backintime
Back In Time Version: 1.2.1
Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details.
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 177, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 363, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no suc h name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 1165, in
^Z [1]+ Stopped /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py kanawha:~ # bg [1]+ /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py & kanawha:~ # ps aux | grep -i serviceHelper root 13399 0.0 0.0 141660 22856 pts/9 S 14:14 0:00 /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py root 13527 0.0 0.0 7680 764 pts/9 S+ 14:15 0:00 grep --color=auto -i serviceHelper kanawha:~ # stat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf File: /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf Size: 899 Blocks: 8 IO Block: 4096 regular file Device: 31h/49d Inode: 5142145 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2022-10-13 09:38:36.363822762 -0400 Modify: 2021-02-25 21:28:34.000000000 -0500 Change: 2022-09-21 18:57:26.358248158 -0400 Birth: 2022-09-21 18:57:26.354248122 -0400 kanawha:~ # cat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
kanawha:~ #
Then I wonder. Will BIT run? Hmm..
kanawha:~ # backintime
Back In Time Version: 1.2.1
Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details.
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 523, in _signal_func def _signal_func(self, message): KeyboardInterrupt
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/dbus/service.py", line 651, in
_message_cb
if not isinstance(message, MethodCallMessage):
SystemError:
Not quite, but you definitely on to something here. thanks for your help!!!
Dwain
On Fri, Oct 14, 2022 at 12:14 PM aryoda @.***> wrote:
@dwainsims https://github.com/dwainsims THX a lot, I can see the strange permission issue here:
dbus-daemon[2058]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
Just to be sure:
1.
Did you call backintime once before the ps to trigger the serviceHelper daemon activation? Then try again
Should show the service process, otherwise it is not running
ps aux | grep -i serviceHelper
Must show a line similar to this:
root 16023 0.0 0.0 70552 22248 ? S Okt11 0:00 /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
2.
Could you please start the serviceHelper daemon with sudo (otherwise registration at the system bus is not allowed): Instead of
usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
use sudo /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py
Please post the traceback here if any 3.
Could you please check if this file exists and post the active permissions with stat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf (should be: `Access (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) 4.
If the file exists could please check if the content corresponds to the Github version of the conf file: cat /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf vs.
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1279206231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPY7GTFM3UQNHLDVPNXDWDGBHPANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
aryoda
commented
2 years ago Note: that once I was able to start the serviceHelper, I could not ctrl-C out of it. I had to ctrl-z and bg the process.
Me too, that seems to be normal
I have no clue so far (perhaps a broken installation of whatever)...
I have just set up a VM and hoped that I could reproduce the issue.
@dwainsims How did you install BiT? Via yast2 GUI? I saw two packages (backintime and backintime-qt) and after installing them everything worked OK (on Linux OpenSuseLeap 5.3.18-150300.59.93-preempt #1 SMP).
BTW: You should use the "code" markup for your script output to improve readability (and scrolling)...
dwainsims
commented
2 years ago Comments below
On Fri, Oct 14, 2022 at 4:42 PM aryoda @.***> wrote:
Note: that once I was able to start the serviceHelper, I could not ctrl-C out of it. I had to ctrl-z and bg the process.
Me too, that seems to be normal
I have no clue so far (perhaps a broken installation of whatever)...
I have just setting up a VM and hoped that I could reproduce the issue.
@dwainsims https://github.com/dwainsims How did you install BiT? Via yast2 GUI?
Yes. Long ago. January? Maybe. That's the weird thing. It had been working fine until one day....
I saw two packages (backintime and backintime-qt) and after installing them everything worked OK (on Linux OpenSuseLeap 5.3.18-150300.59.93-preempt #1 SMP).
I have 3 packages. backintime, backintime-qt, and backintime-lang
BTW: You should use the "code" markup for your script output to improve readability (and scrolling)...
Sorry
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1279444945, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPY72IHUMVPXYSFKFCZ3WDHATXANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
buhtz
commented
2 years ago FYI: There is also a distro bug report at OpenSuse.
aryoda
commented
2 years ago FYI: There is also a distro bug report at OpenSuse.
THX for the reference. The opensuse issue was opened by Dwain Sims who also participated in this issue. I have this issue on my list on position 4 and have just updated my Open Suse VM to the same reported kernel version (and hopefully the same dependecies that cause this problem). I need some time for fixing my other issues first, then I come back here.
dwainsims
commented
2 years ago Thanks! I would still like to get BIT working again!
On Fri, Nov 18, 2022 at 4:53 AM aryoda @.***> wrote:
FYI: There is also a distro bug report at OpenSuse https://bugzilla.opensuse.org/show_bug.cgi?id=1203800.
THX for the reference. The opensuse issue was opened by Dwain Sims who also participated in this issue. I have this issue on my list on position 4 and have just updated my Open Suse VM to the same reported kernel version (and hopefully the same dependecies that cause this problem). I need some time for fixing my other issues first, then I come back here.
— Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/921#issuecomment-1319775569, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGJWPY3SHDBEZZTACLVHF33WI5GX3ANCNFSM4FRR5ZNQ . You are receiving this because you were mentioned.Message ID: @.***>
aryoda
commented
1 year ago @dwainsims Could you please check if this dependency is installed:
python3-dbus-pythonIt also includes the required (python) package dbus.mainloop if I interpret the YaST2 file list correctly...
flymikeGit
commented
1 year ago Same problem, but with fresh install of Ubuntu 22.04
BiT originally installed from Ubuntu PPA but would not start with these same symptoms
Later reinstalled using BiT PPA (both backintime & backintime-qt
$ backintime check-config
Back In Time
Version: 1.3.2
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type 'backintime --license' for details.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 177, in activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 1165, in <module>
startApp()
File "/usr/share/backintime/common/backintime.py", line 517, in startApp
args.func(args)
File "/usr/share/backintime/common/backintime.py", line 1150, in checkConfig
cfg = getConfig(args)
File "/usr/share/backintime/common/backintime.py", line 669, in getConfig
cfg = config.Config(config_path = args.config, data_path = args.share_path)
File "/usr/share/backintime/common/config.py", line 280, in __init__
self.setupUdev = tools.SetupUdev()
File "/usr/share/backintime/common/tools.py", line 1722, in __init__
conn = bus.get_object(SetupUdev.CONNECTION, SetupUdev.OBJECT)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
return self.ProxyObjectClass(self, bus_name, object_path,
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 250, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 182, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 277, in start_service_by_name
return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
$ systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Wed 2023-01-04 09:12:10 EST; 7h ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 1256 (dbus-daemon)
Tasks: 1 (limit: 18682)
Memory: 4.3M
CPU: 6.082s
CGroup: /system.slice/dbus.service
└─1256 @dbus-daemon --system --address=systemd: --nofork --nopidfi>Jan 04 15:34:05 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating via systemd:> Jan 04 15:34:06 FLYMIKE-PC2 dbus-daemon[1256]: [system] Successfully activated > Jan 04 15:36:50 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating via systemd:> Jan 04 15:36:50 FLYMIKE-PC2 dbus-daemon[1256]: [system] Successfully activated > Jan 04 15:37:30 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating via systemd:> Jan 04 15:37:31 FLYMIKE-PC2 dbus-daemon[1256]: [system] Successfully activated > Jan 04 16:37:17 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating service name> Jan 04 16:37:17 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activated service 'net.> Jan 04 16:37:55 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating service name> Jan 04 16:37:55 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activated service 'net.>
Also used qdbusviewer, and confirmed that the BiT serviceHelper does not appear in System Bus
4. Confirm that /usr/share/backintime/qt/serviceHelper.py is installed$ stat /usr/share/backintime/qt/serviceHelper.py File: /usr/share/backintime/qt/serviceHelper.py Size: 13262 Blocks: 32 IO Block: 4096 regular file Device: fd07h/64775d Inode: 4472036 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2023-01-03 13:18:14.720729532 -0500 Modify: 2022-03-12 08:23:43.000000000 -0500 Change: 2023-01-03 13:18:13.064738748 -0500 Birth: 2023-01-03 13:18:13.020738992 -0500
5. Start serviceHelper manually$ cd /usr/share/backintime/qt $ sudo python3 serviceHelper.py Running BIT service.
Seem to succeed. Cannot Ctrl-C out of that.
6. Capture complete log$ journalctl -b --unit=dbus | grep -i backintime >tmp/temp.txt $ cat tmp/temp.txt Jan 04 09:12:46 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.108' (uid=1000 pid=3059 comm="python3 -Es /usr/share/backintime/common/backintim" label="unconfined") (using servicehelper) Jan 04 09:12:46 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied Jan 04 16:37:17 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.149' (uid=1000 pid=37446 comm="python3 -Es /usr/share/backintime/common/backintim" label="unconfined") (using servicehelper) Jan 04 16:37:17 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied Jan 04 16:37:55 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activating service name='net.launchpad.backintime.serviceHelper' requested by ':1.150' (uid=1000 pid=37470 comm="python3 -Es /usr/share/backintime/common/backintim" label="unconfined") (using servicehelper) Jan 04 16:37:55 FLYMIKE-PC2 dbus-daemon[1256]: [system] Activated service 'net.launchpad.backintime.serviceHelper' failed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied
@flymikeGit Thanks for your detailed report. It hope I can reproduce this in a fresh Ubuntu 22.04 VM (which I have to set up once I have time for this issue). I have put the issue on my TODO list.
backintime --diagnostics?backintime and backintime-qt of Ubuntu 22.04 and got this error then?Edit:
Later reinstalled using BiT PPA (both backintime & backintime-qt)
Is my interpretation correct that even after this update to BiT 1.3.2 the error still occurs?
THX!
flymikeGit
commented
1 year ago @flymikeGit Thanks for your detailed report. It hope I can reproduce this in a fresh Ubuntu 22.04 VM (which I have to set up once I have time for this issue). I have put the issue on my TODO list.
- Which Ubuntu flavor (desktop) are you using? I'm using MATE, but have also tried removing backintime-common backintime-qt then installing using the default desktop.
- Could you please provide the output of
backintime --diagnostics? No such option exists:backintime --diagnostics usage: backintime [-h] [--config PATH] [--share-path PATH] [--debug] [--profile NAME | --profile-id ID] [--quiet] [--version] [--license] {backup,backup-job,benchmark-cipher,check-config,decode,last-snapshot,last-snapshot-path,pw-cache,remove,remove-and-do-not-ask-again,restore,shutdown,smart-remove,snapshots-list,snapshots-list-path,snapshots-path,unmount} ... backintime: error: Unknown Argument(s): --diagnostics- Edit: Did you install
backintimeandbackintime-qtof Ubuntu 22.04 and got this error then? YesEdit:
Later reinstalled using BiT PPA (both backintime & backintime-qt)
Is my interpretation correct that even after this update to BiT 1.3.2 the error still occurs?
Installing backintime-common backintime-qt from the Ubuntu 22.04 repo yields BiT version 1.3.2 - which is the same version that is installed if using the BiT repo. THX! Note: on a different installation, I upgraded to 22.04 rather than fresh install. BiT remained at version 1.2.2 (don't know why) and does not have this problem. Q: Is there a .deb file available for BiT 1.2.1?
Ubuntu 18.10 backintime latest commit a5feec75aa1ac733f5d7ce5b9fc22ccc7b56dc81 python3-pyqt4 4.12.1+dfsg-2build1 python3-pyqt5 5.11.2+dfsg-1ubuntu2
Everything was fine until I installed python3-pyqt5. Now I get:
Bit binary packages depend on python3-pyqt4, so I can't uninstall the latter. I need python3-pyqt5 for other packages.
Any suggestion @Germar?