From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 69118@debbugs.gnu.org
Subject: bug#69118: 30.0.50; Crash X server by enlarging the face
Date: Thu, 15 Feb 2024 09:42:20 +0800 [thread overview]
Message-ID: <87frxuzeo3.fsf@yahoo.com> (raw)
In-Reply-To: <871q9f5up2.fsf@lco.mail-host-address-is-not-set> (Jean Louis's message of "Wed, 14 Feb 2024 11:14:17 +0300")
Jean Louis <bugs@gnu.support> writes:
> I am using following face:
>
> Hide Default face: [sample]
> State : STANDARD.
> Basic default face.
> [X] Font Family: DejaVu Sans Mono
> [X] Font Foundry: PfEd
> [X] Width: Value Menu normal
> [X] Height: Value Menu Font size in 1/10 pt: 108
> [X] Weight: Value Menu regular
> [X] Slant: Value Menu normal
> [X] Underline: Value Menu Off
> [X] Overline: Value Menu Off
> [X] Strike-through: Value Menu Off
> [X] Box around text: Value Menu Off
> [X] Inverse-video: Value Menu Off
> [X] Foreground: #303030 Choose (sample)
> [X] Background: #ffffff Choose (sample)
> [X] Stipple: Value Menu None
> [X] Extend: Value Menu Off
> [X] Inherit:
>
> When I go to *Scratch* buffer, I can do C-x + to enlarge the face, and
> if I go to larger face, at certain point the X server crashes. Emacs
> remains in memory.
>
> But because X server crashes, I cannot do again `$ startx'. What I do is
> I open `emacsclient' in console and kill *Scratch* buffer, then I can go
> again to `startx'. Emacs does not crash.
All X server crashes should be reported to the distributor of the
crashing X server, not us. No requests issued by clients should ever
crash the X server, and in general those which do are perfectly
legitimate from a client's perspective.
next prev parent reply other threads:[~2024-02-15 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 8:14 bug#69118: 30.0.50; Crash X server by enlarging the face Jean Louis
2024-02-15 1:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-15 6:50 ` Eli Zaretskii
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=87frxuzeo3.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=69118@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=luangruo@yahoo.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 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.