gtk theme'd checkboxes and radio buttons are drawn wrong

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
11 years ago
5 years ago

People

(Reporter: ori, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
Checkboxes and radio buttons always appear unchecked. When hovering over them, the check mark (if there is one) magically appears, with the wrong color for the theme.

I'm using the ubuntustudio theme available at <http://packages.ubuntu.com/gutsy/source/ubuntustudio-look>.

See the attached video for an example of the bug.

The widgets should really look like this:
<http://ubuntustudio.org/files/US5.png>

Tested on firefox 3 beta 1
(Reporter)

Comment 1

11 years ago
Video is too large to attach:
http://www2.mta.ac.il/~oravtali/firefox-gtk-theme-bug.ogg
Component: OS Integration → Widget: Gtk
Product: Firefox → Core
QA Contact: os.integration → gtk
I thought we kept saying that it was a theme problem, but http://ubuntustudio.org/files/US5.png shows that the theme supports disabled boxes/buttons, so maybe it's our problem?

Dupe of bug 388131?

Comment 3

11 years ago
Hm, I don't see anything funny in the code right now. It looks like the shadow type is set correctly.

This whole thing is confusing me right now. There seem to be three different bugs:

This one: "checked" checkbutton in the normal state does not look "checked"
bug 388131: insensitive checkbuttons look the same as sensitive ones
bug 404962: "checked" checkbutton in the insensitive state does not look "checked"
(Reporter)

Comment 4

11 years ago
Could this be related to me running the 32-bit firefox on a 64-bit machine? A problem linking with libgnomeui or something?

Comment 5

11 years ago
(In reply to comment #4)
> Could this be related to me running the 32-bit firefox on a 64-bit machine? A
> problem linking with libgnomeui or something?
> 

This has nothing to do with libgnomeui. This appears to be an inadequacy in the theme, since very mainstream themes like Clearlooks, Human or Crux don't show this problem.

Comment 6

11 years ago
Hi all. I'm the lead on Ubuntu Studio.

After testing beta1, I'm not seeing this issue from the theme shipping with Gutsy, nor the updated theme in development.

http://img381.imageshack.us/img381/9884/screenshotge1.png (Gutsy theme)

Our theme uses the Murrine engine.

If someone beyond the OP can confirm this behavior I will look into this further.
(In reply to comment #6)
> After testing beta1, I'm not seeing this issue from the theme shipping with
> Gutsy, nor the updated theme in development.

If you wouldn't mind, please check out the latest nightly build of Firefox at ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ and see if you see the problem there.
(Reporter)

Comment 8

11 years ago
Now that Murrine is mentioned, I really the 32-bit app on 64-bit system is to blame. I'm seeing this error:

(firefox-bin:9058): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so: wrong ELF class: ELFCLASS64

Comment 9

11 years ago
Looks fine while using firefox-3.0b2pre.en-US.linux-i686.tar.bz2.

http://img475.imageshack.us/img475/2278/screenshot1wt8.png
(Reporter)

Comment 10

11 years ago
So, should there be some kind of fallback mechanism in case murrine isn't linked?

Comment 11

11 years ago
Hm, I think I know what is going on. The engine is not loaded because of the 32 vs. 64 bit systems. However the theme is loaded, so that themes colors are used. This results in problems because the theme sets text[ACTIVE] to white apparently and the buildin GTK+ theme then draws a white checkmark.
Murrine itself does not have a problem, because it uses a different color to draw the check mark.

So the problem is the mixed 32/64bit enviroment, I think.
Seems like a problem in the local gtk theme setup.  Please file a new bug, with
steps to reproduce, if it still occurs in a recent version of Firefox.  Thanks.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.