Created attachment 9852 [details] Xorg.0.log See attached Xorg.0.log Downgrading to 1.19.5-2.mga7 fixes the problem. That version is still available atm on this mirror: https://mageia.unige.ch/mirror/distrib/cauldron/ [root@R50e marja]# lspcidrake -v | grep Card SMBIOS version fixup (2.33 -> 2.3). Card:Intel 810 and later: Intel Corporation|82852/855GM Integrated Graphics Device [DISPLAY_OTHER] (vendor:8086 device:3582 subv:1014 subd:0562) (rev: 02) yenta_socket : Texas Instruments|PCI1510 PC card Cardbus Controller [BRIDGE_CARDBUS] (vendor:104c device:ac56 subv:3000 subd:0000) Card:Intel 810 and later: Intel Corporation|82852/855GM Integrated Graphics Device [DISPLAY_VGA] (vendor:8086 device:3582 subv:1014 subd:0562) (rev: 02) [root@R50e marja]# I'll try downgrading on another, but 64bit, laptop with another Intel 810 and later Card, too, because since a few days no DMs apart from GDM, and no DEs apart from Gnome (Wayland) work, to see whether it has the same problem with new x11-server.
Created attachment 9853 [details] xorg.conf xorg.conf
Downgrading to v. 1.19.5-2.mga7 fixes the issue on a ThinkPad SL510, too.
Hardware: i586 => AllSource RPM: (none) => x11-server-1.19.6-1.mga7
Can you check the logs in /var/log/Xorg.0.log when running the broken X server so we can see what fails ?
CC: (none) => tmb
(In reply to Thomas Backlund from comment #3) > Can you check the logs in /var/log/Xorg.0.log when running the broken X > server so we can see what fails ? I attached it, see attachment #9852 [details] : [ 79.750] (EE) [ 79.750] (EE) Backtrace: [ 79.750] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x122) [0x81ddaf2] [ 79.751] (EE) 1: ? (?+0x122) [0xb7f94e11] [ 79.752] (EE) 2: ? (?+0x122) [0xb7f94df2] [ 79.753] (EE) 3: /lib/i686/libc.so.6 (gsignal+0x46) [0xb78a9c26] [ 79.753] (EE) 4: /lib/i686/libc.so.6 (abort+0x18b) [0xb78ab50b] [ 79.754] (EE) 5: /lib/i686/libc.so.6 (__assert_fail_base+0x12d) [0xb78a257d] [ 79.755] (EE) 6: /lib/i686/libc.so.6 (__assert_fail+0x3b) [0xb78a25db] [ 79.755] (EE) 7: /usr/libexec/Xorg (_init+0x1f7d) [0x8064b4f] [ 79.755] (EE) 8: /usr/libexec/Xorg (compIsAlternateVisual+0x90) [0x81077f0] [ 79.756] (EE) 9: /usr/lib/xorg/modules/extensions/libglx.so (GlxSetVisualConfigs+0x1ff) [0xb755fd3f] [ 79.756] (EE) 10: /usr/lib/xorg/modules/extensions/libglx.so (GlxSetVisualConfigs+0x755a) [0xb756e20a] [ 79.757] (EE) 11: /usr/lib/xorg/modules/extensions/libglx.so (_init+0x1d0a6) [0xb757b616] [ 79.757] (EE) 12: /usr/libexec/Xorg (InitExtensions+0x4b) [0x80eb89b] [ 79.757] (EE) 13: /usr/libexec/Xorg (InitFonts+0x2b0) [0x807aa50] [ 79.758] (EE) 14: /usr/libexec/Xorg (miPolyFillRect+0x278) [0x8064ee8] [ 79.758] (EE) 15: /lib/i686/libc.so.6 (__libc_start_main+0xf3) [0xb7896433] [ 79.759] (EE) 16: /usr/libexec/Xorg (_start+0x21) [0x8064ce9] [ 79.759] (EE) [ 79.759] (EE) Fatal server error: [ 79.759] (EE) Caught signal 6 (Aborted). Server aborting [ 79.759] (EE) [ 79.759] (EE) Please consult the Mageia support at https://bugs.mageia.org for help. [ 79.759] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 79.759] (EE) [ 79.804] (EE) Server terminated with error (1). Closing log file.
Oops, sorry... I read too quickly and only saw the xorg.conf
(In reply to Thomas Backlund from comment #5) > Oops, sorry... I read too quickly and only saw the xorg.conf No problem, glad you're human :-)
(In reply to Marja van Waes from comment #4) > > [ 79.750] (EE) > [ 79.750] (EE) Backtrace: > [ 79.750] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x122) [0x81ddaf2] > [ 79.751] (EE) 1: ? (?+0x122) [0xb7f94e11] Someone reported something similar, some time ago, after updating to mesa-17.2.0 https://bugs.archlinux.org/task/55551 In his case, downgrading mesa solved the issue. I haven't tried to downgrade mesa instead of x11-server, but am pretty sure I updated them at the same time. Is it possible at all that mesa-17.3.1-1.mga7 is the culprit instead of x11-server? I have two less old laptops with "Intel 810 and later" Cards on which I haven't yet tried new x11-server (but i did update mesa on them). Is it important to know whether this issue is valid for them, too?
(In reply to Marja van Waes from comment #7) > (In reply to Marja van Waes from comment #4) > > > > > [ 79.750] (EE) > > [ 79.750] (EE) Backtrace: > > [ 79.750] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x122) [0x81ddaf2] > > [ 79.751] (EE) 1: ? (?+0x122) [0xb7f94e11] > > Someone reported something similar, some time ago, after updating to > mesa-17.2.0 > https://bugs.archlinux.org/task/55551 > In his case, downgrading mesa solved the issue. > The fix in that bug is in 17.3 > I haven't tried to downgrade mesa instead of x11-server, but am pretty sure > I updated them at the same time. > rpm -qa --last |less will tell you... > Is it possible at all that mesa-17.3.1-1.mga7 is the culprit instead of > x11-server? > Yes. > I have two less old laptops with "Intel 810 and later" Cards on which I > haven't yet tried new x11-server (but i did update mesa on them). Is it > important to know whether this issue is valid for them, too? Would be nice to know if this is a single problem or a widespread one, yes.
The less old ThinkPads (T440 and T420) don't suffer from this bug. Only two older ThinkPads (SL510 an R50e) have it About mesa: On the R50e, I updated x11-server-common-1.19.5-2.mga7.i586 x11-server-xorg-1.19.5-2.mga7.i586 and x11-server-xwayland-1.19.5-2.mga7.i586 to version 1.19.6-1.mga7.i586 again and noticed, after reboot, that Xorg X still crashed immediately. Then I downgraded mesa etc. from v. 17.3.1-1.mga7.i586 to: libdri-drivers-17.3.0-1.mga7.i586 libmesaegl1-17.3.0-1.mga7.i586 libmesaegl1-devel-17.3.0-1.mga7.i586 libmesagl1-17.3.0-1.mga7.i586 libmesagl1-devel-17.3.0-1.mga7.i586 mesa-17.3.0-1.mga7.i586 after reboot, X still didn't work, so the mesa version doesn't matter.
Is this still an issue with: x11-server-1.19.6-3.mga7 x11-driver-video-intel-2.99.917-42.mga7 mesa-17.3.2-2.mga7 ?
Created attachment 9905 [details] Xorg.0.log of the crash with x11-server-1.19.6-3 (In reply to Thomas Backlund from comment #10) > Is this still an issue with: > > x11-server-1.19.6-3.mga7 > x11-driver-video-intel-2.99.917-42.mga7 > mesa-17.3.2-2.mga7 > > ? On the oldest system, using libmesaegl1-devel-17.3.2-2.mga7 libmesaegl1-17.3.2-2.mga7 libmesagl1-devel-17.3.2-2.mga7 mesa-17.3.2-2.mga7 libmesagl1-17.3.2-2.mga7 and x11-driver-video-intel-2.99.917-42.mga7 isn't a problem *but* using the x11-server-1.19.6-3 packages is, Xorg.log still shows the same (same afaics) backtrace. Downgrading to 1.19.5-2.mga7 fixes the problem again.
Attachment 9852 is obsolete: 0 => 1
I'll test whether it is better on the other system that had this issue.
Summary: x11-server-1.19.6-1.mga7 crashes Xorg (Intel 810 and later Card) => x11-server-1.19.6-3.mga7 crashes Xorg (Intel 810 and later Card)Source RPM: x11-server-1.19.6-1.mga7 => x11-server-1.19.6-3.mga7
It didn't get solved for the other laptop, either, sorry.
On the R50e, after updating many x11 packages to the version from updates_testing, Xorg no longer crashes. Among the updates were: x11-server-common-1.19.99.901-1.mga7 x11-server-xorg-1.19.99.901-1.mga7 and x11-driver-video-intel-2.99.917-43.mga7 I'll update the other affected laptop tomorrow.
On the other laptop, too, all our x11-server-1.19.6 releases did crash Xorg. With x11-server-1.19.99.901, retrieved when updating all x11 packages from Cauldron core/updates_testing, the problem is gone :-)
Summary: x11-server-1.19.6-3.mga7 crashes Xorg (Intel 810 and later Card) => x11-server-1.19.6 crashes Xorg (Intel 810 and later Card), x11-server-1.19.99.901 fixes the problem.Source RPM: x11-server-1.19.6-3.mga7 => x11-server-1.19.6-5.mga7Resolution: (none) => FIXEDStatus: NEW => RESOLVED