Before, I also tried the the recipe on https://dev1galaxy.org/viewtopic.php?pid=36120 (building locally and installing mesa-amber) but that did not fix the problem. Now I wonder wether I should undo that, and the best way for doing it (dpkg -r ... for all the 6 packages plus the dependencies they installed plus removing build-essential devscripts which I normally don't use).

#1: Laptop's default configuration. Result: Xorg consistently crashes when visiting certain webpages using chromium-based web browsers.

$ inxi -Gx
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Sony driver: i915
    v: kernel arch: Gen-5.75 bus-ID: 00:02.0
  Device-2: Microdia Webcam type: USB driver: uvcvideo bus-ID: 1-1.2:3
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK)
    direct-render: Yes

#2: Workaround using nomodeset kernel boot parameter. Result: No Xorg crashes at the price of an inactive GPU.

$ inxi -Gx
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Sony driver: N/A
    arch: Gen-5.75 bus-ID: 00:02.0
  Device-2: Microdia Webcam type: USB driver: uvcvideo bus-ID: 1-1.2:3
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vesa
    unloaded: fbdev,modesetting dri: swrast gpu: N/A resolution: 1366x768
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits)
    direct-render: Yes

#3: Current configuration, achieved with /usr/share/X11/xorg.conf.d/09-force-intel-driver.conf and no special kernel boot parameters. Result: No Xorg crashes, GPU is active.

$ inxi -Gx
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Sony driver: i915
    v: kernel arch: Gen-5.75 bus-ID: 00:02.0
  Device-2: Microdia Webcam type: USB driver: uvcvideo bus-ID: 1-1.2:3
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: intel
    dri: crocus gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK)
    direct-render: Yes

Other than this one strange issue on this one laptop, upgrade from Chimaera to Daedalus was smooth for all my machines. Thank you, Devuan team!

Happy hacking!

In short: screen numbers start at 0.

Maybe so, but the affected laptop only has one (built-in) screen and the config file has no effect unless I use Device1.

Reading your post I vaguely recalled a similar issue (many) years ago when I was attempting to go from a single screen layout to a two (and then three) screen layout.

I was trying to get a manually configured xorg.conf file to work but had started the screen numbering at 1 instead of at 0.   

Once I got it to work I never had to look at it again: I have used the same *.conf file with the same hardware through at least four different distributions and now with Devuan since Jesse.

See Device Section here: https://www.x.org/releases/current/doc/ … #heading10

In short: screen numbers start at 0.

Best,

A.

If all of these are true for you:

1. You are experiencing seemingly random Xorg crashes (e.g., while using a chromium-based web browser such as Brave or Chrome) after upgrading to Daedalus

2. After an Xorg crash, /var/log/Xorg.0.log.old shows Fatal server error: (EE) GLSL compile failure

3. Your machine has 5th generation Intel integrated graphics (use inxi -Gx to find out. In my case, command output shows arch: Gen-5.75)

Then try creating /usr/share/X11/xorg.conf.d/09-force-intel-driver.conf with this in it (you may have to change Device1 to Device0):

Section "Device"
	Identifier "Device1"
	Driver "intel"
EndSection

and then reboot. In my case, all Xorg crashes went away.

I hope this helps someone with the same issue.

----------

Some additional details:

In my case, crashes could be reliably triggered by visiting certain product pages on amazon.com while using Brave or Chrome browser (e.g., "Risk: Lord of the Rings Trilogy edition"). Disabling "Use hardware acceleration when available" in the browser did not help. Building, installing, and using mesa-amber as described in this post did not help. Using nomodeset kernel boot parameter does make the crashes go away, but seemingly at the expense of disabling the GPU and losing hardware graphics acceleration.

Here is what I see at the end of /var/log/Xorg.0.log.old after a crash:

vec2 rel_tex_coord(vec2 texture, vec4 wh, int repeat) 
{
	vec2 rel_tex; 
	rel_tex = texture * wh.xy; 
	if (repeat == RepeatFix + RepeatNone)
		return rel_tex; 
	else if (repeat == RepeatFix + RepeatNormal) 
		rel_tex = floor(rel_tex) + (fract(rel_tex) / wh.xy); 
	else if (repeat == RepeatFix + RepeatPad) { 
		if (rel_tex.x >= 1.0) 
			rel_tex.x = 1.0 - wh.z * wh.x / 2.; 
		else if (rel_tex.x < 0.0) 
			rel_tex.x = 0.0; 
		if (rel_tex.y >= 1.0) 
			rel_tex.y = 1.0 - wh.w * wh.y / 2.; 
		else if (rel_tex.y < 0.0) 
			rel_tex.y = 0.0; 
		rel_tex = rel_tex / wh.xy; 
	} else if (repeat == RepeatFix + RepeatReflect) {
		if ((1.0 - mod(abs(floor(rel_tex.x)), 2.0)) < 0.001)
[    63.908] (EE) 
Fatal server error:
[    63.908] (EE) GLSL compile failure
[    63.908] (EE) 
[    63.908] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    63.909] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    63.909] (EE) 
[    63.909] (II) AIGLX: Suspending AIGLX clients for VT switch
[    63.968] (EE) Server terminated with error (1). Closing log file.

P.S. My other laptop, which has integrated Intel graphics Gen-7, is not affected by this problem.