Bug 753954

Summary: [abrt] avogadro-1.0.3-2.fc14: Process /usr/bin/avogadro was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dirk Hoffmann <hoffmann>
Component: openbabelAssignee: Dominik 'Rathann' Mierzejewski <dominik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dominik, itamar, kevin, paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:254134b7e1c6923a3402fbd3068fd51033ea2677
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 22:57:33 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: backtrace none

Description Dirk Hoffmann 2011-11-14 22:52:28 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 55567 bytes
cmdline: avogadro
component: avogadro
Attached file: coredump, 123060224 bytes
crash_function: std::basic_ostream<char, std::char_traits<char> >::sentry::sentry
executable: /usr/bin/avogadro
kernel: 2.6.35.14-103.fc14.i686.PAE
package: avogadro-1.0.3-2.fc14
rating: 4
reason: Process /usr/bin/avogadro was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1321310196
uid: 500

How to reproduce
-----
1. Reading a benzene molecule from the standard library
2. Visualise it, turn it and shift it in "navigation" mode
3. After some movements, program crashes
Comment 1 Dirk Hoffmann 2011-11-14 22:52:31 UTC 
Created attachment 533648 [details]
File: backtrace
Comment 2 Kevin Kofler 2011-11-14 22:57:33 UTC 
That's the same crash. I don't think we need a new report for every affected molecule. ;-)

*** This bug has been marked as a duplicate of bug 753949 ***
Comment 3 Dirk Hoffmann 2011-11-14 23:19:14 UTC 
(In reply to comment #2)
> That's the same crash. 
If you say so.

However, I did not do the same at all to provoke it. And the automatic bug report does not suggest me that it happened before. 

I am sorry, but you will continue to receive a report for every affected situation and every user, as long as you did not repair the bug. ;-)