Which log file(s) do you want to see in order to find the information on the disappearance of wayland.
Well, the logs after you’ve logged in would be good for a start. We need to see why it’s using X instead of Wayland. (Wayland hasn’t “disappeared”, but it’s possible that it’s failing to load and is using X as fallback. We need more information before we can diagnose the issue.)
What would be the output of systemctl list-units|grep -E – ‘gdm|sddm|lxdm|lightdm|kdm|xdm’
If you use lightdm, I think you may try with gdm…
https://www.if-not-true-then-false.com/2018/fedora-switch-display-manager/
Here are some logs.
Important:
09:20:34 kernel: pcieport 0000:04:01.0: can’t change power state from D3cold to D0 (config space inaccessible)
09:20:34 kernel: xhci_hcd 0000:3b:00.0: xHCI host controller not responding, assume dead
09:19:52 systemd: Failed to start Tracker metadata database store and lookup manager.
09:19:46 gdm-session-wor: gkr-pam: unable to locate daemon control file
09:19:42 dbus-broker-lau: Activation request for ‘org.a11y.atspi.Registry’ failed.
09:19:42 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
09:19:42 dbus-broker-lau: Activation request for ‘org.a11y.atspi.Registry’ failed.
09:19:38 systemd: Failed to start Network Manager Wait Online.
System:
09:21:21 kernel: nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.
09:20:35 kernel: pci_bus 0000:04: busn_res: [bus 04-3b] is released
09:20:34 kernel: pcieport 0000:04:01.0: can’t change power state from D3cold to D0 (config space inaccessible)
09:20:34 kernel: xhci_hcd 0000:3b:00.0: USB bus 3 deregistered
09:20:34 kernel: usb usb3: USB disconnect, device number 1
09:20:34 kernel: xhci_hcd 0000:3b:00.0: remove, state 4
09:20:34 kernel: usb usb4: USB disconnect, device number 1
09:20:34 kernel: xhci_hcd 0000:3b:00.0: remove, state 4
09:20:34 kernel: pcieport 0000:00:1d.0: pciehp: Slot(8): Card not present
09:19:53 kernel: pci_bus 0000:3b: Allocating resources
09:19:53 kernel: thunderbolt 0000:05:00.0: enabling device (0000 → 0002)
09:19:53 kernel: hub 4-0:1.0: 2 ports detected
09:19:53 kernel: usb usb4: SerialNumber: 0000:3b:00.0
09:19:53 kernel: xhci_hcd 0000:3b:00.0: Host supports USB 3.1 Enhanced SuperSpeed
09:19:53 kernel: hub 3-0:1.0: 2 ports detected
09:19:53 kernel: usb usb3: SerialNumber: 0000:3b:00.0
09:19:53 kernel: xhci_hcd 0000:3b:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
09:19:53 kernel: pci 0000:3b:00.0: enabling device (0000 → 0002)
09:19:53 kernel: pcieport 0000:04:02.0: enabling device (0000 → 0002)
09:19:53 kernel: pci 0000:03:00.0: bridge window [mem 0x2fd0000000-0x2ff1ffffff 64bit pref]
09:19:53 kernel: PCI: No. 2 try to assign unassigned res
09:19:53 kernel: pcieport 0000:00:1d.0: bridge window [mem 0x2fd0000000-0x2ff1ffffff 64bit pref]
09:19:53 kernel: pci 0000:03:00.0: bridge window [mem 0x2fd0000000-0x2ff1ffffff 64bit pref]
09:19:53 kernel: pci_bus 0000:04: busn_res: [bus 04-3b] end is updated to 3b
09:19:53 kernel: pci 0000:04:02.0: bridge window [mem 0x00000000-0x000fffff 64bit pref]
09:19:53 kernel: pci_bus 0000:06: busn_res: [bus 06-3b] end is updated to 3a
09:19:53 kernel: pci 0000:04:01.0: bridge window [mem 0x00000000-0x000fffff 64bit pref]
09:19:53 kernel: pci_bus 0000:05: busn_res: [bus 05-3b] end is updated to 05
09:19:53 kernel: pci 0000:04:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref]
09:19:53 kernel: pcieport 0000:00:1d.0: pciehp: Slot(8): Card present
09:19:50 kernel: rfkill: input handler disabled
09:19:48 kernel: Bluetooth: RFCOMM ver 1.11
09:19:47 kernel: rfkill: input handler enabled
09:19:40 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
09:19:40 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp60s0: link becomes ready
09:19:40 kernel: wlp60s0: Limiting TX power to 37 (40 - 3) dBm as advertised by 60:3a:7c:5c:2c:f0
09:19:35 kernel: iwlwifi 0000:3c:00.0: FW already configured (0) - re-configuring
09:19:34 kernel: Bluetooth: BNEP socket layer initialized
09:19:34 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
09:19:34 kernel: EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
09:19:34 kernel: ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
09:19:34 kernel: EXT4-fs (nvme0n1p8): mounted filesystem with ordered data mode. Opts: (null)
09:19:34 kernel: audit: type=1130 audit(1588987174.033:95): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
09:19:33 kernel: iwlwifi 0000:3c:00.0 wlp60s0: renamed from wlan0
09:19:32 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
09:19:31 kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
09:19:31 kernel: iTCO_vendor_support: vendor-support=0
09:19:31 kernel: intel_rapl_common: Found RAPL domain dram
09:19:30 kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
09:19:29 kernel: audit: type=1130 audit(1588987169.985:86): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=lvm2-monitor comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
09:19:29 kernel: kauditd_printk_skb: 29 callbacks suppressed
09:19:29 kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
09:19:29 kernel: battery: new extension: Huawei Battery Extension
09:19:29 kernel: input: Huawei WMI hotkeys as /devices/platform/huawei-wmi/input/input25
09:19:29 kernel: thermal thermal_zone11: failed to read out thermal zone (-61)
09:19:29 kernel: ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
09:19:29 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input24
09:19:29 kernel: iwlwifi 0000:3c:00.0: base HW address: 38:37:8b:ee:03:bc
09:19:29 kernel: ACPI Warning: _SB.PCI0.RP01.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200110/nsarguments-59)
09:19:29 kernel: iwlwifi 0000:3c:00.0: Allocated 0x00400000 bytes for firmware monitor.
09:19:29 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
09:19:29 kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 440.82 Wed Apr 1 19:41:29 UTC 2020
09:19:29 kernel: nvidia-uvm: Loaded the UVM driver, major device number 511.
09:19:29 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 440.82 Wed Apr 1 20:04:33 UTC 2020
09:19:29 kernel: USB Video Class driver (1.1.1)
09:19:29 kernel: usbcore: registered new interface driver uvcvideo
09:19:29 kernel: input: HD Camera: HD Camera as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input23
09:19:29 kernel: uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized!
09:19:29 kernel: uvcvideo: Found UVC 1.00 device HD Camera (05c8:03c0)
09:19:29 kernel: Bluetooth: hci0: Firmware revision 0.1 build 50 week 12 2019
09:19:29 kernel: usbcore: registered new interface driver btusb
09:19:29 kernel: iwlwifi 0000:3c:00.0: loaded firmware version 36.77d01142.0 8265-36.ucode op_mode iwlmvm
09:19:29 kernel: Copyright(c) 2003- 2015 Intel Corporation
09:19:29 kernel: Intel(R) Wireless WiFi driver for Linux
09:19:29 kernel: Bluetooth: SCO socket layer initialized
09:19:29 kernel: NET: Registered protocol family 31
09:19:29 kernel: Bluetooth: Core ver 2.22
09:19:29 kernel: videodev: Linux video capture interface: v2.00
09:19:29 kernel: cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
09:19:29 kernel: mc: Linux media interface: v0.10
09:19:29 kernel: nvidia 0000:01:00.0: enabling device (0406 → 0407)
09:19:29 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
09:19:29 kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
09:19:29 kernel: Disabling lock debugging due to kernel taint
09:19:29 kernel: nvidia: module license ‘NVIDIA’ taints kernel.
09:19:29 kernel: ipmi device interface
09:19:29 kernel: IPMI message handler: version 39.2
09:19:28 kernel: idma64 idma64.3: Found Intel integrated DMA 64-bit
09:19:27 kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
09:19:27 kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
09:19:27 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
09:19:27 kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
09:19:27 kernel: mei_me 0000:00:16.0: enabling device (0004 → 0006)
09:19:27 kernel: proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
09:19:27 kernel: intel_rapl_common: Found RAPL domain dram
09:19:25 kernel: Started Journal Service.
09:19:25 kernel: Starting udev Wait for Complete Device Initialization…
09:19:25 kernel: Finished udev Coldplug all Devices.
09:19:25 kernel: Starting udev Kernel Device Manager…
09:19:25 kernel: Finished Create Static Device Nodes in /dev.
09:19:25 kernel: Mounted Temporary Directory (/tmp).
09:19:25 kernel: Starting Create Static Device Nodes in /dev…
09:19:25 kernel: Condition check resulted in Create System Users being skipped.
09:19:25 kernel: Starting Apply Kernel Variables…
09:19:25 kernel: Condition check resulted in Rebuild Hardware Database being skipped.
09:19:25 kernel: Mounting Temporary Directory (/tmp)…
09:19:25 kernel: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
09:19:25 kernel: Mounting FUSE Control File System…
09:19:25 kernel: Reached target Swap.
09:19:25 kernel: Finished Repartition Root Disk.
09:19:25 kernel: nfs-convert.service: Succeeded.
09:19:25 kernel: Finished Create list of static device nodes for the current kernel.
09:19:25 kernel: Mounted Kernel Trace File System.
09:19:25 kernel: EXT4-fs (dm-0): re-mounted. Opts: (null)
09:19:25 kernel: Mounted Huge Pages File System.
09:19:25 kernel: Activated swap /dev/mapper/fedora_localhost–live-swap.
09:19:25 kernel: Adding 7815164k swap on /dev/mapper/fedora_localhost–live-swap. Priority:-2 extents:1 across:7815164k SSFS
09:19:25 kernel: sysroot.mount: Succeeded.
09:19:25 kernel: Starting udev Coldplug all Devices…
09:19:25 kernel: Stopped Journal Service.
09:19:25 kernel: Condition check resulted in Set Up Additional Binary Formats being skipped.
09:19:25 kernel: Stopped Plymouth switch root service.
09:19:25 kernel: plymouth-switch-root.service: Succeeded.
09:19:25 kernel: Starting Preprocess NFS configuration convertion…
09:19:25 kernel: Condition check resulted in Load Kernel Module drm being skipped.
09:19:25 kernel: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling…
09:19:25 kernel: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
09:19:25 kernel: Mounting Kernel Trace File System…
09:19:25 kernel: Activating swap /dev/mapper/fedora_localhost–live-swap…
09:19:25 kernel: Listening on User Database Manager Socket.
09:19:25 kernel: Reached target Slices.
09:19:25 kernel: Stopped target Initrd Root File System.
09:19:25 kernel: Reached target Login Prompts.
09:19:25 kernel: Set up automount Arbitrary Executable File Formats File System Automount Point.
09:19:25 kernel: Started Forward Password Requests to Wall Directory Watch.
09:19:25 kernel: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
09:19:25 kernel: Created slice User and Session Slice.
09:19:25 kernel: systemd-journald.service: Scheduled restart job, restart counter is at 1.
09:19:25 kernel: audit: type=1334 audit(1588987165.120:56): prog-id=15 op=UNLOAD
09:19:25 kernel: Stopped Switch Root.
09:19:25 kernel: initrd-switch-root.service: Succeeded.
09:19:25 kernel: audit: type=1131 audit(1588987165.113:55): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-journald comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
09:19:25 kernel: Console: switching to colour frame buffer device 375x125
09:19:25 kernel: fbcon: Taking over console
09:19:25 kernel: /usr/lib/systemd/system/sssd-kcm.socket:7: ListenStream= references a path below legacy directory /var/run/, updating /var/run/.heim_org.h5l.kcm-socket → /run/.heim_org.h5l.kcm-socket; please update the unit file accordingly.
09:19:25 kernel: /usr/lib/systemd/system/sssd.service:13: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; please update the unit file accordingly.
09:19:25 kernel: audit: type=1334 audit(1588987164.901:51): prog-id=14 op=UNLOAD
09:19:25 kernel: Set hostname to .
09:19:25 kernel: Detected architecture x86-64.
09:19:25 kernel: systemd v245.4-1.fc32 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
09:19:25 kernel: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 24.506ms.
09:19:25 kernel: RTC configured in localtime, applying delta of 480 minutes to system time.
09:19:25 kernel: Successfully loaded SELinux policy in 454.845ms.
09:19:25 kernel: audit: type=1403 audit(1589015964.817:47): auid=4294967295 ses=4294967295 lsm=selinux res=1
09:19:25 kernel: kauditd_printk_skb: 36 callbacks suppressed
09:19:25 kernel: SELinux: policy capability nnp_nosuid_transition=1
09:19:25 kernel: Received SIGTERM from PID 1 (systemd).
Here is the output of systemctl list-units | grep gdm,
82: session-c1.scope loaded active running Session c1 of user gdm
106: gdm.service loaded active running GNOME Display Manager
The grepping of other options does not give any output.
You could check /etc/gdm/custom.conf file, make sure the line:
#WaylandEnable=false
have indeed the # to make it a comment
You could activate debug:
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
And I think check the result with:
journalctl -u gdm.service -b 0 -o short-monotonic
for me this gives something like:
[35846.582269] localhost.localdomain gdm-password][10960]: GdmSessionWorker: state SESSION_OPENED [35846.845599] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'LANG=fr_CA.utf8' [35846.845881] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'XDG_CURRENT_DESKTOP=GNOME' [35846.846026] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'GDMSESSION=gnome' [35846.846178] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'GDM_LANG=fr_CA.utf8' [35846.846280] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'DESKTOP_SESSION=gnome' [35846.846401] localhost.localdomain gdm-password][10960]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_DESKTOP=gnome' [35846.846501] localhost.localdomain gdm-password][10960]: GdmSessionWorker: start program: /usr/libexec/gdm-wayland-session "/usr/bin/gnome-session" [35846.846600] localhost.localdomain gdm-password][10960]: GdmSessionWorker: attempting to change state to SESSION_STARTED [35846.846705] localhost.localdomain gdm-password][10960]: GdmSessionWorker: opening user session with program '/usr/libexec/gdm-wayland-session' [35846.846809] localhost.localdomain gdm-password][10960]: GdmSessionWorker: jumping to VT 2
1 Like
Here are the two outputs,
$ more /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
$ journalctl -u gdm.service -b 0 -o short-monotonic
-- Logs begin at Tue 2020-03-24 12:33:39 CST, end at Sat 2020-05-09 11:23:21 CST. --
[ 18.815959] agn systemd[1]: Starting GNOME Display Manager...
[ 18.827714] agn systemd[1]: Started GNOME Display Manager.
[ 27.238665] agn gdm-password][1644]: gkr-pam: unable to locate daemon control file
[ 27.243505] agn gdm-password][1644]: gkr-pam: stashed password to try later in open session
[ 1461.254505] agn gdm-password][3529]: gkr-pam: unable to locate daemon control file
[ 1461.255948] agn gdm-password][3529]: gkr-pam: stashed password to try later in open session
Well, to be usefull, you have to remove the # before Enable=true (I use sudo nano /etc/gdm/custom.conf … put use your favorite editor… maybe gedit)
then log-out, log-in,
then: journalctl -u gdm.service -b 0 -o short-monotonic
1 Like
Here is the output of the command you mentioned:
-- Logs begin at Tue 2020-03-24 12:33:39 CST, end at Sat 2020-05-09 12:02:42 CST. --
[ 18.452701] agn systemd[1]: Starting GNOME Display Manager...
[ 18.466020] agn gdm[1188]: Enabling debugging
[ 18.467749] agn gdm[1188]: Changing user:group to gdm:gdm
[ 18.470073] agn systemd[1]: Started GNOME Display Manager.
[ 18.471941] agn gdm[1188]: Successfully connected to D-Bus
[ 18.472031] agn gdm[1188]: GdmManager: GDM starting to manage displays
[ 18.472104] agn gdm[1188]: GLib: posix_spawn avoided (fd close requested)
[ 18.474468] agn gdm[1188]: GLib: posix_spawn avoided (fd close requested)
[ 18.496763] agn gdm[1188]: GdmLocalDisplayFactory: enumerating seats from logind
[ 18.497419] agn gdm[1188]: GdmLocalDisplayFactory: X11 login display for seat seat0 requested
[ 18.497527] agn gdm[1188]: GdmLocalDisplayFactory: Adding display on seat seat0
[ 18.497621] agn gdm[1188]: GdmDisplay: id: (null)
[ 18.497677] agn gdm[1188]: GdmDisplay: seat id: (null)
[ 18.497727] agn gdm[1188]: GdmDisplay: session class: greeter
[ 18.497784] agn gdm[1188]: GdmDisplay: initial: no
[ 18.497856] agn gdm[1188]: GdmDisplay: allow timed login: yes
[ 18.497911] agn gdm[1188]: GdmDisplay: local: yes
[ 18.497967] agn gdm[1188]: GdmDisplay: seat id: seat0
[ 18.498025] agn gdm[1188]: GdmDisplay: initial: yes
[ 18.498087] agn gdm[1188]: GdmDisplayStore: Adding display /org/gnome/DisplayManager/Displays/93940827195872 to store
[ 18.498149] agn gdm[1188]: GdmDisplay: Managing display: /org/gnome/DisplayManager/Displays/93940827195872
[ 18.498202] agn gdm[1188]: GdmDisplay: Preparing display: /org/gnome/DisplayManager/Displays/93940827195872
[ 18.500131] agn gdm[1188]: GdmDisplay: Checking kernel command buffer BOOT_IMAGE=(hd0,gpt8)/vmlinuz-5.6.10-300.fc32.x86_64 root=/dev/mapper/fedora_localhost--liv>
[ 18.500252] agn gdm[1188]: GdmDisplay: Failed to read kernel commandline: Could not match gnome.initial-setup= in kernel cmdline
[ 18.500311] agn gdm[1188]: doing initial setup? no
[ 18.500378] agn gdm[1188]: GdmDisplay: prepare display
[ 18.500432] agn gdm[1188]: GdmDisplay: Got automatic login details for display: 0
[ 18.500487] agn gdm[1188]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
[ 18.500550] agn gdm[1188]: GdmSession: Creating D-Bus server for worker for session
[ 18.500786] agn gdm[1188]: GdmSession: D-Bus server for workers listening on unix:abstract=/tmp/dbus-NHg2rvgD
[ 18.500852] agn gdm[1188]: GdmSession: Creating D-Bus server for greeters and such for session (null) (0x55704da3f000)
[ 18.500940] agn gdm[1188]: GdmSession: D-Bus server for greeters listening on unix:abstract=/tmp/dbus-hKPO3Gem
[ 18.501002] agn gdm[1188]: GdmSession: Setting display device: (null)
[ 18.501052] agn gdm[1188]: GdmSession: Created user session for user 42 on display /org/gnome/DisplayManager/Displays/93940827195872 (seat seat0)
[ 18.501107] agn gdm[1188]: GdmDisplay: Running greeter
[ 18.501167] agn gdm[1188]: GdmDisplay: Creating greeter for (null) (null)
[ 18.501224] agn gdm[1188]: GdmLaunchEnvironment: Starting...
[ 18.501285] agn gdm[1188]: GdmLaunchEnvironment: Setting up run time dir /run/gdm/greeter
[ 18.501340] agn gdm[1188]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created
[ 18.501392] agn gdm[1188]: GdmSession: Creating D-Bus server for worker for session
[ 18.501447] agn gdm[1188]: GdmSession: D-Bus server for workers listening on unix:abstract=/tmp/dbus-4o9sQQMa
[ 18.501503] agn gdm[1188]: GdmSession: Creating D-Bus server for greeters and such for session (null) (0x55704da3f120)
[ 18.501559] agn gdm[1188]: GdmSession: D-Bus server for greeters listening on unix:abstract=/tmp/dbus-PJH10eEG
[ 18.501608] agn gdm[1188]: GdmSession: Setting display device: (null)
[ 18.501667] agn gdm[1188]: GdmSession: starting conversation gdm-launch-environment for session (0x55704da3f120)
[ 18.501746] agn gdm[1188]: GdmSessionWorkerJob: Starting worker...
The total output is more than 400 lines. I copied here only the first tens of lines.
1 Like
It does not seems to contains the interesting part.
I suggest you do:
journalctl -u gdm.service -b 0 -o short-monotonic --no-pager | fpaste
that will send it to a web server for 24 hours… and will generate a link you can copy here.
1 Like
I did as you suggested.
$ $ journalctl -u gdm.service -b 0 -o short-monotonic --no-pager | fpaste
Uploading (51.7KiB)...
https://paste.centos.org/view/07d32f1a
2 Likes
hum… you have:
XDG_CURRENT_DESKTOP=GNOME-Greeter:GNOME
where I have:
XDG_CURRENT_DESKTOP=GNOME
I should try to understand why…
Oh well ok, later you have:
[ 30.895823] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'LANG=zh_CN.UTF-8'
[ 30.895903] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'XDG_CURRENT_DESKTOP=GNOME'
[ 30.895951] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'GDMSESSION=gnome'
[ 30.895995] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'GDM_LANG=zh_CN.UTF-8'
[ 30.896036] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'DESKTOP_SESSION=gnome'
[ 30.896077] agn gdm-password][1646]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_DESKTOP=gnome'
[ 30.896112] agn gdm-password][1646]: GdmSessionWorker: start program: /usr/libexec/gdm-x-session --run-script "/usr/bin/gnome-session"
[ 30.896162] agn gdm-password][1646]: GdmSessionWorker: attempting to change state to SESSION_STARTED
[ 30.896210] agn gdm-password][1646]: GdmSessionWorker: opening user session with program '/usr/libexec/gdm-x-session'
[ 30.896247] agn gdm-password][1646]: GdmSessionWorker: jumping to VT 2
which shows that indeed X is started… but not really explains why… still studying it
1 Like
OK. Thank you very much!
I am now reading:
https://wiki.archlinux.org/index.php/GDM#Wayland_and_the_proprietary_NVIDIA_driver
it seems we do have the same files in Fedora, so that:
ln -s /dev/null /usr/lib/udev/rules.d/61-gdm.rules
could probably works… but…
eh… I feel a bit dumb about the way it deactivate it… is there someone who can explain this?
Tried it and got:
[paul@localhost rules.d]$ LANG=C ln -s /dev/null /usr/lib/udev/rules.d/61-gdm.rules
ln: failed to create symbolic link ‘/usr/lib/udev/rules.d/61-gdm.rules’: File exists
which make sense to me…
[paul@localhost rules.d]$ more 61-gdm.rules
# disable Wayland on Hi1710 chipsets ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/libexec/gdm-disable-w ayland" # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/libexec/gdm-disable-wayland" # disable Wayland if modesetting is disabled IMPORT{cmdline}="nomodeset", RUN+="/usr/libexec/gdm-disable-wayland" [paul@localhost rules.d]$I would suggest to just add a # in front of the
DRIVER==“nvidia”, RUN+="/usr/libexec/gdm-disable-wayland"line.
Or maybe accept not using Wayland… or not use proprietary nvidia drivers…
Here is where it was decided to deactivate Wayland with GDM with Nvidia proprietary drivers: data: disable wayland for proprietary nvidia machines (!46) · Merge requests · GNOME / gdm · GitLab
You should probably edit again /etc/gdm/custom.conf and put back the # before the
Enable=true of the [debug] section.
2 Likes
now the question is:
Does your games working well under Wayland (with GDM)?
I am unsure if window-mode would be more afffected.
I don’t play games.
I have a laptop with hybrid graphic cards, one is Nvidia MX150, the other is the Inter on-board card. I installed the Nvidia driver from rpmfusion to reduce power consumption. The nouveau driver of F32 made the screen frozen after login. So I just removed it.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.