Version: (using KDE 4.0.5) Installed from: Fedora RPMs OS: Linux When you run accros tray, hint boxes appear - it's OK, but sometimes 2 hint boxes apper - one, that shows correct info and second empty (black) one. The empty hint box either appears above all windows (most visible case) or below the current visible window - than you can see, that tray shading is not display correctly (there is black line on the edge between tray and window)
could you provide a screenshot too? Thanks.
Created attachment 25635 [details] tray between skype and knapshot is not displayed correctly
Created attachment 25636 [details] bad redrawing Here you can see, that background window is not redrawn correctly
Its there now. Thanks for reminder, I couldn't find a way how to add attatchment when I was submitting this bug. On Thu, Jun 26, 2008 at 11:54 AM, FiNeX <finex@finex.org> wrote: [bugs.kde.org quoted mail] Its there now. Thanks for reminder, I couldn't find a way how to add attatchment when I was submitting this bug.<br><br><div class="gmail_quote">On Thu, Jun 26, 2008 at 11:54 AM, FiNeX <<a href="mailto:finex@finex.org">finex@finex.org</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br> You reported the bug, or are watching the reporter.<br> <br> <a href="http://bugs.kde.org/show_bug.cgi?id=164995" target="_blank">http://bugs.kde.org/show_bug.cgi?id=164995</a><br> finex finex org changed:<br> <br> What |Removed |Added<br> ----------------------------------------------------------------------------<br> CC| |finex finex org<br> <br> <br> <br> ------- Additional Comments From finex finex org 2008-06-26 11:54 -------<br> could you provide a screenshot too?<br> <br> Thanks.<br> </blockquote></div><br>
re comment #2: between 4.0.5 and trunk tons of changes went into the systray. but even if you would use current trunk, it would be still a duplicate of bug #164786 re comment #3: looks like an upstream-bug with your graphic-card vendor/driver (nvidia, right? probably it helps here already if you update your driver). Anyway, there is not much we can do.