Bug #15102 “Dumps core on start” : Bugs : gconf2 package : Ubuntu

Revision history for this message

In Debian Bug tracker #303687, Thomas Bushnell BSG (tb-becket) wrote on 2005-04-08: Re: Bug#303687: Dumps core on start

#1

severity 303687 normal
reassign 303687 gconf2
thanks

"Adam M." <email address hidden> writes:

> Package: gnucash
> Version: 1.8.10-11
> Severity: grave
>
> gnucash dumps core on startup after the latest update.

This is actually a bug in gconf. There is a simple workaround
described in /usr/share/doc/gnucash/README.Debian.

Thomas

Revision history for this message

In Debian Bug tracker #303687, Steve Langasek (vorlon) wrote on 2005-04-08:

#2

severity 303687 grave
reassign 303687 gtkhtml
thanks

Thomas,

On Thu, Apr 07, 2005 at 10:43:39PM -0700, Thomas Bushnell BSG wrote:
> severity 303687 normal
> reassign 303687 gconf2
> thanks

> "Adam M." <email address hidden> writes:

> > Package: gnucash
> > Version: 1.8.10-11
> > Severity: grave

> > gnucash dumps core on startup after the latest update.

> This is actually a bug in gconf.

I disagree most strenuously. Up until this version, gnucash worked *fine*
without gconf; now, I can't pull gnucash up on a remote display at all
because of this bletcherous dependency. I think this is a grave bug in
gtkhtml, and I don't think this version of gnucash should be allowed into
testing until this problem is resolved.

Requiring users to run -- or mock-up -- a GNOME 1.2 environment to run
gnucash just is not reasonable given that gnucash is already the last GNOME
1.2 app standing.

Thanks,
--
Steve Langasek
postmodern programmer

Revision history for this message

In Debian Bug tracker #303687, Thomas Bushnell BSG (tb-becket) wrote on 2005-04-08:

#3

reassign 303687 gconf2
severity 303687 normal
thanks

> I disagree most strenuously. Up until this version, gnucash worked *fine*
> without gconf; now, I can't pull gnucash up on a remote display at all
> because of this bletcherous dependency. I think this is a grave bug in
> gtkhtml, and I don't think this version of gnucash should be allowed into
> testing until this problem is resolved.

This is crazy. gnucash is a gnome-1 program, and works fine on gnome
1.

Gnome-2 claims to support gnome-1 programs, and does, but a mistake
was made in a gconf2 change. The mistake has a simple patch, approved
by upstream, to fix the gconfd-2 daemon to preserve the necessary
backward compatibility.

Moreover, playing BTS tag isn't the way to settle issues. I reported
this already to the gconf2 maintainers, provided them the patch, and
they said they were already in contact with upstream.

gnucash has a simple fix, it's a "normal" bug because it doesn't cause
any serious difficulty.

Moreover, not using gconf is a bug; gtkhtml should and must use gconf
to preserve configuration information. Since there is such a trivial
patch in gconf2 that fixes the problem, I'd suggest that. There is
also a trivial workaround for users, which is why the bug is no more
than "normal" severity.

What I'd like is to actually *fix* the bug, and since the bug is that
gconf-2 promises backward compatibility and fails to deliver, that's
where it should be fixed.

Please don't move the bug around; you don't maintain any of these
packages AFAICT and you aren't helping.

Thomas

Revision history for this message

In Debian Bug tracker #303687, Steve Langasek (vorlon) wrote on 2005-04-08:

#4

severity 303687 grave
tags 303687 sid
thanks

On Thu, Apr 07, 2005 at 11:36:19PM -0700, Thomas Bushnell BSG wrote:
> > I disagree most strenuously. Up until this version, gnucash worked *fine*
> > without gconf; now, I can't pull gnucash up on a remote display at all
> > because of this bletcherous dependency. I think this is a grave bug in
> > gtkhtml, and I don't think this version of gnucash should be allowed into
> > testing until this problem is resolved.
> This is crazy. gnucash is a gnome-1 program, and works fine on gnome
> 1.

> Gnome-2 claims to support gnome-1 programs, and does, but a mistake
> was made in a gconf2 change. The mistake has a simple patch, approved
> by upstream, to fix the gconfd-2 daemon to preserve the necessary
> backward compatibility.

> Moreover, playing BTS tag isn't the way to settle issues.

> Please don't move the bug around; you don't maintain any of these
> packages AFAICT and you aren't helping.

Well, I think it's equally valid to say that this is a libgconf11 bug, for
trying to launch the gnome2 version of gconfd and *not* falling back to
launching the gnome1.2 version. If people want to fix this via gconf2,
that's fine; the important thing then is that this version of gnucash
doesn't get into testing without the fixed version of gconf2 -- which it
won't.

I'll set the severity to grave, because this *is* an RC issue one way or
another; but it also doesn't affect any packages currently in testing. The
defensive thing to do, if you care about getting this version of gnucash
into sarge, would be to sort out the libgconf11/gtkhtml ungraceful behavior
rather than waiting on the gconf2 bug to be fixed...

Does gnucash work with the woody version of gconf2, btw? If not, this is an
issue that will affect partial upgrades from stable, and is therefore also
an RC bug on whichever package on the gnucash side needs to have a versioned
conflicts with gconf2.

--
Steve Langasek
postmodern programmer

Revision history for this message

In Debian Bug tracker #303687, Thomas Bushnell BSG (tb-becket) wrote on 2005-04-08:

#5

Steve Langasek <email address hidden> writes:

> Well, I think it's equally valid to say that this is a libgconf11 bug, for
> trying to launch the gnome2 version of gconfd and *not* falling back to
> launching the gnome1.2 version. If people want to fix this via gconf2,
> that's fine; the important thing then is that this version of gnucash
> doesn't get into testing without the fixed version of gconf2 -- which it
> won't.

Actually, my understanding is that libgconf11 is trying to launch the
normal gnome-1 thing, and the normal gnome-1 thing is not being
supported correctly by gnome2, though gnome2 promises to. But my
understanding may well be inaccurate in this respect.

> I'll set the severity to grave, because this *is* an RC issue one way or
> another; but it also doesn't affect any packages currently in testing. The
> defensive thing to do, if you care about getting this version of gnucash
> into sarge, would be to sort out the libgconf11/gtkhtml ungraceful behavior
> rather than waiting on the gconf2 bug to be fixed...

Can you please explain why this is RC? There is a bug, yes, but it
isn't critical or severe or even serious by the normal standards of
such bugs, since it has such a trivial workaround.

Even if it prevented reports from being generated entirely, it would
only be important in my opinion, though it might be RC. But normal
bugs with trivial workarounds aren't RC.

> Does gnucash work with the woody version of gconf2, btw?

I don't know the history of it well enough to be able to say.

Thomas

Revision history for this message

In Debian Bug tracker #303687, Steve Langasek (vorlon) wrote on 2005-04-08:

#6

On Fri, Apr 08, 2005 at 01:02:43AM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <email address hidden> writes:

> > Well, I think it's equally valid to say that this is a libgconf11 bug, for
> > trying to launch the gnome2 version of gconfd and *not* falling back to
> > launching the gnome1.2 version. If people want to fix this via gconf2,
> > that's fine; the important thing then is that this version of gnucash
> > doesn't get into testing without the fixed version of gconf2 -- which it
> > won't.

> Actually, my understanding is that libgconf11 is trying to launch the
> normal gnome-1 thing, and the normal gnome-1 thing is not being
> supported correctly by gnome2, though gnome2 promises to. But my
> understanding may well be inaccurate in this respect.

An strace shows that libgconf11 is trying to start gconfd-2, not gconfd-1.
It succeeds in starting it, then fails to find the control file in the
desired gnome 1.2 location.

IMHO, the sensible thing for libgconf11 to do in such a case is to fall back
to starting gconfd-1, which is in fact the version in depends on and
therefore the one that is guaranteed to work. ("Guaranteed" in the sense
that you have a legitimate grievance with the maintainer if it doesn't, at
least.)

> > I'll set the severity to grave, because this *is* an RC issue one way or
> > another; but it also doesn't affect any packages currently in testing. The
> > defensive thing to do, if you care about getting this version of gnucash
> > into sarge, would be to sort out the libgconf11/gtkhtml ungraceful behavior
> > rather than waiting on the gconf2 bug to be fixed...

> Can you please explain why this is RC? There is a bug, yes, but it
> isn't critical or severe or even serious by the normal standards of
> such bugs, since it has such a trivial workaround.

It's because it's trivially fixable that I believe it's unreasonable to ask
the user to have to employ such workarounds by hand. Saying "you must create
this symlink before the package is usable" is a *major* usability gaffe.
Documenting it is not a substitute for providing a suitably usable package;
it's far more trivial for you to kludge around this problem in the package
than to ask each user to do so individually.

> Even if it prevented reports from being generated entirely, it would
> only be important in my opinion, though it might be RC. But normal
> bugs with trivial workarounds aren't RC.

Actually, in my case I have some reports open by default in my
configuration; this causes gnucash to crash on startup if I don't already
have gconfd-1 running, or haven't created the compat symlink. Since there's
no GNOME 1.2 environment available in sarge, I'm certainly not going to have
gconfd-1 running by default.

> > Does gnucash work with the woody version of gconf2, btw?

> I don't know the history of it well enough to be able to say.

Someone will have to determine that before I'll consider this version of
gnucash releasable, then.

--
Steve Langasek
postmodern programmer

On Fri, Apr 08, 2005 at 01:02:43AM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <vorlon@debian.org> writes:

> > Well, I think it's equally valid to say that this is a libgconf11 bug, for
> > trying to launch the gnome2 version of gconfd and *not* falling back to
> > launching the gnome1.2 version.  If people want to fix this via gconf2,
> > that's fine; the important thing then is that this version of gnucash
> > doesn't get into testing without the fixed version of gconf2 -- which it
> > won't.

> Actually, my understanding is that libgconf11 is trying to launch the
> normal gnome-1 thing, and the normal gnome-1 thing is not being
> supported correctly by gnome2, though gnome2 promises to.  But my
> understanding may well be inaccurate in this respect.

An strace shows that libgconf11 is trying to start gconfd-2, not gconfd-1.
It succeeds in starting it, then fails to find the control file in the
desired gnome 1.2 location.

IMHO, the sensible thing for libgconf11 to do in such a case is to fall back
to starting gconfd-1, which is in fact the version in depends on and
therefore the one that is guaranteed to work.  ("Guaranteed" in the sense
that you have a legitimate grievance with the maintainer if it doesn't, at
least.)

> > I'll set the severity to grave, because this *is* an RC issue one way or
> > another; but it also doesn't affect any packages currently in testing.  The
> > defensive thing to do, if you care about getting this version of gnucash
> > into sarge, would be to sort out the libgconf11/gtkhtml ungraceful behavior
> > rather than waiting on the gconf2 bug to be fixed...

> Can you please explain why this is RC?  There is a bug, yes, but it
> isn't critical or severe or even serious by the normal standards of
> such bugs, since it has such a trivial workaround.

It's because it's trivially fixable that I believe it's unreasonable to ask
the user to have to employ such workarounds by hand.  Saying "you must create
this symlink before the package is usable" is a *major* usability gaffe.
Documenting it is not a substitute for providing a suitably usable package;
it's far more trivial for you to kludge around this problem in the package
than to ask each user to do so individually.

> Even if it prevented reports from being generated entirely, it would
> only be important in my opinion, though it might be RC.  But normal
> bugs with trivial workarounds aren't RC.

Actually, in my case I have some reports open by default in my
configuration; this causes gnucash to crash on startup if I don't already
have gconfd-1 running, or haven't created the compat symlink.  Since there's
no GNOME 1.2 environment available in sarge, I'm certainly not going to have
gconfd-1 running by default.

> > Does gnucash work with the woody version of gconf2, btw?

> I don't know the history of it well enough to be able to say.

Someone will have to determine that before I'll consider this version of
gnucash releasable, then.

-- 
Steve Langasek
postmodern programmer

Revision history for this message

In Debian Bug tracker #303687, Josselin Mouette (joss) wrote on 2005-04-08: reassign 303687 to gconf

#7

# Automatically generated email from bts, devscripts version 2.8.10
reassign 303687 gconf

Revision history for this message

In Debian Bug tracker #303687, Thomas Bushnell BSG (tb-becket) wrote on 2005-04-08: Re: Bug#303687: Dumps core on start

#8

Steve Langasek <email address hidden> writes:

> An strace shows that libgconf11 is trying to start gconfd-2, not gconfd-1.
> It succeeds in starting it, then fails to find the control file in the
> desired gnome 1.2 location.

Ok, then perhaps it's true that fixing libgconf11 is best.
Regardless, those packages are both maintained by the same (generally
nonresponsive) maintainer.

> It's because it's trivially fixable that I believe it's unreasonable to ask
> the user to have to employ such workarounds by hand. Saying "you must create
> this symlink before the package is usable" is a *major* usability gaffe.
> Documenting it is not a substitute for providing a suitably usable package;
> it's far more trivial for you to kludge around this problem in the package
> than to ask each user to do so individually.

My first inclination was simply to add a tweak to the script to create
the necessary symlink. But this seems brittle; it will prevent the
program working correctly on a gnome-1 system, won't it? By contrast,
starting gconfd-1 is also surely wrong; my understanding is that it is
seriously wrong to have both gconfd-1 and gconfd-2 running at the same
time, but perhaps I'm understanding incorrectly. And starting
gconfd-1 is brittle also, even if harmless, because it might already
be running.

So I'm happy to put either of these or something else in the gnucash
startup script if you can explain which you think best and why.

> Actually, in my case I have some reports open by default in my
> configuration; this causes gnucash to crash on startup if I don't already
> have gconfd-1 running, or haven't created the compat symlink. Since there's
> no GNOME 1.2 environment available in sarge, I'm certainly not going to have
> gconfd-1 running by default.

Sure, but that's still not RC. The bug doesn't prevent gnucash from
working, it simply requires you to put a symlink in place.

If you are correct that the bug is in libgconf11, then it is certainly
in the current sarge version also.

Thomas

Steve Langasek <vorlon@debian.org> writes:

> An strace shows that libgconf11 is trying to start gconfd-2, not gconfd-1.
> It succeeds in starting it, then fails to find the control file in the
> desired gnome 1.2 location.

Ok, then perhaps it's true that fixing libgconf11 is best.
Regardless, those packages are both maintained by the same (generally
nonresponsive) maintainer.

> It's because it's trivially fixable that I believe it's unreasonable to ask
> the user to have to employ such workarounds by hand.  Saying "you must create
> this symlink before the package is usable" is a *major* usability gaffe.
> Documenting it is not a substitute for providing a suitably usable package;
> it's far more trivial for you to kludge around this problem in the package
> than to ask each user to do so individually.

My first inclination was simply to add a tweak to the script to create
the necessary symlink.  But this seems brittle; it will prevent the
program working correctly on a gnome-1 system, won't it?  By contrast,
starting gconfd-1 is also surely wrong; my understanding is that it is
seriously wrong to have both gconfd-1 and gconfd-2 running at the same
time, but perhaps I'm understanding incorrectly.  And starting
gconfd-1 is brittle also, even if harmless, because it might already
be running.

So I'm happy to put either of these or something else in the gnucash
startup script if you can explain which you think best and why.

> Actually, in my case I have some reports open by default in my
> configuration; this causes gnucash to crash on startup if I don't already
> have gconfd-1 running, or haven't created the compat symlink.  Since there's
> no GNOME 1.2 environment available in sarge, I'm certainly not going to have
> gconfd-1 running by default.

Sure, but that's still not RC.  The bug doesn't prevent gnucash from
working, it simply requires you to put a symlink in place.

If you are correct that the bug is in libgconf11, then it is certainly
in the current sarge version also.

Thomas

Revision history for this message

In Debian Bug tracker #303687, Josselin Mouette (joss) wrote on 2005-04-08: Bug#303687: Should be fixed

#9

Could you please tell us whether gnucash still crashes for you with the
latest (1.0.9-7) gconf packages?

Thanks,
--
.''`. Josselin Mouette /\./\
: :' : <email address hidden>
`. `' <email address hidden>
`- Debian GNU/Linux -- The power of freedom

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-08:

#10

Automatically imported from Debian bug report #303687 http://bugs.debian.org/303687

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-08:

#11

Download full text (6.0 KiB)

Message-Id: <email address hidden>
Date: Fri, 08 Apr 2005 00:24:46 -0500
From: "Adam M." <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Dumps core on start

Package: gnucash
Version: 1.8.10-11
Severity: grave

gnucash dumps core on startup after the latest update.

open("/home/adamm/.gconfd/lock/ior", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/share/locale/en_CA.UTF-8/LC_MESSAGES/gconf1.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale/en_CA.utf8/LC_MESSAGES/gconf1.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale/en_CA/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1 ENOENT
(No such file or directory)
close(10) = 0
close(11) = 0
write(2, "\n", 1
) = 1
write(2, "gtkhtml", 7gtkhtml) = 7
write(2, "-", 1-) = 1
write(2, "ERROR **: ", 10ERROR **: ) = 10
write(2, "gconf error: Failed to contact c"..., 276gconf error: Failed
to contact configuration server (a likely cause of this is that you have
an existing configuration server (gconfd) running, but it isn't
reachable from here - if you're logged in from two machines at once, you
may need to enable TCP networking for ORBit)

) = 276
write(2, "\naborting...\n", 13
aborting...
) = 13
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(14241, 14241, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT (core dumped) +++

-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)

Versions of packages gnucash depends on:
ii bonobo 1.0.22-2.2 The GNOME Bonobo System.
ii gdk-imlib1 1.9.14-16.2 imaging library for use with gtk (
ii gnucash-common 1.8.10-11 A personal finance tracking progra
ii guile-1.6-libs 1.6.7-1 Main Guile libraries
ii guile-1.6-slib 1.6.7-1 Guile SLIB support
ii libart2 1.4.2-19 The GNOME canvas widget - runtime
ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio
ii libbonobo2 1.0.22-2.2 The GNOME Bonobo library.
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libdate-manip-perl 5.42a-3 a perl library for manipulating da
ii libdb3 3.2.9-22 Berkeley v3 Database Libraries [ru
ii libesd0 0.2.35-2 Enlightened Sound Daemon - Shared
ii libfinance-quote-per 1.08-1 Perl module for retrieving stock q
ii libfreetype6 2.1.7-2.3 FreeT...

Message-Id: <E1DJlz4-0003iD-Ut@mira.lan.galacticasoftware.com>
Date: Fri, 08 Apr 2005 00:24:46 -0500
From: "Adam M." <gnuman1@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Dumps core on start

Package: gnucash
Version: 1.8.10-11
Severity: grave

gnucash dumps core on startup after the latest update.

open("/home/adamm/.gconfd/lock/ior", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/share/locale/en_CA.UTF-8/LC_MESSAGES/gconf1.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale/en_CA.utf8/LC_MESSAGES/gconf1.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale/en_CA/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/gconf1.mo", O_RDONLY) = -1 ENOENT
(No such file or directory)
close(10)                               = 0
close(11)                               = 0
write(2, "\n", 1
)                       = 1
write(2, "gtkhtml", 7gtkhtml)                  = 7
write(2, "-", 1-)                        = 1
write(2, "ERROR **: ", 10ERROR **: )              = 10
write(2, "gconf error: Failed to contact c"..., 276gconf error: Failed
to contact configuration server (a likely cause of this is that you have
an existing configuration server (gconfd) running, but it isn't
reachable from here - if you're logged in from two machines at once, you
may need to enable TCP networking for ORBit)

) = 276
write(2, "\naborting...\n", 13
aborting...
)         = 13
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(14241, 14241, SIGABRT)           = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT (core dumped) +++

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)

Versions of packages gnucash depends on:
ii  bonobo               1.0.22-2.2          The GNOME Bonobo System.
ii  gdk-imlib1           1.9.14-16.2         imaging library for use with gtk (
ii  gnucash-common       1.8.10-11           A personal finance tracking progra
ii  guile-1.6-libs       1.6.7-1             Main Guile libraries
ii  guile-1.6-slib       1.6.7-1             Guile SLIB support
ii  libart2              1.4.2-19            The GNOME canvas widget - runtime 
ii  libaudiofile0        0.2.6-6             Open-source version of SGI's audio
ii  libbonobo2           1.0.22-2.2          The GNOME Bonobo library.
ii  libc6                2.3.2.ds1-20        GNU C Library: Shared libraries an
ii  libdate-manip-perl   5.42a-3             a perl library for manipulating da
ii  libdb3               3.2.9-22            Berkeley v3 Database Libraries [ru
ii  libesd0              0.2.35-2            Enlightened Sound Daemon - Shared 
ii  libfinance-quote-per 1.08-1              Perl module for retrieving stock q
ii  libfreetype6         2.1.7-2.3           FreeType 2 font engine, shared lib
ii  libgal23             0.24-1.4            G App Libs (run time library)
ii  libgconf11           1.0.9-6             GNOME configuration database syste
ii  libgdk-pixbuf-gnome2 0.22.0-7            The GNOME1 Canvas pixbuf library
ii  libgdk-pixbuf2       0.22.0-7            The GdkPixBuf image library, gtk+ 
ii  libghttp1            1.0.9-15            original GNOME HTTP client library
ii  libglade-gnome0      1:0.17-3            Library to load .glade files at ru
ii  libglade0            1:0.17-3            Library to load .glade files at ru
ii  libglib1.2           1.2.10-9            The GLib library of C routines
ii  libgnome32           1.4.2-19            The GNOME libraries
ii  libgnomeprint15      0.37-5              The GNOME Print architecture - run
ii  libgnomesupport0     1.4.2-19            The GNOME libraries (Support libra
ii  libgnomeui32         1.4.2-19            The GNOME libraries (User Interfac
ii  libgtk1.2            1.2.10-17           The GIMP Toolkit set of widgets fo
ii  libgtkhtml1.1-3      1.1.10-4            HTML rendering/editing library - r
ii  libguile-ltdl-1      1.6.7-1             Guile's patched version of libtool
ii  libguppi16           0.40.3-11           GNOME graph and plot component
ii  libgwrapguile1       1.3.4-12            g-wrap: Tool for exporting C libra
ii  libice6              4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library
ii  libltdl3             1.5.6-6             A system independent dlopen wrappe
ii  liboaf0              0.6.10-3            The GNOME Object Activation Framew
ii  libofx1              1:0.7.0-7           library to support Open Financial 
ii  liborbit0            0.5.17-9            Libraries for ORBit - a CORBA ORB
ii  libpopt0             1.7-5               lib for parsing cmdline parameters
ii  libqthreads-12       1.6.7-1             QuickThreads library for Guile
ii  libsm6               4.3.0.dfsg.1-12.0.1 X Window System Session Management
ii  libstdc++5           1:3.3.5-12          The GNU Standard C++ Library v3
ii  libx11-6             4.3.0.dfsg.1-12.0.1 X Window System protocol client li
ii  libxext6             4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte
ii  libxi6               4.3.0.dfsg.1-12.0.1 X Window System Input extension li
ii  libxml1              1:1.8.17-10         GNOME XML library
ii  libzvt2              1.4.2-19            The GNOME zvt (zterm) widget
ii  oaf                  0.6.10-3            The GNOME Object Activation Framew
ii  psfontmgr            0.11.8-0.1          PostScript font manager -- part of
ii  slib                 3a1-4.2             Portable Scheme library
ii  x-ttcidfont-conf     17                  Configure TrueType and CID fonts f
ii  xlibs                4.3.0.dfsg.1-12     X Keyboard Extension (XKB) configu
ii  zlib1g               1:1.2.2-4           compression library - runtime

-- no debconf information

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-08:

#12

Message-ID: <email address hidden>
Date: Thu, 07 Apr 2005 22:43:39 -0700
From: Thomas Bushnell BSG <email address hidden>
To: "Adam M." <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#303687: Dumps core on start

severity 303687 normal
reassign 303687 gconf2
thanks

"Adam M." <email address hidden> writes:

> Package: gnucash
> Version: 1.8.10-11
> Severity: grave
>
> gnucash dumps core on startup after the latest update.

This is actually a bug in gconf. There is a simple workaround
described in /usr/share/doc/gnucash/README.Debian.

Thomas

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-08:

#13

Message-ID: <email address hidden>
Date: Thu, 7 Apr 2005 23:23:58 -0700
From: Steve Langasek <email address hidden>
To: Thomas Bushnell BSG <email address hidden>, <email address hidden>
Cc: "Adam M." <email address hidden>, <email address hidden>
Subject: Re: Bug#303687: Dumps core on start

--fWddYNRDgTk9wQGZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

severity 303687 grave
reassign 303687 gtkhtml
thanks

Thomas,

On Thu, Apr 07, 2005 at 10:43:39PM -0700, Thomas Bushnell BSG wrote:
> severity 303687 normal
> reassign 303687 gconf2
> thanks

> "Adam M." <email address hidden> writes:

> > Package: gnucash
> > Version: 1.8.10-11
> > Severity: grave

> > gnucash dumps core on startup after the latest update.

> This is actually a bug in gconf.

I disagree most strenuously. Up until this version, gnucash worked *fine*
without gconf; now, I can't pull gnucash up on a remote display at all
because of this bletcherous dependency. I think this is a grave bug in
gtkhtml, and I don't think this version of gnucash should be allowed into
testing until this problem is resolved.

Requiring users to run -- or mock-up -- a GNOME 1.2 environment to run
gnucash just is not reasonable given that gnucash is already the last GNOME
1.2 app standing.

Thanks,
--=20
Steve Langasek
postmodern programmer

--fWddYNRDgTk9wQGZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCViN7KN6ufymYLloRApnJAJ9RQYdza0f/Mai19XLD8OsoXCkSeACfVwHb
eO9krCajndPQ3gU1Imq1bBY=
=3RYq
-----END PGP SIGNATURE-----

--fWddYNRDgTk9wQGZ--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-08:

#14

Message-ID: <email address hidden>
Date: Thu, 07 Apr 2005 23:36:19 -0700
From: Thomas Bushnell BSG <email address hidden>
To: Steve Langasek <email address hidden>
Cc: <email address hidden>, "Adam M." <email address hidden>,
<email address hidden>
Subject: Re: Bug#303687: Dumps core on start