[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Andrea Corbellini
Thanks for your help making Ubuntu better. This bug was filed using an outdated version of libglib (yours is 2.36.0-1ubuntu1, latest is 2.36.0-1ubuntu2). This is the most probable reason why the retrace failed. Because the latest version of libglib may have fixed this bug, I'm invalidating it.

[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Jim Nelson
Andrea, can you provide a link to the ticket or commit for the fixed bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1165576 Title: geary crashed with SIGABRT in raise() To manage notifications

[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Andrea Corbellini
Jim, the bug hasn't been fixed upstream. It has been patched in Ubuntu, see: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/saucy/glib2.0/saucy/revision/193/gobject/gtype.c (the patch contains links to two tickets in the Gnome bug tracker) -- You received this bug notification because

[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Jim Nelson
The two tickets pointed to by that patch are dealing with adding interfaces to an class after init, and much of the discussion has to do with C# (and presumably Mono) and gtkmm (C++) dealing with this problem. As far as I know, Vala doesn't suffer from this problem. We have no C# or C++ code in

[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Andrea Corbellini
** Patch added: dependencies.diff https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1165576/+attachment/3669187/+files/dependencies.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1165576

[Bug 1165576] Re: geary crashed with SIGABRT in raise()

2013-05-07 Thread Andrea Corbellini
The problem is that Apport cannot build retraces for packages that are no longer in the archive, so the only way to obtain useful information is to let the crash happen again and let the user file a new bug report. By the way, glib2.0 was the only package I've checked. Probably there are other