Your message dated Sat, 04 Aug 2012 10:57:35 +0200
with message-id <[email protected]>
and subject line Closing Bug#680857: gnucash-bin: error while loading shared 
libraries: libgtkhtml-3.8.so.15
has caused the Debian Bug report #680857,
regarding gnucash-bin: error while loading shared libraries: 
libgtkhtml-3.8.so.15
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.)


-- 
680857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680857
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnucash
Version: 1:2.4.10-5
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
Error message appears on startup. Application then fails. I consider this 
release critical.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Tryed launching first from menu system, then from gnome terminal. No change.
   * What was the outcome of this action?
Still unusable.
   * What outcome did you expect instead?
That the application opens my accounting and lets me work.

This shared library is no longer mentioned in the dependencies within synaptic, 
so I am left
wondering how I am getting this error message.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
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 gnucash depends on:
ii  gconf-service              3.2.5-1
ii  gnucash-common             1:2.4.10-5
ii  guile-1.8                  1.8.8+1-8
ii  guile-1.8-libs             1.8.8+1-8
ii  libaqbanking34             5.0.24-1
ii  libc6                      2.13-34
ii  libcairo2                  1.12.2-2
ii  libcrypt-ssleay-perl       0.58-1
ii  libdate-manip-perl         6.32-1
ii  libdbi1                    0.8.4-6
ii  libfinance-quote-perl      1.17+git20120506-1
ii  libgconf-2-4               3.2.5-1
ii  libgdk-pixbuf2.0-0         2.26.1-1
ii  libglade2-0                1:2.6.4-1
ii  libglib2.0-0               2.32.3-1
ii  libgnome-keyring0          3.4.1-1
ii  libgnome2-0                2.32.1-2
ii  libgnomecanvas2-0          2.30.3-1
ii  libgnomeui-0               2.24.5-2
ii  libgoffice-0.8-8           0.8.17-1.2
ii  libgtk2.0-0                2.24.10-1
ii  libgwengui-gtk2-0          4.3.3-1
ii  libgwenhywfar60            4.3.3-1
ii  libhtml-tableextract-perl  2.11-1
ii  libhtml-tree-perl          5.02-1
ii  libktoblzcheck1c2a         1.39-1
ii  libofx4                    1:0.9.4-2.1
ii  libpango1.0-0              1.30.0-1
ii  libwebkitgtk-1.0-0         1.8.1-3.1
ii  libwww-perl                6.04-1
ii  libx11-6                   2:1.5.0-1
ii  libxml2                    2.8.0+dfsg1-4
ii  perl                       5.14.2-12
ii  slib                       3b1-3.1
ii  zlib1g                     1:1.2.7.dfsg-13

Versions of packages gnucash recommends:
ii  gnucash-docs  2.4.1-3
ii  yelp          3.4.2-1

Versions of packages gnucash suggests:
pn  libdbd-mysql    <none>
pn  libdbd-pgsql    <none>
pn  libdbd-sqlite3  <none>

-- no debconf information



--- End Message ---
--- Begin Message ---
tags 680857 + unreproducible
thanks

Dear Gerold,

as we did not get any of the requested information from you, and as we
have some evidence (e.g. gnucash-bin not being part of the package) that
this issue seems to be specific to your installation, we consider this
bug invalid. Hence I am closing it now.

If you still want to provide the requested information, please feel free
and send it to the Gnucash maintainer, i.e. to
[email protected]. We will then consider to re-open this bug
as needed.

Regards,
Micha

--- End Message ---

Reply via email to