-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BIT won't start #1052
Comments
Same here on Manjaro Linux and building from source fails during the test. It seems to be something with
|
I also have the same error on Manjaro Testing. `Back In Time Back In Time comes with ABSOLUTELY NO WARRANTY. INFO: Update to config version 6 During handling of the above exception, another exception occurred: Traceback (most recent call last): |
The issue was resolved with the |
Confirmed, now running as expected. |
I still got the same error with version 5.14.1 (ubuntu 20.04) |
I found a solution, I uninstalled pip3 PyQt5 Fixed it for me on ubuntu 20.04 running |
Same Problem here,
Interesting though, I have another similar machine just with slight differences and there BIT works normal. Thanks a lot in advance! |
Thanks for reporting and debugging! Does this bug still happen for anyone, or have updates eliminated the problem? |
This error message is reported in several issues: Related to: #1233, #1014, #1013, #963, #921, #756 @emtiu Could/should this type of issue be "escalated" to a "high incident"? |
Thanks for the good spot! I'll try and combine/collect those Issues. Yes, High is the right label for this problem. It's always the rolling release distros that run into this kind of trouble, isn't it? ;) Moving target makes it so much harder to reproduce. |
If this here is the main/collecting issue for all the duplicates can we modify its title to a more informative one please? |
Hey there! Trying to get it running on Xubuntu 19.04 and this comes up.
`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/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 363, in get_name_owner
's', (bus_name,), **keywords)
File "/usr/lib/python3/dist-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/qt/app.py", line 1592, in
cfg = backintime.startApp('backintime-qt')
File "/usr/share/backintime/common/backintime.py", line 521, in startApp
return getConfig(args, False)
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 279, in init
self.setupUdev = tools.SetupUdev()
File "/usr/share/backintime/common/tools.py", line 1715, in init
conn = bus.get_object(SetupUdev.CONNECTION, SetupUdev.OBJECT)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 243, in get_object
follow_name_owner_changes=follow_name_owner_changes)
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 280, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
`
Anyone an idea what to do?
The text was updated successfully, but these errors were encountered: