Bug#648159: marked as done (libglib2.0-0: GLib-GObject-CRITICAL triggers Fatal IO error 11)

Wed Apr 4 10:21:06 BST 2018

Your message dated Wed, 4 Apr 2018 10:18:58 +0100
with message-id <20180404091858.GA8152 at espresso.pseudorandom.co.uk>
and subject line Re: Bug#648159: Info received (Bug#648159: Info received (Bug#648159: libglib2.0-0: GLib-GObject-CRITICAL triggers Fatal IO error 11))
has caused the Debian Bug report #648159,
regarding libglib2.0-0: GLib-GObject-CRITICAL triggers Fatal IO error 11
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.)

-- 
648159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648159
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Skippy le Grand Gourou <lecotegougdelaforce at free.fr>
Subject: libglib2.0-0: GLib-GObject-CRITICAL triggers Fatal IO error 11
Date: Wed, 09 Nov 2011 09:42:55 +0100
Size: 4205
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20180404/21283f40/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Simon McVittie <smcv at debian.org>
Subject: Re: Bug#648159: Info received (Bug#648159: Info received (Bug#648159: libglib2.0-0: GLib-GObject-CRITICAL triggers Fatal IO error 11))
Date: Wed, 4 Apr 2018 10:18:58 +0100
Size: 2957
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20180404/21283f40/attachment-0001.mht>