Bug 766391

Summary: [abrt] picard-0.16-1.fc16: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kerry <mothlight>
Component: picardAssignee: Alex Lancaster <alex>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: alex
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d1a425e8933f3efd0c6d36963734cffa3f66cce7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-08 18:51:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: build_ids
none
File: smolt_data
none
File: backtrace none

Description Kerry 2011-12-12 00:21:12 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/picard
comment:        Running picard from command line. Crashed during startup.
crash_function: pthread_cond_wait@@GLIBC_2.3.2
environ:        
executable:     /usr/bin/python
kernel:         3.1.1-2.fc16.i686.PAE
maps:           
pid:            9248
pwd:            /mnt/Samsung2TB/MusicDownloads/new14
reason:         Process /usr/bin/python was killed by signal 11 (SIGSEGV)
time:           Mon 12 Dec 2011 11:05:19 EST
uid:            500
username:       nice

backtrace:      Text file, 255807 bytes
build_ids:      Text file, 6644 bytes
smolt_data:     Text file, 2459 bytes

var_log_messages:
:Dec 12 07:51:56 politemadness yum[19357]: Updated: libselinux-python-2.1.6-5.fc16.i686
:Dec 12 07:53:32 politemadness yum[19357]: Updated: policycoreutils-python-2.1.4-12.fc16.i686
:Dec 12 11:05:23 politemadness abrt[9259]: Saved core dump of pid 9248 (/usr/bin/python) to /var/spool/abrt/ccpp-2011-12-12-11:05:19-9248 (95203328 bytes)
Comment 1 Kerry 2011-12-12 00:21:14 UTC 
Created attachment 545458 [details]
File: build_ids
Comment 2 Kerry 2011-12-12 00:21:16 UTC 
Created attachment 545459 [details]
File: smolt_data
Comment 3 Kerry 2011-12-12 00:21:22 UTC 
Created attachment 545460 [details]
File: backtrace
Comment 4 Kerry 2011-12-12 01:24:21 UTC 
Ahh, it looks as though 

# rpm -e nvidia-settings xorg-x11-drv-nvidia-290.10-1.fc16.i686 xorg-x11-drv-nvidia-libs-290.10-1.fc16.i686 kmod-nvidia-3.1.1-2.fc16.i686-290.06-1.fc16.3.i686 kmod-nvidia-3.1.1-2.fc16.i686.PAE-290.06-1.fc16.3.i686

fixes this problem (along with lots of other mysterious crashes.
Comment 5 Alex Lancaster 2012-05-08 18:51:00 UTC 
Closing as per comment #4.