Bug #34
closedsynapse
100%
Description
Hey there Arnud,
When i bring up the synapse application (it's like gnomedo without all the gnome dependencies) the transparancy is not being handled correctly. It's probably not confined to synapse, there are probably other apps for which this is a problem as well. Also, when i start up xorg/awesome the screen is black, and i have to move the terminal window around to refresh those areas.
Screen shots attached. Let me know how i can help you debug this.
Thanks!!
gentoo kernel 3.2.1
x86_64 intel core 2 quad Q9300 8g ram
xorg 1.11.2-r2
nvidia-drivers: 290.10
nvidia 8800 GT
Files
Updated by Arnaud Fontaine over 12 years ago
- Category set to Core
- Assignee set to Arnaud Fontaine
- Priority changed from Normal to High
Thank you very much for your bug report.
About synapse, after checking it seems that gnome volume has the same problem as rounded corners are not displayed properly. I will look into that and get back to you then.
About the startup issue, as with the latest release (0.3), I cannot reproduce this issue, I think I would need further information ;-). Do you get any warning messages from Unagi? Also could you please attach your configuration or command line for rxvt? Does it only happen with rxvt? How did you set the background? Could you please tell me which version/commit of Unagi you're using?
Updated by Arnaud Fontaine over 12 years ago
I have split up this issue in two separate issues, one about Synapse (this one) and another one for the startup issue. Feel free to comment about the startup issue on #35. Many thanks!
Updated by Arnaud Fontaine over 12 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset db92a6922ada26be23c4b0847fff49f5ba8f514f.
Updated by Toby Smithe over 11 years ago
Hi,
I'm suffering a similar/the same problem using version 0.3.3 in Ubuntu raring, under the i3 window manager. I've attached a screenshot, showing synapse with visual artifacts, the i3bar, and a transparent cairo-clock.
Is there anything else I should provide to help you?
Cheers,
Toby
Updated by Toby Smithe over 11 years ago
Actually, it seems to have been a bug in i3 itself, and is fixed in the development branch there. Sorry to bother you!