Bug 753954 - [abrt] avogadro-1.0.3-2.fc14: Process /usr/bin/avogadro was killed by signal 11 (SIGSEGV)
Summary: [abrt] avogadro-1.0.3-2.fc14: Process /usr/bin/avogadro was killed by signal ...
Keywords:
Status: CLOSED DUPLICATE of bug 753949
Alias: None
Product: Fedora
Classification: Fedora
Component: openbabel
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:254134b7e1c6923a3402fbd3068...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 22:52 UTC by Dirk Hoffmann
Modified: 2011-11-14 23:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 22:57:33 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (54.26 KB, text/plain)
2011-11-14 22:52 UTC, Dirk Hoffmann
no flags Details

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. ;-)


Note You need to log in before you can comment on or make changes to this bug.