i have the exact issue (and version) as comment #2. on Maverick. -- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/587565
Title: gwibber-services remain after exiting Gwibber Status in Gwibber: Fix Released Bug description: finding multiple instances of gwibber-service running, when it was presumed these are closed when gwibber exits. Apparently using up twitter api calls. gwibber most likely should be able to detect if an instance of gwibber-service is already running, and or offer to start/restart the single instance of gwibber-service if gwibber is unloaded, or then relaunched later in the session. In Lucid, at this time, when closing gwibber from anything but the "Gwibber > Quit", gwibber-service appears to remain running. Relaunching gwibber appears to also generate new instances of gwibber-service, eating up api calls to to twitter, etc. This can be reproduced albeit inconsistently. If I close gwibber from the Gwibber >Quit option within gwibber, all instances of gwibber close properly. However clicking the (x) from gwibber's title-bar closes gwibber, but all gwibber-service processes remain. These processes continue using api calls to twitter. This because apparent when I relaunch gwibber or another client and discover I've exceeded twitter api refresh requests. After quitting gwibber via the (x): root@mobuntu:~# ps ax |grep gwib 1559 ? SLl 13:43 /usr/bin/python /usr/bin/gwibber-service 32219 ? S 0:19 /usr/bin/python /usr/bin/gwibber-service 32220 ? R 0:20 /usr/bin/python /usr/bin/gwibber-service 32282 pts/0 S+ 0:00 grep --color=auto gwib To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/587565/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
