indicator-me may crash after service restart

Bug #643906 reported by David Barth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Me Menu
Fix Released
Medium
Cody Russell
indicator-me (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

If the indicator-me-service fails and is restarted by the indicator, the indicator entry may trigger a crasher.

Steps to reproduce:
- load the indicator (indicator-lodaer can help for debugging this)
- killall indicator-me-service (it's automatically restarted by running indicators, like the one just started aboe)
- look at the me menu until it says "Post message..." (or killall again until it says "Post message..."
- clock in the entry and start typing something, after the 1 characted the indicator crashes.

The backtrace shows something is failing in ido while routing a signal. It may come from routing a signal to a previous instance of an entry that should have been disposed since.

Revision history for this message
David Barth (dbarth) wrote :
Changed in indicator-me:
assignee: nobody → Cody Russell (bratsche)
importance: Undecided → Medium
milestone: none → ubuntu-10.10
status: New → Triaged
Revision history for this message
David Barth (dbarth) wrote :

See the related branch where I've added debug messages in the function i connected with the dbusmenuitem destructor.

David Barth (dbarth)
Changed in indicator-me:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-me - 0.2.10-0ubuntu1

---------------
indicator-me (0.2.10-0ubuntu1) maverick; urgency=low

  * New upstream release
    - indicator-me may crash after service restart (LP: #643906)
  * debian/control: depends on latest libindicator-dev (LP: #637692)
 -- Didier Roche <email address hidden> Wed, 22 Sep 2010 18:35:49 +0200

Changed in indicator-me (Ubuntu):
status: New → Fix Released
Omer Akram (om26er)
Changed in indicator-me:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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