persistent crash

persistent crash

[John ff]

How do I stop this error?

Master build from source
==John ffitch
Debugger entered--Lisp error: (wrong-number-of-arguments
#f(compiled-function (&optional device) #<bytecode
-0x1d28e41334b4e2c8>) 2) 
  device-class(#<frame *GNU Emacs* - GNU Emacs at weir 0x28051d0> "SEM
  USB Keyboard") 
  minibuffer-setup-on-screen-keyboard()
  read-from-minibuffer("Find file: " "~/" (keymap (keymap (32
  . minibuffer-complete-word)) keymap (down . next-history-element)
  (up . previous-history-element) (32 . minibuffer-complete-word) (10
  . minibuffer-complete-and-exit) (13 . minibuffer-complete-and-exit)
  keymap (down . next-history-element) (up . previous-history-element)
  (menu-bar keymap (minibuf "Minibuf" keymap (tab menu-item "Complete"
  minibuffer-complete :help "Complete as far as possible") (space
  menu-item "Complete Word" minibuffer-complete-word :help "Complete
  at most one word") (63 menu-item "List Completions"
  minibuffer-completion-help :help "Display all possible completions")
  "Minibuf")) (M-down . minibuffer-next-completion) (M-up
  . minibuffer-previous-completion) (27 keymap (13
  . minibuffer-choose-completion) (103 keymap (27 keymap (99
  . switch-to-completions))) (118 . switch-to-completions)) (prior
  . switch-to-completions) (63 . minibuffer-completion-help) (32
  . minibuffer-complete-word) (backtab . minibuffer-complete) (9
  . minibuffer-complete) keymap (menu-bar keymap (minibuf "Minibuf"
  keymap (previous menu-item "Previous History Item"
  previous-history-element :help "Put previous minibuffer history
  element in the minibuffer") (next menu-item "Next History Item"
  next-history-element :help "Put next minibuffer history element in
  the minibuffer") (isearch-backward menu-item "Isearch History
  Backward" isearch-backward :help "Incrementally search minibuffer
  history backward") (isearch-forward menu-item "Isearch History
  Forward" isearch-forward :help "Incrementally search minibuffer
  history forward") (return menu-item "Enter" exit-minibuffer
  :key-sequence "\15" :help "Terminate input and exit minibuffer")
  (quit menu-item "Quit" abort-recursive-edit :help "Abort input and
  exit minibuffer") "Minibuf")) (24 keymap (down
  . minibuffer-complete-defaults) (up . minibuffer-complete-history))
  (13 . exit-minibuffer) (10 . exit-minibuffer) (7
  . minibuffer-keyboard-quit) (C-tab . file-cache-minibuffer-complete)
  (9 . self-insert-command) (XF86Back . previous-history-element) (up
  . previous-history-element) (prior . previous-history-element)
  (XF86Forward . next-history-element) (down . next-history-element)
  (next . next-history-element) (27 keymap (60
  . minibuffer-beginning-of-buffer) (114
  . previous-matching-history-element) (115
  . next-matching-history-element) (112 . previous-history-element)
  (110 . next-history-element))) nil file-name-history "~/" nil)

completing-read-default("Find file: " read-file-name-internal
  file-exists-p confirm-after-completion "~/" file-name-history "~/"
  nil)

coAmpleting-read("Find file: " read-file-name-internal file-exists-p confirm-after-completion "~/" file-name-history "~/")
  read-file-name-default("Find file: " nil "~/" confirm-after-completion nil nil)
  read-file-name("Find file: " nil "~/" confirm-after-completion)
  find-file-read-args("Find file: " confirm-after-completion)
  byte-code("\300\301\302 \"\207" [find-file-read-args "Find file: " confirm-nonexistent-file-or-buffer] 3)
  call-interactively(find-file nil nil)
  command-execute(find-file)

Re: persistent crash

[Eli Zaretskii]

> Date: Tue, 13 Feb 2024 17:07:41 +0000
> From: John ff <jpff@codemist.co.uk>
> 
> How do I stop this error?
> 
> Master build from source
> ==John ffitch
> Debugger entered--Lisp error: (wrong-number-of-arguments
> #f(compiled-function (&optional device) #<bytecode
> -0x1d28e41334b4e2c8>) 2) 
>   device-class(#<frame *GNU Emacs* - GNU Emacs at weir 0x28051d0> "SEM
>   USB Keyboard") 
>   minibuffer-setup-on-screen-keyboard()
>   read-from-minibuffer("Find file: " "~/" (keymap (keymap (32

How to reproduce this?

Re: persistent crash

[john]

This has been happening for the last week or 10 days.

I build from source master on GNU/Linux  after a git pull.  I have been 
doing this for some years.  It stopped running with no apparent errors. 
I moved y
to use an older emacs (GNU Emacs 27.2 (build 1, x86_64-suse-linux-gnu, 
GTK+ Version 3.24.34, cairo version 1.16.0)) but I failed to run 
report-emacs-bug


For me I launch emacs under X and FVWM and type C-x C-f and it 
crashes.  I 
have failed to win back control as it produces these back-traces whatever 
type.  I have done a make bootstrap but it made no difference
I did see a message about cj=l being deprecated but I do not know whp is 
loading it.

==John ffitchOn Tue, 13 Feb 2024, Eli Zaretskii wrote:
  ( (
>> Date: Tue, 13 Feb 2024 17:07:41 +0000
>> From: John ff <jpff@codemist.co.uk>
>>
>> How do I stop this error?
>>
>> Master build from source
>> ==John ffitch
>> Debugger entered--Lisp error: (wrong-number-of-arguments
>> #f(compiled-function (&optional device) #<bytecode
>> -0x1d28e41334b4e2c8>) 2)
>>   device-class(#<frame *GNU Emacs* - GNU Emacs at weir 0x28051d0> "SEM
>>   USB Keyboard")
>>   minibuffer-setup-on-screen-keyboard()
>>   read-from-minibuffer("Find file: " "~/" (keymap (keymap (32
>
> How to reproduce this?
>

Re: persistent crash

[Andreas Schwab]

On Feb 13 2024, John ff wrote:

> How do I stop this error?
>
> Master build from source
> ==John ffitch
> Debugger entered--Lisp error: (wrong-number-of-arguments
> #f(compiled-function (&optional device) #<bytecode
> -0x1d28e41334b4e2c8>) 2) 

You need to find out where this definition of the device-class function
comes from.  It does not come from Emacs.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: persistent crash

[Eli Zaretskii]

> Date: Tue, 13 Feb 2024 17:49:09 +0000 (GMT)
> From: john <jpff@codemist.co.uk>
> cc: emacs-devel@gnu.org
> 
> For me I launch emacs under X and FVWM and type C-x C-f and it 
> crashes.  I 
> have failed to win back control as it produces these back-traces whatever 
> type.  I have done a make bootstrap but it made no difference
> I did see a message about cj=l being deprecated but I do not know whp is 
> loading it.

I guess this doesn't happen if you start "emacs -Q"?  If so, look at
your customizations to find the minimal set that still produces the
Lisp errors, and post the results here.

Re: persistent crash

[john]

It does not crash immediately with -Q
But it happens if I remove all my customisations and also if i remove 
contents of .emacs

I think the problem is in local-lisp which is a collection of useful bits 
picked up over the years.  All predate lexical binding for example as I do.

I am working my way through these files but I have a limping system.  In 
particular rmail and associates is weaker and the anti spam stuff,

Thank you for being so polite to a old programmer.

==John ffitch


On Tue, 13 Feb 2024, Eli Zaretskii wrote:

>> Date: Tue, 13 Feb 2024 17:49:09 +0000 (GMT)
>> From: john <jpff@codemist.co.uk>
>> cc: emacs-devel@gnu.org
>>
>> For me I launch emacs under X and FVWM and type C-x C-f and it
>> crashes.  I
>> have failed to win back control as it produces these back-traces whatever
>> type.  I have done a make bootstrap but it made no difference
>> I did see a message about cj=l being deprecated but I do not know whp is
>> loading it.
>
> I guess this doesn't happen if you start "emacs -Q"?  If so, look at
> your customizations to find the minimal set that still produces the
> Lisp errors, and post the results here.
>