Hide Forgot
Description of problem: Normally using avogadro, running some optimizations. Avogadro is very unstable. Version-Release number of selected component: avogadro-1.0.3-16.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: avogadro crash_function: std::ostream::flush executable: /usr/bin/avogadro kernel: 3.11.10-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 std::ostream::flush at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream.tcc:219 #1 std::ostream::sentry::sentry at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream.tcc:52 #2 std::__ostream_insert<char, std::char_traits<char> > at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream_insert.h:82 #3 operator<< <std::char_traits<char> > at /usr/include/c++/4.8.1/ostream:535 #4 OBFFLog at /usr/src/debug/openbabel-2.3.2/include/openbabel/forcefield.h:1013 #5 OpenBabel::OBForceField::PrintTypes at /usr/src/debug/openbabel-2.3.2/src/forcefield.cpp:781 #6 OpenBabel::OBForceField::Setup at /usr/src/debug/openbabel-2.3.2/src/forcefield.cpp:891 #7 Avogadro::Molecule::dipoleMoment at /usr/src/debug/avogadro-1.0.3/libavogadro/src/molecule.cpp:727 #8 Avogadro::DipoleEngine::updateDipole at /usr/src/debug/avogadro-1.0.3/libavogadro/src/engines/dipoleengine.cpp:158 #9 Avogadro::DipoleEngine::renderOpaque at /usr/src/debug/avogadro-1.0.3/libavogadro/src/engines/dipoleengine.cpp:68
Created attachment 836246 [details] File: backtrace
Created attachment 836247 [details] File: cgroup
Created attachment 836248 [details] File: core_backtrace
Created attachment 836249 [details] File: dso_list
Created attachment 836250 [details] File: environ
Created attachment 836251 [details] File: exploitable
Created attachment 836252 [details] File: limits
Created attachment 836253 [details] File: maps
Created attachment 836254 [details] File: open_fds
Created attachment 836255 [details] File: proc_pid_status
Created attachment 836256 [details] File: var_log_messages
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.