Ask Your Question
1

Wayland/Gnome slow - where shall I report it?

asked 2017-07-31 13:24:13 -0600

bouquetbouquet gravatar image

I decided to go all in with Wayland on a new laptop since it had newer components. It's usable, but there's clearly a lot to be done to get it smoothed out. I have a few annoyances and (possibly) bugs to report, but I'm not certain if they're gnome or wayland, or maybe it's Fedora's implementation. Any suggestions where I should report these first few items:

  1. Drawing new windows flashes a black square before the window is drawn.
  2. Compositing features like exposé are choppy, like I'm running this on an ancient computer.
  3. Switching to/from docked setup causes inconsistencies in icon size, scaling, and geometry.

For science:

$ uname -a
Linux figbar.troutpocket.local 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/fedora-release 
Fedora release 26 (Twenty Six)

$ lspci
00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
3a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)
3a:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
3b:00.0 Network controller: Intel Corporation Device 24fb (rev 10)
3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961

I think Mutter version is relevant:
$ rpm -qa | grep mutter
mutter-3.24.4-1.fc26.x86_64
edit retag flag offensive close merge delete

Comments

for the sake of testing, to validate gnome or wayland as possible issues, do the following.

sudo vi /etc/gdm/custom.conf
WaylandEnable=false

Then if gnome is slow, with wayland disabled, you have your answer.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2017-07-31 13:58:07 -0600 )edit

Switching to gnome is WAY faster and smoother. Also, my Keepass auto-type works in gnome-terminal with X11 where no input is entered when using Wayland. I knew this would work better, but I wanted to contribute some usage experience for Wayland to get it off the ground.

bouquetbouquet gravatar imagebouquetbouquet ( 2017-07-31 18:22:07 -0600 )edit

Not sure if wayland will ever get off the ground. I have seen dev talk on nvidia and at other linux forums, the support is dodgy and the drivers, open source and proprietary are having a hard time working, amd, nvidia or other video cards. I need stable 24/7 access to my machine, so I will stay with proprietary. running 384.59 on cinnamon desktop, and it flys.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2017-08-01 09:08:09 -0600 )edit

1 Answer

Sort by » oldest newest most voted
3

answered 2017-08-01 09:05:50 -0600

rdebeasi gravatar image

You could start by looking for existing bugs in Wayland-related issues on GNOME bugzilla. For non-Wayland GNOME bugs, gnome-shell and mutter might be good places to look.

For more detailed information, see How to debug Wayland problems on the Fedora wiki.

As @steveebey73742 mentioned, it would be worth checking whether the problem occurs with Wayland disabled. (You can switch Wayland off by logging out, clicking the cog on the login screen, choosing "Gnome on Xorg", and logging back in.) If a component doesn't work with Wayland, the problem could still be with the component rather than Wayland itself, but it's a good data point to have.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2017-07-31 13:24:13 -0600

Seen: 1,078 times

Last updated: Aug 01 '17