clearlinux / distribution

Placeholder repository to allow filing of general bugs/issues/etc against the Clear Linux OS for Intel Architecture linux distribution
524 stars 29 forks source link

39420: Xorg segmentation fault #2912

Open sebastiencs opened 1 year ago

sebastiencs commented 1 year ago

I've just updated Clearlinux to 39420, and Xorg refuses to start with this error:

[  1533.842] (EE) 
[  1533.842] (EE) Backtrace:
[  1533.842] (EE) 0: /usr/bin/X (xorg_backtrace+0x47) [0x56015cbe6f27]
[  1533.842] (EE) 1: /usr/bin/X (0x56015ca82000+0x168df9) [0x56015cbeadf9]
[  1533.842] (EE) 2: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (0x56015bfed000+0x3c720) [0x56015c029720]
[  1533.842] (EE) 3: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0x1346df0) [0x560159dd2df0]
[  1533.842] (EE) 4: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0x135c4ef) [0x560159de84ef]
[  1533.842] (EE) 5: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0xb8018) [0x560158b44018]
[  1533.842] (EE) 6: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0xb8bb5) [0x560158b44bb5]
[  1533.842] (EE) 7: /usr/lib64/libgbm.so.1 (0x56015b1fc000+0x620a) [0x56015b20220a]
[  1533.842] (EE) 8: /usr/lib64/xorg/modules/libglamoregl.so (glamor_back_pixmap_from_fd+0xdf) [0x56015b16353f]
[  1533.842] (EE) 9: /usr/lib64/xorg/modules/libglamoregl.so (glamor_egl_create_textured_pixmap+0x70) [0x56015b163620]
[  1533.842] (EE) 10: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0x56015ca62000+0x14285) [0x56015ca76285]
[  1533.842] (EE) 11: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0x56015ca62000+0x8e08) [0x56015ca6ae08]
[  1533.842] (EE) 12: /usr/bin/X (0x56015ca82000+0xbce8e) [0x56015cb3ee8e]
[  1533.842] (EE) 13: /usr/bin/X (InitRootWindow+0x11) [0x56015cb35171]
[  1533.842] (EE) 14: /usr/bin/X (0x56015ca82000+0x863bc) [0x56015cb083bc]
[  1533.842] (EE) 15: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (0x56015bfed000+0x23937) [0x56015c010937]
[  1533.842] (EE) 16: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (__libc_start_main+0x85) [0x56015c0109f5]
[  1533.842] (EE) 17: /usr/bin/X (_start+0x21) [0x56015cac2991]
[  1533.842] (EE) 
[  1533.842] (EE) Segmentation fault at address 0x14
[  1533.842] (EE) 
Fatal server error:
[  1533.842] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  1533.842] (EE) 
[  1533.842] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[  1533.842] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  1533.842] (EE) 
[  1533.842] (II) AIGLX: Suspending AIGLX clients for VT switch
[  1533.857] (EE) Server terminated with error (1). Closing log file.

I understand that clearlinux is focused on cloud/server usage. But for us, xorg users on desktop, would it be possible to somehow test xorg before a new update of clearlinux is released ? Being unable to start X on clearlinux is quite frequent, see this issue from december. As much as I like clearlinux, such issue makes the experience quite frustrating...

fenrus75 commented 1 year ago

For the desktop, wayland is really the way to go; that's the path we use and test.

On Wed, Jun 21, 2023 at 2:01 AM Sebastien Chapuis @.***> wrote:

I've just updated Clearlinux to 39420, and Xorg refuses to start with this error:

[ 1533.842] (EE) [ 1533.842] (EE) Backtrace: [ 1533.842] (EE) 0: /usr/bin/X (xorg_backtrace+0x47) [0x56015cbe6f27] [ 1533.842] (EE) 1: /usr/bin/X (0x56015ca82000+0x168df9) [0x56015cbeadf9] [ 1533.842] (EE) 2: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (0x56015bfed000+0x3c720) [0x56015c029720] [ 1533.842] (EE) 3: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0x1346df0) [0x560159dd2df0] [ 1533.842] (EE) 4: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0x135c4ef) [0x560159de84ef] [ 1533.842] (EE) 5: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0xb8018) [0x560158b44018] [ 1533.842] (EE) 6: /usr/lib64/dri/iris_dri.so (0x560158a8c000+0xb8bb5) [0x560158b44bb5] [ 1533.842] (EE) 7: /usr/lib64/libgbm.so.1 (0x56015b1fc000+0x620a) [0x56015b20220a] [ 1533.842] (EE) 8: /usr/lib64/xorg/modules/libglamoregl.so (glamor_back_pixmap_from_fd+0xdf) [0x56015b16353f] [ 1533.842] (EE) 9: /usr/lib64/xorg/modules/libglamoregl.so (glamor_egl_create_textured_pixmap+0x70) [0x56015b163620] [ 1533.842] (EE) 10: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0x56015ca62000+0x14285) [0x56015ca76285] [ 1533.842] (EE) 11: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0x56015ca62000+0x8e08) [0x56015ca6ae08] [ 1533.842] (EE) 12: /usr/bin/X (0x56015ca82000+0xbce8e) [0x56015cb3ee8e] [ 1533.842] (EE) 13: /usr/bin/X (InitRootWindow+0x11) [0x56015cb35171] [ 1533.842] (EE) 14: /usr/bin/X (0x56015ca82000+0x863bc) [0x56015cb083bc] [ 1533.842] (EE) 15: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (0x56015bfed000+0x23937) [0x56015c010937] [ 1533.842] (EE) 16: /usr/lib64/glibc-hwcaps/x86-64-v3/libc.so.6 (__libc_start_main+0x85) [0x56015c0109f5] [ 1533.842] (EE) 17: /usr/bin/X (_start+0x21) [0x56015cac2991] [ 1533.842] (EE) [ 1533.842] (EE) Segmentation fault at address 0x14 [ 1533.842] (EE) Fatal server error: [ 1533.842] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 1533.842] (EE) [ 1533.842] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 1533.842] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 1533.842] (EE) [ 1533.842] (II) AIGLX: Suspending AIGLX clients for VT switch [ 1533.857] (EE) Server terminated with error (1). Closing log file.

I understand that clearlinux is focused on cloud/server usage. But for us, xorg users on desktop, would it be possible to somehow test xorg when a new update of clearlinux is released ? Being unable to start X on clearlinux is quite frequent, see this issue https://github.com/clearlinux/distribution/issues/2797#issuecomment-1363209617 from december. As much as I like clearlinux, such issue makes the experience quite frustrating...

— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2912, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ54FIDEJPXHQF6374NPQDXMKZ6VANCNFSM6AAAAAAZONQCSU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

giuseppetavera commented 1 year ago

I have the same problem too