Description of problem: If you start Firefox from the KDE menu, the window comes up fairly quickly, but the startup notification keeps bouncing until it times out (about 30 seconds). Version-Release number of selected component (if applicable): firefox-3.0-0.54.beta5.fc9.i386 How reproducible: Every time Steps to Reproduce: 1. Start Firefox from the KDE menu Actual results: Bouncing firefox icon on cursor for about 30 seconds Expected results: Bouncing firefox should go away after window opens
This is unfortunately problem with KDE -- there is not enough feedback between the non-KDE application being started and KDE notification system.
But what can we do in KDE about that?
Did a search of bugs.kde.org could not find a similar report. Please file an upstream report for this issue and update this report with upstream info. Thanks Steven
Does firefox not use startup-notification?
Apparently not. If missing startup-notification is not considered a bug, it should at least be considered a feature request. Nothing kde can do here (afaict) -> firefox. firefox folks are welcome to close wontfix.
According to https://bugzilla.mozilla.org/show_bug.cgi?id=223492 startup-notification should have been fixed in the November last year.
Yeah, what makes you think it doesn't have startup notification support? It does, we've already uncovered (and fixed) bugs in metacity because of it.
*shrug*, I naively figured no (direct) deps on startup-notification implied no support. My bad. At this point all we have is finger pointing, both kde4 and firefox claim to support startup-notification. So, now we've gotta figure out how to debug it sufficiently to determine where things are going wrong. Fwiw, this only happens with firefox, thunderbird seems fine. For giggles I may try firefox2 and/or some other xulrunner-based apps. Regardless, I'll help take the torch on the kde-side of things (and reassign accordingly). Any input from "the other side" would be appreciated. Mary, could you report this to upstream bugs.kde.org? We'll see what they have to say. (Otherwise, I'll do when I have banked enough round-tuits).
The no deps thing is fallout from bug 443015 (see also bug 443112). But it is properly built and linked and everything. I'd imagine since KDE supports notification, something else on the spin would bring it in. If not, then this could potentially be the cause of the bug?
Maybe? What I'm using currently is $ rpm -q xulrunner firefox xulrunner-1.9-0.54.beta5.fc9.x86_64 firefox-3.0-0.54.beta5.fc9.x86_64
So should I file this upstream or not?
Re: comment #11 Mary, yes, please.
Done.
Mary, Can you update this report with the info from your upstream bug report. Thanks, Steven
It's included in this bug's metadata, but okay, here is the direct link to the upstream bug: http://bugs.kde.org/show_bug.cgi?id=161109 No upstream activity yet ...
D'oh my bad, missed it when I looked over the bug.
*** This bug has been marked as a duplicate of 445543 ***