Ever since I accepted the system upgrade on the morning of the 27th, I have been experiencing repeated abrupt logouts that map precisely to segfaults and general protection faults that appear in /var/log/messages. The latest is at 12:21:45 today.
See comments below, including my gzipped /var/log/messages.
The segfault at Dec 28 16:13:00 happened at the same second when someone responded to me from Slack, which I had minimized.
Many of these segfaults/logouts have happened at the instant when gnome-shell-pomodoro has reached the end of a pomodoro.
I'm 99% sure I have experienced this issue when neither Slack nor gnome-shell-pomodoro was running. I never experienced this before upgrading on the morning of the 27th.
In addition to tracking down the bug for the sake of the project, I'm hoping you can help me with some workaround so that my wonderful new Librem will be useful again. I contacted Purism support and they sent me here.
I'm rep on Keybase. I have a core dump file I found in my home directory that I can share with someone if I know what key to encrypt it to.
I have uninstalled Slack at Mladen's suggestion. I will see if that helps matters.
Third-party software includes GitKraken, TiddlyDesktop, Mailspring, Geary, Keybase, Yubico Authenticator. I have qml-module-io-thp-pyotherside/experimental,now 1.4.0-2 amd64 installed since Yubico Authenticator depends on that.
Attached is the output of apt list --installed.
Just had two logouts in a row pairing with consecutive gnome-shell-pomodoro notifications a few minutes apart.
Jan 1 11:37:46 sans gnome-shell[20943]: g_value_set_object: assertion 'g_value_type_compatible (G_OBJECT_TYPE (v_object), G_VALUE_TYPE (value))' failed Jan 1 11:37:46 sans gnome-shell[20943]: g_value_set_object: assertion 'G_IS_OBJECT (v_object)' failed Jan 1 11:37:46 sans kernel: [437686.951777] gnome-shell[20943]: segfault at 30 ip 00007f37b8133c9f sp 00007ffced00d968 error 4 in libgobject-2.0.so.0.5400.2[7f37b80fe000+52000] Jan 1 11:37:46 sans file-roller[11352]: Error reading events from display: Broken pipe Jan 1 11:37:46 sans gnome-pomodoro[21031]: Error reading events from display: Broken pipe Jan 1 11:37:46 sans gnome-terminal-[22525]: Error reading events from display: Broken pipe Jan 1 11:37:46 sans gnome-session[20912]: gnome-session-binary[20912]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jan 1 11:37:46 sans org.gnome.Shell.desktop[20943]: (EE) Jan 1 11:37:46 sans org.gnome.Shell.desktop[20943]: Fatal server error: Jan 1 11:37:46 sans org.gnome.Shell.desktop[20943]: (EE) failed to read Wayland events: Broken pipe Jan 1 11:37:46 sans org.gnome.Shell.desktop[20943]: (EE) ... Jan 1 11:54:26 sans kernel: [438687.419021] gnome-shell[13644]: segfault at 100000001 ip 00007f7552886c9f sp 00007ffce0871a28 error 4 in libgobject-2.0.so.0.5400.2[7f7552851000+52000] Jan 1 11:54:26 sans gnome-pomodoro[13745]: Error reading events from display: Broken pipe Jan 1 11:54:26 sans gnome-terminal-[14314]: Error reading events from display: Broken pipe Jan 1 11:54:26 sans org.gnome.Shell.desktop[13644]: (EE) Jan 1 11:54:26 sans org.gnome.Shell.desktop[13644]: Fatal server error: Jan 1 11:54:26 sans org.gnome.Shell.desktop[13644]: (EE) failed to read Wayland events: Broken pipe Jan 1 11:54:26 sans org.gnome.Shell.desktop[13644]: (EE)
I have the Xwayland core dump for the second one saved, along with my Xwayland binary, if helpful. Just need a GPG public key to encrypt it.
Please let me know what further information I can provide to move toward solving this problem with my brand new computer running the bundled OS.
Obviously I will need to avoid using gnome-shell-pomodoro for now. I have quit that program.
My /var/log/messages shows speech-driver segfaulting all over the place yesterday, even overnight while my screen was locked (and I wasn't running anything in particular, maybe web and email were up).
I see the latest gnome-pomodoro has a fix regarding gnome-shell segfaults:
https://github.com/codito/gnome-pomodoro/commit/fe52244d43cc8fbd0c1752d51693501f3fb32f84
I've not been getting them while keeping both Slack and gnome-pomodoro off. After rolling with this new version of gnome-pomodoro for a while, if things are still stable I'll try Slack and see what happens. Thanks very much for your team's assistance.
Sure:
$ dpkg -l gnome-shell-pomodoro Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==================================-======================-======================-========================================================================= ii gnome-shell-pomodoro 0.13.4-1 amd64 GNOME Shell time-management app
To be clear, I seem to have picked up the fix with the recent gnome-shell-pomodoro update that I had just installed at the time of my last comment. I have not had an "auto logout" (gnome-shell crash) since.
I was having some remaining (perhaps unrelated) problems with temporary but long freezes of the mouse cursor, which seems to have disappeared when I quit the Mailspring email client I had been using and began using Geary instead. Perhaps there is a problem somewhere in the Electron stack used by Mailspring and Slack.
I seem to have picked up the fix with the recent gnome-shell-pomodoro update
Cool - just checking it was fixed with 0.13.4-1 :)