In the past, I noticed that when I tried to run timeshift-gtk from an icon on a GUI panel, the application didn't start after I enter my password in the password window. Well, I ran pkexec timeshift-gtk in the terminal and entered my password in the window again, and I saw a GTK "cannot open display" warning in the terminal window. It turned out that modifying the /bin/timeshift-launcher script in the following way makes it so that I can open timeshift-gtk with the first method (I still get the same error for the terminal method):
Change line 21 of the script from this:
pkexec ${app_command}to this:
pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY ${app_command}It's possible that one or more other lines in the script need to be changed to get the command line method to work, although I used it troubleshoot the first problem, so it's likely not as important.
Whether this is an upstream issue or something wrong specifically in the omniverse repo, please consider making this change. Thanks!
I am running Openbox-dinit, updated timeshift yesterday and have no problems running 'timeshift-gtk' as root.
I know this is not helping you with your problem, but just thought that I would point out that in my particular configuration I am not experiencing any problems :)
i would start with reading the thread here as to explain why it might not be working
https://stackoverflow.com/questions/2400965/authenticating-gtk-app-to-run-with-root-permissions
which you clearly knew. sorry for chiming in.
Well I'm using XFCE which is another GTK-based DE. So idk what the deal is
But the issue
isn't that the password authentication window doesn't come up at all (it does), it's just that without the above modification to the shell script, the application (Timeshift) doesn't display once I correctly type in my password and press OK. And this wouldn't be so much of an issue for me if pacman
didn't overwrite the shell script every time an update to Timeshift is installed.
And since the other guy is running another GTK-based DE and is not having this issue: no, I don't know what the issue is. Although it may be a bug with XFCE, which is what I use.