gwibber-bugs team mailing list archive
-
gwibber-bugs team
-
Mailing list archive
-
Message #01963
[Bug 436554] Re: Integration with indicator-applet not working properly
** No longer affects: null
--
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/436554
Title:
Integration with indicator-applet not working properly
Status in Gwibber:
Fix Released
Bug description:
I've noticed some quirks with Gwibber 2 in Karmic and indicator-applet
(or indicator-messages now).
1) For some reason the gwibber entry in the menu loses the separator
below when gwibber is open. This makes the menu inconsistent and
weird.
2) Quitting the gwibber GUI does not close gwibber-daemon. Because of
this, indicator-applet still thinks gwibber is running. I don't know
if this is intentional or not, but I think if the user clicked on
"quit" he expects gwibber to close *for good*, not invisibly run in
the background.
3) "Close to tray" is not working. Gwibber closes completely even when
this option is checked. For the indicator-session, the issue (2) more
or less "compensates" this error, but the gwibber GUI is re-opened
(instead of simply restored) when the gwibber entry in indicator-
applet is clicked, which is sub-optimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/436554/+subscriptions