"= AUTHENTICATING FOR =Īuthentication is needed to run `/usr/bin/rsync' as the super userĢ) Simultaneously, in graphic mode, it displays as before :
Grsync password password#
Running grsync (with superuser mode checked) in test mode, in a non-root terminal :ġ) the password prompt is displayed (but password is not accepted) (I don't have any record of orphans removed before grsync stopped working.) Maybe there is a missing dependency somewhere ? I have periodically removed (most but not all) reported orphans. So there is some problem with how grsync is now doing it. The terminal is opened using gksu for authentification, which has never caused any problems. It is this command line that executes correctly in a terminal (with root privileges). It is displayed just before the error message, which indicates an authentication error. The command line generated by grsync starts with pkexec. The last containing libpolkit-agent-1.so.0. I have polkit (containing pkexec), polkit-gnome, and lib64polkit1_0 installed (all 64bit). It was like I was running and over-sized tablet.) (In passing, I had forgotten how dramatically different the default gnome3 theme was from gnome2. I'm using the gnome classic desktop, with a customized menu bar, and thunar for files, but I don't think that is related. (by TV, I think.)Īnyway, that coincides with the rsync output of grsync working in a terminal with root privileges. I vaguely remember comments on the dev list a while back about changes related to authentication. I would suspect it is somehow related to systemd changes, but that is only a wild guess. So apparently it is a problem with authentication. I get exactly the same error message (with "run as superuser" checked). (Since even on my account there are some files with root or other owners.) I tried with a fresh user, and it *seemed* to work, until I checked the "superuser" option, which I always use for my backups with grsync. Not sure when I installed the update.Ĭlassifying as "critical", as a typical user will not likely think of the workaround, and it is totally non-functional without.
Grsync password update#
This problem did not occur before the last update in February, although it is possible that I skipped an update. (Must use root privileges if that is required by the rsync command, of course.) However, the rsync command generated by grsync works perfectly if copy/pasted into a terminal.
Note that "/dev/tty" does exist, as it should. "Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address When launching rsync, it aborts the process with : (That is, up to pressing the test or run button.) Grsync works normally up to launching rsync, including saving any configuration changes made.
0 kommentar(er)
