Bugzilla – Bug 1045553
ncurses version of yast2 is started instead of qt/gtk
Last modified: 2017-09-18 12:55:55 UTC
Created attachment 729862 [details] yast2 logs running yast21 --gtk/qt always ends up with yast2 being started in ncurses. #rpm -qv yast2 yast2-3.2.38-1.1.x86_64 # rpm -qv libyui-qt-pkg7 libyui-qt-pkg7-2.45.12-1.4.x86_64 # rpm -qv libyui-qt7 libyui-qt7-2.47.1-1.3.x86_64 y2logs in attachment. Feel free to ask for more info.
Do you run it e.g. from root terminal / konsole which was started from non-privileged X environment?
(In reply to Michal Filka from comment #1) > Do you run it e.g. from root terminal / konsole which was started from > non-privileged X environment? How do I find out whether X environment is non-privileged? I run it from gnome-terminal as superuser in standard GNOME session. It used to work before just fine.
Is the $DISPLAY environment var set?
looks similar to bug 1046317
(In reply to Steffen Winterfeldt from comment #3) > Is the $DISPLAY environment var set? Hm. No. echo $DISPLAY says nothing.
(In reply to Vit Pelcak from comment #5) > (In reply to Steffen Winterfeldt from comment #3) > > Is the $DISPLAY environment var set? > > Hm. No. echo $DISPLAY says nothing. Then you don't have a working X11 environment. Please make sure $DISPLAY is set.
Just did a tw gnome install and the DISPLAY var was correctly set in the gnome terminal. yast worked fine. Sorry, I think this a config issue on your side. Probably you're unsetting DISPLAY in one of your scripts.
rheia:~ # export DISPLAY=:0 rheia:~ # echo $DISPLAY :0 rheia:~ # yast2 sw_single No protocol specified terminate called after throwing an instance of 'YUIException' what(): Can't open display /sbin/yast2: line 448: 7509 Aborted (core dumped) $ybindir/y2start $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS rheia:~ # echo $DISPLAY :0
I also tried > xdg-su -c yast2 (gnomesu:7687): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. And yast was not started.
Did you do a default installation or did you change some settings? I cannot reproduce this.
I found the reason. It is caused by Wayland/Weston. When you install gnome-session-wayland, then Wayland is used. Wayland is probably lacking this functionality. When you uninstall gnome-session-wayland, it works again. So I believe bug should be reassigned to Xorg/Wayland maintainers. Sorry for the noise.
I guess this happens on a GNOME session running on Wayland. I would say, that GNOME needs to make sure X apps run on Xwayland, if needed. Reassigning to GNOME component.
Looks like a duplicate of bug 955101.
*** Bug 1046317 has been marked as a duplicate of this bug. ***
(In reply to Felix Zhang from comment #13) > Looks like a duplicate of bug 955101. This is indeed the same issue - wayland per default does not allow 'foreign connections' of users (root is not the user owning the wayland screen output) a workaround is posted in this bug - a more permanent solution is being worked on *** This bug has been marked as a duplicate of bug 955101 ***