seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not sure what I'm doing.
I did close my laptop (Macbook Pro mid-2010) lid, instead of closing Ubuntu.
It's been over 24 hours since I did that and now I'm just opening again.
I do not have it set to require my password when I reopen my laptop.
Let me know if I can provide more info.
Thanks for your awesome product!
-Bob.
<email address hidden>
----
# lsb-release -rd
Description: Ubuntu Disco Dingo (development branch)
Release: 19.04
# apt-cache policy seahorse
seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
*** 3.32-1 500
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: seahorse 3.32-1
ProcVersionSign
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 1 19:24:19 2019
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2019-03-30 (3 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
ProcCmdline: /usr/bin/seahorse --gapplication-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: seahorse
StacktraceTop:
__assert_fail_base (fmt=0x7f2fc9952588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__GI___assert_fail (assertion=
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1820584, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.