Arch Linux

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!
Tasklist

FS#56167 - [gdm] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by Khar Tahk (khartahk) - Monday, 30 October 2017, 17:26 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 31 October 2017, 20:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

Description:
After an upgrade to 3.26.2-1 I can't login. It stops at terminal right before login screen should launch.

Additional info:
* version: 3.26.2-1


Steps to reproduce:
- upgrade from gdm-3.26.1-1 to gdm-3.26.2-1
- restart computer
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 31 October 2017, 20:48 GMT
Reason for closing:  Fixed
Comment by Kerr (zefkerrigan) - Monday, 30 October 2017, 18:00 GMT
I have the same problem. Only the GNOME Xorg session works. GNOME Wayland does not work anymore.
Comment by Kerr (zefkerrigan) - Monday, 30 October 2017, 18:09 GMT
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.
Comment by Christopher Brown (brownch) - Monday, 30 October 2017, 18:20 GMT
I have the same issue, using the NVIDIA driver with a GTX 1080. I get the same non-responsive blank screen with Wayland or Xorg. I wish I had some useful debug info, but for the life of me I couldn't find anything in any log anywhere, even with debug enabled. Anyway, I downgraded back to the 3.26.1-1 package and all is well again.
Comment by Lauri Koskela (luryus) - Monday, 30 October 2017, 18:37 GMT
I'm having the same issue. Logs attached.

Starting gdm prints "Failed to create backend: Unable to open display, DISPLAY not set" which does not happen after downgrading back to 3.26.1-1.
   gdm_logs.txt (13.2 KiB)
Comment by Khar Tahk (khartahk) - Monday, 30 October 2017, 19:12 GMT
I have an intel graphics:
lspci -k | grep -i -A 2 -E "(display|vga|3d)"
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller
Kernel driver in use: i915
P.S.
Can someone change the title to: after upgrading to 3.26.2-1 gdm stops before showing the log-in screen
I can't find any way to edit my original bug report.
Comment by Erick Will (erickwill) - Monday, 30 October 2017, 19:42 GMT
Same problem here, almost the same hardware spec as well.
Comment by Dillen Meijboom (dmeijboom) - Monday, 30 October 2017, 20:42 GMT
I have the same problem. Downgrading to 3.26.1-1 fixed it. I've forced GDM to use X-server instead of Wayland. Also, I saw some X-server error saying that there is no such display 0 or something.

Loading...