Yast GUI not working on tumbleweed

After i updated to newest version of tumbleweed the yast gui does not work in any desktop (KDE or Gnome) below are the errors I see in the y2log file

2024-12-12 14:11:48 <1> SuSE-Tumbleweed(36173) [ui] YUI.cc(YUI):83 This is libyui 4.6.3
2024-12-12 14:11:48 <1> SuSE-Tumbleweed(36173) [ui] YUI.cc(YUI):84 Creating UI with threads
2024-12-12 14:11:48 <1> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(YQUI):110 This is libyui-qt 4.6.3
2024-12-12 14:11:48 <3> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):660 Failed to create wl_display (No such file or directory)
2024-12-12 14:11:48 <1> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):647 Could not load the Qt platform plugin “wayland” in “” even though it was found.
2024-12-12 14:11:48 <1> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):647 Could not load the Qt platform plugin “xcb” in “” even though it was found.
2024-12-12 14:11:48 <3> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):660 This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
2024-12-12 14:11:48 <3> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):660
2024-12-12 14:11:48 <3> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):660 Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.
2024-12-12 14:11:48 <3> SuSE-Tumbleweed(36173) [qt-ui] YQUI.cc(qMessageHandler):660

The text version does work . Im not sure what the issue is any help would be appreciated.

Hi and welcome, this may be a good starting point > openSUSE:Report a YaST bug - openSUSE Wiki

Additionally please create a bug report here > https://bugzilla.opensuse.org/

@hoiatl wrote:

Are you using Wayland?
If yes, login using the option “Plasma / X11” and see if that works.

I did try that and same results

will look at thx

You forgot to describe how you run YaST.

It doesnt matter if I start it from the command line or app launcher, its the same result

Also one of the “solutions” i found online was to boot to the tumbleweed dvd and run the repair option and reinstall the system files. This also did not work

Check if the following packages are installed:

LT-B:~ # zypper --no-refresh se -i yui
Loading repository data...
Reading installed packages...

S  | Name                 | Summary                                                   | Type
---+----------------------+-----------------------------------------------------------+--------
i+ | libyui-ncurses-pkg16 | Libyui - yast2 package selector widget for the NCurses UI | package
i  | libyui-ncurses16     | Libyui - NCurses (text based) user interface              | package
i  | libyui-qt-graph16    | Libyui - Qt graph widget                                  | package
i+ | libyui-qt-pkg16      | Libyui - Qt package selector                              | package
i  | libyui-qt16          | Libyui - Qt (graphical) user interface                    | package
i  | libyui16             | Libyui - GUI abstraction library                          | package
LT-B:~ # 

Loading repository data

Reading installed packages


S | Name | Summary | Type
—±------------------------------±-----------------------------------------------------------------±-------
i | libyui-devel | Libyui header files and examples | package
i | libyui-ncurses-devel | Libyui - Header fles for the NCurses (text based) user interface | package
i+ | libyui-ncurses-pkg-devel | Libyui-ncurses-pkg header files | package
i+ | libyui-ncurses-pkg16 | Libyui - yast2 package selector widget for the NCurses UI | package
i+ | libyui-ncurses-rest-api-devel | Libyui - Header files for the NCurses REST API plugin | package
i | libyui-ncurses-rest-api16 | Libyui - REST API plugin for the Ncurses frontend | package
i+ | libyui-ncurses-tools | Libyui - tools for the NCurses (text based) user interface | package
i+ | libyui-ncurses16 | Libyui - NCurses (text based) user interface | package
i | libyui-qt-devel | Libyui - Header files for the Qt (graphical) user interface | package
i+ | libyui-qt-graph-devel | Libyui - Header files for the Qt graph widget | package
i+ | libyui-qt-graph16 | Libyui - Qt graph widget | package
i+ | libyui-qt-pkg-devel | Libyui-qt-pkg header files | package
i+ | libyui-qt-pkg16 | Libyui - Qt package selector | package
i+ | libyui-qt-rest-api-devel | Libyui - Header files for the Qt REST API plugin | package
i | libyui-qt-rest-api16 | Libyui - The REST API plugin for the Qt frontend | package
i+ | libyui-qt16 | Libyui - Qt (graphical) user interface | package
i | libyui-rest-api-devel | Libyui - REST API header files | package
i | libyui-rest-api16 | Libyui - REST API plugin, the shared part | package
i+ | libyui16 | Libyui - GUI abstraction library | package
i+ | perl-yui | Perl bindings for libyui | package
i+ | python3-yui | Python 3 bindings for libyui | package
i+ | ruby-yui | Ruby bindings for libyui | package
i+ | ruby3.3-rubygem-libyui-rake | Rake tasks that provide basic workflow for libyui development | package
SuSE-Tumbleweed:/home/hoi #

here is another crazy issue I can run Qt programs as a normal user but whenever it needs root elevation it fails:

SuSE-Tumbleweed:/home/hoi # wireshark
** (wireshark:144402) 21:40:55.512396 [GUI CRITICAL] – This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

SuSE-Tumbleweed:/home/hoi # transmission

(transmission-gtk:146035): Gtk-WARNING **: 21:46:03.494: Failed to open display

what would cause root elevation to fail to open a gui app???

How exactly you do “root elevation”?

P.S. Use preformatted text when posting computer output. Your posts are barely readable.

Elevated Privaledges

-Seasons Greetings

not sure what you are asking , but I put in the root password to elevate to root

I found this thread, now when I do what badshah400 advises it works. The yast2 gui appears. Im not sure why this is or how to fix. any help would be appreciated and may help other users

(now my issue is that when i try to launch the program, in this case yast2 from the desktop as normal user I get the dialog box for the root password, after I put in the password the yast2 gui fails to appear)

also when do use su from command prompt and then launch the program, after I close the yast2 gui I get this message:

SuSE-Tumbleweed:/home/hoi # yast2
QStandardPaths: runtime directory ‘/run/user/1000’ is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 475

I am seeing exactly the same error when trying to run yast2 in Hyprland. There are some suggestions out there but didn’t tried. There is a command that one of the guru here posted not long ago and it works in hyprland. If I see the thread I will post it here.

su keeps your user’s session environment which is what the error is about. Always use su - to switch to root user environment. If you also need to run Wayland programs:

su -w WAYLAND_DISPLAY -l root

And exactly like OP you do not explain how you run yast2 so it is impossible to guess what goes wrong.

Hi, I used

su -c yast2, kdesu yast2, /usr/bin/xdg-su -c /sbin/yast2
su (root password) then as root yast2 with no joy

That’s in Hyprland, then I found your post in this thread:

That was the one that worked in Hyprland.
On a side note in wayfire the yast2 launcher doesn’t work. The command under the launcher is /usr/bin/xdg-su -c /sbin/yast2
but running su -c yast2 in the terminal, yast2 works.

Does Hyprland have Xwayland (or any other X11 support)?