Bug#357540: marked as done (gconf2: Failed to get lock)

Mon Feb 2 13:48:03 UTC 2009

Your message dated Mon, 02 Feb 2009 14:45:22 +0100
with message-id <1233582322.18512.53.camel at tomoyo>
and subject line Fixed in experimental
has caused the Debian Bug report #357540,
regarding gconf2: Failed to get lock
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 owner at bugs.debian.org
immediately.)

-- 
357540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357540
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Ross Boylan <ross at biostat.ucsf.edu>
Subject: gconf2: Failed to get lock
Date: Fri, 17 Mar 2006 15:46:23 -0800
Size: 3164
Url: http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090202/f99d7ebe/attachment.eml 
-------------- next part --------------
An embedded message was scrubbed...
From: Josselin Mouette <joss at debian.org>
Subject: Fixed in experimental
Date: Mon, 02 Feb 2009 14:45:22 +0100
Size: 2314
Url: http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090202/f99d7ebe/attachment-0001.eml 