Bug 203652

Summary: Update notification bubble attached to wrong panel icon
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: pirutAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: berrange, lmacken, majain, mclasen, papapizza
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-11 22:43:55 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:
Bug Depends On:    
Bug Blocks: 150224    
Attachments:
Description Flags
Screenshot of falsely attached update notification bubble none

Description Joachim Frieben 2006-08-22 20:37:51 UTC 
Description of problem:
As the attached screenshot demonstrates, the notification bubble of
the "pup" update manager is slightly displaced. It seems to originate
from the power manager icon whereas it should be attached to the "pup"
icon (actually associated with "yum-updatesd-2.9.4-4").

Version-Release number of selected component (if applicable):
pirut-1.1.9-1

How reproducible:
Always.

Steps to Reproduce:
1. Wait until new updates are available.
2. Log in to "GNOME" session.
  
Actual results:
Notification bubble is "attached" to "g-p-m" notification panel icon.

Expected results:
Notification bubble is "attached" to "pup/yum-updatesd" notification
panel icon.

Additional info:
None.
Comment 1 Joachim Frieben 2006-08-22 20:39:12 UTC 
Created attachment 134671 [details]
Screenshot of falsely attached update notification bubble
Comment 2 Luke Macken 2006-08-23 02:26:35 UTC 
Known issue.  The notification is displayed in a gobject.add_idle() callback, so
I'm not sure why this is still happening.

Jeremy, any ideas?
Comment 3 Jeremy Katz 2006-09-11 21:19:48 UTC 
*** Bug 205805 has been marked as a duplicate of this bug. ***
Comment 4 John (J5) Palmieri 2006-09-11 21:41:11 UTC 
I would say timeout a second or so.  Actually if you are loading up a whole
session it might take a while for the window to be mapped.  This is only an
issue when you first start puplet.  Waiting a few seconds before assaulting the
user witha popup is actually a good idea anyway.  The real fix is to detect when
the window is fully realized.  Perhaps attaching to a mapped signal or something
similar?
Comment 5 Jeremy Katz 2006-09-11 22:43:55 UTC 
Hacked around in CVS, although I expect that a full fix really requires the
notification daemon to dtrt
Comment 6 Jeremy Katz 2006-09-13 14:18:43 UTC 
*** Bug 206254 has been marked as a duplicate of this bug. ***
Comment 7 Mayank Jain 2006-09-13 14:28:17 UTC 
Hi, which library is used to create such popups?
Thanks,
Mayank
Comment 8 Matthias Clasen 2006-09-13 14:34:03 UTC 
Jeremy, don't tell them !!! :-)
Comment 9 Matthias Clasen 2006-09-22 02:38:37 UTC 
*** Bug 207379 has been marked as a duplicate of this bug. ***
Comment 10 Jeremy Katz 2006-09-22 17:28:21 UTC 
*** Bug 207707 has been marked as a duplicate of this bug. ***