Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. 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#64010 - [mesa/libglvnd] X refuses to start after upgrading to mesa 19.2.0 / libglvnd 1.2.0

Attached to Project: Arch Linux
Opened by Boudhayan Gupta (baloneygeek) - Thursday, 03 October 2019, 23:22 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 13 October 2019, 13:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

I have Intel graphics on my laptop (lspci: VGA compatible controller: Intel Corporation HD Graphics 5500). After doing a system update, X refuses to start. My Xorg.0.log is attached.

Downgrading mesa to 19.1.7-1 and libglvnd to 1.1.1-1 makes X start up again.

The issue seems to be the same as described in this BBS post: https://bbs.archlinux.org/viewtopic.php?id=249639

This task depends upon

Closed by  Jelle van der Waa (jelly)
Sunday, 13 October 2019, 13:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in mesa-19.2.1
Comment by Boudhayan Gupta (baloneygeek) - Thursday, 03 October 2019, 23:33 GMT Comment by kursu (kursu) - Friday, 04 October 2019, 01:32 GMT
Tried with xf86-video-intel driver?
Comment by Nick Boughton (tiberiouse) - Friday, 04 October 2019, 09:14 GMT
I have the same problem and the xf86-video-intel-driver installed. My xorg log is attached. Oddly this bug does not manifest on my other laptop that also has an intel graphics card. The system where the bug occurs has the following hardware:

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)

The bug occurs with both the stock Arch kernel and the Arch-zen kernel. My other laptop has a skylake chipset and works fine.
Comment by loqs (loqs) - Saturday, 05 October 2019, 18:13 GMT Comment by Manifest0 (Manifest0) - Sunday, 06 October 2019, 13:33 GMT
I'm also having this issue.
Comment by Alexandr (Stezko) - Tuesday, 08 October 2019, 13:16 GMT
Not fixed.
Checked versions: mesa 19.2.0-2 and 19.2.0-3 libglvnd 1.2.0-1

(EE) 0: /usr/lib/Xorg (xorg_backtrace+0x4d) [0x55c3b478269d]
(EE) 1: /usr/lib/Xorg (0x55c3b46d0000+0xa8be8) [0x55c3b4778be8]
(EE) 2: /usr/lib/libc.so.6 (0x7f8657f5c000+0x3a7e0) [0x7f8657f967e0]
(EE) 3: /usr/lib/dri/i965_dri.so (0x7f8655b9e000+0x619f4e) [0x7f86561b7f4e]
(EE) 4: /usr/lib/dri/i965_dri.so (0x7f8655b9e000+0x61d3a4) [0x7f86561bb3a4]
(EE) 5: /usr/lib/dri/i965_dri.so (0x7f8655b9e000+0x111ca7) [0x7f8655cafca7]
(EE) 6: /usr/lib/dri/i965_dri.so (0x7f8655b9e000+0x1801ff) [0x7f8655d1e1ff]
(EE) 7: /usr/lib/xorg/modules/extensions/libglx.so (0x7f8656db0000+0x2dace) [0x7f8656dddace]
(EE) 8: /usr/lib/xorg/modules/extensions/libglx.so (0x7f8656db0000+0x11877) [0x7f8656dc1877]
(EE) 9: /usr/lib/Xorg (_CallCallbacks+0x34) [0x55c3b483d644]
(EE) 10: /usr/lib/Xorg (0x55c3b46d0000+0x9dc53) [0x55c3b476dc53]
(EE) 11: /usr/lib/Xorg (InitExtensions+0x89) [0x55c3b487a8b9]
(EE) 12: /usr/lib/Xorg (0x55c3b46d0000+0x37526) [0x55c3b4707526]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0x7f8657f82ee3]
(EE) 14: /usr/lib/Xorg (_start+0x2e) [0x55c3b47083be]
(EE) Floating point exception at address 0x7f86561b7f4e
Fatal server error:
(EE) Caught signal 8 (Floating point exception). Server aborting

Comment by Alexandr (Stezko) - Thursday, 10 October 2019, 14:02 GMT
Who checked 19.2.1 for the presence of this error?
Comment by Boudhayan Gupta (baloneygeek) - Thursday, 10 October 2019, 18:14 GMT
Confirmed fixed using the 19.2.1 package from testing.
Comment by Clément Cazaud (clem) - Friday, 11 October 2019, 13:03 GMT
mesa-19.2.1-1 with libglvnd-1.2.0-2 doesn't fix the issue in my case.

Loading...