This might be a gnome problem, but....
I've noticed that, on occasion (frequently), when I try to look at or
modify my display configuration, the Applications->System
Settings->Display doesn't come up. It asks for the root password, which
I give it, and then nothing.
I ran system-config-display form the command line, but it dies thus:
[root at mhullrichter mhr]# system-config-display
* no cardMem, assuming 8192
* no cardMem, assuming 8192
Trying with card: VESA driver (generic)
* no cardMem, assuming 8192
Traceback (most recent call last):
File "/usr/share/system-config-display/xconf.py", line 380, in ?
dialog = xConfigDialog.XConfigDialog(hardware_state, xconfig,
rhpl.videocard.VideoCardInfo())
File "/usr/share/system-config-display/xConfigDialog.py", line 566,
in
__init__
self.xml.get_widget("secondMonitorLabel").set_text(monitor_list[1].model
name)
TypeError: GtkLabel.set_text() argument 1 must be string, not None
I seem to be missing an argument from the call, but I'm not sure what
goes there, and even so, when I run it from the menu, shouldn't it have
the right data and run?
Thanks.
Mark Hull-Richter Linux Kernel Engineer
(949) 680-3082 - Office (949) 680-3001 - Fax (949) 632-8403 -
Mobile
mhull-richter at datallegro.com <mailto:mhull-richter at datallegro.com>
www.datallegro.com <http://www.datallegro.com>
85 Enterprise, 2nd Floor, Aliso Viejo, CA 92656
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070319/c6c87262/attachment.html>
Mark Hull-Richter wrote:> This might be a gnome problem, but?. > > I?ve noticed that, on occasion (frequently), when I try to look at or > modify my display configuration, the Applications->System > Settings->Display doesn?t come up. It asks for the root password, which > I give it, and then nothing. > > I ran system-config-display form the command line, but it dies thus: > > snip < > > I seem to be missing an argument from the call, but I?m not sure what > goes there, and even so, when I run it from the menu, shouldn?t it have > the right data and run?You should probably try 'system-config-display --reconfig'. It may be that your current xorg.conf has something not parse-able in it, the --reconfig switch starts from scratch. Worth a try, anyway. Remember, paranoia is a good thing, make a copy of your xorg.conf first! BTW, this just works with X11's configuration file, it doesn't have any dependency on Gnome or KDE. -- Jay Leafey - Memphis, TN jay.leafey at mindless.com -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4011 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20070319/ba068b82/attachment.bin>
On Mon, 19 Mar 2007, Mark Hull-Richter wrote:> This might be a gnome problem, but....Well, it is a Gnome problem to the extent that Gnome components, such as the pygtk2 (2 M) pulls in gtk2 widgets (12 M of widget) for a 1/2 M config tool. We discused this in IRC a couple weeks ago, and I talked a customer through it just this morning, as to this bloat into s-c-tools, and the lack of there being an effective enumeration tool for RPM to use to enumerate Pythonic 'includes' to find such Requires. If I cared, I'd file a bug upstream, but as all right thinking people install Gnome, I doubt it would get much attention ;0 In some install paths (such as moving a server to add X) such that you can install s-c-display, and not know that a needed element was missing. The underlying Pythonic code displaced the former (lighter) code which did this in prior s-c-display's without the Gnomish parts -- Don't you feel better with nicer widgets? And there are lovely UI standards. Is the check box on the side you like? That said, at least there is some tool for people willing to bloat their box and use Gnome. Oh -- and man xorg.conf is there for the rugged individualist The other trap for the unwary with a new install is that the xfs needs to be running, and have fonts, etc.> I ran system-config-display form the command line, but it dies thus: > > [root at mhullrichter mhr]# system-config-display > * no cardMem, assuming 8192 > > Traceback (most recent call last): > > File "/usr/share/system-config-display/xconf.py", line 380, in ?*** first hint -- Python code -- silent included modules are not findable to RPM at build time. As all right thinking prople install Gnome, they are not needed here of course.> TypeError: GtkLabel.set_text() argument 1 must be string, not Nonelets check the man page: man GtkLabel hmmm -- no man page -- oh, that's right -0- it's Gnome -- it does not NEED no steenkin' man pages. As I enable the updatedb, I find: [herrold at centos-4 ~]$ locate GtkLabel /usr/share/gtk-doc/html/gtk/GtkLabel.html and that is enough to remind me of this trap good luck - Russ Herrold
> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Jay Leafey > Sent: Monday, March 19, 2007 1:40 PM > To: CentOS mailing list > Subject: Re: [CentOS] system-display-config doesn't run right > > You should probably try 'system-config-display --reconfig'. It may be > that your current xorg.conf has something not parse-able in it, the > --reconfig switch starts from scratch. Worth a try, anyway.Remember,> paranoia is a good thing, make a copy of your xorg.conf first! >Tried that (including the backups). When it came up, it didn't have any of the right settings, and when I tried to set them properly, it didn't give me the right options, so I killed it. I have a dual head display (2 17" flat panels) configured as 1024x768 side by side, or at least that's what I think it is - could be 1280x1024 x 2. The existing xorg.conf files look ok, but neither system-config-display nor gconfd-2 works - s-c-d just dies with no traces or messages, and gconfd-2 just dies. Ph00!