From: Waleed Yousef <wyousef@fcih.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 42896@debbugs.gnu.org
Subject: bug#42896: 27.1; startup error after un update
Date: Fri, 09 Oct 2020 17:19:47 -0700 [thread overview]
Message-ID: <871ri76ifw.fsf@fcih.net> (raw)
In-Reply-To: <874kn4kxhz.fsf@web.de> (Michael Heerdegen's message of "Fri, 09 Oct 2020 03:18:32 +0200")
It opens fine without registry file. For backtrace, I sent it in the
previous email. Can you please detail what exactly I should provide.
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Waleed Yousef <wyousef@fcih.net> writes:
>
>> I renamed the registry to (.gnus.registry.eieio.recent) and started
>> gnus. The same problem exists; moreover, gnus did not initialize
>> another registry even when I prompted manually
>> gnus-registry-initialize
>
> Ok, then we need some more information to investigate.
>
> Can you please post a backtrace of the error? Thx.
>
> And: Does Gnus start normally if you turn off using the Gnus registry in
> your setup?
>
> TIA,
>
> Michael.
next prev parent reply other threads:[~2020-10-10 0:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 1:55 bug#42896: 27.1; startup error after un update Waleed Yousef
2020-08-17 2:31 ` Eli Zaretskii
2020-08-22 21:16 ` Lars Ingebrigtsen
[not found] ` <87blhidfss.fsf@web.de>
[not found] ` <87ft6ut18q.fsf@fcih.net>
[not found] ` <87tuv9r3b0.fsf@web.de>
2020-10-08 18:48 ` Waleed Yousef
2020-10-09 1:18 ` Michael Heerdegen
2020-10-10 0:19 ` Waleed Yousef [this message]
2020-10-12 8:19 ` Michael Heerdegen
2020-10-12 15:46 ` Waleed Yousef
2020-10-13 10:29 ` Michael Heerdegen
2020-10-13 14:00 ` Waleed Yousef
2020-10-13 15:39 ` Robert Pluim
2020-10-13 16:12 ` Michael Heerdegen
2020-10-13 17:10 ` Waleed Yousef
2020-10-13 18:55 ` Basil L. Contovounesios
2020-10-14 3:47 ` Lars Ingebrigtsen
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=871ri76ifw.fsf@fcih.net \
--to=wyousef@fcih.net \
--cc=42896@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).