unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@alaskasi.com>
To: 39584-done@debbugs.gnu.org
Subject: bug#39584: evolution: involid page id error when composing emails
Date: Thu, 04 Jun 2020 10:08:51 -0800	[thread overview]
Message-ID: <fc69a70820586e1aae8db439943bc3d67e27e99a.camel@alaskasi.com> (raw)
In-Reply-To: <af057e1a9fa2414c0e29d33e5f5bfe09355b5ff0.camel@alaskasi.com>

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

I have been using evolution heavily for about two days and have not
seen the error appear again. I used to see it about 10 times a day.

-- 
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com

[-- Attachment #2: Type: text/html, Size: 740 bytes --]

      parent reply	other threads:[~2020-06-04 18:10 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
2020-06-04 18:08 ` Christopher Howard [this message]

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=fc69a70820586e1aae8db439943bc3d67e27e99a.camel@alaskasi.com \
    --to=christopher@alaskasi.com \
    --cc=39584-done@debbugs.gnu.org \
    /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).