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
--
You received this bug notification because you are a member of
** Changed in: indicator-messages (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To
This is not a bug in Geary.
** No longer affects: geary (Ubuntu Quantal)
** Changed in: geary (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
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
** Changed in: geary
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: geary (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
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.
** Attachment added: reproduce-lp1064314.py
** Description changed:
Impact:
libmessaging-menu clients can hit a segfault in some conditions
Test Case:
- No defined testcase, just check that the libmessaging-menu users keep working
(gwibber, geary, empathy, ...)
+ Run the python script from comment #11, with the fixed version it
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
** Also affects: indicator-messages (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: geary (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: indicator-messages (Ubuntu Quantal)
Importance: Undecided = High
** Changed in:
** Changed in: indicator-messages
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage
** Description changed:
+ Impact:
+ libmessaging-menu clients can hit a segfault in some conditions
+
+ Test Case:
+ No defined testcase, just check that the libmessaging-menu users keep working
(gwibber, geary, empathy, ...)
+
+ Regression Potential:
+ Nothing specific, the fix is a simple
** Changed in: indicator-messages
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: geary (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
** Changed in: geary
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage notifications about this
** Changed in: indicator-messages
Assignee: (unassigned) = Lars Uebernickel (larsu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
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
** Changed in: indicator-messages
Importance: Undecided = Critical
** Changed in: indicator-messages
Status:
** Branch linked: lp:~larsu/indicator-messages/lp1064314
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage notifications about
** Changed in: indicator-messages (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage
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
Our ticket is at http://redmine.yorba.org/issues/5984
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064314
Title:
geary crashed with SIGABRT in __libc_message()
To manage notifications about this
21 matches
Mail list logo
