Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#56136 - gdm starts as xsession but restart of gdm launches a wayland session
Attached to Project:
Arch Linux
Opened by Michael Pusterhofer (feanor12) - Friday, 27 October 2017, 09:29 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 01 November 2017, 05:18 GMT
Opened by Michael Pusterhofer (feanor12) - Friday, 27 October 2017, 09:29 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 01 November 2017, 05:18 GMT
|
DetailsDescription:
When I boot and look at the started gdm it is running on a xsession. When restarting gdm via CTRL+ALT+F2 -> "systemctl restart gdm" it starts as wayland session. I think there may be a missing dependency in systemd, because on normal startups I see Okt 27 11:15:45 michael-arch systemd[1]: Started GNOME Display Manager. Okt 27 11:15:46 michael-arch gdm[371]: GdmDisplay: display lasted 0,524233 seconds Okt 27 11:15:46 michael-arch gdm[371]: Child process -450 was already dead. Okt 27 11:15:46 michael-arch gdm[371]: Child process 437 was already dead. Okt 27 11:15:46 michael-arch gdm[371]: Unable to kill session worker process Additional info: gdm: 3.26.1-1 systemd: 235.8-1 |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 01 November 2017, 05:18 GMT
Reason for closing: Fixed
Additional comments about closing: Gdm 3.26.2.1
Wednesday, 01 November 2017, 05:18 GMT
Reason for closing: Fixed
Additional comments about closing: Gdm 3.26.2.1
Probably some timing issue, KMS graphics driver loading after wayland is started for example.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
mesa: 17.2.3-1
I have xf86-video-amdgpu:1.4.0-1 and xf86-video-ati:1:7.10.0-1 installed. I think radeonsi is used. How do I check this?
➜ ~ dmesg|grep modesetting
[ 4.748940] [drm] radeon kernel modesetting enabled.
[ 4.763282] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x1462:0x2733 0x00).
[ 7.247128] [drm] amdgpu kernel modesetting enabled.
I have:
$ lspci -k | grep -i -A 2 -E "(display|vga|3d)"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
Subsystem: Gigabyte Technology Co., Ltd Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
Kernel driver in use: amdgpu
With Mesa, not AMDGPU-PRO.
lspci -k | grep -i -A 2 -E "(display|vga|3d)"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Subsystem: Micro-Star International Co., Ltd. [MSI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Kernel driver in use: radeon