-
Notifications
You must be signed in to change notification settings - Fork 201
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 does not start: "Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name", related to pyqt5 and/or dbus packages #921
Comments
No such issue on Debian buster with: |
I get the same exact error messages on a fresh install of Fedora 29 -- Python version 3.7.0. |
I have the same problem with Fedora Workstation 29 on three different devices and in a freshly installed VM. |
Same error here, started after upgrading to Ubuntu 18.10 from 18.4. |
+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 |
I am now on Ubuntu 19.04 disco with python3-pyqt5 5.11.3+dfsg-1. |
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. |
Exact same issue on Arch. |
Hi everyone, |
On Ubuntu disco 19.04, this issue is gone with the upgraded
|
Hi everyone, Issue occurred on Debian GNU/Linux bullseye/sid with python3-pyqt5 5.12.3+dfsg-2. |
This comment was marked as off-topic.
This comment was marked as off-topic.
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
So it seems that at on such a KDE neon system, that 5th line with the ImportError seems to be the issue:
... which I don't understand. However, when I open a Python REPL shell and issue a:
...I don't see any import error, such as Backintime is inducing. Where should I look next to isolate this? |
Another way to test this:
Which immediately gives:
Is anyone else seeing this? |
SOLUTION! I found that the import order has an effect on inducing the ImportError crash. In
However, if the import order is changed to this, then there are no ImportError crashes!
I can now start and run backintime-qt! |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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? |
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
<#921 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJWPY72IHUMVPXYSFKFCZ3WDHATXANCNFSM4FRR5ZNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…fix Arch Linux build error (#1335) * Partially resolve bug #921 (BiT CLI side, serviceHelper system D-Bus daemon issues are still under investigation) * Fix #1233: Arch Linux build test and installation failure * Fix #1333: Backintime fails to build on Arch * Add better documentation for installation on Arch using AUR package Authored-by: aryoda <11374410+aryoda@users.noreply.github.com>
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. |
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
<#921 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJWPY3SHDBEZZTACLVHF33WI5GX3ANCNFSM4FRR5ZNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dwainsims Could you please check if this dependency is installed:
It also includes the required (python) package dbus.mainloop if I interpret the YaST2 file list correctly... |
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 Diagnostics:
Also used qdbusviewer, and confirmed that the BiT serviceHelper does not appear in System Bus
Seem to succeed. Cannot Ctrl-C out of that.
|
@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.
Edit:
Is my interpretation correct that even after this update to BiT 1.3.2 the error still occurs? THX! |
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.
|
Ubuntu 22.04 does still provide only BiT v1.2.1 so I guess you have added our BiT PPA You can check this via OK, BiT 1.3.2
I suggest to install the new upcoming release 1.3.3 which is already available as DEB package for Ubuntu. If the DBus service helper (or any other error) is happening again in BiT v1.3.3 please post supportive information here so that I can assist you. Once the release makes its way to our "stable" PPA you can delete the "testing" ppa and add "stable" instead...
I guess you mean BiT v1.2.1 and 1.2.2 was a typo. v1.2.1 is the default package in Ubuntu 22.04 (see above)
Yes, eg. if you remove our BiT PPA and install it from the original Ubuntu repo again: |
Can anyone of you reproduce the problem with the latest 1.3.3 release? |
Using Arch, BackInTime version 1.3.3-dev. The issue is now completely resolved for me! I can open BackInTime just fine. |
Using a Ubuntu 22.04-based distro, version 1.3.3-3~jammy works completely fine for me as well. |
Based on your feedback and the known difference between the reported 1.1.24 / 1.2.1 and the the latest 1.3.3 I assume it is fixed. If there is no fresh information the issue will be closed in the near future. But It is up to aryoda who is assigned to this issue to finally close it. |
So OpenSUSE Leap 15.3 provides
BIT 1.2.1-bp153.1.12
Python3-Dbus 1.2.16.-6.3.1
Still failing to launch.
I plan to upgrade to OpenSUSE Leap 15.5, but I would really like to do a
backup before I start. (sort of a Chicken-Egg problem.) I guess I need
to explore a different backup tool for the short term, with hopes that BIT
will run on 15.5.
Dwain
…On Sat, Oct 8, 2022 at 6:13 PM Michael Büker ***@***.***> wrote:
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:
- @dwainsims <https://github.com/dwainsims> on OpenSUSE 15.3 (above)
- @bighegi <https://github.com/bighegi> Ubuntu 20.04 LTS (in #1052
(comment)
<#1052 (comment)>
)
- @Kleysley <https://github.com/Kleysley> on Arch (in #1233 (comment)
<#1233 (comment)>
)
It seems to me like the problem here isn't really with pyqt5, but rather
an unsatisfied dbus dependency (in which case #1233
<#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.
—
Reply to this email directly, view it on GitHub
<#921 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJWPY3XWLFMMSC4JQD6BB3WCHWZFANCNFSM4FRR5ZNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think this bug is fixed in BiT v1.3.3++ and I vote to close this issue after a cooling-off period of two weeks. Please veto here if the same problem occurs in BiT v.1.3.3++ (preferably reproducible ;-) |
I am closing this now (cooling-off period expired without further reports). Please open a new issue if the latest version of BiT should still fail with the same issue |
Ubuntu 18.10
backintime latest commit a5feec7
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?
The text was updated successfully, but these errors were encountered: