You are not logged in.

#1 2023-05-22 13:28:39

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

[Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

I've had a lot of gnome-shell core-dumps since upgraded to Gnome 44. Anyone else having the same experience? Most of them happened during booting into the desktop environment. But tonight when I was updating my system from terminel (linux kernel, nvidia and stuff), Shell just crashed and logged me out of gnome and my monitor went to black and it says No signal. Had to go to tty3 to reboot. Had no idea if my update went successful or not. I should also mention that my monitors also wouldn't wake up after resuming from suspend (no signal) since upgraded to 44. Should also be related to this issue. Output from coredumpctl info: https://gist.github.com/tfhavingfun/3d1 … aa20c47116

journalctl output from the crash during updating: https://gist.github.com/tfhavingfun/3db … bd7e772db9

My system: linux 6.3.3.arch1-1;
(RTX 3080TI) nvidia 530.41.03-12;
I've go two 4k monitors connected;
Running on X11;
Shell extensions: Dash to Dock; Freon; User theme

Can anyone shed some light on what's causing this? Thanks.

Edit: Latest mutter update fixed the issue for me. It's indeed related to the wacom module.

Last edited by ghfujianbin (2023-06-08 01:32:39)

Offline

#2 2023-05-22 14:11:40

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

There're three types:

Stack trace of thread 858:
#0  0x00007f601929f26c n/a (libc.so.6 + 0x8926c)
#1  0x00007f601924fa08 raise (libc.so.6 + 0x39a08)
#2  0x000055d466615f19 n/a (gnome-shell + 0x3f19)
#3  0x00007f601924fab0 n/a (libc.so.6 + 0x39ab0)
#4  0x00007f601929f26c n/a (libc.so.6 + 0x8926c)
#5  0x00007f601924fa08 raise (libc.so.6 + 0x39a08)
#6  0x00007f6019238538 abort (libc.so.6 + 0x22538)
#7  0x00007f60192392db n/a (libc.so.6 + 0x232db)
#8  0x00007f60192a91b7 n/a (libc.so.6 + 0x931b7)
#9  0x00007f60192ab6ae n/a (libc.so.6 + 0x956ae)
#10 0x00007f60192adcb3 __libc_free (libc.so.6 + 0x97cb3)
#11 0x00007f6019b19447 g_datalist_clear (libglib-2.0.so.0 + 0x39447)
#12 0x00007f601a1284a4 g_object_unref (libgobject-2.0.so.0 + 0x224a4)
#13 0x00007f60198a40c4 clutter_event_free (libmutter-clutter-12.so.0 + 0x680c4)
#14 0x00007f60195c0cd8 n/a (libmutter-12.so.0 + 0x1c0cd8)
#15 0x00007f60194f621d n/a (libmutter-12.so.0 + 0xf621d)
#16 0x00007f6019b3a53b g_main_context_dispatch (libglib-2.0.so.0 + 0x5a53b)
#17 0x00007f6019b97219 n/a (libglib-2.0.so.0 + 0xb7219)
#18 0x00007f6019b39c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#19 0x00007f60194cdc5b meta_context_run_main_loop (libmutter-12.so.0 + 0xcdc5b)
#20 0x000055d466615526 n/a (gnome-shell + 0x3526)
#21 0x00007f6019239850 n/a (libc.so.6 + 0x23850)
#22 0x00007f601923990a __libc_start_main (libc.so.6 + 0x2390a)
#23 0x000055d466615835 n/a (gnome-shell + 0x3835)
Stack trace of thread 1643:
#0  0x00007f7bbe55ceac n/a (libnvidia-glcore.so.530.41.03 + 0x115ceac)
#1  0x00007f7bbe804e18 n/a (libnvidia-glcore.so.530.41.03 + 0x1404e18)
#2  0x00007f7bbe6e0fb1 n/a (libnvidia-glcore.so.530.41.03 + 0x12e0fb1)
#3  0x00007f7bbe6e1618 n/a (libnvidia-glcore.so.530.41.03 + 0x12e1618)
#4  0x00007f7bbe6f0909 n/a (libnvidia-glcore.so.530.41.03 + 0x12f0909)
#5  0x00007f7be2d3e99f n/a (libmutter-cogl-12.so.0 + 0x6c99f)
#6  0x00007f7be2d45e81 n/a (libmutter-cogl-12.so.0 + 0x73e81)
#7  0x00007f7be2d460ff n/a (libmutter-cogl-12.so.0 + 0x740ff)
#8  0x00007f7be2d46ad7 n/a (libmutter-cogl-12.so.0 + 0x74ad7)
#9  0x00007f7be2d47b8d n/a (libmutter-cogl-12.so.0 + 0x75b8d)
#10 0x00007f7be2d50427 cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-12.so.0 + 0x7e427)
#11 0x00007f7be2a8f3b5 n/a (libmutter-12.so.0 + 0x8f3b5)
#12 0x00007f7be2a8ff94 n/a (libmutter-12.so.0 + 0x8ff94)
#13 0x00007f7be2b04362 n/a (libmutter-12.so.0 + 0x104362)
#14 0x00007f7be2ef189b n/a (libmutter-clutter-12.so.0 + 0xb589b)
#15 0x00007f7be2eb0855 n/a (libmutter-clutter-12.so.0 + 0x74855)
#16 0x00007f7be313a53b g_main_context_dispatch (libglib-2.0.so.0 + 0x5a53b)
#17 0x00007f7be3197219 n/a (libglib-2.0.so.0 + 0xb7219)
#18 0x00007f7be3139c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#19 0x00007f7be2acdc5b meta_context_run_main_loop (libmutter-12.so.0 + 0xcdc5b)
#20 0x000055e47f8a5526 n/a (gnome-shell + 0x3526)
#21 0x00007f7be2839850 n/a (libc.so.6 + 0x23850)
#22 0x00007f7be283990a __libc_start_main (libc.so.6 + 0x2390a)
#23 0x000055e47f8a5835 n/a (gnome-shell + 0x3835)
Stack trace of thread 1676:
#0  0x00007f21f5b26cf7 _XSend (libX11.so.6 + 0x41cf7)
#1  0x00007f21f5b1f6c9 XQueryExtension (libX11.so.6 + 0x3a6c9)
#2  0x00007f21f316ce17 n/a (libXext.so.6 + 0x6e17)
#3  0x00007f21f3172f28 XSyncTriggerFence (libXext.so.6 + 0xcf28)
#4  0x00007f21f6106031 n/a (libmutter-12.so.0 + 0x106031)
#5  0x00007f21f6106225 n/a (libmutter-12.so.0 + 0x106225)
#6  0x00007f21f6d30531 g_object_run_dispose (libgobject-2.0.so.0 + 0x22531)
#7  0x00007f21f60b6c16 meta_display_close (libmutter-12.so.0 + 0xb6c16)
#8  0x00007f21f60d499a n/a (libmutter-12.so.0 + 0xd499a)
#9  0x00007f21f6d30531 g_object_run_dispose (libgobject-2.0.so.0 + 0x22531)
#10 0x00007f21f60cde2e meta_context_destroy (libmutter-12.so.0 + 0xcde2e)
#11 0x00005597bd9f15e9 n/a (gnome-shell + 0x35e9)
#12 0x00007f21f5e39850 n/a (libc.so.6 + 0x23850)
#13 0x00007f21f5e3990a __libc_start_main (libc.so.6 + 0x2390a)
#14 0x00005597bd9f1835 n/a (gnome-shell + 0x3835)

#1 "g_datalist_clear" is the most common one.

#1 & #3 look like the glib2 slice-is-malloc situation, #2 would rather point at the GL driver.
I'd say "run memtest" but you'd see crashes in other processes.
And everything goes through libmutter.

pacman -Qm
pacman -Qikk mutter

And try w/o

Shell extensions: Dash to Dock; Freon; User theme

resp. a fresh user account.

Offline

#3 2023-05-23 12:53:15

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Thanks a lot for bringing this forward. I'm experiencing the same problem(s) since the upgrade with my Thinkpad and especially in combination with my USB3 Dockingstation.

Offline

#4 2023-05-24 02:10:30

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Thank you Seth for looking into this. I had another crash today when doing pacman update. I wonder why would updating packages ( no kernel, nvidia) cause a Shell crash? Can you take a look at the new dump/log files?
Coredumpctl: https://gist.github.com/tfhavingfun/446 … 92364dd43b
Journalctl: https://gist.github.com/tfhavingfun/c56 … a20abeb764
Pacman log: https://gist.github.com/tfhavingfun/939 … 43cf3dc289

Offline

#5 2023-05-24 06:10:45

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Partial update or, for gnome specifically and *very* common, incompatible extensions.

seth wrote:

And everything goes through libmutter.

pacman -Qm
pacman -Qikk mutter

And try w/o

Shell extensions: Dash to Dock; Freon; User theme

resp. a fresh user account.

Add

pacman -Qm

to that.

Offline

#6 2023-05-24 07:00:17

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

I'm not the thread starter, but here are my pacman outputs:

❯ pacman -Qm
saga-gis 9.0.1-2

~ 
❯ pacman -Qikk mutter
Name            : mutter
Version         : 44.1+r2+g82bd40dcbc-1
Description     : Window manager and compositor for GNOME
Architecture    : x86_64
URL             : https://gitlab.gnome.org/GNOME/mutter
Licenses        : GPL
Groups          : None
Provides        : libmutter-12.so=0-64
Depends On      : colord  dconf  gnome-desktop-4  gnome-settings-daemon  graphene  gsettings-desktop-schemas
                  lcms2  libcanberra  libgudev  libinput  libsm  libsysprof-capture  libxkbcommon-x11
                  libxkbfile  pipewire  startup-notification  xorg-xwayland
Optional Deps   : None
Required By     : gnome-shell
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 14,11 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : So 07 Mai 2023 17:33:38
Install Date    : Mo 08 Mai 2023 08:19:43
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

mutter: 590 total files, 0 altered files

I've also removed all gnome related config and started fresh. Problems seem to be gone. I've not altered any/few of the gnome defaults yet: changed the default background image, changed <alt-tab> behaviour, only one extension installed and active so far: "start new instance".

Last edited by gaelic (2023-05-24 07:01:08)

Offline

#7 2023-05-24 07:12:23

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Here are the pacman outputs:

pacman -Qm
celt 0.11.3-4
davinci-resolve 18.1.4-1
espeak 1:1.48.04-3
gamin 0.1.10-9
gfbgraph 0.2.5-1
gnome-getting-started-docs 3.38.1-1
gnome-online-miners 3.34.0-2
js52 52.9.0-4
js60 60.9.0-2
js68 68.12.0-1
lcms 1.19-7
libbloom 1.6-3
libcorkipset 1.1.1+20150311-3
libglade 2.6.4-7
libgweather 40.0+r87+g80e5a652-2
libmagick6 6.9.11.58-1
libnm-glib 1.18.5dev+12+ga8746f48ca-1
libnm-gtk 1.8.19dev+21+geebf7f95-1
libopenaptx 0.2.0-1
libzapojit 0.0.3+14+g2dace3f-2
metis 5.1.0.p10-2
mozilla-common 1.4-6
opencolorio1 1.1.1-3
openjpeg 1.5.2-2
openssl-1.0 1.0.2.u-1
pcmciautils 018-8
pygtk 2.24.0-8
python2 2.7.18-5
python2-cairo 1.18.2-4
python2-gobject 3.36.1-5
python2-gobject2 2.28.7-6
qt5-webkit 5.212.0alpha4-15
shadowsocks-libev 3.3.5-4
substance-painter 7.1.1-1
tracker 1:2.3.6+r7+gb27396252-1
tracker-miners 1:2.3.5+r3+gd9d61d87f-1
vino 3.22.0+74+g7a95e10-1
xorg-font-utils 7.6-6
pacman -Qikk mutter
Name            : mutter
Version         : 44.1+r2+g82bd40dcbc-1
Description     : Window manager and compositor for GNOME
Architecture    : x86_64
URL             : https://gitlab.gnome.org/GNOME/mutter
Licenses        : GPL
Groups          : None
Provides        : libmutter-12.so=0-64
Depends On      : colord  dconf  gnome-desktop-4  gnome-settings-daemon  graphene  gsettings-desktop-schemas  lcms2  libcanberra  libgudev  libinput  libsm  libsysprof-capture
                  libxkbcommon-x11  libxkbfile  pipewire  startup-notification  xorg-xwayland
Optional Deps   : None
Required By     : gnome-shell
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 14.11 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : Sun 07 May 2023 11:33:38 PM CST
Install Date    : Fri 19 May 2023 04:32:37 PM CST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

mutter: 590 total files, 0 altered files

Offline

#8 2023-05-24 07:16:38

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

ghfujianbin has some foreign packages I could see to cause interference, but gaelic doesn't.
Mutter itself is fine for either of you and w/

I've also removed all gnome related config and started fresh. Problems seem to be gone.

It *seems* to be the usual "gnome update broke my extensions" dance - though those typically crash somewhere in javascript.

Offline

#9 2023-05-24 07:16:54

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

gaelic wrote:

I've also removed all gnome related config and started fresh. Problems seem to be gone. I've not altered any/few of the gnome defaults yet: changed the default background image, changed <alt-tab> behaviour, only one extension installed and active so far: "start new instance".

What have you done to remove all gnome configs? Do you still see any core dumps from journalctl? Especially those from user 120(gdm session)? Thanks.

Offline

#10 2023-05-24 07:23:52

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

seth wrote:

ghfujianbin has some foreign packages I could see to cause interference, but gaelic doesn't.
Mutter itself is fine for either of you and w/

I've also removed all gnome related config and started fresh. Problems seem to be gone.

It *seems* to be the usual "gnome update broke my extensions" dance - though those typically crash somewhere in javascript.

Thanks Seth. I can see a lot of shell core dumps during X startup (user 120 by gdm) even w/o any extensions enabled. So it's safe for to to remove those foreign pkgs from

pacman -Qmd

, right?

Offline

#11 2023-05-24 07:32:15

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Those are your AUR packages, python2 might be stale leftovers from before it got dropped from the repos.
You'll have to dedcide case-by-case what you want to/need to retain.

We haven't seen a coredump from gaelic, have we?

ay 24 09:19:43 ryzen systemd-coredump[1918]: Process 862 (gnome-shell) of user 120 dumped core.
  
  Stack trace of thread 862:
  #0  0x00007ff959e9f26c n/a (libc.so.6 + 0x8926c)
  #1  0x00007ff959e4fa08 raise (libc.so.6 + 0x39a08)
  #2  0x0000560889a10f19 n/a (gnome-shell + 0x3f19)
  #3  0x00007ff959e4fab0 n/a (libc.so.6 + 0x39ab0)
  #4  0x00007ff959e9f26c n/a (libc.so.6 + 0x8926c)
  #5  0x00007ff959e4fa08 raise (libc.so.6 + 0x39a08)
  #6  0x00007ff959e38538 abort (libc.so.6 + 0x22538)
  #7  0x00007ff959e392db n/a (libc.so.6 + 0x232db)
  #8  0x00007ff959ea91b7 n/a (libc.so.6 + 0x931b7)
  #9  0x00007ff959eab6ae n/a (libc.so.6 + 0x956ae)
  #10 0x00007ff959eadcb3 __libc_free (libc.so.6 + 0x97cb3)
  #11 0x00007ff95a719447 g_datalist_clear (libglib-2.0.so.0 + 0x39447)
  #12 0x00007ff95ae0d4a4 g_object_unref (libgobject-2.0.so.0 + 0x224a4)
  #13 0x00007ff95a4a40c4 clutter_event_free (libmutter-clutter-12.so.0 + 0x680c4)
  #14 0x00007ff95a1c0cd8 n/a (libmutter-12.so.0 + 0x1c0cd8)
  #15 0x00007ff95a0f621d n/a (libmutter-12.so.0 + 0xf621d)
  #16 0x00007ff95a73a53b g_main_context_dispatch (libglib-2.0.so.0 + 0x5a53b)
  #17 0x00007ff95a797219 n/a (libglib-2.0.so.0 + 0xb7219)
  #18 0x00007ff95a739c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
  #19 0x00007ff95a0cdc5b meta_context_run_main_loop (libmutter-12.so.0 + 0xcdc5b)
  #20 0x0000560889a10526 n/a (gnome-shell + 0x3526)
  #21 0x00007ff959e39850 n/a (libc.so.6 + 0x23850)
  #22 0x00007ff959e3990a __libc_start_main (libc.so.6 + 0x2390a)
  #23 0x0000560889a10835 n/a (gnome-shell + 0x3835)

looks a lot like a glib2-related issue (the problem isn't glib2 directly, a recent change just exposed a lot of broken code)

Let'S first look at

ldd /usr/bin/gnome-shell

Offline

#12 2023-05-24 07:44:44

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Output from

ldd /usr/bin/gnome-shell
	linux-vdso.so.1 (0x00007fffc3f2f000)
	libshell-12.so => /usr/lib/gnome-shell/libshell-12.so (0x00007f4424c00000)
	libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f4424a2b000)
	libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f4424ef3000)
	libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f44248e0000)
	libatk-bridge-2.0.so.0 => /usr/lib/libatk-bridge-2.0.so.0 (0x00007f4424eb8000)
	libgjs.so.0 => /usr/lib/libgjs.so.0 (0x00007f442477d000)
	libmutter-clutter-12.so.0 => /usr/lib/mutter-12/libmutter-clutter-12.so.0 (0x00007f442463c000)
	libmutter-cogl-pango-12.so.0 => /usr/lib/mutter-12/libmutter-cogl-pango-12.so.0 (0x00007f4424eaa000)
	libgirepository-1.0.so.1 => /usr/lib/libgirepository-1.0.so.1 (0x00007f4424618000)
	libmutter-12.so.0 => /usr/lib/libmutter-12.so.0 (0x00007f4424200000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f44245f3000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f4424016000)
	libgnome-shell-menu.so => /usr/lib/gnome-shell/libgnome-shell-menu.so (0x00007f44245e8000)
	libst-12.so => /usr/lib/gnome-shell/libst-12.so (0x00007f442453a000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f44244f4000)
	libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f4423ee4000)
	libmutter-cogl-12.so.0 => /usr/lib/mutter-12/libmutter-cogl-12.so.0 (0x00007f4423e28000)
	libgraphene-1.0.so.0 => /usr/lib/libgraphene-1.0.so.0 (0x00007f44244d5000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f4423ce5000)
	libpolkit-agent-1.so.0 => /usr/lib/libpolkit-agent-1.so.0 (0x00007f44244c9000)
	libpolkit-gobject-1.so.0 => /usr/lib/libpolkit-gobject-1.so.0 (0x00007f44244ab000)
	libgcr-4.so.4 => /usr/lib/libgcr-4.so.4 (0x00007f4423c53000)
	libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007f4423b70000)
	libnm.so.0 => /usr/lib/libnm.so.0 (0x00007f44239ff000)
	libsecret-1.so.0 => /usr/lib/libsecret-1.so.0 (0x00007f442399b000)
	libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f44244a3000)
	libgnome-desktop-4.so.2 => /usr/lib/libgnome-desktop-4.so.2 (0x00007f4424483000)
	libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f442447c000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00007f4423981000)
	libmount.so.1 => /usr/lib/libmount.so.1 (0x00007f4423933000)
	libffi.so.8 => /usr/lib/libffi.so.8 (0x00007f4424471000)
	libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007f4423898000)
	libatspi.so.0 => /usr/lib/libatspi.so.0 (0x00007f442385e000)
	libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f4423836000)
	libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f44237e5000)
	libmozjs-102.so => /usr/lib/libmozjs-102.so (0x00007f4421800000)
	libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f442378e000)
	libcairo-gobject.so.2 => /usr/lib/libcairo-gobject.so.2 (0x00007f4423783000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f4421400000)
	libjson-glib-1.0.so.0 => /usr/lib/libjson-glib-1.0.so.0 (0x00007f4423758000)
	libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f44236ef000)
	libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f44235f3000)
	libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x00007f44217e0000)
	libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f44217d0000)
	libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f44217b8000)
	libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f4421769000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f442167c000)
	libwayland-server.so.0 => /usr/lib/libwayland-server.so.0 (0x00007f44213ea000)
	libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007f44213d8000)
	libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f4421352000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f442133d000)
	libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f4424466000)
	libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f44235ee000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f4421330000)
	libXtst.so.6 => /usr/lib/libXtst.so.6 (0x00007f4421328000)
	libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f4421314000)
	libwacom.so.9 => /usr/lib/libwacom.so.9 (0x00007f4421306000)
	libcolord.so.2 => /usr/lib/libcolord.so.2 (0x00007f44212ab000)
	liblcms2.so.2 => /usr/lib/liblcms2.so.2 (0x00007f4421245000)
	libxkbcommon.so.0 => /usr/lib/libxkbcommon.so.0 (0x00007f44211fe000)
	libcanberra.so.0 => /usr/lib/libcanberra.so.0 (0x00007f44211eb000)
	libgudev-1.0.so.0 => /usr/lib/libgudev-1.0.so.0 (0x00007f44211de000)
	libudev.so.1 => /usr/lib/libudev.so.1 (0x00007f44211ab000)
	libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so.0 (0x00007f442119f000)
	libpipewire-0.3.so.0 => /usr/lib/libpipewire-0.3.so.0 (0x00007f44210c0000)
	libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f44210b9000)
	libICE.so.6 => /usr/lib/libICE.so.6 (0x00007f442109b000)
	libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f442108f000)
	libxkbfile.so.1 => /usr/lib/libxkbfile.so.1 (0x00007f4421067000)
	libxkbcommon-x11.so.0 => /usr/lib/libxkbcommon-x11.so.0 (0x00007f442105e000)
	libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f4421059000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f442102c000)
	libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007f442101a000)
	libxcb-res.so.0 => /usr/lib/libxcb-res.so.0 (0x00007f4421014000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f442100f000)
	libSM.so.6 => /usr/lib/libSM.so.6 (0x00007f4421004000)
	libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f4420fed000)
	libinput.so.10 => /usr/lib/libinput.so.10 (0x00007f4420f97000)
	libgbm.so.1 => /usr/lib/libgbm.so.1 (0x00007f4420f87000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f4424f8b000)
	libGLESv2.so.2 => /usr/lib/libGLESv2.so.2 (0x00007f4420f75000)
	libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f4420f3c000)
	libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f4420eb9000)
	libtiff.so.6 => /usr/lib/libtiff.so.6 (0x00007f4420e20000)
	libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f4420d43000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f4420d36000)
	libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f4420d27000)
	libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f4420d22000)
	libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f4420c75000)
	libgck-2.so.2 => /usr/lib/libgck-2.so.2 (0x00007f4420c40000)
	libp11-kit.so.0 => /usr/lib/libp11-kit.so.0 (0x00007f4420b0d000)
	libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f44209c5000)
	libcap.so.2 => /usr/lib/libcap.so.2 (0x00007f44209b9000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f4420986000)
	libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007f44208b1000)
	liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007f442088f000)
	libsmime3.so => /usr/lib/libsmime3.so (0x00007f4420867000)
	libnss3.so => /usr/lib/libnss3.so (0x00007f442072f000)
	libnspr4.so => /usr/lib/libnspr4.so (0x00007f44206ee000)
	libtss2-esys.so.0 => /usr/lib/libtss2-esys.so.0 (0x00007f4420651000)
	libtss2-mu.so.0 => /usr/lib/libtss2-mu.so.0 (0x00007f44205ff000)
	libtss2-rc.so.0 => /usr/lib/libtss2-rc.so.0 (0x00007f44205f5000)
	libtss2-tctildr.so.0 => /usr/lib/libtss2-tctildr.so.0 (0x00007f44205eb000)
	libxkbregistry.so.0 => /usr/lib/libxkbregistry.so.0 (0x00007f44205e1000)
	libseccomp.so.2 => /usr/lib/libseccomp.so.2 (0x00007f44205c2000)
	libblkid.so.1 => /usr/lib/libblkid.so.1 (0x00007f4420584000)
	libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f4420510000)
	libthai.so.0 => /usr/lib/libthai.so.0 (0x00007f4420505000)
	libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f44204e2000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f44204b7000)
	libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f44203fd000)
	libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f44203cb000)
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x00007f44203c0000)
	libtdb.so.1 => /usr/lib/libtdb.so.1 (0x00007f44203a8000)
	libltdl.so.7 => /usr/lib/libltdl.so.7 (0x00007f442039d000)
	libxcb-util.so.1 => /usr/lib/libxcb-util.so.1 (0x00007f4420394000)
	libxcb-xkb.so.1 => /usr/lib/libxcb-xkb.so.1 (0x00007f4420375000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f442036d000)
	libuuid.so.1 => /usr/lib/libuuid.so.1 (0x00007f4420364000)
	libmtdev.so.1 => /usr/lib/libmtdev.so.1 (0x00007f442035d000)
	libevdev.so.2 => /usr/lib/libevdev.so.2 (0x00007f442033d000)
	libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f442032a000)
	libbrotlidec.so.1 => /usr/lib/libbrotlidec.so.1 (0x00007f442031c000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f4420317000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f4420312000)
	libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f44202ea000)
	libnssutil3.so => /usr/lib/libnssutil3.so (0x00007f44202b8000)
	libplds4.so => /usr/lib/libplds4.so (0x00007f44202b3000)
	libplc4.so => /usr/lib/libplc4.so (0x00007f44202ac000)
	libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007f441fe00000)
	libtss2-sys.so.1 => /usr/lib/libtss2-sys.so.1 (0x00007f4420283000)
	libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f441fc98000)
	libdatrie.so.1 => /usr/lib/libdatrie.so.1 (0x00007f442027a000)
	libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f442024c000)
	libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f441fc8d000)
	libbrotlicommon.so.1 => /usr/lib/libbrotlicommon.so.1 (0x00007f441fc68000)
	libicuuc.so.72 => /usr/lib/libicuuc.so.72 (0x00007f441fa00000)
	libicudata.so.72 => /usr/lib/libicudata.so.72 (0x00007f441dc00000)

Offline

#13 2023-05-24 08:02:34

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

seth wrote:

ghfujianbin has some foreign packages I could see to cause interference, but gaelic doesn't.
Mutter itself is fine for either of you and w/

I've also removed all gnome related config and started fresh. Problems seem to be gone.

It *seems* to be the usual "gnome update broke my extensions" dance - though those typically crash somewhere in javascript.

This might be the case. This is really a huge drawback using gnome.

ghfujianbin wrote:
gaelic wrote:

I've also removed all gnome related config and started fresh. Problems seem to be gone. I've not altered any/few of the gnome defaults yet: changed the default background image, changed <alt-tab> behaviour, only one extension installed and active so far: "start new instance".

What have you done to remove all gnome configs? Do you still see any core dumps from journalctl? Especially those from user 120(gdm session)? Thanks.

I've removed everything related to gnome or gtk in .config and .local/share (including evince, nautilus, gvfs, ...), also all themes installed via pacman and the .themes folder.

Since I've done this there were no problems yet. I'll post a coredump and info if i run into problems again.

Last edited by gaelic (2023-05-24 08:03:27)

Offline

#14 2023-05-24 08:04:50

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

You can access previous coredumps, https://wiki.archlinux.org/title/Core_d … _core_dump
It would be helpfl to see whether they've the same pattern as the OP - these might be different problems.

Offline

#15 2023-05-24 08:26:32

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Allright. Here's the last coredump I experienced:

https://gist.github.com/luchmhor/fab123 … 34c34ec892

and the journalctl from the moment I remove the USB-C cable from the docking station where I expect the laptop to go to sleep and resume without any problem afterwards:

https://gist.github.com/luchmhor/91ef56 … 10b4a05fc2

Offline

#16 2023-05-24 10:44:58

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Unfortunately a new gnome profile w/o extensions, etc. did not resolve the issue. I decided to remove the laptop from the dock before lunch and reconnected after. The Screens on the dock did not power up. I opened the lid of the laptop and saw that the gnome-shell crashed and my session was not resumed but a new one started. I still had to reboot because docking was not working anymore. I did the reboot from the console login in as root.

Heres again the coredump info:

https://gist.github.com/luchmhor/a4f74e … ed41c4d5b0

and the journalctl:

https://gist.github.com/luchmhor/c77f23 … 9c5b37fa95

Next time I try to put the laptop to sleep before unplugin from the dock, but as stated above it was working before the update.

Offline

#17 2023-05-24 14:18:35

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Crashes straight in mutter, the backtrace looks different from OP and wrt

Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Mai 22 17:15:21 angus gnome-shell[2173]: Page flip failed: drmModeAtomicCommit: Invalid argument
Mai 24 12:08:01 angus gnome-shell[2169]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Mai 24 12:08:01 angus gnome-shell[2169]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Mai 24 12:08:01 angus gnome-shell[2169]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Mai 24 12:08:01 angus gnome-shell[2169]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Mai 24 12:08:01 angus gnome-shell[2169]: Page flip failed: drmModeAtomicCommit: Invalid argument

and

I decided to remove the laptop from the dock before lunch

and

I remove the USB-C cable from the docking station where I expect the laptop to go to sleep

kinda suggests this is heavily related to a change in the available outputs.

Does it happen w/ gnome on X11?

Edit: when yo're running docked, is the internal display enabled?
What if you enable it before undocking?

Last edited by seth (2023-05-24 14:29:31)

Offline

#18 2023-05-24 17:14:27

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

seth wrote:

Edit: when yo're running docked, is the internal display enabled?
What if you enable it before undocking?

Yes exactly my impression. I will try tomorrow at work immediately in the morning to reproduce the case again as it is (Laptop Lid is closed all the time), the again with the lid open, and lastly with Gnome on X11.

Offline

#19 2023-05-25 07:34:30

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Sadly the problem stays the same with the internal display active:

https://gist.github.com/luchmhor/da921b … bf357bbb6e

In there is the journal of 2 tries:

- First I connect the closed and suspended laptop and I can login without any trouble. Then I unplug (still closed lid) and the gnome-shell crashes.
- I poweroff and start the laptop with the lid open and undocked.
- Then I pluig with the lid open, and after a while pull the plug ...

Offline

#20 2023-05-25 08:26:00

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Just another thing to add: Noticed that all crashes during pacman operation can be related to this hook: 30-system-udev-reload.hook. Pacman operation without this hook run doesn't usually trigger crash.

Offline

#21 2023-05-25 08:39:47

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,410

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

You can try commenting the trigger and the settle line in the script it calls, see e.g. https://bbs.archlinux.org/viewtopic.php?id=284249 (do check whether you have a bogus evdev xorg config condition) and https://bugs.archlinux.org/task/77789

Last edited by V1del (2023-05-25 08:40:23)

Offline

#22 2023-05-25 13:08:50

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

V1del wrote:

do check whether you have a bogus evdev xorg config condition

Hmm. I do have a xorg conf file for my tablet like this (50-huion.conf):

Section "InputClass"
        Identifier      "Huion H1060P"
        MatchIsTablet   "on"
        MatchDevicePath "/dev/input/event*"
        MatchUSBID      "256c:006d"
        Driver          "wacom"
EndSection

Section "InputClass"
        Identifier      "Huion buttons"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        MatchUSBID      "256c:006d"
        Driver          "evdev"
EndSection

When I delete the whole file, I don't get gnome-shell core-dumps during booting up any more. But even with only the top "wacom" part which I need for my tablet to work, gnome-shell still dumps core. Also resuming from suspend still crashes gnome-shell and gives me black screen(no signal) even without that 50-huion.conf file.

Last edited by ghfujianbin (2023-05-25 13:09:37)

Offline

#23 2023-05-25 14:28:14

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,410

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

You should generally not "need" either unless you find the wacom driver to provide features the libinput driver doesn't give you. But if that is the case, then follow my advice in the other thread to disable the udev trigger so that you are at least not kicked anymore when doing pacman updates.

Offline

#24 2023-05-25 14:28:54

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Also coredumps that match wacom+boot and resume from S3 (w/o the file) so we can separate the conditions.

Also check the xorg.*.log.old's after a gnome crash (to see whether that's maybe just a follow-up from an X11 crash)

Offline

#25 2023-05-25 16:23:29

ghfujianbin
Member
Registered: 2013-11-10
Posts: 21

Re: [Solved]Too many core-dumps for Gnome-shell since upgraded to Gnome 44

Xorg log before login (has gnome shell dump by uid 120): https://gist.github.com/tfhavingfun/876 … 3058cffb2d
coredumps that match wacom+boot: https://gist.github.com/tfhavingfun/a9a … e1debf8932
resume from S3 (w/o the file): https://gist.github.com/tfhavingfun/2cb … 9ac14a9031
I don't see any obvious X server crash from xorg log, other than this (from journalctl after resume from sleep):

May 25 18:22:03 ryzen gnome-shell[2789]: X Error of failed request:  BadMatch (invalid parameter attributes)
May 25 18:22:03 ryzen gnome-shell[2789]:   Major opcode of failed request:  140 (RANDR)
May 25 18:22:03 ryzen gnome-shell[2789]:   Minor opcode of failed request:  7 (RRSetScreenSize)
May 25 18:22:03 ryzen gnome-shell[2789]:   Serial number of failed request:  306
May 25 18:22:03 ryzen gnome-shell[2789]:   Current serial number in output stream:  308
May 25 18:22:02 ryzen systemd[1243]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2.
May 25 18:22:02 ryzen systemd[1243]: Stopped GNOME Shell on X11.

Last edited by ghfujianbin (2023-05-25 16:24:50)

Offline

Board footer

Powered by FluxBB