Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#23912 - [xfdesktop] Defect pseudo-transparency in terminals

Attached to Project: Arch Linux
Opened by henning mueller (phects) - Sunday, 24 April 2011, 13:12 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 09 March 2012, 08:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


After the update from xfdesktop-4.8.1-2 to 4.8.2-1 rxvt-unicode and terminal stopped having pseudo-transparent (without compositing manager, software rendered) backgrounds.

Additional info:
* xfdesktop-4.8.2-1
* rxvt-unicode-9.10-1
* terminal-0.4.7-1

Steps to reproduce:
* Install xfdesktop-4.8.2-1
* Startup "terminal" and activate pseudo-transparent background (in Settings/Appearance/Background).
* The expected background of the terminal would be a shaded part of the desktop wallpaper. Instead it's the configured terminal background color shaded.

I couldn't get any debug output; feel free to suggest a way to collect it.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 09 March 2012, 08:04 GMT
Reason for closing:  Upstream
Comment by Andreas Radke (AndyRTR) - Sunday, 24 April 2011, 14:15 GMT Comment by Leonid Isaev (lisaev) - Wednesday, 11 May 2011, 15:42 GMT
I thinks this is the consequence of the fix for that shutdown problem: Enabling compositing should help...
Comment by Andreas Radke (AndyRTR) - Sunday, 05 June 2011, 21:21 GMT
I had huge load on my notebook when using Xfce terminal. I removed ~/.config/Terminal and now everything seems fine again (running testing). Can you try this?
Comment by Andreas Radke (AndyRTR) - Sunday, 23 October 2011, 09:36 GMT
status? upstream says it's fixed: