GNU bug report logs - #79343
Hung after xinput remove-master

Previous Next

Package: emacs;

Reported by: Fake Baka <spoof1024 <at> gmail.com>

Date: Sat, 30 Aug 2025 01:30:03 UTC

Severity: normal

Done: Po Lu <luangruo <at> yahoo.com>

Full log


Message #8 received at 79343 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Fake Baka <spoof1024 <at> gmail.com>, Po Lu <luangruo <at> yahoo.com>
Cc: 79343 <at> debbugs.gnu.org
Subject: Re: bug#79343: Hung after xinput remove-master
Date: Sat, 30 Aug 2025 21:51:11 +0300
> From: Fake Baka <spoof1024 <at> gmail.com>
> Date: Fri, 29 Aug 2025 21:07:58 +0300
> 
> Steps to reproduce:
> xinput create-master test
> xinput remove-master 11      # 11 is id of master device I got, your id may vary
> 
> Effect:
> All Emacs processes got hung: no response on input, no GUI output, SIGTERM killed windows, but not the
> processes.

Thanks.  Po Lu, any comments or suggestions?

> GDB bt full output:
> Starting program: /home/y/tmp/emacs-debug/emacs-30.2/src/emacs -Q --name db
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffef98f6c0 (LWP 234009)]
> [New Thread 0x7fffef18e6c0 (LWP 234010)]
> [New Thread 0x7fffee98d6c0 (LWP 234011)]
> [New Thread 0x7fffee1096c0 (LWP 234013)]
> [New Thread 0x7fffed1ff6c0 (LWP 234014)]
> [New Thread 0x7fffec9fe6c0 (LWP 234015)]
> 
> Thread 1 "emacs" received signal SIGABRT, Aborted.

How did you trigger SIGABRT in Emacs?




This bug report was last modified 4 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.