Your message dated Tue, 04 Aug 2009 15:51:18 +0200
with message-id <1249393879.7253.0.ca...@leidi>
and subject line Re: Bug#533030: avogadro: seg fault in Sid version
has caused the Debian Bug report #533030,
regarding avogadro: seg fault in Sid version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
533030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533030
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: avogadro
Version: 0.9.4-3
Severity: grave
Justification: renders package unusable
Latest version of avogadro fails with a seg. fault on startup:
daddy:~# avogadro
"Avogadro version: 0.9.4 Git:
LibAvogadro version: 0.9.4 Git: "
Locale: "en_US"
path = "/usr/bin/../share/avogadro/i18n/"
"/usr/bin/../share/avogadro/i18n/avogadro_en_US.qm" not found.
"System has OpenGL support."
"About to test OpenGL capabilities."
"OpenGL capabilities found: "
"Double Buffering."
"Direct Rendering."
"Antialiasing."
Searching for plugins in "/usr/bin/../lib/avogadro/colors"
Searching for plugins in "/usr/bin/../lib/avogadro/engines"
Searching for plugins in "/usr/bin/../lib/avogadro/extensions"
Searching for plugins in "/usr/bin/../lib/avogadro/tools"
Searching for plugins in "/usr/bin/../lib/avogadro/contrib"
Segmentation fault
???????????
Kenward
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages avogadro depends on:
ii libavogadro0 0.9.4-3 Molecular Graphics and Modelling S
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-5 GCC support library
ii libgl1-mesa-glx [libgl1] 7.4.1-1 A free implementation of the OpenG
ii libglew1.5 1.5.1-4 The OpenGL Extension Wrangler - ru
ii libglu1-mesa [libglu1] 7.4.1-1 The OpenGL utility library (GLU)
ii libopenbabel3 2.2.1-4 Chemical toolbox library
ii libqt4-network 4.5.1-2 Qt 4 network module
ii libqt4-opengl 4.5.1-2 Qt 4 OpenGL module
ii libqtcore4 4.5.1-2 Qt 4 core module
ii libqtgui4 4.5.1-2 Qt 4 GUI module
ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3
ii libx11-6 2:1.2.1-1 X11 client-side library
ii python-numpy 1:1.2.1-1 Numerical Python adds a fast array
ii python-qt4 4.5-1 Python bindings for Qt4
ii python2.5 2.5.4-1 An interactive high-level object-o
avogadro recommends no packages.
avogadro suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Am Montag, den 27.07.2009, 00:04 -0700 schrieb Kenward Vaughan:
> On Wed, 2009-07-08 at 23:00 +0200, Daniel Leidert wrote:
> > Am Mittwoch, den 08.07.2009, 12:48 -0700 schrieb Kenward Vaughan:
> > > On Wed, 2009-07-08 at 21:28 +0200, Daniel Leidert wrote:
> > > > Hello Kenward,
> > > >
> > > > Do you still observe the segmentation fault with the latest version of
> > > > avogadro in Sid?
> > > >
> > > > Regards, Daniel
> > >
> > > Nope. Now it's the following:
> > >
> > > daddy:~# avogadro
> > > terminate called after throwing an instance of
> > > 'boost::python::error_already_set'
> > > Aborted
> >
> > We are aware of this one. See
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536281#10 for the quick
> > workaround.
> >
> > After "fixing" this issue: Do you still get a segmentation fault?
>
> Sorry about the lag... I've been away.
>
> The seg fault disappeared after the above change.
>
> Additionally, I just reinstalled due to a slowly failing HD and several
> years of Sid (which I believe adds up to a pile of cruft floating
> about). Avogadro (and everything else) now flies...
Closing then.
Regards, Daniel
--- End Message ---
