indicator-messages blue even though there are no messages

Bug #1234680 reported by Gema Gomez
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
indicator-messages (Ubuntu)
Invalid
High
Unassigned

Bug Description

After an indicator-messages crash the indicator comes back up and shows an empty queue (it lost all the messages, notifications in it) and it is blue. See screen capture attached.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: indicator-messages 13.10.1+13.10.20130930-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.5-0ubuntu1
Architecture: armhf
Date: Sun Oct 6 12:29:50 2013
InstallationDate: Installed on 2013-10-03 (3 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131003)
MarkForUpload: True
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Gema Gomez (gema) wrote :
Revision history for this message
Gema Gomez (gema) wrote :
tags: added: avengers qa-touch rls-s-incoming
Thomas Strehl (strehl-t)
Changed in indicator-messages (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
Revision history for this message
Charles Kerr (charlesk) wrote :

I suspect this behavior's cause is the same as what's causing bug #1234680, which has indicator-message-service dying as it tries to change the message indicator's icon.

Leaving open as a standalone bug for now, pending 1234680's resolution.

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

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

Changed in indicator-messages (Ubuntu):
status: New → Confirmed
Revision history for this message
Ted Gould (ted) wrote :

The issue here is that messaging menu is crashed and it stays crashed. When the list is empty the backend is down. We need to switch the indicators over to upstart jobs to get reliable restarting of the services, which is targeted for 14.04.

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

Are you sure this happens after the service crashed? If so, this is a bug in unity8 (or more likely qmenumodel), which should respawn the service. Alternatively, it should not show the messaging menu at all when the service is down.

Ted, we can respawn without upstart as well. That's what we're doing in libindicator.

I'm asking because this could also be the bug that didn't clear the "blue" status after dismissing messages, which I've just fixed in lp:~larsu/indicator-messages/blue.

Changed in indicator-messages (Ubuntu):
assignee: Charles Kerr (charlesk) → Lars Uebernickel (larsu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue?

Changed in indicator-messages (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
tags: removed: rls-s-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

No reply, closing the bug

Changed in indicator-messages (Ubuntu):
assignee: Lars Uebernickel (larsu) → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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