Description of problem: Every time I start luckybackup (as non-root user) it asks for password. Earlier versions didn't do that. According to developer it's an error. Version-Release number of selected component (if applicable): luckybackup-0.3.5-2.fc12.i686 How reproducible: Just starting program as normal user. Steps to Reproduce: 1. Open Konsole (not as root) 2. Type "luckybackup" Actual results: Asking for root-password Expected results: Program running in non-root mode Additional info: Package luckybackup-0.3.5-1.fc.i686.rpm available at this address http://www.kde-apps.org/content/show.php/luckyBackup?content=94391&PHPSESSID=82d71774a348411ea336e01f4647c70a is OK
Yes, the "error" is volitional. Well, and the result is as well a problem with the system we use in Fedora. We use consolekit to gain root access. The problem there is that you cant have the same binary running as root and non-root. When you run luckybackup it calls the symlink in /usr/bin that points to the binary in /usr/sbin. The problem started since we dont have that su-to-root that is used for gnome in the .desktop file to gain root. Gnome in Fedora uses consolekit. We dont even have gnomesu to call. That would have made it possible to have luckybackup running as root and non-root. It would have been possible as a "KDE only" version. Since there are ways like kdesu or parts in the .desktop file. The way i implemented it, it's usable for every Desktop Environment in Fedora, not just KDE and ready for the future (consolekit).
This seems unsatisfactory. One side effect is that logs and configuration files are saved under /root/.luckyBackup where a normal user can't see them by default. Is the primary purpose of this program not for regular users to backup their personal data? Surely "administrators" use other tools to do system backups like partition mirroring programs and the like? If nothing else I would very much like to see the KDE only fix implemented.
Well, looks like i missed to read the bits about beesu. Let me try if it works correctly with it in GNOME, XFCE, LXDE and i will change it to the default behavior soon. Thanks for reporting the bug.
luckybackup-0.3.5-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc12
luckybackup-0.3.5-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc11
luckybackup-0.3.5-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc13
luckybackup-0.3.5-3.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update luckybackup'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc12
luckybackup-0.3.5-3.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update luckybackup'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc11
luckybackup-0.3.5-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update luckybackup'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/luckybackup-0.3.5-3.fc13
It would probably be good for upstream to write the app to use PolicyKit, which is intended to handle exactly this kind of situation (an app which needs different privileges for different usage). We'd like to keep a lid on the privilege escalation methods used in Fedora, and PolicyKit seems good for most situations... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have just downloaded new package. Everything seems to be OK now.
(In reply to comment #10) > It would probably be good for upstream to write the app to use PolicyKit, which > is intended to handle exactly this kind of situation (an app which needs > different privileges for different usage). We'd like to keep a lid on the > privilege escalation methods used in Fedora, and PolicyKit seems good for most > situations... This is a good idea. I will talk to upstream. Thanks Adam.
luckybackup-0.3.5-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
luckybackup-0.3.5-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
luckybackup-0.3.5-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
Uh, I haven't tested this, but I think there's an easy way to fix this while still using consolehelper: ln -s %{_bindir}/luckybackup %{buildroot}%{_sbindir}/luckybackup-root ln -s consolehelper %{_bindir}/luckybackup-root Then running luckybackup-root should give you luckybackup running as root through consolehelper and running just luckybackup should let it run as your user.