Bug 701795

Summary:	Getting each notification 4 times
Product:	[Fedora] Fedora	Reporter:	Marcus Nitzschke <kenda>
Component:	gwibber	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	maxx, mikem, scampa.giovanni, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gwibber-3.1.0-1.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-27 23:54:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcus Nitzschke 2011-05-03 21:27:26 UTC

Description of problem:
I'm getting each notification four times. This leeds to an overhead of popup notifications.

Version-Release number of selected component (if applicable):
3.0.0.1

Steps to Reproduce:
1. Start Gwibber
2. Create an account
3. Minimize Gwibber to tray
4. Wait for new messages
  
Actual results:
Each new message leads to four identical notification popups.

Expected results:
Should only lead to one notification.

Comment 1 Tom "spot" Callaway 2011-05-11 18:04:08 UTC

*** Bug 703923 has been marked as a duplicate of this bug. ***

Comment 2 Mike McLean 2011-06-14 14:35:56 UTC

Same issue here, except 3x instead of 4. Also get tray icons for each message if I don't click on them when I pop up (not cumulative, just three tray icons for messages, plus the main gwibber one).

Comment 3 Mike McLean 2011-06-14 14:48:03 UTC

restarted and now it's four. Seems to match the number of copies of /usr/bin/gwibber-service that are running.

Comment 4 Mike McLean 2011-06-14 16:21:35 UTC

I killed off all but one of the gwibber-service processes. It helped temporarily, but eventually an extra one was spawned.

Comment 5 Tom "spot" Callaway 2011-06-14 16:30:24 UTC

Yeah. This is because gwibber is designed to be "multi-threaded" by spawning off multiple server tasks, and unfortunately, each one of them is handling notifications. In a very initial glance, there did not seem to be a clean way to resolve this, without redesigning the core.

Comment 6 Mads Villadsen 2011-06-14 18:11:01 UTC

According to a comment here:

https://bugs.launchpad.net/gwibber/+bug/777476

the problem seems to be solved with gwibber 3.1.0.

I haven't had a chance to try it out myself, though.

Comment 7 Tom "spot" Callaway 2011-06-14 19:43:32 UTC

3.1.0 looks like it doesn't do it anymore. Please test the update (coming right up) and give karma.

Comment 8 Fedora Update System 2011-06-14 20:17:08 UTC

gwibber-3.1.0-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/gwibber-3.1.0-1.fc14

Comment 9 Fedora Update System 2011-06-14 20:17:17 UTC

gwibber-3.1.0-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/gwibber-3.1.0-1.fc15

Comment 10 Fedora Update System 2011-06-15 18:26:33 UTC

Package gwibber-3.1.0-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gwibber-3.1.0-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/gwibber-3.1.0-1.fc15
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2011-06-27 23:54:29 UTC

gwibber-3.1.0-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2011-06-27 23:55:58 UTC

gwibber-3.1.0-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.