| Summary: | Documented ways to run backintime as root do not work. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bob mckay <urilabob> |
| Component: | backintime | Assignee: | hannes <johannes.lips> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | i, johannes.lips, projects.rg |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-13 14:58:24 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: | |
|
Description
bob mckay
2016-09-28 03:01:27 UTC
OK, problem partly solved: sudo.conf originally contained: wheel ALL=(ALL) ALL I have added: rim ALL=(ALL) ALL and rim can now successfully run 'sudo -i backintime' - though it beats me why adding the 'rim' line should make a difference when rim was already a member of wheel. The point is, this needs to be documented, at minimum in the man page. What also needs documenting is the correct recipe for running the configuration gui for setting up root backup. Clicking on the root backup icon still doesn't work. So far, it's looking like what is needed is: sudo -i -E backintime-qt4 (it brings up the configuration screen OK, but I still have to confirm that I can save and run the configuration - this will take a while as I need another backup disk to do the test). Works for me. Did you try backintime-qt4-root in a terminal? I doubt backintime can run with sudo, better use 'pkexec backintime-qt4'. Is it possible you have done additional configuration to allow the root gui to run from the icon? It still does not launch for me, and as I said, this is a very recent, close-to-stock f24 installation. The only thing that works for me to get a root gui still is:
sudo -i -E backintime-qt4-root
which allowed me to create and run backintime root configurations. Even that only worked after I added my user (rim) to the sudoers file (I have reconfirmed that rim was already a member of wheel). I can confirm specifically that
pkexec backintime-qt4-root
does not work. It gives the error message
No protocol specified
app.py: cannot connect to X server :0.0
Again, it's not recommended to use sudo for backintime. Use backintime-qt4 as normal user, or with pkexec if in need with root rights. Use backintime-qt4-root for root user, it should prompt you for the password if you run it as normal user. Mind the difference between the binaries backintime-qt4 and backintime-qt4-root! There is a backintime-qt4-root command, so no need for sudo here. Think that can be closed. |