From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: EMACS: failed to commit changes to dconf: The connection is closed
Date: Fri, 13 May 2022 18:38:55 -0600 [thread overview]
Message-ID: <CAK-n8j6zaYPdO45_=cAQ6vRJvQmc9VHxMgegao+TaxW+tgZ9MQ@mail.gmail.com> (raw)
I'm running GNU Emacs 28.1 (build 2, x86_64-pc-cygwin, GTK+ Version
3.22.28, cairo version 1.17.4) of 2022-04-13 in an xterm in Cygwin X.
I have a file open. If I click on File | Save As... I get several
copies of the following message:
(emacs:2775): dconf-WARNING **: failed to commit changes to dconf:
The connection is closed
What's happening here?
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://ad1c.us
next reply other threads:[~2022-05-14 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 0:38 Jim Reisert AD1C [this message]
2022-05-14 2:04 ` Ken Brown
2022-05-14 4:44 ` Brian Inglis
2022-05-14 17:32 ` Jim Reisert AD1C
2022-05-14 17:39 ` Jim Reisert AD1C
2022-05-15 1:40 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK-n8j6zaYPdO45_=cAQ6vRJvQmc9VHxMgegao+TaxW+tgZ9MQ@mail.gmail.com' \
--to=jjreisert@alum.mit.edu \
--cc=cygwin@cygwin.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.
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).