-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wayland] Cannot launch BiT as root #836
Comments
This is a problem with Wayland. Take a look at this Bug and the workaround:
|
Hello, I'm using
When I go back to X session, everything is fine. I tried every known workaround without success :
Each time backintime fails silently (for logged user or root) I also compiled git master branch (Version: 1.2.0 git branch 'master' hash '7d24d1d' . That is < 1.2.1, is it normal ?) : same result. |
I found my workaround :
line 4 , replace : by
And now you can start backintime as usual with Activities / Application Menu. |
Now Ubuntu 21.04 defaults to wayland session, but the workaround above does not work anymore for root.
then replace
with
|
@Saroumane THX for reporting your work-around here! I have assigned this issue to myself and will revisit it when I find the time to investigate all Wayland-related issus (I am currently trying to fix other most-pressing issues.) Regarding your proposed work-around: I am wondering if directly executing BiT via |
I can reproduce the non-starting BiT-GUI as root on OpenSuse TumbleWeed with Wayland. Trying the proposed work-around
did not work but in fact starting BiT with I also tried Perhaps the wayland security model is so strict now that wayland root GUIs are no longer working. It could be related to #1592 since Qt5 is fully blocking... |
I think using the standard X11/xcb plugin of Qt5 is the way to solve this problem (instead of using
So I will change the Once we refactor BiT to fully support native |
The launcher of
Since this is stable for 4 years now I will do the same for our GUI launcher. The big challenges are
|
…robing.py" hangs; Cannot launch BiT (root) on Wayland - "qt5_probing.py" hangs when BiT is run as root and no user is logged into a desktop environment - BiT (root) starter script does not set Qt5 wayland-egl plugin anymore but uses the default (like BiT userland) - Improve logging (all sub process do now use the log context "backintime" too for easy journalctl grepping
…robing.py" hangs; Cannot launch BiT (root) on Wayland - "qt5_probing.py" hangs when BiT is run as root and no user is logged into a desktop environment - BiT (root) starter script does not set Qt5 wayland-egl plugin anymore but uses the default (like BiT userland) - Improve logging (all sub processes do now use the log context "backintime" too for easy journalctl grepping
…h BiT (root) on Wayland * "qt5_probing.py" hangs when BiT is run as root and no user is logged into a desktop environment * BiT (root) starter script does not set Qt5 wayland-egl plugin anymore but uses the default (like BiT userland) * Different Wayland Qt plugin was used in BiT (root) vs. BiT user-space: Now no wayland is enforced anymore * Improve logging (all sub processes do now use the log context "backintime" too for easy journalctl filtering via the ) Was PR #1597
Closed with PR #1597 |
Hello,
I recently update to Ubuntu 17.10, under Gnome. I try to launch BiT from Gnome, but it does not work (nothing happen). From a terminal, launching backintime-qt4 works fine (Version: 1.1.24), but for my purpose I need root authorisation. When I launch in a terminal pkexec backintime-qt4 I get the following error code: «Invalid MIT-MAGIC-COOKIE-1 keyapp.py: cannot connect to X server :0».
BiT is essential for me, what can I do to overcome this problem ?
Best regards.
The text was updated successfully, but these errors were encountered: