From: Eli Zaretskii <eliz@gnu.org>
To: "Ľuboš Pinteš" <lubos.pintes@gmail.com>
Cc: 68755@debbugs.gnu.org
Subject: bug#68755: 29.2; Emacs crashes repeatedly after some steps
Date: Sat, 27 Jan 2024 13:25:04 +0200 [thread overview]
Message-ID: <86a5or81db.fsf@gnu.org> (raw)
In-Reply-To: <95800b95-5214-43f9-81b9-2af2041f34ed@gmail.com> (lubos.pintes@gmail.com)
> Date: Sat, 27 Jan 2024 10:08:11 +0100
> From: Ľuboš Pinteš
> <lubos.pintes@gmail.com>
>
> From: lubos.pintes@gmail.com
> Subject: 29.2; Emacs crashes repeatedly after some steps
> --text follows this line--
> 1. I customized a little, my .emacs is below:
> (custom-set-variables
> ;; custom-set-variables was added by Custom.
> ;; If you edit it by hand, you could mess it up, so be careful.
> ;; Your init file should contain only one such instance.
> ;; If there is more than one, they won't work right.
> '(global-visual-line-mode t)
> '(line-number-mode nil)
> '(package-archives
> '(("gnu" . "https://elpa.gnu.org/packages/")
> ("nongnu" . "https://elpa.nongnu.org/nongnu/")
> ("melpa" . "https://melpa.org/packages/")))
> '(package-install-upgrade-built-in t)
> '(package-native-compile t)
> '(package-selected-packages
> '(hydra httprepl faceup go-translate bind-key eglot eldoc flymake
> jsonrpc org project soap-client use-package verilog-mode))
> '(package-version-column-width 0))
> (custom-set-faces
> ;; custom-set-faces was added by Custom.
> ;; If you edit it by hand, you could mess it up, so be careful.
> ;; Your init file should contain only one such instance.
> ;; If there is more than one, they won't work right.
> )
>
> 2. M-x package-list-packages
>
> 3. Pressed U.
>
> 4. Pressed x. I needed to press it more times, it was not finished. As a
> screenreader user, it seemed to me that Emacs is not responsive during
> the installation process.
> So I tried to interrupt speech by pressing some keys.
>
> 5. After installation of 11 packages I pressed q and exited Emacs.
>
> 6. Run Emacs again and press C-h f, gomoku
>
> 7. After this Emacs crashes.
>
> 8. If it matters I installed Emacs through scoop package manager.
Thanks. Please run Emacs under GDB, and when it crashes, produce a
backtrace from the crash ("thread apply all bt") and post the
backtrace here.
next prev parent reply other threads:[~2024-01-27 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 9:08 bug#68755: 29.2; Emacs crashes repeatedly after some steps Ľuboš Pinteš
2024-01-27 11:25 ` Eli Zaretskii [this message]
[not found] ` <b7b62209-3733-4868-8a0d-bf794ad8aac4@gmail.com>
2024-01-27 13:35 ` Eli Zaretskii
2024-01-27 14:03 ` Ľuboš Pinteš
2024-01-27 14:37 ` Eli Zaretskii
2024-01-27 15:00 ` Ľuboš Pinteš
2024-01-27 15:35 ` Eli Zaretskii
2024-01-27 15:42 ` Ľuboš Pinteš
2024-01-27 15:50 ` Eli Zaretskii
2024-01-27 17:16 ` Ľuboš Pinteš
2024-01-27 18:40 ` Eli Zaretskii
2024-01-28 8:23 ` Eli Zaretskii
2024-01-28 17:46 ` Ľuboš Pinteš
2024-01-28 19:00 ` Corwin Brust
2024-01-28 19:37 ` Ľuboš Pinteš
2024-01-28 20:01 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5or81db.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68755@debbugs.gnu.org \
--cc=lubos.pintes@gmail.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/emacs.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).