dual screen setup: contents of both screens are shifted right by one pixel

Bug #472716 reported by didgethesky
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Karmic Koala
VGA: Radeon HD 4550, proprietary fglrx driver

I am using a dual screen setup with two TFTs in portrait mode, DFP5 is right of DFP1, which I activate with
"xrandr --output DFP1 --mode 1920x1200 --rotate left --output DFP5 --mode 1920x1200 --rotate left --right-of DFP1"

After that, xrandr correctly shows that DFP1 starts at 0x0:
"DFP1 connected 1200x1920+0+0"
and DFP5's origin is shifted 1200 pixel to the right, so starts at 1200x0 :
"DFP5 connected 1200x1920+1200+0"

Now there is a one pixel thick column on the left edge of the left screen. It's in a ubuntu-background-like brownish color, but does not belong to the background image content at that position. A maximized window on the left screen will not conver this column but instead overlap by one column to the right screen. So the windows rightmost pixel column is drawn as the leftmost column on the right screen. A window maximized on the right screen will not cover that overlapping column but "hang out" by one pixel column on the right side of the right screen. So everything is right shifted by one. This is also true for the gnome panels displayed on the left screen.

This bug was present in Jaunty and still is after upgrading to Karmic

Tags: karmic
Philip Muškovac (yofel)
affects: ubuntu → fglrx-installer (Ubuntu)
Revision history for this message
didgethesky (didgethesky) wrote :

Whoever assigned this to fglrx-installer: I don't think this is related in any way to fglrx.

I just switched to open source "radeon" driver. That got me rid of some other weird stuff (a 'ghost mouse cursor' in the left screen, when the real one was in the right one, and an area along the right border of the left screen where the cursor simply vanished)

But the problem descibed in this bug is the same with driver 'radeon'. So it's either an ati hardware thing or related to gnome/xserver/...

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
David Tombs (dgtombs) wrote :

Thanks for the update, didgethesky. Assigning to -ati driver.

affects: fglrx-installer (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Revision history for this message
David Tombs (dgtombs) wrote :

I'm sorry, I missed that it was present with /both/ drivers. Assigning to xorg instead.

Can you please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 472716

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: xserver-xorg-video-ati (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
didgethesky (didgethesky) wrote :

Hi,

I'd be glad to provide you with more information. But unfortunately the makers of apport-collect did not think of proxies ...
I'm behind my company's firewall but apport-collect ignores both the proxy settings in gnome system settings and in environment vars.

Is there another way to manually upload the needed data to launchpad?

By the way:
this bug affects both the gnome and the kde desktop in exactly the same way.

Revision history for this message
David Tombs (dgtombs) wrote :

Oh, bummer. apport-collect is essentially a hack which just directly attaches stuff to launchpad, so we probably can't get it to work.

Probably the best course of action would be to file a new bug report, using "apport-cli xorg". This will give you an option to store the report to a file. You can then save that file and send it later using "apport bug [path to file]."

If this is successful, please post the new bug's number as a comment in this one. Thank you!

Revision history for this message
NeilGreenwood (neil-greenwood) wrote :

You could try what it says here about 'Reporting Bugs From a Different Machine':

https://wiki.ubuntu.com/X/Reporting#Reporting%20Bugs%20from%20a%20Different%20Machine

Revision history for this message
Jamie Kitson (jamie-kitson) wrote :

I tried the aport-collect but that suggested that it would be better if I created another bug, see bug 666058.

Revision history for this message
David Tombs (dgtombs) wrote :

Thank, Jamie. I'm closing this bug because it has does not have enough information to triage. didgethesky, please file the new bug as requested if possible.

Changed in xorg (Ubuntu):
status: Incomplete → Invalid
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.