Bug#1003887: marked as done (terminology: outputs error on start: Could not fetch a node located at 0x40000004529e)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2026 19:49:13 -0700
with message-id <aq7375p45hxfyvlmhxunb34u7wqc7my5kubeoht7phmsmisawg at pbvkdhyimwqx>
and subject line Re: Bug#1003887: terminology: outputs error on start: Could not fetch a node located at 0x40000004529e
has caused the Debian Bug report #1003887,
regarding terminology: outputs error on start: Could not fetch a node located at 0x40000004529e
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.)


-- 
1003887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003887
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Tomas Pospisek <tpo_deb at sourcepole.ch>
Subject: terminology: outputs error on start: Could not fetch a node located at 0x40000004529e
Date: Mon, 17 Jan 2022 18:29:37 +0100
Size: 9168
URL: <http://alioth-lists.debian.net/pipermail/pkg-e-devel/attachments/20260513/43aa4bc5/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Ross Vandegrift <rvandegrift at debian.org>
Subject: Re: Bug#1003887: terminology: outputs error on start: Could not fetch a node located at 0x40000004529e
Date: Tue, 12 May 2026 19:49:13 -0700
Size: 3219
URL: <http://alioth-lists.debian.net/pipermail/pkg-e-devel/attachments/20260513/43aa4bc5/attachment-0001.eml>