From: Po Lu <luangruo@yahoo.com>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 55422@debbugs.gnu.org, pieter.van.prooijen@teloden.nl
Subject: bug#55422: Emacs not starting due to gsettings changes.
Date: Sun, 15 May 2022 12:19:43 +0800 [thread overview]
Message-ID: <87fslbsa00.fsf@yahoo.com> (raw)
In-Reply-To: <87k0an1m10.fsf@codeisgreat.org> (Pankaj Jangid's message of "Sun, 15 May 2022 09:32:03 +0530")
[Please do not change the subject line when replying to bug reports.]
Pankaj Jangid <pankaj@codeisgreat.org> writes:
> Is the fix available on master. Because in the latest pull, I am still
> getting the error. And Emacs is not starting.
Please set a breakpoint on this part of xsettings.c:
GVariant *val;
const char *antialias;
- if (!xg_settings_key_valid_p (settings, GSETTINGS_FONT_ANTIALIASING))
return;
val = g_settings_get_value (settings, GSETTINGS_FONT_ANTIALIASING);
What is the return of `xg_settings_key_valid_p'?
next prev parent reply other threads:[~2022-05-15 4:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 3:20 bug#55422: Emacs not starting due to gsettings changes Pankaj Jangid
2022-05-15 3:24 ` bug#55422: [Various] " Pankaj Jangid
2022-05-15 4:02 ` bug#55422: Still not starting Pankaj Jangid
2022-05-15 4:19 ` Po Lu [this message]
2022-05-15 5:17 ` bug#55422: Emacs not starting due to gsettings changes Pankaj Jangid
2022-05-15 5:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 6:08 ` Pankaj Jangid
2022-05-15 6:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 7:31 ` Pankaj Jangid
2022-05-15 7:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 9:29 ` Pankaj Jangid
2022-05-15 9:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 11:21 ` Pankaj Jangid
2022-05-15 11:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 7:42 ` Eli Zaretskii
2022-05-15 9:33 ` Pankaj Jangid
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=87fslbsa00.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=55422@debbugs.gnu.org \
--cc=pankaj@codeisgreat.org \
--cc=pieter.van.prooijen@teloden.nl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.