Bug 473967 - Firefox plasma icon stops responding during KDE session
Summary: Firefox plasma icon stops responding during KDE session
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-01 16:41 UTC by Sammy
Modified: 2009-05-26 16:23 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-26 16:23:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sammy 2008-12-01 16:41:16 UTC
One of the irritating problems I am having with KDE-4.1.3 on F9 is this:

When I first login the firefox icon on the desktop (plasma) works fine
in starting firefox when clicked on. Exiting and restarting firefox works
most of the time too.

BUT at least once or twice a day the icon becomes unresponsive to clicks.
Nothing happens.....HOWEVER if one checks the running processes everytime
you click on the icon a new process starts but none of them show on my
screen!! Login out and back in solves it. Killing all the firefox sessions
does not.

Also, which may be related is that if as an ordinary user I su to root from
konsole window and start a KDE application like konqueror it does not show
on my screen even though the application is running. This happens with all
applications. Is there a problem with setting the terminal?

Thanks

Comment 1 Steven M. Parrish 2009-02-06 15:23:40 UTC
Is this still an issue with 4.1.4?

Comment 2 Sammy 2009-02-06 17:06:51 UTC
Yes, but not for F10 and F11 since there is an esd patch (and gtk patch)
that fixes this problem and is integrated in to the versions in F10 and
F11. I applied the patch to esd and have not had this problem since. If
no one else is complaining you can let the bug die.
Thanks

Comment 3 Steven M. Parrish 2009-05-26 16:23:06 UTC
As requested am going to kill this one. F9 is just about EOL and its not an issue with F10+


Note You need to log in before you can comment on or make changes to this bug.