256848 - Mozilla and Gtk sizing issues.

Status: RESOLVED EXPIRED

(Core Graveyard :: GFX: Gtk, defect)

Description

[mega.watt]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040810
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040810

I'm using a Gtk2+xft build. On Mozilla 1.7, this problem didn't happen. However,
when I've migrated to Mozilla 1.7.1, I've noticed that it was using my window
manager gtk fonts. That should be a good thing, except that now I'm getting the
same problem I got from other programs: menus get too big! When I click a page,
for example, the right-click mouse menu often is displayed offscreen, even
though it isn't really large. I'm using a font called "Architect" (True Type),
size 14.
This problem does NOT happen on a non xft build!

Reproducible: Always
Steps to Reproduce:
1. Get a Mozilla 1.7.1 gtk2 build. 
2. Set up anti-alised fonts in your window manager, then try selecting different
fonts.
3. Load Mozilla.
4. If you've done everything correctly, your menus should go offscreen! 
Actual Results:  
Annoying offscreen menus, offscreen and very large preferences window (I have to
press maximize so I can resize it correctly).

Expected Results:  
All the menus should fit my screen monitor (it uses an 800x600 resolution, 24
million colors).

Comment 1

[Felix Miata]

Which Linux? Does your X configuration file (in etc/X11 xorg.conf, XF86Config or
XF86Config-4) contain an uncommented line in section monitor 'DisplaySize width
height'? Do you have a file /etc/X11/Xresources with an uncommented line 
'Xft.dpi: #dpi'? In your mozilla font prefs, is Display resolution set to
something other than "System setting"?

Comment 2

[mega.watt]

I use Slackware Linux 9.0, but I've upgraded it so much it can't be called "9.0"
anymore (it uses kernel 2.6.8, for, example).

This is my monitor section (using X.org version 6.7, but using an
/etc/X11/XF86config file).

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30-54

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-120

EndSection

I have no such file called "Xresources". And my Mozilla font prefers are set to
"system settings". 

I hope that helps. :)

Comment 3

[Felix Miata]

In Section "Monitor" add the following:

     DisplaySize     300    225

and restart X. Fonts and dialogs should be a different size from what you have
now. If you don't like the result, adjust the numbers and try again. 300 means
mm display width, and 225 means mm display height. They need not be the actual
dimensions of your display.

If adding/changing the DisplaySize fails to do the job, then create a file
/etc/X11/Xresources and in it put the following:

     Xft.dpi: 90

If that has an effect, but not enough to suit, reduce that number to shrink
things, or increase it to enlarge things.

As a possible alternative to all the above, adjust your 'Section "Screen"' to
provide higher resolution modes, such as "1152x864" or "1024x768".

All of the above is actually X configuration and should impact far more than
just Mozilla, and make this bug invalid if it solves your problem.

Comment 4

[mega.watt]

I've added all you asked me to, but the only way out was to change the font
size. That font was small, so I had to use Sans. 

I'm **** with gtk because it is resizing my applications 10x than it actually
needs to, and then all my apps get offscreen. I'm so **** that if things keep
at this rate, I might go back to Windows.

Comment 5

[Felix Miata]

Doesn't sound you performed the additional tests I recommended. Instead of
     DisplaySize     300    225

try
      DisplaySize     400    300
and
     DisplaySize     240    180
 
and instead of
     Xft.dpi: 90

     Xft.dpi: 80
and
     Xft.dpi: 75

In addition to a resolution increase to "1024x768" or higher. None of these will
take effect without a complete X server restart.

Comment 6

[mega.watt]

I've tried everything you told me. As I said before, on Mozilla the solution of
setting making the fonts smaller solved the problem. However, for other gtk
apps, the only solution was setting X to run on 1024x768. However, as I use a
15'' monitor, the screen gets too small and flashy, so it gives me a headache
looking into it. 

I've seen this on other gtk programs, so I assume it's NOT your fault about how
gtk is drawn on the screen. However, it uses much more space than it needs and
I'm **** about this.

Comment 7

[Felix Miata]

Not a Mozilla bug.

Comment 8

[mega.watt]

Attachment: Crashing url

This is one example of page that should make Mozilla crash. Currently I'm using
Mozilla 1.7.2 on Slackware 10.

Comment 9

[mega.watt]

That URL may not work. Going to this url directly should make Mozilla crash:

www.receita.fazenda.gov.br/ 

Comment 10

[mega.watt]

Attachment: useless

Strace log of Mozilla before crashing.

Comment 11

[mega.watt]

Attachment: junk

This is a valgrind dump of the crash happening. Hope this helps too.

Comment 12

[timeless]

Comment on attachment 166905 [details]
junk

./run-mozilla.sh `which valgrind` ./mozilla-bin

Comment 13

[timeless]

Comment on attachment 166904 [details]
useless

please don't ever post straces unless someone explicitly requests them

we almost always want a *stack*trace. this can usually be achieved by:
1. build w/ --enable-debug or --enable-debugger-info-modules
2. ./mozilla -g -d gdb
 3. run
 4. bt

Comment 14

[timeless]

please limit bug reports to a single problem. if you have another problem, file
a new bug. a crash has nothing to do with sizing issues and therefore does not
belong in a bug about sizing issues.

Comment 15

[mega.watt]

Attachment: ./run-mozilla.sh `which valgrind` ./mozilla-bin

./run-mozilla.sh `which valgrind` ./mozilla-bin

Comment 16

[mega.watt]

There. A new attachment according to what [e-mail] asked me.

Comment 17

[mega.watt]

I've found out Mozilla is much more prone to crashing when certain themes are
installed. Here's the theme I currently use (but the one on that page is a later
version).

http://freshmeat.net/redir/plastikzilla/51078/url_bz2/plastikzilla-crystalsvg-1.0.2-20040523.tar.bz2

I hope this can contribute to you. If you want the original theme please contact me.

Comment 18

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 19

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.