Bug 575113

Summary: [abrt] crash in hugin-2009.2.0-1.fc12: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mark Flitter <mflitter>
Component: huginAssignee: Bruno Postle <bruno>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bruno, jspaleta
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:6c0ca13b2cba58002e1c2afcdbaad8f1d6362cb3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-07 21:39:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mark Flitter 2010-03-19 13:50:54 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: hugin
component: hugin
executable: /usr/bin/hugin
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: hugin-2009.2.0-1.fc12
rating: 4
reason: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

comment
-----
[flits@<hostname>] hugin
MainFrame::RestoreLayoutOnNextResize()
Segmentation fault (core dumped)

How to reproduce
-----
1.started hugin on the command line
2.clicked next at the tip of the day screen.
3.
Comment 1 Mark Flitter 2010-03-19 13:50:56 UTC 
Created attachment 401250 [details]
File: backtrace
Comment 2 Bruno Postle 2010-03-20 21:35:48 UTC 
Hi, I see that you are using the proprietary nvidia drivers. Can you switch back to the default fedora nouveau drivers and see if this helps?

See also bug #562231 https://bugzilla.redhat.com/show_bug.cgi?id=562231
Comment 3 Mark Flitter 2010-04-07 14:53:28 UTC 
Switched back to nouveau and problem resolved.

suggest we close this BZ
Comment 4 Bruno Postle 2010-04-07 21:39:59 UTC 

*** This bug has been marked as a duplicate of bug 562231 ***