Home_greyopenFATE - openSUSE feature tracking > #322297
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Yast2 working in wayland

Feature state

openSUSE Distribution
New

Description

Wayland is coming with big steps. First distributions (eg fedora) already use it as default. Gnome should be already stable with it, Plasmas support is getting better and better. Some other DE already support it out of the box. Wayland is a lot more secure than Xserver and it is the future. I think it is time to bring Yast2's support for this. At the moment a user who wants to run wayland has just 2 solutions:

- Running yast in textmode (which is not a solution for non-geek users)

- Switch to another distribution, which offers better support

There were already some bugs opened by opensuse users. So you see the feature is already needed.

https://bugzilla.opensuse.org/show_bug.cgi?id=955101

Discussion


icons/user_comment.png D. L. wrote: (9 months ago)

Just repeating here the workaround from the bug (so you have a VERY good workaround between your two options provided):
xhost +LOCAL:

This entire issue is not limited to YaST - but in fact ANY GUI application running as a different user (most likely root)

icons/user_comment.png F. C. wrote: (9 months ago)

However, there is an interesting question here: why isn't YaST able to start in Wayland mode directly, since it is using Qt5. It should be able to run natively in Wayland and not requires X11..

icons/user_comment.png F. C. wrote: (9 months ago)

A "slightly" more secure way:

xhost +SI:localuser:root

This is equivalent to the current security model used currently on SLE12 / Leap.

icons/user_comment.png F. C. wrote: (9 months ago)

yast2 control center (Qt) or yast2 modules can be started in Wayland after installing libqt5-wayland and setting "QT_QPA_PLATFORM=wayland". But you need to be a regular user

icons/user_comment.png K. H. wrote: (8 weeks ago)

In the end xhost +SI:localuser:root is just a workaround and not a long term solution. With Wayland not budging on running GUI apps as root, it probably will be necessary run yast as a normal user and ask for the root password once changes are made (possibly using polkit).

icons/user_comment.png S. L. wrote: (6 weeks ago)

I think due to security reasons, you can select one of solution below:
1) Create list of trusted Wayland compositors and allow to run application as another user only on it
2) Allow to start single program in new Wayland session, but without desktop (only compositor and programs are running). When user tries to start second and next programs as this user, programs will start in the same Wayland sessions
3) (I don't know if it is possible, because I don't know low level kernel internals, but). Create Wayland proxy, which would be run as root, so can run tasks as another user. When user decides to run program as another user, virtual window will be created. When this window isn't window nearest to user, user can interact with desktop normally. In other case overlay of windows belonged to user this window is connected will be displayed. When user click outside own window, overlay will minimize.

Please tell me if you cannot understand my ideas. I must wrote, I didn't know Wayland internals, UDev and Linux kernel internals well.

Last change: 13 days ago
Voting
Score: 20
  • Negative: 0
  • Neutral: 0
  • Positive: 20
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint