Having trouble with Gnome wayland


I have very less idea about display managers. I have Nvidia proprietary card. But gnome wayland doesn’t play so well with it I think. I face issues like, screen recorders like SImple Screen recorder or Kazam not working properly, Blank screen after recording. After logging using Xorg, all the issue are solved. I just wanted to know, should I continue using Gnome xorg? I just don’t any issues with my desktop. My full system details are given below:

Machine:   Type: Laptop System: HP product: HP ProBook 450 G5 v: N/A serial: <superuser/root required> 
           Mobo: HP model: 837D v: KBC Version 02.3D.00 serial: <superuser/root required> UEFI: HP v: Q85 Ver. 01.11.01 
           date: 04/27/2020 
Battery:   ID-1: BAT0 charge: 33.1 Wh condition: 41.9/41.9 Wh (100%) 
CPU:       Info: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP L2 cache: 6144 KiB 
           Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 799 2: 802 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel 
           Device-2: NVIDIA GM108M [GeForce 930MX] driver: nvidia v: 455.45.01 
           Device-3: Chicony HP HD Camera type: USB driver: uvcvideo 
           Display: x11 server: X.org 1.20.9 driver: modesetting resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.2.3 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.4.80-2-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: enp2s0 state: down mac: 10:e7:c6:dc:e7:16 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
           IF: wlp3s0 state: up mac: 74:e5:f9:06:7a:7f 
Drives:    Local Storage: total: 1.02 TiB used: 9.81 GiB (0.9%) 
           ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB 
           ID-2: /dev/sdb vendor: HP model: SSD S700 120GB size: 111.79 GiB 
Partition: ID-1: / size: 109.24 GiB used: 9.80 GiB (9.0%) fs: ext4 dev: /dev/sdb2 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 0.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 256 Uptime: 1h 18m Memory: 15.07 GiB used: 1.98 GiB (13.2%) Shell: Zsh inxi: 3.1.08```

could I suggest you to wrap your system information with triple ``` symbols in both ends instead of single? Not an expert opinion, but when Xorg version works, then why even bother with trying to get it to work with Wayland? I would stick to what works :slight_smile: (unless ofc you need the other one for some specific reason).

1 Like

Sorry, but I don’t have much idea how to post code on forum, that’s why I messed up.

Yes, xorg works perfectly, and I am using it right now. But I am curious, why the default session starts with wayland if it has so many issues?

:man_shrugging:t2: because they want bigger adoption? if people fail to use “some software” in Wayland, they hope it puts some more pressure on devs of said “some software” to make it Wayland compatible (faster)? Then again it makes Gnome itself look bad when everything doesn’t work out of the box. I have no idea, what are they thinking :smiley:

1 Like

If you didn’t enable it explicitly, that shouldn’t be the case. The /lib/udev/rules.d/61-gdm.rules udev rule should disable the Wayland session for GDM+GNOME if the nvidia driver is loaded.

1 Like