Bug 157046 - icon highlighting bug on desktop
Summary: icon highlighting bug on desktop
Status: RESOLVED DUPLICATE of bug 152797
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-31 19:23 UTC by thomas klein
Modified: 2008-02-06 01:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description thomas klein 2008-01-31 19:23:57 UTC 
Version:            (using KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

Moving the mouse cursor over an icon produce the highlighting of it.

When moving randomly over multiple icons on the desktop, sometime, the highlight wont disappear as shown here : http://www.lanterne.org/desktop_icon_highlight_bug.jpg
Comment 1 Pino Toscano 2008-01-31 21:29:02 UTC 

*** This bug has been marked as a duplicate of 152797 ***
Comment 2 thomas klein 2008-02-05 20:19:19 UTC 
same bug on kubuntu kde 4.0.1
Comment 3 Pino Toscano 2008-02-05 20:34:41 UTC 
Your problem was _already_ reported, no need to track _two_ bugs.
If the problem is still there, report in the original bug report.

*** This bug has been marked as a duplicate of 152797 ***
Comment 4 thomas klein 2008-02-05 22:50:05 UTC 
hmmm, I don't understand... This bug is still, at least for me, present on my system running kde 4.0.1 and you want me to reopen another "Resolved Bug" ?

Perhaps you prefer a new bug report ?
Comment 5 Sebastian Sauer 2008-02-06 01:22:26 UTC 
From reading http://bugs.kde.org/show_bug.cgi?id=152797#c8 I would assume, that this is fixed in Qt 4.4 which KDE 4.1 will be based on.

That means, that we just can't fix it for KDE 4.0.x and that would explain why it still can be reproduced even with trunk compiled against Qt 4.3.

So, I don't believe to create a new report for that issue does have any effect ;)