Bug 466103 - Buttons not positioned properly when using Compiz
Summary: Buttons not positioned properly when using Compiz
Keywords:
Status: CLOSED DUPLICATE of bug 446457
Alias: None
Product: Fedora
Classification: Fedora
Component: nodoka-theme-gnome
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F10Target FedoraMini
TreeView+ depends on / blocked
 
Reported: 2008-10-08 10:54 UTC by Peter Robinson
Modified: 2008-10-24 20:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-24 20:48:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screen shot showing theme issues. (132.29 KB, image/png)
2008-10-08 11:05 UTC, Peter Robinson
no flags Details
Another screen shot (114.95 KB, image/png)
2008-10-10 21:07 UTC, Peter Robinson
no flags Details

Description Peter Robinson 2008-10-08 10:54:52 UTC
I'm seeing some issues with the rendering of the default theme on Fedora 10 beta (and all later updates). There is a screen shot attached which shows the issues. The device is a eeePC 901 with a 1024x600 res screen with intel graphics. Some of the issues include:
- Min/Max/Close buttons a separated
- Clock date/time font too big for panel
- Task text at bottom too big for panel
- Menu text is a much better size but it looks to be top aligned rather than vertically centred.

The text in general seems to be quite large, but that might be me being use to larger res screens. One example is that the ekiga startup config wizard doesn't fit to the screen (nor evolution but its generally massive).

Comment 1 Peter Robinson 2008-10-08 11:05:08 UTC
Created attachment 319742 [details]
screen shot showing theme issues.

Comment 2 Martin Sourada 2008-10-08 13:46:58 UTC
(In reply to comment #0)
> I'm seeing some issues with the rendering of the default theme on Fedora 10
> beta (and all later updates). There is a screen shot attached which shows the
> issues. The device is a eeePC 901 with a 1024x600 res screen with intel
> graphics. Some of the issues include:
> - Min/Max/Close buttons a separated
That might be issue either with metacity theme or metacity itself, try switching to another theme

> - Clock date/time font too big for panel
> - Task text at bottom too big for panel
> - Menu text is a much better size but it looks to be top aligned rather than
> vertically centred.
> 
> The text in general seems to be quite large, but that might be me being use to
> larger res screens. One example is that the ekiga startup config wizard doesn't
> fit to the screen (nor evolution but its generally massive).
All the rest is a problem with too big fonts, set them to smaller size. Is your DPI set correctly? 

Anyway, icons are obviously rendered OK, so this bug (well, it's probably two different bugs) should be filled under different component.

Comment 3 Peter Robinson 2008-10-08 13:53:42 UTC
> > issues. The device is a eeePC 901 with a 1024x600 res screen with intel
> > graphics. Some of the issues include:
> > - Min/Max/Close buttons a separated
> That might be issue either with metacity theme or metacity itself, try
> switching to another theme

Happens with compiz too
 
> > - Clock date/time font too big for panel
> > - Task text at bottom too big for panel
> > - Menu text is a much better size but it looks to be top aligned rather than
> > vertically centred.
> > 
> > The text in general seems to be quite large, but that might be me being use to
> > larger res screens. One example is that the ekiga startup config wizard doesn't
> > fit to the screen (nor evolution but its generally massive).
> All the rest is a problem with too big fonts, set them to smaller size. Is your
> DPI set correctly? 

How would I tell?
 
> Anyway, icons are obviously rendered OK, so this bug (well, it's probably two
> different bugs) should be filled under different component.

What component would that be?

Comment 4 Martin Sourada 2008-10-08 14:48:36 UTC
(In reply to comment #3)
> > > issues. The device is a eeePC 901 with a 1024x600 res screen with intel
> > > graphics. Some of the issues include:
> > > - Min/Max/Close buttons a separated
> > That might be issue either with metacity theme or metacity itself, try
> > switching to another theme
> 
> Happens with compiz too
> 
Well, that would suggest the problem is with nodoka-metacity-theme, but since that haven't changed since F9 and it F9 it works, I am not sure...

> > > - Clock date/time font too big for panel
> > > - Task text at bottom too big for panel
> > > - Menu text is a much better size but it looks to be top aligned rather than
> > > vertically centred.
> > > 
> > > The text in general seems to be quite large, but that might be me being use to
> > > larger res screens. One example is that the ekiga startup config wizard doesn't
> > > fit to the screen (nor evolution but its generally massive).
> > All the rest is a problem with too big fonts, set them to smaller size. Is your
> > DPI set correctly? 
> 
> How would I tell?
Go to System->Preferences->Look and Feel->Appearances, select Fonts tab and click Details at the top there should be Resolution. If that number is incorrect for the screen res (in pixels)/screen real size (in inches) than I'd guess it's a problem with xorg detecting wrongly the size of your display. If it's correct and the font sizes are aroud 10pt (I think that's the default setting) then I guess the default is not optimised for ultra-small screens...

> 
> > Anyway, icons are obviously rendered OK, so this bug (well, it's probably two
> > different bugs) should be filled under different component.
> 
> What component would that be?
Not sure, check the comments above, it might help a little.

Comment 5 Peter Robinson 2008-10-08 15:12:06 UTC
Moving to nodoka-theme-gnome (closest match to nodoka-metacity-theme so presume they're built from same src package) but as a note this eeePC has never had F-9 installed on it, it was clean install from Live-CD to F-10 Alpha, then another clean Live-CD to F-10 Beta.

Will investigate the screen size/res issue too.

Comment 6 Martin Sourada 2008-10-10 20:43:18 UTC
(In reply to comment #5)
> Moving to nodoka-theme-gnome (closest match to nodoka-metacity-theme so presume
> they're built from same src package) but as a note this eeePC has never had F-9
> installed on it, it was clean install from Live-CD to F-10 Alpha, then another
> clean Live-CD to F-10 Beta.
> 
That's the correct match. I've checked the image you attached once again and it seems you have compositing turned on so I guess you have compiz tunred on (unless you tweaked with metacity gconf settings for compositing). Based on my experience with F10 Beta (and F9 as well) I presume the issue is that the nodoka metacity theme is rendered wrong when using compiz instead of metacity for some reason (it's rendered correctly when using metacity, even on F10 beta).

> Will investigate the screen size/res issue too.
Please use another bug for that then (since it's unrelated) ;-)

Comment 7 Peter Robinson 2008-10-10 21:07:06 UTC
Created attachment 320059 [details]
Another screen shot

Comment 8 Peter Robinson 2008-10-10 21:13:48 UTC
Yes, I'm running compiz. Just enabled straight through the Desktop Effects. I've attached another screenshot where the menu fonts have changed size (seems a little random).

Comment 9 Martin Sourada 2008-10-10 22:16:44 UTC
I'm changing the bug description to better fit what this bug is about. Please file another bug (or mention it in fedora-test-list) for the fonts problem, but I guess it might be just that the screen size is too small (and has high DPI) which makes the fonts (as font size is in real-world units, not in pixels) too big (relatively to the screen size).

Comment 10 Thomas J. Baker 2008-10-13 20:24:05 UTC
I've seen compiz render the metacity theme incorrectly and reported the bug https://bugzilla.redhat.com/show_bug.cgi?id=465470 along with one fix (upgrade to compiz 0.7.8).

Comment 11 Adel Gadllah 2008-10-24 20:48:19 UTC

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


Note You need to log in before you can comment on or make changes to this bug.