abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/bin/python -tt /usr/sbin/nvidia-config-display component: python executable: /usr/bin/python kernel: 2.6.31.6-166.fc12.x86_64 package: python-2.6.2-2.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 381696 [details] File: backtrace
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? What version of pyxf86config do you have installed? Looking at the backtrace, it looks like the problem occurred in the program's single thread in __libc_free inside /usr/lib64/python2.6/site-packages/ixf86configmodule.so Looks similar to bug 551230. Reassigning component from "python" to "pyxf86config"
Sean: does the "segmentation fault" (SIGSEGV) happen if you run the script as root/via sudo? I've got a feeling that the /usr/sbin/nvidia-config-display script is one from a 3rd party repository; if so there's a case that this isn't a bug in Fedora per se. Having said that it seems wrong that it can cause a SIGSEGV inside ixf86configmodule.so (which is part of Fedora). Sean got back to me via private email with this information, which I'm taking the liberty of posting here: --- begin quote --- [egner@quadbox ~]$ /usr/sbin/nvidia-config-display An error occured while backing up the file '/etc/gdm/custom.conf' Please make sure you have permissions to modify the necessary configuration file(s). Traceback: Permission denied Segmentation fault (core dumped) I ran it from the command prompt as root and got the following print. [root@quadbox egner]# /usr/sbin/nvidia-config-display Segmentation fault (core dumped) Version [root@quadbox egner]# rpm -q pyxf86config pyxf86config-0.3.37-7.fc12.x86_64 --- end quote --- Hope this is helpful
Sean: another question, what's the output of running: rpm -qf /usr/sbin/nvidia-config-display please?
Dave: Output as requested. [root@quadbox egner]# rpm -qf /usr/sbin/nvidia-config-display xorg-x11-drv-nvidia-190.42-5.fc12.x86_64 I also ran debuginfo-install pyxf86xonfig, and reported it with ABRT. The bug number assigned was 553359.
*** Bug 553359 has been marked as a duplicate of this bug. ***
Attachment 382296 [details] to bug 553359 contains a more full symbolic backtrace of the crash; it indicates the problem occurs as the program is bailing out with a python-level exception, with a call to xf86freeInputList from xf86freeConfig, where the invalid free occurs.
*** Bug 552592 has been marked as a duplicate of this bug. ***
*** Bug 552448 has been marked as a duplicate of this bug. ***
*** Bug 558186 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 539939 ***