This bug was fixed in the package accountsservice -
0.6.55-0ubuntu12~20.04.1
---------------
accountsservice (0.6.55-0ubuntu12~20.04.1) focal; urgency=medium
* Backport from groovy to focal.
accountsservice (0.6.55-0ubuntu12) groovy; urgency=medium
* Cherry-pick from unstable.
* Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)
-- Iain Lane <iain.l...@canonical.com> Tue, 05 May 2020 17:05:26 +0100
** Changed in: accountsservice (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1843982
Title:
Various programs crashed with SIGSEGV in g_str_hash() from
g_hash_table_lookup() from update_user()
Status in accountsservice:
Fix Released
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Focal:
Fix Released
Status in accountsservice package in Debian:
Confirmed
Bug description:
[ Description ]
When accountsservice's daemon is restarted - particularly when there
is a user configured for auto login - it can cause code using its
library to crash. This is bad because gnome-shell is one of those
users which crashes.
[ QA ]
Configure a user for automatic login in gnome-shell.
Update to this SRU, and then *restart your system*. The crash is in
the library part, and so you will still see it if programs loaded the
buggy version. Restarting is the easiest way to make sure you're not
on it.
Restart accounts-daemon.service (sudo systemctl restart accounts-
daemon.service) a few times, leaving several seconds between each
attempt.
See that it crashes if you don't have this SRU, and doesn't if you do
have it.
---
Test that fast user switching still works properly.
---
Take a look at the error reports listed below and hopefully see them
not occurring (barring the usual noise) with the SRU.
[ Regression potential ]
We think this is safe - it tells clients that the daemon is away when
it quits, and is back when it comes back. They should get appropriate
signals to indicate this. Nevertheless, these signals are sent when
they weren't before now, so that could cause problems. Watch out for
errors creeping up with this SRU.
We wondered upstream whether some more protections might be needed.
I'm thinking that those should be *additional* safety rails around
this fix, but it could actually be that more is needed and this fix
isn't complete.
[ Original report ]
https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e9696933336c7
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 10:29:16 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2019-05-24 (112 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=nb_NO.UTF-8
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
