Summary: | Dark / Black panel on second login after installation when running without compositing (Air theme) | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Eike Hein <hein> |
Component: | panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 4ernov, a.samirh78, andresbajotierra, bruno.leon, cacouret, daniel, echidnaman, groszdanielpub, hanna.et.scott, hessijames, homoludens1000, kde, kdebugsbmw, m.debruijne, marcin.slusarz, mefoster, nico.schloemer, notmart, oliver.henshaw, p.zaskorski, philippe.roubach, rdieter, reavertm, sharuzzaman, sl-bugskde, theosib, thug2_w32 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Broken-looking panel
panels in dual-head configuration Plasma pixmap cache (Air theme) index Plasma pixmap cache (Air theme) data |
Actually, the driver/X situation above isn't quite correct. In fact KDE is running in a NX 3.4.0 session. The X server presented to KDE by NX does not support the COMPOSITE extension, hence the inability to use Desktop Effects. The NX client is running on a machine having the X and nVidia packages described above (and has compositing; the panel works fine there). However, I've also observed the problem with somewhat older KDE, Qt and X and probably VESA (or Cirrus?) drivers in a KVM VM, and the user reports from the cited IRC channels were probably with a broad range of software and hardware configurations. The common factor being no compositing. (Addendum: Where "somewhat older" still means "trunk past KDE 4.3"; probably around beta1 or beta2 of 4.4. The problem wasn't in KDE 4.3.) I'm seeing this too on Fedora 12 with KDE 4.3.95 from kde-redhat. This is a laptop with a "Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller". With disabled desktop effects I'm seeing exactly what Eike is seeing - if I enable effects the corruption is still there but much lighter and not as prominent and disturbing. Sven, I think with "the corruption is still there" you probably mean the stripes and such seen in the panel background - that's actually part of the updated Air theme's decorative elements, the whole "Quadros" design that the default wallpaper had going on for a while as well. I agree it's not quite as intuitive to understand as deco as the simpler diagonal striping in 4.3 was. I've already talked to the theme authors about it, especially the fact that the deco is a bit too heavy-handed on non-composited panels (i.e. even when they render correctly on the first start after installation). But the bug here isn't that, but the panel going black (instead of the normal greyish appearance for non-composited panels). (In reply to comment #4) > Sven, I think with "the corruption is still there" you probably mean the > stripes and such seen in the panel background - that's actually part of the > updated Air theme's decorative elements, You're right - it never occured to me that the background could be there on purpose - looks a lot like display corruption to me ;) > But the bug here isn't that, but the panel going black (instead of the normal > greyish appearance for non-composited panels). Ok - just to be sure - even if that part of my comment was wrong: I *am* seeing the black appearance when compositing is disabled on my system. same problem here, compositing disabled, nvidia binary drivers 190.53 and kde 4.3.98 (rc3) on opensuse 11.2. every time i switch to my external screen with the nvida-settings tool the panel turns black. it also happens when resizing the panel, depending on it's height, it switches between gray and black. turning on compositing makes it gray again. Created attachment 40790 [details]
panels in dual-head configuration
black panel bug shows here, too (ATI Mobility Radeon HD 3650, Catalyst 10.1), compositing disabled, dual head configuration.
At each login, the panel on the second screen is black, changing its size forth and back brings it back to Air's default colour. Enabling compositing is not an option since this is unusable with the Catalyst drivers atm :(
Also got this problem on my Netbook with Intel GMA950 in some user accounts some times - so this does seem not to be specific to any graphics card.
same pb here bugs #225842 same pb here bug #225842 I get the same problem with fglrx and compositing disabled. Restarting plasma (kquitapp plasma-desktop && kstart plasma-desktop) does not change anything (I guess the background is cached?). Changing to another theme and back again works around this problem but after restarting plasma the panel background is broken again. Also, from the screenshots in here and in bug 226652 and 226637 is seems the dark area is always the same size no matter how wide the panel is. *** Bug 225842 has been marked as a duplicate of this bug. *** *** Bug 226652 has been marked as a duplicate of this bug. *** Bug 224666 contains more information Dario: Bug 224666 is this bug. Err.. I mean, bug 226652. From bug 228411: (same symptoms on a vertical panel, with screenshots): The background of my main desktop panel is switched from its regular one (Air) to a different, illegible one on the following two occasions: (1) Whenever I choose 'unlock widgets' from the panel menu. (2) After rebooting my system. *** Bug 228411 has been marked as a duplicate of this bug. *** From bug 228962: After upgrade from 4.3.5 to 4.4.0 half of the bottom panel has weird background (see attached screenshot). I'm not sure why but it manifests only with 1920x1080 resolution. This bug happens with both nouveau and nvidia drivers, so it's probably not driver related *** Bug 228962 has been marked as a duplicate of this bug. *** Well, there is definitely something wrong the the pixmap cache: - Stop plasma-desktop, remove .kde{,4}/cache-${HOSTNAME}/kpc/plasma_theme_default.{data,index} and restart plasma-desktop and the panel background will be fixed. (until the next restart of plasma) - The plasma_theme_default.index is 32.1 MiB and plasma_theme_default.data 120.5 MiB. Thankfully though they're sparse files and only use 20 and 120 blocks respectively. (everything except at the very start is null bytes) - Most of the other files in the kpc dir are 1.3 MiB for the .index and 5.0 MiB for the .data, only amarok.{index,data} is as large as the plasma one. Most of the other .data files take up more disk space though. - Also the cache seem to stay around for all themes you ever tried even though plasma doesn't really take longer to start without the cache file around. Created attachment 41251 [details]
Plasma pixmap cache (Air theme) index
Saved by a plasma that started without any cache. Starting plasma with this file present will result in the partially dark panel.
Created attachment 41252 [details]
Plasma pixmap cache (Air theme) data
Saved by a plasma that started without any cache. Starting plasma with this file present will result in the partially dark panel.
This is still a problem in KDE 4.4.1. This likes to happen to me when I toggle compositing. My compositing control is still grayed out. I have the latest open source ATI drivers. "no compositing" is irrelevant - today this bug ocurred to me while compositing was enabled i confirm "compositing = no" => black panel ("compositing= yes" => black panel) with low probability *** Bug 230587 has been marked as a duplicate of this bug. *** I have the same problem. I am running 4.4.2 on Fedora 12. I will try testing if "compositing = yes" works better. My computer does not support compositing apparently - changing theme for now. *** Bug 235809 has been marked as a duplicate of this bug. *** mandriva 2010.1b2 kde 4.4.3 no more pb. the control panel bar is good *** Bug 229721 has been marked as a duplicate of this bug. *** marking as fixed, since it's 99% sure it's fixed in trunk. if it surfaces again (only with trunk) please reopen I can't say anything about trunk, but sorry, guys, it's not backported to latest stable again and again with new 4.4.x releases. Should we reopen it to get it backported before the end of 4.4 cycle? *** Bug 237605 has been marked as a duplicate of this bug. *** mandriva 2010.1rc kde 4.4.3 pb is there again ! Issue from Gentoo bugtracker - https://bugs.gentoo.org/show_bug.cgi?id=305169 If it's possible, please backport fix to 4.4 branch. At least indication what trunk revision is supposed to fix this bug would be nice. Pb is present in Lucid using KDE 4.4.4, with compositing enabled or not. openSUSE-11.3 which was released last week with KDE-4.4.4 , qt-4.6.3 , xorg-7.5 also still has this issue. https://bugzilla.novell.com/show_bug.cgi?id=613824 Same problem in Fedora 13/14 with KDE 4.5 and nouveau driver (with mesa driver experimental for the 3D effects). I'd like to mention that the bug was reproducible for me even after change from 4.4.x to 4.5.0 until I cleared /var/tmp/ After that I can't reproduce it anymore on 4.5.0. Hi, This bug was still present in version 4.4.5-1 in Debian Squeeze. As Squeeze was freezed to become Stable release soon, it is important that this bug was really fixed in Squeeze. Debian KDE team in uncertain which commit is the real fix. If it can be identified, I can suggest to them to cherry pick the fix and apply it to Debian's source. Please let me know the commit number, or appreciate your comment on Debian bug report related to this issue at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564941 Thanks. [Comment from a bug triager] There is a new case in KDE SC 4.5.1: bug 253861. May be this report should be reopened. Regards |
Created attachment 40324 [details] Broken-looking panel There seems to be some sort of problem with the SVG cache for the panel containment when running without compositing. When installing a new KDE version, the panel initially looks fine, but after the second login comes up looking dark and broken (see attached screenshot). This is with KDE SC 4.3.95 (aka 4.4rc2), Qt 4.6.1, xorg-server 1.7.4 and nVidia binary drivers on a 64bit Fedora 12 installation, but has been the case for several past KDE 4.4 pre-releases on older Qt, xorg and nVidia packages. This is a common problem; multiple users in #kde and #fedora-kde and #gentoo-kde have reported the same (as such this report is probably a dupe, but I couldn't find a report and notmart wasn't aware of one).