geary crashed with SIGABRT in __libc_message()

Bug #1064314 reported by schoobami
68
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Geary
Fix Released
Undecided
Unassigned
Messaging Menu
Fix Released
Critical
Lars Karlitski
geary (Ubuntu)
Invalid
Medium
Unassigned
indicator-messages (Ubuntu)
Fix Released
High
Unassigned
Quantal
Won't Fix
High
Unassigned

Bug Description

Impact:
libmessaging-menu clients can hit a segfault in some conditions

Test Case:
Run the python script from comment #11, with the fixed version it should hit an error

Regression Potential:
Nothing specific, the fix is a simple one for a understood bug
---

Reentered my credientials because of new generated password with 2-step-verification

--
Description: Ubuntu quantal (development branch)
Release: 12.10
--

 Installed: 0.2.0-0ubuntu2
  Candidate: 0.2.0-0ubuntu2
  Version table:
 *** 0.2.0-0ubuntu2 0
        500 http://se.archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status
     0.2.0-0~734~quantal1 0
        500 http://ppa.launchpad.net/yorba/daily-builds/ubuntu/ quantal/main i386 Packages

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: geary 0.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Tue Oct 9 12:54:36 2012
ExecutablePath: /usr/bin/geary
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: geary
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: geary
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: geary crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-09-30 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
schoobami (adam-shiervani) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb53e3a68 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xa7e3328) at malloc.c:5007
 standard_free (mem=0xa7e3328) at /build/buildd/glib2.0-2.34.0/./glib/gmem.c:98
 g_free (mem=0xa7e3328) at /build/buildd/glib2.0-2.34.0/./glib/gmem.c:252
 g_error_free (error=0xa623430) at /build/buildd/glib2.0-2.34.0/./glib/gerror.c:476

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in geary (Ubuntu):
importance: Undecided → Medium
summary: - geary crashed with SIGABRT in raise()
+ geary crashed with SIGABRT in __libc_message()
tags: removed: need-i386-retrace
Revision history for this message
Jim Nelson (yorba-jim) wrote :

Looking at the stack trace, it appears Geary is dying inside of Messaging Menu:

#8 0xb58ce595 in export_menus_and_actions (source=0x0, res=0xa77a530, user_data=0xa848090) at messaging-menu.c:203

It's possible Geary is doing something wrong here, but maybe the Messaging Menu guys could take a look and offer a clue?

Revision history for this message
Jim Nelson (yorba-jim) wrote :
Omer Akram (om26er)
Changed in indicator-messages:
assignee: nobody → Lars Uebernickel (larsu)
Revision history for this message
Lars Karlitski (larsu) wrote :

Definitely a bug in libmessaging-menu: `error` is not cleared before using it again.

Thanks for reporting this!

Changed in indicator-messages:
milestone: none → 12.10.5
importance: Undecided → Critical
status: New → In Progress
Changed in indicator-messages (Ubuntu):
status: New → Triaged
Omer Akram (om26er)
Changed in indicator-messages (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in geary (Ubuntu):
status: New → Confirmed
Jim Nelson (yorba-jim)
Changed in geary:
status: New → Confirmed
Lars Karlitski (larsu)
Changed in indicator-messages:
status: In Progress → Fix Committed
Changed in indicator-messages (Ubuntu Quantal):
importance: Undecided → High
status: New → Triaged
Lars Karlitski (larsu)
Changed in indicator-messages:
status: Fix Committed → Fix Released
description: updated
Changed in indicator-messages (Ubuntu Quantal):
status: Triaged → In Progress
Revision history for this message
Steve Langasek (vorlon) wrote :

> No defined testcase

If this is an understood bug, the test case should explain how to reproduce that bug and verify that it's fixed.

Revision history for this message
Lars Karlitski (larsu) wrote :

The crash is triggered when the same process creates a MessagingMenuApp for the same desktop id more than once. The attached python script produces the crash.

This happened in geary because of bug #1065169.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in geary (Ubuntu Quantal):
status: New → Confirmed
Jim Nelson (yorba-jim)
Changed in geary:
status: Confirmed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello schoobami, or anyone else affected,

Accepted indicator-messages into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/indicator-messages/12.10.5-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in indicator-messages (Ubuntu Quantal):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

This is not a bug in Geary.

no longer affects: geary (Ubuntu Quantal)
Changed in geary (Ubuntu):
status: Confirmed → Invalid
Changed in indicator-messages (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in indicator-messages (Ubuntu Quantal):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.