| Summary: | [oxygen-gtk] Gtk menu font color | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Raphael Groner <raphgro> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | hugo.pereira |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | oxygen-gtk-1.2.5-1.mga3 | CVE: | |
| Status comment: | |||
| Attachments: |
menu of claws-mail notification icon
Xfce's panel menu |
||
|
Description
Raphael Groner
2012-07-01 11:24:59 CEST
Created attachment 2514 [details]
menu of claws-mail notification icon
Created attachment 2515 [details]
Xfce's panel menu
Well, if composition is disabled in Xfce's settings, menus are shown well, but of course without transparency. $ lspci |grep VGA 00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller (rev 02) $ urpmq -r x11-driver-video-intel libdrm2 libdrm2-2.4.37-2.mga3 x11-driver-video-intel-2.19.0-8.mga3 I detected that it happens only when the theme oxygen-gtk is active for Xfce. Summary:
Gtk menu font color =>
[oxygen-gtk] Gtk menu font color
Manuel Hiebel
2012-07-01 21:46:18 CEST
CC:
(none) =>
hugo, jani.valimaa
Jani Välimaa
2012-07-01 21:47:53 CEST
CC:
jani.valimaa =>
(none) I think this is a release blocker due to the fact that the theme is unusable with that broken rendering. Again: It happens only if composition is enabledand only with oxygen-gtk as the active theme, in Xfce. I can't say anything about KDE, Gnome, etc. Priority:
Normal =>
release_blocker I'll look into it. I think it is a conflict between the use of ARGB by xfce to enable menu transparency, and the way oxygen gtk uses ARGB to have bevel corners. I have no idea of xfce's way to achieve transparency :( What happens if you disable transparency in xfce, (rendering things "opaque") without turning off compositing PS: conflict means: might not mean that it is oxygen-gtk's fault but possibly xfce. Meaning: oxygen-gtk does not have this issue on any other desktop environment (kde, gnome, as far as I know). Also: what is your graphics card. Also: can anybody reproduce with a different graphics card I know nothing about xfce. How to I enable compositing and transparency ? It seems here this (compositing) is not the default. ... so that I would not call it a release blocker, since the default appears perfectly usable here. (In reply to comment #7) > What happens if you disable transparency in xfce, (rendering things "opaque") > without turning off compositing I played with the various transparency settings of Xfce, it doesn't change anything to the broken oxygen menu rendering. But a disabled composition fixes it (removing the checkbox marker). It could well be that there's some conflict in the logic. (In reply to comment #8) > Also: what is your graphics card. see comment #3 ok. So in the end, I enabled transparency (window manager tweaks) and cannot reproduce. See: http://imagebin.org/219114 My GC is intel also (sorry if I missed comment #3 first). 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) x11-driver-video-intel-2.19.0-2.mga2 libdrm_intel1-2.4.33-1.mga2 vaapi-driver-intel-1.0.15-2.mga2 I think the release blocker flag should be removed (sorry). And I would close as upstream. Not much (In reply to comment #9) > I know nothing about xfce. How to I enable compositing and transparency ? $ xfconf-query -T -c xfwm4 -p /general/use_compositing (In reply to comment #11) It's Cauldron (mga3 packages) here. You seem to test with mga2 packages. ... that is correct. (sorry missed that too) But I have latest oxygen (from git). I'd recommand you try roll back intel drivers ... meant: "not much I (oxygen-gtk dev) can do about it on oxygen-gtk's side" what is the status of this bug ? also, is it really a blocker one ? Keywords:
(none) =>
NEEDINFO Thanks for your questions. Sorry, I've forgotten this bug. Due to the fact that I've given up with doing some further testing, I'll close this bug. Priority:
release_blocker =>
Normal |