seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed

[Elias Rudberg]

This bug is seen in the list at https://errors.ubuntu.com/ where it says: seahorse -- Ubuntu 20.04 -- seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed.

According to the list at https://errors.ubuntu.com/ it occurred 3201 times the past week, so it clearly happens to many people and not only me, but there is still no bug report associated with it. Therefore I am making this bug report now, hoping this can be associated with the bug listed at https://errors.ubuntu.com/ and help developers become aware of the problem.

This is for Ubuntu 20.04.

Package: seahorse 3.36-1
PackageArchitecture: amd64

[linuxien_ref (untruclong-durabombarder)]

Hi,

+1

For me :
3 installations Ubuntu 20.04 on 3 differents machines and a lot of random seahorse crashes.
Common point : My profile, my keys.
But it happens also with other users.

When we know seahorse functions, we can be afraid about a possible security issue :(

his is for Ubuntu 20.04.

Package: seahorse 3.36-1
PackageArchitecture: amd64

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* the issue seems similar to bug #1820584

This will help us to find and resolve the problem.

[Elias Rudberg (eliasrudberg)]

> * Is this reproducible?

I don't have an exact way to reproduce it but it happens hundreds of times each day, presumably for many different users, as seen at https://errors.ubuntu.com/

However, although the "seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed." error is listed there at https://errors.ubuntu.com/ as one of the most frequent crashes, it has no bug report assigned to it there. How can we associate the error at https://errors.ubuntu.com/ to this bug report?

I see that the importance was set to "low" -- is that really a good idea given that this is one of the most frequent crashes at https://errors.ubuntu.com/ ?

[Elias Rudberg (eliasrudberg)]

Looking at the code it seems the assertion that was triggered is in the source code of the avahi package, so it probably makes sense to mark this as a duplicate of bug #1820584 for avahi.