bug#42896: 27.1; startup error after un update

[Michael Heerdegen]

Waleed Yousef <wyousef@fcih.net> writes:

> Sorry, can you please guide me how I should provide it?

Sure.

You basically only need to set the variable `debug-on-error' to t,
e.g. with

  M-: (setq debug-on-error t) RET

This will make the debugger pop-up for most kinds of errors.  Then
reproduce the error with your recipe and post the contents of the
debugger buffer.

Detail: the debugger buffer will have more readable contents if you load
the elisp sources of the related elisp files before.  You can get an
idea of which packages are involved by looking for the names of the
called functions in the debugger.  Probably loading "gnus-registry.el"
should be good enough.  You can use the command `find-library' to find
the source files, and use e.g. `load-buffer', or L from dired, to load
it.

When done, set `debug-on-error' back to nil:

  M-: (setq debug-on-error nil) RET

Does that work for you?


TIA,

Michael.