After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784793 - How to discover which server (Mutter, Weston, Xwayland...) does run under GNOME3 on Wayland?
How to discover which server (Mutter, Weston, Xwayland...) does run under GNO...
Status: RESOLVED INVALID
Product: gnome-system-log
Classification: Core
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-system-log-maint
gnome-system-log-maint
Depends on:
Blocks:
 
 
Reported: 2017-07-11 13:20 UTC by _nobody_
Modified: 2017-07-12 07:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description _nobody_ 2017-07-11 13:20:31 UTC
Simple/trivial question: How to discover which server (Mutter, Weston, Xwayland... you name it) runs under GNOME3 on Wayland?

We, GNOME3 users, we should have easy method to extract this info from GNOME3. Don't you agree?

Thank you,
_nobody_
Comment 1 Cosimo Cecchi 2017-07-11 14:49:02 UTC
Note that:
- bugzilla is not a support forum to simply ask question. It's a place to report bugs in software modules. Please refrain from posting questions like these on the GNOME bugzilla in the future.
- gnome-system-log has nothing to do with Wayland and compositing servers.

However, you're lucky because I know the very simple answer: mutter is the Wayland compositor that gnome-shell uses.
Comment 2 _nobody_ 2017-07-11 16:45:33 UTC
> However, you're lucky because I know the very simple answer: mutter is the
> Wayland compositor that gnome-shell uses.

Really? You betcha?!

OK, let me present to you the new facts!

I finally discover what Wayland server I am running at GNOME on Wayland!

[user@localhost ~]$ loginctl 
   SESSION        UID USER             SEAT             TTY             
         4       1000 user             seat0            /dev/tty7       
        c1         42 gdm              seat0            /dev/tty1       
         2          0 root             seat0            tty6            

3 sessions listed.
[user@localhost ~]$ loginctl show-session 2 -p Type
Type=tty
[user@localhost ~]$ loginctl show-session 4 -p Type
Type=wayland
[user@localhost ~]$ loginctl show-session c1 -p Type
Type=wayland
[user@localhost ~]$ ps -elf | grep X
0 S gdm        1481   1311  0  80   0 - 66519 -      Jul10 tty1     00:02:33 /usr/bin/Xwayland :1024 -rootless -noreset -listen 4 -listen 5 -displayfd 6
0 S user       1938   1930  0  80   0 - 70783 ep_pol Jul10 tty7     00:02:30 /usr/bin/Xwayland :0 -rootless -noreset -listen 4 -listen 5 -displayfd 6
0 S user      37054   3099  0  80   0 - 29861 pipe_w 15:05 pts/0    00:00:00 grep --color=auto X
[user@localhost ~]$ 

It is... Xwayland???

So, Houston, we have here The Problem! ;-)

_nobody_
Comment 3 _nobody_ 2017-07-11 16:49:54 UTC
You see... Cosimo. I would like GNOME-shell on Wayland to do Xorg server lookalike Xorg.0.log logging. Do you understand the point?

And this was NOT a question. Just request for enhancement! GNOME-shell should provide to us this info (How to discover which server (Mutter, Weston, Xwayland...) does run under GNOME3 on Wayland?), don't you agree???

Thank you,
_nobody_
Comment 4 Cosimo Cecchi 2017-07-12 00:38:54 UTC
The reason you see Xwayland in the process list is because you're using some X applications under Wayland. In that case, Xwayland will act as a bridge between the application and whatever Wayland compositor you're using -- it has nothing to do with GNOME.

I am not sure what "Xorg server lookalike Xorg.0.log logging" means; Xorg server logging can be configured in a number of ways, and it's again mostly up to the distribution setup and out of GNOME's control. How a Wayland compositor logs is up to each individual compositor.

If you would like mutter/gnome-shell to log differently, please open an enhancement request against mutter or gnome-shell.
Comment 5 _nobody_ 2017-07-12 04:07:45 UTC
> The reason you see Xwayland in the process list is because you're using
> some X applications under Wayland. In that case, Xwayland will act as a
>  bridge between the application and whatever Wayland compositor you're
> using -- it has nothing to do with GNOME.

Cosimo,

I need to know what is "whatever Wayland compositor you're using"? I know it has NOTHING to do with GNOME, but I would like GNOME to somehow query this info for me and get me back this info, since I have no clue what is beneath XWayland (Xorg server emulation, I suppose)?!

This Bugzilla is actually a request for the new feature, as I just described it (enhancement)!

_nobody_
Comment 6 Cosimo Cecchi 2017-07-12 07:49:51 UTC
(In reply to _nobody_ from comment #5)
> I need to know what is "whatever Wayland compositor you're using"? I know it
> has NOTHING to do with GNOME, but I would like GNOME to somehow query this
> info for me and get me back this info, since I have no clue what is beneath
> XWayland (Xorg server emulation, I suppose)?!
> 
> This Bugzilla is actually a request for the new feature, as I just described
> it (enhancement)!

Perhaps I'm not making my point clear...

If you're running GNOME under Wayland, the compositor is mutter. That can't be configured -- it's not like a window manager in the X11 days. gnome-shell runs as a mutter plugin and that's the only way it can run if you're using it with Wayland. As a consequence of that, there's nothing to query.

The use of Xwayland is purely about how each individual application that hasn't been ported to use Wayland natively runs in any Wayland environment (and gnome-shell is one of them); it is completely unrelated to how the desktop session itself runs.

If you're still unclear about how all this work, I encourage you to reach out to e.g. the support forum of your distribution, or a mailing list specific to Wayland users instead of posting here again.