Bug 780258 - Classic: Enable Wayland
Classic: Enable Wayland
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: extensions-module
3.23.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2017-03-19 12:20 UTC by Jeremy Bicha
Modified: 2017-11-25 02:26 UTC (History)
6 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Jeremy Bicha 2017-03-19 12:20:18 UTC
GNOME Shell is now Wayland by default, but GNOME Classic is X only.

Just add a gnome-classic.desktop to /usr/share/wayland-sessions/
Comment 1 Florian Müllner 2017-03-19 13:47:10 UTC
(In reply to Jeremy Bicha from comment #0)
> GNOME Shell is now Wayland by default, but GNOME Classic is X only.

Considering that classic is targeting people who are reluctant to move on, this is kind of intentional. Admittedly desktop icons not being available on wayland played a part there, and that limitation has since been fixed. Still, there will always be differences between X and wayland, and the former is clearly more "classic" than the latter ...
Comment 2 Jeremy Bicha 2017-03-19 13:56:23 UTC
I think Classic is about having something that looks more traditional but is still built on top of the latest GNOME.

A major audience for GNOME Classic is the RHEL desktop right? Maybe Red Hat would want to default to Wayland in their next major release?

My only hesitation is that this expands the default session list from 3 to 4 which is starting to get a bit long. On the other hand, everything in there is for a reason. I guess we could get it back to 2 again if we added a toggle switch to Settings for Wayland.
Comment 3 q2dg 2017-04-04 21:35:03 UTC
I agree completely with Jeremy: I understand Classic as a Gnome3 desktop with some predefined installed extensions which show a more classical view...but plumb-technology should be the same.
Comment 4 Florian Müllner 2017-11-25 02:26:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/issues/24.

Note You need to log in before you can comment on or make changes to this bug.