[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed

2020-07-28 Thread Elias Rudberg
*** This bug is a duplicate of bug 1820584 ***
https://bugs.launchpad.net/bugs/1820584

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.

** This bug has been marked a duplicate of bug 1820584
   seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888585

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed

2020-07-28 Thread Elias Rudberg
>  * 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/ ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888585

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed

2020-07-27 Thread Sebastien Bacher
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.

** Changed in: seahorse (Ubuntu)
   Importance: Undecided => Low

** Changed in: seahorse (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888585

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed

2020-07-27 Thread linuxien_ref
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888585

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs