Bug 314740 - panel blur effect transparency randomly stops working
Summary: panel blur effect transparency randomly stops working
Status: RESOLVED DUPLICATE of bug 179042
Alias: None
Product: plasma4
Classification: Plasma
Component: panel (show other bugs)
Version: 4.10.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-09 02:47 UTC by Willian Dziura
Modified: 2018-01-23 22:30 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
qdbus org.kde.kwin /KWin supportInformation (6.01 KB, application/octet-stream)
2013-03-02 13:43 UTC, hamelg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Willian Dziura 2013-02-09 02:47:03 UTC
I go to Desktop Effects and select  the "Blur" effect. Then click apply.
Nothing happens, and the panel stays with a white background. Also because the panel background is white, the clock is unreadable.

Deleting the file ~/.kde4/share/config/kwinrc and rebooting temporarily solves the problem.
And Blur effect is enabled. 

But if i shut the computer down and then turn it on again, after logging into KDE, blur is disabled and the panel turns white again.




Reproducible: Always

Steps to Reproduce:
1. Go to desktop effects and enable the "Blur" effect.
2. Nothing changes (the panel stays completely opaque, white.)
3. In the terminal, go to ~/.kde4/share/config/ and delete the file kwinrc. Reboot.
4. The panel blur is now working, panel is semi-transparent.
5. Shut down, and turn the computer back on, login.  The panel blur is gone, and the panel  turns white and opaque.

turnd 

Actual Results:  
The panel is white, completely opaque, and text from widgets such as the clock is barely visible.



Expected Results:  
The panel blur and transparency should have been kept, even after the computer was shut down and then turned back on.


For me, it seems like plasma refuses to keep my settings.

I have an AMD Radeon HD 6450 low profile graphics card,  and i've installed AMD Catalyst 13.1 from arch linux official repository.
Comment 1 modellbaukeller 2013-02-09 21:58:12 UTC
Confirmed also under Arch.

Besides, I get the same problem with VBox emulating a so-called "InnoTek Graphics Adapter", so this possibly isn't just a gfxdriver-caused issue but a Plasma-related one…

Is anyone expecting the same with NVIDIA-cards or any other brands?
Comment 2 Willian Dziura 2013-02-12 00:53:41 UTC
I have found a workaround for this, i've replaced the catalyst proprietary driver with the xf86-video-ati opensource one.

Now everything is working right, full panel blur.

This appears to be a bug related to plasma and catalyst.
Comment 3 Willian Dziura 2013-02-12 01:01:11 UTC
Note, i've noticed this problem in KDE SC 4.9.95, 4.9.97, 4.9.98 and now in 4.10.0.
And other users on arch linux forums, also confirmed this bug; they have AMD/ATi cards too.
Comment 4 hamelg 2013-03-02 13:42:54 UTC
Hello, i am an archlinux user and i am affected by this bug since upgrading to 4.10.
Sometimes, blur effect works again randomly.
Here is my setup : 'qdbus org.kde.kwin /KWin supportInformation'
Comment 5 hamelg 2013-03-02 13:43:44 UTC
Created attachment 77685 [details]
qdbus org.kde.kwin /KWin supportInformation
Comment 6 hamelg 2013-03-02 13:50:54 UTC
perhaps related to http://forum.kde.org/viewtopic.php?f=111&t=109970 ?
Comment 7 modellbaukeller 2013-04-08 14:05:35 UTC
*** This bug has been confirmed by popular vote. ***
Comment 8 hamelg 2013-04-23 19:40:02 UTC
is it a duplicate of https://bugs.kde.org/show_bug.cgi?id=179042 ?
Comment 9 Gleb Popov 2013-04-30 09:35:45 UTC
I confirm this on FreeBSD 9 with KDE 4.{8,9,10} and nvidia proprietary driver. Logging out and in fixes problem until next reboot.
Comment 10 clemens.oppenauer 2013-07-16 13:24:03 UTC
As someone has posted on the forums:
"You could copy /usr/share/autostart/plasma-desktop.desktop to ~/.kde/share/autostart and replace
- Exec=plasma-desktop
+Exec=sleep 2; plasma-desktop"

Apparently it seems to be a timing related issue, where plasma starts before kwin has fully started. It's really easy to fix and I hope this gets fixed soon.
Comment 11 Nate Graham 2018-01-23 22:30:36 UTC

*** This bug has been marked as a duplicate of bug 179042 ***