You are not logged in.

Pages: 1

#1 2021-03-03 10:29:53

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

GNOME crashes

Hello.

There is some time when my GNOME crashes without no reason I know.

After that crash, I have to go to the CLI (ALT + F2) mode and then back to the GUI mode (ALT + F1).

Could anyone help me with finding the problem?

Here's journalctl log: https://pastebin.com/raw/xQ5QLehK

Offline

#2 2021-03-03 14:46:00

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,567

Re: GNOME crashes

Please define "crash" - there's no segfdault or abort in that log.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2021-03-03 18:33:59

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

Re: GNOME crashes

The white blinking cursor in the left top corner of the black screen - then I do ALT + F2, it starts CLI mode and then ALT + F1, it shows log in screen.

Offline

#4 2021-03-03 19:44:32

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,567

Re: GNOME crashes

Does that happen after a succesful login or is this the apparent end of the boot process?
In case of the latter try https://wiki.archlinux.org/index.php/Ke … _KMS_start

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2021-03-04 19:07:54

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

Re: GNOME crashes

It always happens after boot process and sometimes it happens while I am logged up and doing some internet stuff.

Should I still try it?

Last edited by wannabewalkie (2021-03-04 19:09:03)

Offline

#6 2021-03-04 20:56:05

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,567

Re: GNOME crashes

Yes, but since it happens at runtime as well it's probably not the only issue.

it happens while I am logged up and doing some internet stuff

"it" being

then ALT + F1, it shows log in screen

ie. your session is terminated?

Please post a complete system journal from a boot where that happened (eg. "sudo journalctl -b -1" will print the one from the previous boot)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2021-03-04 22:14:01

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

Re: GNOME crashes

https://pastebin.com/raw/5UJfbuwf

Try to find: Stopped target GNOME Wayland Session

About that time it crashes (terminates session, according to what I found in journalctl) again.

Anyway, thanks a lot for you time!

Offline

#8 2021-03-04 22:29:31

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,567

Re: GNOME crashes

Mar 04 23:01:18 user systemd[755]: org.gnome.Shell@wayland.service: Failed with result 'core-dump'.
Mar 04 23:01:18 user systemd-coredump[9443]: Process 818 (gnome-shell) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 818:
                                                 #0  0x00007f03ccf52ef5 raise (libc.so.6 + 0x3cef5)
                                                 #1  0x000056476ed49ad9 n/a (gnome-shell + 0x2ad9)
                                                 #2  0x00007f03ccf52f80 __restore_rt (libc.so.6 + 0x3cf80)
                                                 #3  0x00007f03ccf52ef5 raise (libc.so.6 + 0x3cef5)
                                                 #4  0x00007f03ccf3c862 abort (libc.so.6 + 0x26862)
                                                 #5  0x00007f03cdd75084 n/a (libglib-2.0.so.0 + 0x1d084)
                                                 #6  0x00007f03cddcfbad g_assertion_message_expr (libglib-2.0.so.0 + 0x77bad)
                                                 #7  0x00007f03cd1d6f6b n/a (libmutter-7.so.0 + 0xf1f6b)
                                                 #8  0x00007f03cd1a6b88 n/a (libmutter-7.so.0 + 0xc1b88)
                                                 #9  0x00007f03cd3a1d7d _clutter_event_process_filters (libmutter-clutter-7.so.0 + 0x72d7d)
                                                 #10 0x00007f03cd3cb915 n/a (libmutter-clutter-7.so.0 + 0x9c915)
                                                 #11 0x00007f03cd3cc562 _clutter_process_event (libmutter-clutter-7.so.0 + 0x9d562)
                                                 #12 0x00007f03cd3e9ca0 _clutter_stage_queue_event (libmutter-clutter-7.so.0 + 0xbaca0)
                                                 #13 0x00007f03cd26b490 n/a (libmutter-7.so.0 + 0x186490)
                                                 #14 0x00007f03cddabb84 g_main_context_dispatch (libglib-2.0.so.0 + 0x53b84)
                                                 #15 0x00007f03cddffc21 n/a (libglib-2.0.so.0 + 0xa7c21)
                                                 #16 0x00007f03cddab0d3 g_main_loop_run (libglib-2.0.so.0 + 0x530d3)
                                                 #17 0x00007f03cd1b110f meta_run (libmutter-7.so.0 + 0xcc10f)
                                                 #18 0x000056476ed49417 n/a (gnome-shell + 0x2417)
                                                 #19 0x00007f03ccf3db25 __libc_start_main (libc.so.6 + 0x27b25)
                                                 #20 0x000056476ed4960e n/a (gnome-shell + 0x260e)
Mar 04 23:01:16 user gnome-shell[818]: mutter:ERROR:../mutter/src/ui/frames.c:1116:meta_frame_left_click_event: code should not be reached
Mar 04 23:01:16 user gnome-shell[818]: Bail out! mutter:ERROR:../mutter/src/ui/frames.c:1116:meta_frame_left_click_event: code should not be reached

https://gitlab.gnome.org/GNOME/mutter/-/issues/1666

But this will hardly be the pre-login issue.
Did that happen during the provided boot journal as well?

Edit, the bug even references a coincidental https://wiki.archlinux.org/index.php/GD … ite_cursor

Last edited by seth (2021-03-04 22:30:35)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2021-03-05 00:18:58

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

Re: GNOME crashes

I've deleted all journalctl logs and reboot the system: https://pastebin.com/raw/9v9DefBd

I've noticed some weird things:

Mar 05 01:08:19 user gnome-session[420]: gnome-session-binary[420]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user gnome-session-binary[420]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user gnome-session[420]: gnome-session-binary[420]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user gnome-session-binary[420]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user gnome-session[420]: gnome-session-binary[420]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user gnome-session-binary[420]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mar 05 01:08:19 user kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
Mar 05 01:08:19 user gnome-shell[430]: Failed to create backend: No drm devices found
Mar 05 01:08:19 user gnome-session[420]: gnome-session-binary[420]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mar 05 01:08:19 user gnome-session-binary[420]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mar 05 01:08:19 user gnome-session-binary[420]: Unrecoverable failure in required component org.gnome.Shell.desktop
Mar 05 01:08:19 user gdm[339]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 01:08:19 user systemd[1]: session-1.scope: Succeeded.
Mar 05 01:08:19 user systemd-logind[316]: Session 1 logged out. Waiting for processes to exit.
Mar 05 01:08:19 user gdm[339]: Gdm: Child process -413 was already dead.
Mar 05 01:08:19 user gdm[339]: Gdm: Child process -413 was already dead.
Mar 05 01:08:19 user systemd-logind[316]: Removed session 1.

Then I started the GUI manually:

Mar 05 01:08:19 user systemd-logind[316]: New session 3 of user gdm.
Mar 05 01:08:19 user systemd[1]: Started Session 3 of user gdm.

Is it the problem, like you've mentioned above or could it be something else?

Last edited by wannabewalkie (2021-03-05 00:20:54)

Offline

#10 2021-03-05 01:21:46

wannabewalkie
Member
Registered: 2021-03-03
Posts: 6

Re: GNOME crashes

Adding video driver to MODULES and re-generating initramfs have fixed the problem.

The crashing after logging in to will probably be fixed by next Mutter update.

Offline

#11 2021-03-05 07:20:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,567

Re: GNOME crashes

Cool.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB