system-config-display crashing

[Robert M. Albrecht]

Hi,

thanks, that fixed the glibc-bug for me.

Now the tool does seem to have another problem.

cu romal

[root at helios ~]# system-config-display
Traceback (most recent call last):
   File "/usr/share/system-config-display/xconf.py", line 311, in <module>
     hardware_state = XF86HardwareState(xconfig)
   File "/usr/lib/python2.5/site-packages/rhpxl/xhwstate.py", line 177, 
in __init__
     self.init_from_xconfig(xconfig)
   File "/usr/lib/python2.5/site-packages/rhpxl/xhwstate.py", line 296, 
in init_from_xconfig
     self.all_resolutions.sort (compare_resolution)
   File "/usr/lib/python2.5/site-packages/rhpxl/xhwstate.py", line 60, 
in compare_resolution
     (w1, h1) = resolution_from_string(res1)
   File "/usr/lib/python2.5/site-packages/rhpxl/xhwstate.py", line 49, 
in resolution_from_string
     (w, h) = string.split (res, "x")
ValueError: need more than 1 value to unpack


Jeremy Katz schrieb:
> On Sat, 2007-01-06 at 11:13 -0700, Michal Jaegermann wrote:
>> On Sun, Jan 07, 2007 at 01:50:01AM +0900, sangu wrote:
>>> Please See : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212780
>> And also
>> https://bugzillha.redhat.com/bugzilla/show_bug.cgi?id=220923
>> and I suspect that other similar ones can be found if you will
>> carefuly search through bugzilla.
> 
> Okay, I had enough time today to finally look into these.
> 
> Prior to python 2.5, PyObject_{malloc,realloc,free} and
> PyMem_{malloc,realloc,free} were essentially just defines to the system
> level functions.  With python 2.5, they instead do some other actions
> that are different for each family of functions so that the memory usage
> of the interpreter can drop at times.[1]  Hence, inconsistent use ==>
> segfaults.
> 
> Fixed up libuser, newt and pyxf86config (which were the ones I could
> find bugs on).
> 
> Jeremy
> 
> [1] http://docs.python.org/whatsnew/ports.html
>