http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c1 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@suse.com Flags| |needinfo?(mvidner@suse.com) --- Comment #1 from Steffen Winterfeldt --- Martin, an idea? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |fvogt@suse.com, | |hpj@suse.com, | |lnussel@suse.com, | |sreeves@suse.com --- Comment #3 from Ludwig Nussel --- from an IRC chat in the factory channel the following is needed: - yast needs to switch to gui not only for $DISPLAY but also WAYLAND_DISPLAY - a new pam module or pam_xauth patches - the pam module needs to create and set XDG_RUNTIME_DIR for the target user - the pam module needs link the wayland socket of the origin user to the runtime dir of the target user -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c5 --- Comment #5 from Fabian Vogt --- It's also necessary to set QT_QPA_PLATFORM=wayland if (only) WAYLAND_DISPLAY is set to force Qt to use the wayland platform plugin. This should be done in a YaST startup script AFAICT. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c7 --- Comment #7 from Fabian Vogt --- (In reply to Ludwig Nussel from comment #6)

Why doesn't Qt do that by default?

I don't know either. Until recently, the XCB plugin did actually abort() when connection failed, maybe that's why they didn't implement it yet. AFAIK this is planned for Qt 5.11 - maybe we can backport it. The question is: Do we want that? It would result in Qt applications on GNOME Wayland to use wayland instead of using Xwayland, which is a pretty big behaviour change. So I don't think so.

Anyways $DISPLAY would be exported if bug 1084737 leads to using xauth for Xwayland.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c9 --- Comment #9 from Fabian Vogt --- (In reply to Ludwig Nussel from comment #8)

(In reply to Fabian Vogt from comment #7)

...

(In reply to Ludwig Nussel from comment #6)

...

Why doesn't Qt do that by default?

I don't know either. Until recently, the XCB plugin did actually abort() when connection failed, maybe that's why they didn't implement it yet. AFAIK this is planned for Qt 5.11 - maybe we can backport it.

The question is: Do we want that? It would result in Qt applications on GNOME Wayland to use wayland instead of using Xwayland, which is a pretty big behaviour change.

What's the benefit from running Qt apps under GNOME Wayland through the X compat layer?

Many: 1) Not hitting missing features in the compositor 2) Not hitting missing features in the client 3) Not hitting missing features in the protocol (middle click paste?) 4) Not hitting protocol incompatibilities 5) Not hitting other behaviour changes - Qt applications will look different as the X font settings aren't used anymore, for instance Also, some applications might unconditionally expect an X connection, which means they just crash. Many applications (like YaST) didn't account for wayland which can result in missing window icons. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c10 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com Flags| |needinfo?(lnussel@suse.com) | |, needinfo?(fvogt@suse.com) --- Comment #10 from Lukas Ocilka --- Apart from comment #3 and comment #5, is there anything else that YaST needs to implement? In which exact circumstances should it do so? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c12 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lnussel@suse.com) | --- Comment #12 from Ludwig Nussel --- I guess you still want to add the check WAYLAND_DISPLAY in parallel to DISPLAY -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c15 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com Assignee|yast-internal@suse.de |jreidinger@suse.com --- Comment #15 from Josef Reidinger --- note: I tested it now with plasma session with wayland and works without any modification. But it is true, that plasma have DISPLAY and also WAYLAND_DISPLAY defined. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1083907 http://bugzilla.suse.com/show_bug.cgi?id=1083907#c17 --- Comment #17 from Josef Reidinger --- and fix merged. Regarding that xdg-su if you know better alternative that works in both env and we want to support it for serious amount of time, then we can replace all entries in desktop files that use it. -- You are receiving this mail because: You are on the CC list for the bug.