Package: gnochm
Version: 0.9.7-1
Severity: normal

On Wed, Jun 07, 2006 at 01:49:54AM -0700, Sean Dwyer wrote:
> [snip]
> after I
> installed the gnochm package using apt-get, it would seg fault when I
> tried
> to start it. After some tinkering, I found that it was seg faulting
> when
> "import gconf" was called  in the gnochm script in /usr/bin (line 55).
> I
> fixed it by upgrading my python2.3-gtk2 package from version 2.6.1-2
> to
> 2.8.2-3. This caused python2.3-glade2 to be upgraded and
> python2.3-cairo to
> be installed as well. I don't know if the solution would be to change
> the
> versions of python2.3-gtk2 and python2.3-glade2 required for gnochm,
> but I
> thought someone should know. Maybe my python setup was simply in a
> weird
> state.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)

Versions of packages gnochm depends on:
ii  gconf2                        2.14.0-1   GNOME configuration database syste
ii  python                        2.3.5-5    An interactive high-level object-o
ii  python-chm                    0.8.2-4    Python binding for CHMLIB
ii  python-glade2                 2.8.2-3    GTK+ bindings: Glade support
ii  python-gnome2                 2.12.3-2   Python bindings for the GNOME desk
ii  python-gnome2-extras          2.12.1-2.1 Python bindings for the GNOME desk
ii  python-gtk2                   2.8.2-3    Python bindings for the GTK+ widge
ii  scrollkeeper                  0.3.14-11  A free electronic cataloging syste
ii  shared-mime-info              0.17-2     FreeDesktop.org shared MIME databa

Versions of packages gnochm recommends:
ii  python-cjkcodecs              1.1.1-1.2  Python Unicode Codecs Collection f

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to