Subject: GLib-GObject-WARNING **: g_object_set_valist: construct property
"sm-connect" for object `GnomeProgram' can't be set
Date: Mon, 24 May 2004 20:53:01 +0200
Package: debconf
Version: 1.4.25
Severity: normal
When I install packages or run dpkg-reconfigure I get messages like these:
GLib-GObject-WARNING **: g_object_set_valist: construct property "sm-connect" for object `GnomeProgram' can't be set after construction at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 47.
I just tried dpkg-reconfiguring a package. After getting this message
(twice, with different line numbers) I _do_ get a GNOME debconf window
which seems to function correctly, so this may not be a serious problem.
I'm not sure that this is debconf's fault. Please reassign if necessary.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=en_IE@euro, LC_CTYPE=en_IE@euro
Versions of packages debconf depends on:
ii debconf-i18n 1.4.25 full internationalization support
ii perl-base 5.8.3-3 The Pathologically Eclectic Rubbis
-- debconf information:
* debconf/priority: low
* debconf/frontend: Gnome
Subject: Re: DBTS#250751: GLib-GObject-WARNING **: g_object_set_valist:
construct property "sm-connect" for object `GnomeProgram' can't be set
Date: Wed, 09 Jun 2004 11:42:29 +0200
On Wed, 2004-06-09 at 10:01, Jérôme Warnier wrote:
> I have the same problem, could you explain more in details how you fixed
> it?
I upgraded from sarge to sid. Unfortunately I don't know what
actually fixed the problem.
--
Thomas Hood
Information stored: Bug#250751; Package debconf.
(full text, mbox, link).
Subject: Re: DBTS#250751: GLib-GObject-WARNING **: g_object_set_valist:
construct property "sm-connect" for object `GnomeProgram' can't be set
Date: Wed, 09 Jun 2004 12:22:15 +0200
Le mer 09/06/2004 à 11:42, Thomas Hood a écrit :
> On Wed, 2004-06-09 at 10:01, Jérôme Warnier wrote:
> > I have the same problem, could you explain more in details how you fixed
> > it?
>
> I upgraded from sarge to sid. Unfortunately I don't know what
> actually fixed the problem.
This bug shouldn't have been closed then, but tagged "sarge". I hit the
same bug, after having removed most GNOME 1.4 packages still lying
around, I think.
> --
> Thomas Hood
--
Jérôme Warnier
Consultant
BeezNest
http://beeznest.net
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.