FS#58602 - [js52] coredumps in gnome-shell

Attached to Project: Arch Linux
Opened by Tobias Munk (schmunk) - Tuesday, 15 May 2018, 08:36 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 31 January 2019, 18:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Gnome3 frequently restarts since the last update

Additional info:
* GNOME Shell 3.28.2
* see also attached core dump

journalctl-log just before the dump...

May 15 10:29:23 xps-15 kernel: pool[8269]: segfault at 0 ip 00007f8e69362661 sp 00007f8dc970ca18 error 4 in libc-2.27.so[7f8e69208000+1b3000]
May 15 10:29:23 xps-15 systemd[1]: Started Process Core Dump (PID 8270/UID 0).
-- Subject: Unit systemd-coredump@7-8270-0.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-coredump@7-8270-0.service has finished starting up.
--
-- The start-up result is RESULT.
May 15 10:29:24 xps-15 polkitd[541]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.670, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from bus)
May 15 10:29:24 xps-15 gnome-session[1365]: gnome-session-binary[1365]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
May 15 10:29:24 xps-15 gnome-session-binary[1365]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
May 15 10:29:24 xps-15 systemd-coredump[8271]:

Steps to reproduce:
* "just" using Gnome
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 31 January 2019, 18:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  gnome-shell 3.28.3
Comment by Tobias Munk (schmunk) - Tuesday, 15 May 2018, 09:40 GMT Comment by Christopher Davis (brainblasted) - Thursday, 31 January 2019, 18:16 GMT
This should be fixed - the GitLab issue has since been closed.

Loading...