Konversation menus not re-connected to the unity panel after a crash or restart
Bug #761482 reported by
David Barth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity Foundations |
Invalid
|
Medium
|
Aurélien Gâteau | ||
appmenu-qt |
Fix Released
|
High
|
Aurélien Gâteau |
Bug Description
I'm running konversation, and once i restart the unity-panel-
affects: | libdbusmenu-qt → appmenu-qt |
Changed in unity-foundations: | |
status: | Confirmed → Invalid |
Changed in appmenu-qt: | |
importance: | Undecided → High |
Changed in appmenu-qt: | |
status: | Confirmed → Fix Committed |
Changed in appmenu-qt: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In addition, I see a lot of those debug messages on the console after the panel service is restarted:
void DBusMenuExporte rPrivate: :fillLayoutItem (DBusMenuLayout Item*, QMenu*, int, int, const QStringList&): No id for action