inhibit exit if the indicator is present

Bug #353112 reported by Ken VanDine
54
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-applet (Ubuntu)
Fix Released
Medium
Ted Gould
pidgin-libnotify (Ubuntu)
Fix Released
High
Ted Gould

Bug Description

Binary package hint: pidgin-libnotify

By default we now disable the pidgin icon in the notification area and rely on the message indicator applet for access to the buddy list. This works fine once you access the buddy list from the indicator applet, but if you close the buddy list window before accessing pidgin from the indicator applet pidgin exits.

This is not only confusing, but not very intuitive. In our default configuration (with the indicator applet), pidgin should not exit unless you chose Buddies->Quit in the buddy list window. Clicking the "X" should just hide the window.

However, there are other configurations users might have that would leave them without a way to access the buddy list at all. If for example a user of xubuntu closes the buddy list, it gets hidden and he has know way to raise that buddy list again. Launching pidgin a second time doesn't help, it just detects pidgin is running and exits.

To address the scenario where there is no indicator, we should be able to check if the indicator is present (bug 352616) and inhibit exit if it is. If not, closing the buddy list will actually exit.

Related branches

Changed in pidgin-libnotify (Ubuntu):
assignee: nobody → ted-gould
status: New → Confirmed
Changed in pidgin-libnotify (Ubuntu):
importance: Undecided → High
Ted Gould (ted)
Changed in pidgin-libnotify (Ubuntu):
milestone: none → ubuntu-9.04
Changed in indicator-applet (Ubuntu):
assignee: nobody → ted-gould
importance: Undecided → Medium
milestone: none → ubuntu-9.04
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-applet - 0.1.5-0ubuntu1

---------------
indicator-applet (0.1.5-0ubuntu1) jaunty; urgency=low

  * debian/control: Switching libindicate0 to libindicate1 to express
    the fact that the binary compatibility is broken.
  * debian/libindicate0.install changed to debian/libindicate1.install
  * New upstream version:
    * Adds new API for detecting interests of various listeners. Implemented
      on both client and server side. (LP: #353112)
    * Makes it so that all objects down to the menu now use the gtkstyle
      naming from FUSA to ensure that they all pick up the theme hacks that
      are set for FUSA. (LP: #334490)
    * Explicitly sets the about window's window icon. (LP: #356437)

 -- Ted Gould <email address hidden> Fri, 03 Apr 2009 15:09:33 -0500

Changed in indicator-applet (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pidgin-libnotify - 0.14-1ubuntu8

---------------
pidgin-libnotify (0.14-1ubuntu8) jaunty; urgency=low

  * /debian/patches/indicate.patch:
    * Putting the notifications for a particular conversation
      into a list and closing the entire list when the
      conversation is focused to clear out possible queued
      notifications (LP: #351670)
    * Making it so that indicators and notifications from chats
      also wait from indicating for notifing when the account
      has just connected.
    * Do not make headers have protected ampersands and other HTML-isms
      in the strings. Patch by Cody Russell. (LP: #356147)
    * Use the libindicate interests interface to determine when there
      is someone looking at pidgin with the ability to control visibility
      of the application. Control it if so. (LP: #353112)
    * Change it so that the buddy information is stored in the callback
      instead of user data. Merging in show_button.patch.
  * /debian/control: libindicate 0.1.5
  * /debian/patches/show_button.patch: Moved into indicate.patch

 -- Ted Gould <email address hidden> Tue, 31 Mar 2009 08:23:33 -0500

Changed in pidgin-libnotify (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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