Bug 493496 - [radeon test day] cloned video not cloned [mobility x1600]
Summary: [radeon test day] cloned video not cloned [mobility x1600]
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 11
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-01 23:50 UTC by Bill McGonigle
Modified: 2018-04-11 14:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-24 19:23:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot, in case that helps (1.06 MB, image/png)
2009-04-02 02:01 UTC, Bill McGonigle
no flags Details
Xorg.0.log (69.34 KB, text/plain)
2009-04-05 04:21 UTC, Bill McGonigle
no flags Details

Description Bill McGonigle 2009-04-01 23:50:41 UTC
from the livecd: upon login, on the laptop display the task bar is missing and the menubar doesn't stretch to the whole screen width.  On the external DVI both are fine.  The video isn't really cloned.

With the GNOME display applet, both displays are labeled as 'LG 24"' and the laptop display shows as being mostly covered by the DVI in the arrange applet.  I would estimate that the amount of laptop display sticking out the right side, from under the DVI display, is the same percentage of its total that the menubar doesn't stretch all the way across (maybe 15% or so in both cases).  Could just be correlated, I'm sure.

If I rearrange by hand, the labels update correctly and it seems to do a spanned desktop (xrandr ran?).


smolt:
  http://www.smolts.org/client/show/pub_84fdcccc-d29d-4a50-8032-3855cfb8ff32

Comment 1 Bill McGonigle 2009-04-02 02:01:09 UTC
Created attachment 337707 [details]
screenshot, in case that helps

Comment 2 Matěj Cepl 2009-04-03 16:13:05 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach /var/log/Xorg.* to this bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 Bill McGonigle 2009-04-05 04:21:35 UTC
Created attachment 338197 [details]
Xorg.0.log

only one X server running.

Comment 4 François Cami 2009-04-08 22:34:52 UTC
Thanks for the logs, switching to ASSIGNED.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Bug Zapper 2009-06-09 13:03:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Matěj Cepl 2009-11-05 18:24:38 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 7 Bill McGonigle 2009-11-19 18:58:09 UTC
I no longer have this hardware, so unable to test again.

Comment 8 Bug Zapper 2010-04-27 13:26:03 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Vedran Miletić 2010-05-24 19:23:52 UTC
Closing per comment 7.

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

[This triage is part of collective effort done by students of University of
Rijeka Department of Informatics.]


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