From: Marius Bakke <marius@gnu.org>
To: Christopher Howard <christopher@alaskasi.com>, 39584@debbugs.gnu.org
Subject: bug#39584: evolution: involid page id error when composing emails
Date: Tue, 02 Jun 2020 21:26:43 +0200 [thread overview]
Message-ID: <87367dw9os.fsf@gnu.org> (raw)
In-Reply-To: <c478722de2ab6c6fe11b29849ff7a7815ddb0350.camel@alaskasi.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Christopher Howard <christopher@alaskasi.com> writes:
> After updating system and user to
> f51fd97ec54a98668d63c52d8a6bd75d8dc3292e, I am not able to reproduce
> the problem, at least with a quick test. I send a few dozen emails a
> day, so I should know within a day or two if the problem is really
> gone, and will let you know if it isn't.
>
> Gnome settings is show Gnome version 3.34.2.
That is great news, thanks for following through.
You can close this bug yourself by sending an email to "NNNNN-done"
where NNNNN is the issue ID (39584). The message will still be
delivered to subscribers.
Fingers crossed! :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-02 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 2:09 bug#39584: evolution: involid page id error when composing emails Christopher Howard
2020-02-14 16:07 ` Marius Bakke
2020-02-14 21:12 ` Christopher Howard
2020-02-14 21:12 ` Christopher Howard
2020-02-18 21:56 ` Christopher Howard
2020-02-22 0:39 ` Christopher Howard
2020-02-23 13:45 ` Christopher Howard
2020-02-25 0:18 ` bug#39584: evolution: invalid page id error Christopher Howard
2020-03-04 21:38 ` Christopher Howard
2020-03-16 19:40 ` bug#39584: evolution: involid page id error when composing emails Christopher Howard
2020-05-30 17:32 ` Marius Bakke
2020-06-01 17:10 ` Christopher Howard
2020-06-02 19:20 ` Christopher Howard
2020-06-02 19:26 ` Marius Bakke [this message]
2020-06-04 18:08 ` Christopher Howard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87367dw9os.fsf@gnu.org \
--to=marius@gnu.org \
--cc=39584@debbugs.gnu.org \
--cc=christopher@alaskasi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).