Bug 751055

Summary: applications which launch straight to tray confuse KDE's bouncing launch notification thing
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 23:18:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Adam Williamson 2011-11-03 11:28:46 UTC
when you launch an app in KDE you get a mini version of the app's icon bouncing next to your cursor until it launches. however, if the app launches straight to the tray, this notification system gets confused: the app launches, but the icon just keeps bouncing until it hits a fairly long timeout. to reproduce just launch 'kwikdisk' from System: it loads into the tray almost immediately, but the icon keeps bouncing.

Comment 1 Adam Williamson 2011-11-03 11:28:59 UTC
F16 RC5.

Comment 2 Adam Williamson 2011-11-03 11:29:49 UTC
krandrtray also reproduces this.

Comment 3 Kevin Kofler 2011-11-03 15:33:52 UTC
I think this one needs to be fixed in the relevant .desktop files. AIUI, they need to either disable startup notifications or set an X-DBUS-StartupType which works. (The name is relatively bad because this entry is actually KDE-specific. It used to be X-DCOP-StartupType, but when they moved from DCOP to D-Bus, they just renamed it with s/DCOP/DBUS/ (sic) instead of using X-KDE.) Of course, another question is why the default startup notification type doesn't work for system tray icons. (Does it wait for a window to come up?)

Comment 4 Fedora End Of Life 2013-01-16 19:31:12 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 23:18:54 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.