[Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
After some more digging and having reproduced the issue a few more times, here is what seems to happen. Seahorse is running, using the avahi library. Seahorse has called avahi_glib_poll_new() and some AvahiTimeout timeouts have been created. Then things are stopped because the computer is about to be rebooted. Seahorse is closing down and therefore does some cleanup, among other things it calls avahi_glib_poll_free() which calls cleanup_timeouts() which destroys all the timeouts. However, after the timeouts were destroyed, there still exists a pointer to one of those timeouts in the dispatch_timeout member in a ConnectionData struct. For some reason the dispatch_timeout_callback() function is called at this point, and it does "ConnectionData *d = userdata" and that ConnectionData struct has inside it a dispatch_timeout pointer which is now invalid because the timeout was destroyed, its memory was freed, as a result of the avahi_glib_poll_free() call earlier. dispatch_timeout_callback() passes the ConnectionData *d to request_dispatch() which calls timeout_update() passing the invalid d->dispatch_timeout pointer, which is then used and happens to point to some garbage which gives the assertion failure. Not sure exactly how to fix the problem, but it seems bad that pointers to destroyed data structures are still lying around, maybe things should be destroyed in a different order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
I added some extra debug output in avahi and waited for the error to
happen again, in this way found out that the assertion failure happens
when the time_event_queue_root(q) call gives NULL so that the "else"
part is used in update_timeout() in avahi-core/timeeventq.c:
static void update_timeout(AvahiTimeEventQueue *q) {
AvahiTimeEvent *e;
assert(q);
if ((e = time_event_queue_root(q)))
q->poll_api->timeout_update(q->timeout, >expiry);
else
q->poll_api->timeout_update(q->timeout, NULL); <-- assertion failure
inside this call
}
So time_event_queue_root(q) gives NULL which means that q->prioq->root
is NULL. Why would that happen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820584
Title:
seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
Assertion `!t->dead' failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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
*** 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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Related: bug #1888585 ( https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585 ) The error "seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed." is listed with hundreds of occurrences each day at https://errors.ubuntu.com/ but there is no bug report assigned to it there, the "Bug report" column is empty. Should it be associated with this bug report, or perhaps with bug #1888585 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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
> * 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] [NEW] seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed
Public bug reported: 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 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- 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 1824705] [NEW] gnome-sound-recorder crashes when trying to play sound clip
Public bug reported: When I open the "Sound Recorder" program (gnome-sound-recorder) it shows a list of sound clips that I have recorded earlier. If I click the play button next to any of the sound clips, the program crashes. The gnome-sound-recorder version used is 3.28.1-4 Expected behavior: sound clip is played. Observed behavior: program crashed, no sound played. This problem is reproducible, it crashes like this every time I try it. Here is some of the info from the .crash file that was created in the /var/crash/ directory: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:18:00 2019 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1542889273 ProcCmdline: /usr/bin/gjs /usr/bin/gnome-sound-recorder More detailed info is available in the attached file. ** Affects: gnome-sound-recorder (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Part of crash file that was generated in /var/crash directory" https://bugs.launchpad.net/bugs/1824705/+attachment/5255688/+files/truncated_usr_bin_gjs-console.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824705 Title: gnome-sound-recorder crashes when trying to play sound clip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1824705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823404] [NEW] Memory errors reported by valgrind for gdebi-gtk
Public bug reported: This is for gdebi version 0.9.5.7+nmu2. When running gdebi-gtk through valgrind, for example like this: valgrind gdebi-gtk -h that shows lots of memory errors, for example: - Conditional jump or move depends on uninitialised value(s) - Use of uninitialised value of size 8 - Invalid read of size 4 - Address 0x4e68020 is 304 bytes inside a block of size 2,208 free'd and so on. So there are bugs in the code that can cause the program to crash. One example of a used that got a crash is here: https://askubuntu.com/questions/1131516/gdebi-gtk-segmentation-fault-core-dumped ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823404 Title: Memory errors reported by valgrind for gdebi-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1823404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
