Bug#601897: marked as done (libnotify1: Raises exception if notify_uninit is called immediately after notify_init)

Wed Apr 27 19:33:12 BST 2022

Your message dated Wed, 27 Apr 2022 20:32:14 +0200
with message-id <1595A688-2C77-4E8F-AB65-73D0C0145F83 at getmailspring.com>
and subject line Bug #601897
has caused the Debian Bug report #601897,
regarding libnotify1: Raises exception if notify_uninit is called immediately after notify_init
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.)

-- 
601897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601897
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: John Lindgren <john.lindgren at tds.net>
Subject: libnotify1: Raises exception if notify_uninit is called immediately after notify_init
Date: Sat, 30 Oct 2010 15:44:32 -0400
Size: 5940
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20220427/93e9b62d/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Marco Trevisan <marco at trevi.me>
Subject: Bug #601897
Date: Wed, 27 Apr 2022 20:32:14 +0200
Size: 3110
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20220427/93e9b62d/attachment-0001.eml>