Description of problem: I'm getting a steady trickle of bugs assigned to me when /usr/bin/python segfaults. The great majority of these appear to be due to assertion failures in C extension modules as called by the scripts being run. For example, see bug 533460. This appears to be an assertion failure within gobject python wrappings defined specifically for the elisa package. For a segfault involving a python process, where e.g. cmdline: /usr/bin/python /usr/bin/elisa would it be possible to determine the package owning the script, and if it is owned, assign the bug to that component, rather than to "python"? (rpm -qf /usr/bin/elisa in this example)? Thanks
Regardless of whether the crash occurrs in a code that's part of the python runtime, or application code, this should always be reported against the RPM corresponding to the application if there is one. It is not at all helpful for all virt-manager bugs to be reported against 'python', instead of 'virt-manager'. Agree with Dave that doing a rpm -qf on the script's filename seems like a pretty good idea to get the vast majority of reports going to the right place in BZ.
Yes, should be possible to parse the real app name. The current problem is that if some app creates a coredump, ABRT detects it and just read /proc/<pid>/exe to derminde the executable and in the case of bug in python extension it says /usr/bin/python, but we already have a code that reads the cmdline from coredump, which should help with this bug. Jirka
(flipping component back from "0xFFFF" to "abrt"; issue with bugzilla's web UI?)
In https://bugzilla.redhat.com/show_bug.cgi?id=543517#c1 jmoskovc said: > I have written a patch for #533521 and now it's in the testing phase, so you > should be soon freed of bugs caused by extensions.
This is already done in git and it should be in 1.0.3 too IIRC. Changing to "MODIFIED"
abrt-1.0.6-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.6-1.fc12
abrt-1.0.6-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1470
abrt-1.0.6-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.