Your message dated Wed, 27 Jan 2010 16:21:53 +0100
with message-id <[email protected]>
and subject line Re: Bug#566272: shares-admin fails to start: Error loading UI
has caused the Debian Bug report #566272,
regarding shares-admin fails to start: Error loading UI 
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.)


-- 
566272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566272
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-system-tools
Version: 2.22.0-3
Severity: normal

shares-admin does not start and yields  the following error message:
** (shares-admin:7155): CRITICAL **: Error loading UI: Duplicate object id 
'label' on line 144 (previously on line 97)

The line numbers probably refer to one of the backend scripts - but I could not 
find out which nor why it would fail.

Best regards

Oliver
-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-k7-100118 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-system-tools depends on:
ii  gconf2                  2.22.0-1         GNOME configuration database syste
ii  gksu                    2.0.0-8          graphical frontend to su
ii  libatk1.0-0             1.22.0-1         The ATK accessibility toolkit
ii  libc6                   2.7-18           GNU C Library: Shared libraries
ii  libcairo2               1.6.4-7          The Cairo 2D vector graphics libra
ii  libdbus-1-3             1.2.1-5+lenny1   simple interprocess messaging syst
ii  libgconf2-4             2.22.0-1         GNOME configuration database syste
ii  libglib2.0-0            2.22.2-2~bpo50+1 The GLib library of C routines
ii  libgnomevfs2-0          1:2.22.0-5       GNOME Virtual File System (runtime
ii  libgtk2.0-0             2.18.3-1~bpo50+1 The GTK+ graphical user interface 
ii  libnautilus-extension1  2.20.0-7         libraries for nautilus components 
ii  liboobs-1-4             2.22.0-2         GObject based interface to system-
ii  libpango1.0-0           1.20.5-5         Layout and rendering of internatio
ii  perl                    5.10.0-19lenny2  Larry Wall's Practical Extraction 
ii  system-tools-backends   2.6.0-2lenny3    System Tools to manage computer co

Versions of packages gnome-system-tools recommends:
ii  gnome-control-center        1:2.22.2.1-2 utilities to configure the GNOME d

Versions of packages gnome-system-tools suggests:
ii  ntp               1:4.2.4p4+dfsg-8lenny3 Network Time Protocol daemon and u
ii  samba-common      2:3.2.5-4lenny7        Samba common files used by both th
pn  wvdial            <none>                 (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.28.2-1

On 23/01/10 08:56, [email protected] wrote:
Bonjour Josselin,

Merci beaucoup for the quick response and for pointing me to the right file (I 
was looking in the backends directory).

ii  libgtk2.0-0             2.18.3-1~bpo50+1 The GTK+ graphical user
interface
I think this was pulled in by building nvidia-settings and the new 
nvidia-driver 190.43, which was required by the 2.6.32 kernel that I am forced 
to use. Once you start upgrading _one_ package...

I guess we could do a stable upgrade to fix that, but I consider it of
low priority.
I just changed the second defintion of "label" into "label2". That fixes it.
(I should probably build a new local package...)

But you are right: low priority, as I am probably the one in a million who has 
this issue due to a newer kernel and a backported package.

Closing for unstable since it's fixed there. It can still be tracked in stable if there was interest but I agree this is low prio.

Cheers,
Emilio


--- End Message ---

Reply via email to