You are not logged in.
- Topics: Active | Unanswered
#1 2023-12-30 03:15:19
- ConanEdogawa
- Member
- Registered: 2023-12-30
- Posts: 1
GNOME 45 crashed when I login
Hi everyone.
Recently I installed Arch Linux with GNOME Desktop Environment. However, when I login, GNOME crashed, with graphical issues.
The log here.
PID: 20436 (gnome-shell)
UID: 1001 (ConanEdogawa)
GID: 1001 (ConanEdogawa)
Signal: 6 (ABRT)
Timestamp: Sat 2023-12-30 10:47:39 CST (19min ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: /user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@x11.service
Unit: user@1001.service
User Unit: org.gnome.Shell@x11.service
Slice: user-1001.slice
Owner UID: 1001 (ConanEdogawa)
Boot ID: 9960180c035a45bbb160a48c2c8528c7
Machine ID: 63f1e982f1934e1ab137eb8040d3083e
Hostname: Conan-PC
Storage: /var/lib/systemd/coredump/core.gnome-shell.1001.9960180c035a45bbb160a48c2c8528c7.20436.1703904459000000.zst (present)
Size on Disk: 13.9M
Message: Process 20436 (gnome-shell) of user 1001 dumped core.
Stack trace of thread 20436:
#0 0x00007fb2706ac83c n/a (libc.so.6 + 0x8e83c)
#1 0x00007fb27065c668 raise (libc.so.6 + 0x3e668)
#2 0x0000560a41acf109 n/a (gnome-shell + 0x4109)
#3 0x00007fb27065c710 n/a (libc.so.6 + 0x3e710)
#4 0x00007fb2706ac83c n/a (libc.so.6 + 0x8e83c)
#5 0x00007fb27065c668 raise (libc.so.6 + 0x3e668)
#6 0x00007fb2706444b8 abort (libc.so.6 + 0x264b8)
#7 0x00007fb2588a0b94 n/a (crocus_dri.so + 0xa0b94)
#8 0x00007fb2599ee1dc n/a (crocus_dri.so + 0x11ee1dc)
#9 0x00007fb258e10aef n/a (crocus_dri.so + 0x610aef)
#10 0x00007fb25898f03f n/a (crocus_dri.so + 0x18f03f)
#11 0x00007fb2588b9774 n/a (crocus_dri.so + 0xb9774)
#12 0x00007fb268094894 n/a (libEGL_mesa.so.0 + 0x32894)
#13 0x00007fb2680897e4 n/a (libEGL_mesa.so.0 + 0x277e4)
#14 0x00007fb26807e918 n/a (libEGL_mesa.so.0 + 0x1c918)
#15 0x00007fb26807600d n/a (libEGL_mesa.so.0 + 0x1400d)
#16 0x00007fb270373a65 n/a (libmutter-cogl-13.so.0 + 0x9fa65)
#17 0x00007fb270365f0e cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-13.so.0 + 0x91f0e)
#18 0x00007fb27089e3a5 n/a (libmutter-13.so.0 + 0x9e3a5)
#19 0x00007fb27089efb7 n/a (libmutter-13.so.0 + 0x9efb7)
#20 0x00007fb270915602 n/a (libmutter-13.so.0 + 0x115602)
#21 0x00007fb270cedf19 n/a (libmutter-clutter-13.so.0 + 0xb9f19)
#22 0x00007fb270ca7a75 n/a (libmutter-clutter-13.so.0 + 0x73a75)
#23 0x00007fb270f34f69 n/a (libglib-2.0.so.0 + 0x59f69)
#24 0x00007fb270f93367 n/a (libglib-2.0.so.0 + 0xb8367)
#25 0x00007fb270f35b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#26 0x00007fb2708d829b meta_context_run_main_loop (libmutter-13.so.0 + 0xd829b)
#27 0x00007fb26fdf84f6 n/a (libffi.so.8 + 0x74f6)
#28 0x00007fb26fdf4f5e n/a (libffi.so.8 + 0x3f5e)
#29 0x00007fb26fdf7b73 ffi_call (libffi.so.8 + 0x6b73)
#30 0x00007fb270dbefb7 n/a (libgjs.so.0 + 0x47fb7)
#31 0x00007fb270dc9bb8 n/a (libgjs.so.0 + 0x52bb8)
#32 0x00007fb26f39a948 n/a (libmozjs-115.so + 0x159a948)
#33 0x00007fb26f0212b6 n/a (libmozjs-115.so + 0x12212b6)
#34 0x00007fb26f013fdd n/a (libmozjs-115.so + 0x1213fdd)
#35 0x00007fb26f4f7433 _ZN2JS4CallEP9JSContextNS_6HandleINS_5ValueEEES4_RKNS_16HandleValueArrayENS_13MutableHandleIS3_EE (libmozjs-115.so + 0x16f7433)
#36 0x00007fb270dff082 n/a (libgjs.so.0 + 0x88082)
#37 0x00007fb270e05e8f gjs_context_eval_module (libgjs.so.0 + 0x8ee8f)
#38 0x00007fb270e06191 gjs_context_eval_module_file (libgjs.so.0 + 0x8f191)
#39 0x0000560a41ace57f n/a (gnome-shell + 0x357f)
#40 0x00007fb270645cd0 n/a (libc.so.6 + 0x27cd0)
#41 0x00007fb270645d8a __libc_start_main (libc.so.6 + 0x27d8a)
#42 0x0000560a41ace9e5 n/a (gnome-shell + 0x39e5)
Stack trace of thread 20442:
#0 0x00007fb270720f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007fb270f932b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007fb270f33162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007fb2715eafde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007fb270f66a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20448:
#0 0x00007fb2706a74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fb2706a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007fb25891385c n/a (crocus_dri.so + 0x11385c)
#3 0x00007fb25890ab8c n/a (crocus_dri.so + 0x10ab8c)
#4 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20443:
#0 0x00007fb2706a74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fb2706a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007fb26f304fa1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-115.so + 0x1504fa1)
#3 0x00007fb26f304e43 n/a (libmozjs-115.so + 0x1504e43)
#4 0x00007fb26f55fe4e n/a (libmozjs-115.so + 0x175fe4e)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 21028:
#0 0x00007fb27072c73d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fb270f8ecd3 g_cond_wait_until (libglib-2.0.so.0 + 0xb3cd3)
#2 0x00007fb270f00185 n/a (libglib-2.0.so.0 + 0x25185)
#3 0x00007fb270f002e7 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x252e7)
#4 0x00007fb270f6937e n/a (libglib-2.0.so.0 + 0x8e37e)
#5 0x00007fb270f66a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#6 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#7 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20948:
#0 0x00007fb27072ebf6 epoll_wait (libc.so.6 + 0x110bf6)
#1 0x00007fb258537869 n/a (libspa-support.so + 0x16869)
#2 0x00007fb25852958d n/a (libspa-support.so + 0x858d)
#3 0x00007fb270141db2 n/a (libpipewire-0.3.so.0 + 0x45db2)
#4 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20438:
#0 0x00007fb27072c73d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fb270f8e2f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7)
#2 0x00007fb270f001b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3 0x00007fb270f68a8e n/a (libglib-2.0.so.0 + 0x8da8e)
#4 0x00007fb270f66a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20445:
#0 0x00007fb2706a74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fb2706a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007fb25891385c n/a (crocus_dri.so + 0x11385c)
#3 0x00007fb25890ab8c n/a (crocus_dri.so + 0x10ab8c)
#4 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20446:
#0 0x00007fb2706a74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fb2706a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007fb25891385c n/a (crocus_dri.so + 0x11385c)
#3 0x00007fb25890ab8c n/a (crocus_dri.so + 0x10ab8c)
#4 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20439:
#0 0x00007fb270720f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007fb270f932b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007fb270f33162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007fb270f331b2 n/a (libglib-2.0.so.0 + 0x581b2)
#4 0x00007fb270f66a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20441:
#0 0x00007fb270720f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007fb270f932b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007fb270f35b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#3 0x00007fb27113919c n/a (libgio-2.0.so.0 + 0x11219c)
#4 0x00007fb270f66a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 20444:
#0 0x00007fb2706a74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fb2706a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007fb26f304fa1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-115.so + 0x1504fa1)
#3 0x00007fb26f304e43 n/a (libmozjs-115.so + 0x1504e43)
#4 0x00007fb26f55fe4e n/a (libmozjs-115.so + 0x175fe4e)
#5 0x00007fb2706aa9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fb27072e7cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64The PC hardware info here.
Operating System: Arch Linux
Kernel Version: 6.6.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Core™2 Duo CPU T7250 @ 2.00GHz
Memory: 2.8 GiB of RAM
Graphics Processor: Mesa Mobile Intel® GM45 Express Chipset
Manufacturer: LENOVO
Product Name: ZHAOYANG E43
System Version: Rev 1.0What should I do now?
Offline
#2 2023-12-30 14:35:59
- R.F.Buser
- Member
- Registered: 2018-04-02
- Posts: 7
Re: GNOME 45 crashed when I login
The culprit is the crocus driver for intel graphics hardware. It comes with the mesa package. Recently they made it default. You can just switch back to the i965 driver and your problem should be solved. You do this by placing the line
export MESA_LOADER_DRIVER_OVERRIDE=i965
into /etc/profile or ~/.profile
In my case I could still get a terminal after gdm login by typing
ter....
and then clicking on the terminal icon. Gnome-shell would only crash, if I would try to access the dash. If you can't get a terminal like this, you have to boot into rescue or multi-user mode. You do this by typing 'e', as soon as you get the grub prompt, when booting. Move to the "linux" line and either add the argument
systemd.unit=rescue.target
or
systemd.unit=multi-user.target
in case you need the network. After pressing F10 you will eventually get a bash in a console to make the above entry.
The current arch package with the broken crocus driver is
mesa 1:23.3.1-1
Offline
#3 2023-12-31 17:50:23
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,273
Re: GNOME 45 crashed when I login
You also need to switch to mesa-amber for hardware this old. And I'm fairly certain this isn't even eligible for i965 but even using i915 still.
Generally speaking I wouldn't be surprised if GNOME has higher requirements than can be given by that hardware anyway.
Offline
#4 2024-01-19 17:30:18
- R.F.Buser
- Member
- Registered: 2018-04-02
- Posts: 7
Re: GNOME 45 crashed when I login
You don't have to switch to mesa-amber, because mesa contains the old drivers, too. Of course, if mesa-amber would have been installed, the crocus driver could not have been chosen. Indeed, the crocus driver is not meant to run on old hardware. The problem was, that mesa would not choose the correct old driver (in my case, when setting the variable mentioned above to i965, mesa chooses correctly the i915 driver).
I just tested with mesa 1:23.3.3-1. Mesa now chooses the i915 driver without the MESA_LOADER_DRIVER_OVERRIDE variable being set. So, the problem is fixed, even if you stick with the mesa package.
According to pacman, if you switch from mesa to mesa-amber you save 53MB of disk space.
Offline
#5 2024-01-19 17:37:56
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 13,729
Re: GNOME 45 crashed when I login
You don't have to switch to mesa-amber, because mesa contains the old drivers, too.
No, it does not. All of the non-Gallium3D drivers were completely removed from mesa and are only available in mesa-amber.
Last edited by Scimmia (2024-01-19 17:38:07)
Offline
#6 2024-01-21 01:00:58
- R.F.Buser
- Member
- Registered: 2018-04-02
- Posts: 7
Re: GNOME 45 crashed when I login
This is true. But I was only focusing on the drivers which are relevant for this thread (crocus versus i915) and with "old drivers" I meant "drivers for old hardware". Sorry, if I caused some confusion. Of course, the i915 driver is only contained in the mesa package, because it is based on the Gallium interface, but it only supports Gen 3 Intel hardware. So at least in this case the mesa package supports old hardware. This is the message I wanted to convey.
Coming back to the main issue: According to this Phoronix article the Mesa3D community is working on the crocus driver such that it will support old hardware and make the i915 driver obsolete. I am pretty convinced, that the the fact that we (Intel Gen 3 users) got these crashes with mesa 1:23.3.1-1 not because there was a bug in the code for the driver choice. Instead, I think, the developers thought that the crocus driver is ready for Gen 3 hardware. The "fix" in 1:23.3.3-1 is just the workaround falling back to the i915 driver again. I assume sooner or later we again will get a mesa version where Gen 3 hardware will be driven by crocus.
Offline