Created attachment 337843 [details] offending xorg.conf Running system-config-display in Rawhide with an /etc/X11/xorg.conf file set up for the NVIDIA proprietary driver crashes: [adamw@adam 10osvendor]$ system-config-display Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 376, in <module> dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, rhpxl.videocard.VideoCardInfo()) File "/usr/share/system-config-display/xConfigDialog.py", line 641, in __init__ if len(self.xconfig.layout[0].adjacencies) > 1: IndexError: index out-of-bounds the xorg.conf in question is attached. brianv confirmed the same happens to him (he's also using the NVIDIA proprietary driver). If I rename xorg.conf temporarily, s-c-d starts up correctly.
I get the same issue even without the twinview statements. I'm using akmod-nvidia.x86_64 from RPMFusion.
I am going to abuse my powers and triage my own bug =) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have the same problem on a computer that has an Nvidia 9800GT. I'm using Fedora 11 beta
Reproduced on: Linux xxx 2.6.29.3-140.fc11.i686.PAE #1 SMP Tue May 12 10:44:10 EDT 2009 i686 i686 i386 GNU/Linux with nVidia Corporation GeForce 8400 GS (rev a1)
reproduced on: Linux moose 2.6.29.3-140.fc11.i686.PAE #1 SMP Tue May 12 10:44:10 EDT 2009 i686 i686 i386 GNU/Linux with nVidia Corporation NV41.8 [GeForce Go 6800] (rev a2)
Oh and I should add that I don't have either of the TwinView* lines either in xorg.conf
I have almost the same problem here. system-display-config will not open at all on F10 (KDE 4.2.3). If I run it in the terminal, I get the following Python errors: Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 312, in <module> hardware_state = XF86HardwareState(xconfig) File "/usr/lib64/python2.5/site-packages/rhpxl/xhwstate.py", line 174, in __init__ self.init_from_xconfig(xconfig) File "/usr/lib64/python2.5/site-packages/rhpxl/xhwstate.py", line 260, in init_from_xconfig if screen.device: AttributeError: 'NoneType' object has no attribute 'device' I tried what Adam said (renaming my xorg.conf file) and it starts up as it should. I will attach my xorg.conf file for reference.
Created attachment 345704 [details] My xorg.conf This is my xorg.conf. The way Xorg autoconfigures my card (using X -configure) probably has something to do with this bug. If I run X -configure I get a lot of output about too many screens detected for the device (I never has this issue in the past, so I am assuming the new Xorg has had a regression). So, this attached xorg.conf was mostly edited by hand. Oh, and like the guy above, my video card is: nVidia Corporation GeForce 8400 GS (rev a1)
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
On my Fedora 11 system when I run system-config-display I get the following error message and I'm not using nvidia hardware but rather an Intel video chipset. system-config-display Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 376, in <module> dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, rhpxl.videocard.VideoCardInfo()) File "/usr/share/system-config-display/xConfigDialog.py", line 665, in __init__ self.xml.get_widget("secondMonitorLabel").set_text(monitor_list[1].modelname) TypeError: GtkLabel.set_text() argument 1 must be string, not None Let me know if I can provide anything further.
That's a different bug, you should file it separately. And attach your xorg.conf :) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Will do.
Is bug 509078 a duplicate?
*** Bug 509078 has been marked as a duplicate of this bug. ***
Reproduced here too, didn't happen with "nv" driver, appeared after installed nvidia modules from RPMFusion. Fedora 11 fully updated as of August 9, 2009. My output: ------------------------------------------------------------ $ system-config-display (system-config-display:2484): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (system-config-display:2484): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 376, in <module> dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, rhpxl.videocard.VideoCardInfo()) File "/usr/share/system-config-display/xConfigDialog.py", line 641, in __init__ if len(self.xconfig.layout[0].adjacencies) > 1: IndexError: index out-of-bounds $ ------------------------------------------------------------ My xorg.conf (generated upon install of nvidia kmod and nvidia xorg driver via yum): ------------------------------------------------------------ # Xorg configuration created by livna-config-display Section "Files" ModulePath "/usr/lib/xorg/modules/extensions/nvidia" ModulePath "/usr/lib/xorg/modules" EndSection Section "ServerFlags" Option "AIGLX" "on" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" Option "AddARGBGLXVisuals" "True" EndSection Section "Extensions" Option "Composite" "Enable" EndSection ------------------------------------------------------------
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.]
since no-one ever touches s-c-d, no, this has not been fixed with an update. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I am installing a new desktop system that is suffering from this issue. I tried the command in comment #16 (yum upgrade --enablerepo='*-updates-testing') and still have the same issue. It would seem this has not been corrected yet.
I've just run into this issue on Fedora 12 (package system-config-display-2.2-1.fc12.x86_64) after installing the proprietary nVidia driver. I think I know what's going on... The issue appears to be caused by a bounds violation on an empty layout[] collection in the Python object which represents the xorg.conf file. This only occurs when there is an existing xorg.conf file which does not contain an explicit "ServerLayout" section. A workaround is to run "system-config-display --reconfig", which should write a new xorg.conf file with the "ServerLayout" section included. As to the root cause, see /usr/share/system-config-display/xconf.py: - If we are doing a reconfigure, or if there is no existing xorg.conf, then the xconfig object is populated from the call to hardware_state.generate_xconfig on line 331 of xconf.py. This object is initially set up by xf86config.createTemplate() with a dummy layout[0] entry. In this case no problem occurs. - In other cases (i.e. not a reconfigure, and if xorg.conf exists), the xconfig object is built from the xorg.conf file via xf86config.readConfigFile() on line 308 of xconf.py. It appears that if there isn't a "ServerLayout" section in the file, then the layout[] collection is returned empty. This causes a bounds violation when an attempt is made to access layout[0]. (The script assumes all over the place that layout[0] exists). I would have thought this can be fixed up quite easily by adding a dummy layout object to the list in cases where none was found in the xorg.conf file. Not sure exactly where the best place is to do this though.
(In reply to comment #19) > A workaround is to run "system-config-display --reconfig", which should write.. Thanks, that did the trick for me!
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
The same issue occurs on a fully updated F12 system including package system-config-display-2.2-1.fc12.x86_64.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
it still does this. it'll keep doing it until anyone actually touches the s-c-d code. =) I'm just going to switch the version field to Rawhide to avoid the EOL stuff happening. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I'm going to have to bug out on this as I don't have an nvidia card to test with any more.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Hello, Still getting this: Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 378, in <module> dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig, videocard.VideoCardInfo()) File "/usr/share/system-config-display/xConfigDialog.py", line 640, in __init__ if len(self.xconfig.layout[0].adjacencies) > 1: IndexError: index out-of-bounds [Ankur@070905042 ~]$ rpm -q system-config-display system-config-display-2.2-1.fc12.x86_64 (I'm on F13) regards, Ankur
*** Bug 505972 has been marked as a duplicate of this bug. ***
*** Bug 434695 has been marked as a duplicate of this bug. ***
*** Bug 616045 has been marked as a duplicate of this bug. ***
*** Bug 533653 has been marked as a duplicate of this bug. ***
*** Bug 557644 has been marked as a duplicate of this bug. ***
*** Bug 546699 has been marked as a duplicate of this bug. ***
The duplicate `system` is weird indeed. Why mark older bugs as duplicates? Why use this NVIDIA specific one (not a general description at least) as a bug that should stay? Why no real bug fixing but only bug list cleanups? What can we test?
Why on earth choose a bug that exists w.r.t. a proprietary driver to carry all the 'duplicate' bugs?
updating it to f13. s-c-d was actually orphaned for f14 so it's not valid for f14. "Why on earth choose a bug that exists w.r.t. a proprietary driver to carry all the 'duplicate' bugs?" well, it shouldn't fall over whatever the contents of xorg.conf are. it isn't particularly important which bugs get marked as dupes, just that we have one bug to track the problem. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
So I guess we can close this one now. There's no s-c-d any more, right?
it's orphaned, which isn't entirely the same thing, but never mind.