gusty/RC1 thinks it has a 1024x768 screen on a 1680x1050 screen

Bug #152247 reported by Englbert Westermeier
6
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Incomplete
Undecided
Tormod Volden

Bug Description

in gusty Kubuntu RC1

Reproducible when starting from LiveCD.
Not tested with a installed system.

desktop effects are not activated.

KDE control bar:
control bar sticks to a screen size of 1024 x 768 on a screen with 1680x1050
It is possible to place the control bar manually (drag-and-drop) to the location where it should be (real bottom of the screen).
Then, if you open the Kmenu, it will be displayed not right above the control bar but within the 1024x768 boundaries. That means about 1050 - 768 = 282 pixel to high above the kicker.

maximising windows:
Case 1: try to maximise a window within the boundaries of this 1024x768 "screen" = > window will be will be maximised to a size of 1024x768 pixel.
Case 2: try to maximise a window outside of this boundaries => window will be maximised to the full size of the screen

Revision history for this message
unggnu (unggnu) wrote :

If you are using an Intel graphic card it is possible a duplicate of Bug #131646.

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

I'm afraid but it's an ATI MOBILITY RADEON 9600/9700 Series graphic card.

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :
Revision history for this message
unggnu (unggnu) wrote :

Please provide more information like xorg.conf and the output of lspci. If you have compiz enabled please deactivate it since it has a similar problem with Intel graphic.

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

here is the lspci output as you requested

compiz is not activated. To be precise: The live system (I haven't jet installed gusty) doesn't activate desktop effects on my system. (at least I can't see any...)

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

here is the xorg.conf

I think I already know what you are going to say:
The resolution in this xorg.conf file is wrong.
In the Screen section it says:

Modes "1024x768"

instead of

Modes "1680x1050"

As I'm not a xorg specialist, I just changed that line and tested. Same Problem.
I have to say, my laptop display is broken so I can't tell you what happens there.
But I would guess, that it is set up perfectly correct.

So the whole problem seams to be a wrong xorg.conf configuration when booting from LiveCD.

unggnu (unggnu)
Changed in xserver-xorg-video-ati:
status: Incomplete → New
Revision history for this message
Tormod Volden (tormodvolden) wrote :

What do you get if you run without any xorg.conf?

Changed in xserver-xorg-video-ati:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

good question!

Again tested with the liveCD!

1. boot
2. logout of X session
3. sudo rm /etc/X11/xorg.conf
4. startx
Result: No change. Same thing.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Please attach Xorg.0.log

Revision history for this message
unggnu (unggnu) wrote :

Please try the command "xrandr --output TV --off". If it doesn't help please post the output of xrandr. Maybe it is similar to the Intel problem.

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

here is the Xorg.0.log for a start

results of xrandr comming up...

Revision history for this message
Tormod Volden (tormodvolden) wrote :

From looking at the log, I think the driver detects two screens connected, the second is a 1024x768 display at the LVDS output. Please try to disable the LVDS output. See http://wiki.debian.org/XStrikeForce/HowToRandR12 for how to.

What exactly is your screen/connectors configuration?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

This could be bug #156550

Revision history for this message
Englbert Westermeier (spam-bertwest) wrote :

Oh dear! I totally forgot this issue!
Sorry!

Yes, the screenshots in the bug #156550 look similar.
This issue can be "solved" like described in the other bug report: Install the fglrx drivers and do a proper config in the xorg.conf.

How to go on?
Do you still need further information?
This bug could be marked as duplicate of the other bug ...
For me personally it also could be marked as fixed (egoistic, I know:-)

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks, I'll make it a duplicate. If it's "fixed" when using fglrx, it could be a bug in the -ati driver, or the "proper config" does something to it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.