BigDesktop (fglrx) causes display oddities



MailNews: Message Display
14 years ago
13 years ago


(Reporter: Kevin MacPherson, Unassigned)


Firefox Tracking Flags

(Not tracked)



(3 attachments)



14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040216 Debian/1.6.x.1-10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040216 Debian/1.6.x.1-10

When using BigDesktop option with fglrx drivers (One framebuffer, two heads, no
Ximerama support) especially the mail client but also forms in Mozilla are
thrown off.

In the mail client I get double spaced lines for all folder and mail listings.
The font in the mail body as well as for forms in Mozilla Browser are very small.
I've tried quite a few options to try to get a "normal" display but I can't get
it to display properly.

With BigDesktop I am using 2048x1024 as aresolution and unlike Ximerama it does
not limit application to fullscreen on one head or the other.

If you need screen caps I can see about e-mailing them to someone or putting
them on an FTP site.

Reproducible: Always
Steps to Reproduce:
1. Setup BigDesktop using fglxrconfig
2. Open Mozilla Mail

Actual Results:  
The diplay is using Double Lines for lists and small text in the body.

Expected Results:  
It should display normally as in single head.

It seems that since the desktop is returning 2048x1024 instead of the head's
resolution for a resultion it is messing up something in the display portion of

I can send a screen cap to show what I mean from Single Head to BigDesktop for
the changes that happen.

Comment 1

14 years ago
Created attachment 143848 [details]
Mozilla Mail on BigDesktop

This is how it displays on BigDesktop

Comment 2

14 years ago
Created attachment 143849 [details]
Mozilla Mail on Single Head

This is how Mozilla Mail appears on Single Head (I think the way it should

Comment 3

14 years ago
Resembles bug 104576. CC

Comment 4

14 years ago
Created attachment 143870 [details]
xdpyinfo from BigDesktop setup
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.