Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1692673
| Summary: | Backintime does not start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephan Mueller <smueller> |
| Component: | backintime | Assignee: | hannes <johannes.lips> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | bonfostar, brizly, cunio, dinel.mk.two, johannes.lips, l88629, ogassner, paolo.mozzati, projects.rg, rosset.filipe |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | backintime-1.2.0-3.fc30 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-05 02:19:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This is most probably a duplicate of bug https://bugzilla.redhat.com/show_bug.cgi?id=1662259 . Please try the workaround by changing the group on the following file: chgrp dbus /usr/libexec/dbus-1/dbus-daemon-launch-helper *** This bug has been marked as a duplicate of bug 1662259 *** I do not think it is a duplicate. My dbus helper app is 4750 root:dbus I think it has more to do with Python. The python sys.path is /usr/lib64/python3.7/site-packages whereas the backintime python files are in /usr/lib/python3.7/site-packages Ok, yeah was a bit quick. Probably a packaging change is necessary with the move to Python 3 and the removal of all python2 related stuff. I am confirming the bug. *** Bug 1700894 has been marked as a duplicate of this bug. *** Can you please check, if this build solves the issue for you: https://koji.fedoraproject.org/koji/buildinfo?buildID=1260123 Everything seems to work fine. Confirmed, working. backintime-1.2.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1c4862b2e backintime-1.2.0-1.fc30 works but updating the qt package does not work because of the package name change, you have to remove all backintime package and reinstall the new ones or use --nodeps. backintime-qt should obsolete backintime-qt4. Well, that's actually, what's in the spec file and also in the rpm: rpm -qp --obsoletes backintime-qt-1.2.0-2.fc30.noarch.rpm backintime-gnome < 1.1.12-1 backintime-kde < 1.1.12-1 backintime-qt4 <= 1.1.24-7 Not sure, what's the issue. Should be fixed now, with the latest version on koji: https://koji.fedoraproject.org/koji/taskinfo?taskID=34552556 backintime-1.2.0-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1c4862b2e backintime-1.2.0-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1c4862b2e Similar problem has been detected: after update from fedora29 to fedora30 backintime doesn't start reporter: libreport-2.10.0 cmdline: python3 /usr/share/backintime/qt4/app.py crash_function: module exception_type: ModuleNotFoundError executable: /usr/share/backintime/qt4/app.py interpreter: python3-3.7.3-1.fc30.x86_64 kernel: 5.0.9-301.fc30.x86_64 package: backintime-qt4-1.1.24-7.fc30 reason: app.py:34:<module>:ModuleNotFoundError: No module named 'tools' runlevel: N 5 type: Python3 uid: 1000 Just updated backintime from testing. Everything seems fine! Similar problem has been detected: After upgrading to F30, backintime doesn't start anymore. reporter: libreport-2.10.0 cmdline: python3 /usr/share/backintime/qt4/app.py crash_function: module exception_type: ModuleNotFoundError executable: /usr/share/backintime/qt4/app.py interpreter: python3-3.7.3-1.fc30.x86_64 kernel: 5.0.9-301.fc30.x86_64 package: backintime-qt4-1.1.24-7.fc30 reason: app.py:34:<module>:ModuleNotFoundError: No module named 'tools' runlevel: N 5 type: Python3 uid: 1000 packages from updates-testing work perfectly. Similar problem has been detected: first start after upgrading to fedora 30. Instant crash :( reporter: libreport-2.10.0 cmdline: python3 /usr/share/backintime/qt4/app.py crash_function: module exception_type: ModuleNotFoundError executable: /usr/share/backintime/qt4/app.py interpreter: python3-3.7.3-1.fc30.x86_64 kernel: 5.0.9-301.fc30.x86_64 package: backintime-qt4-1.1.24-7.fc30 reason: app.py:34:<module>:ModuleNotFoundError: No module named 'tools' runlevel: N 5 type: Python3 uid: 1000 The update has just been pushed to stable and the issue should be gone shortly. backintime-1.2.0-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Backintime does not start. The following log is performed as normal user: $ backintime python3: can't open file '/usr/share/backintime/common/backintime.py': [Errno 2] No such file or directory $ backintime-qt4 Traceback (most recent call last): File "/usr/share/backintime/qt4/app.py", line 34, in <module> import tools ModuleNotFoundError: No module named 'tools' Version-Release number of selected component (if applicable): 1.1.24-7.fc30 How reproducible: Always Steps to Reproduce: 1. Simply install F30 and backintime. Additional info: Note: backintime-plugins does not install due to dependency issues. Even with installing that package using rpm --nodeps the issue above does not go away.