From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.bugs Subject: bug#34983: 27.0.50; Gnus cannot start Date: Mon, 25 Mar 2019 07:58:49 -0700 Message-ID: <87k1gnhufq.fsf@ericabrahamsen.net> References: <87k1gn53i6.fsf@bzg.fr> <87woknkfdc.fsf@ericabrahamsen.net> <87ftrbpije.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="26658"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 34983@debbugs.gnu.org To: Bastien Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Mar 25 16:02:43 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h8R7Y-0006lR-T0 for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 Mar 2019 16:02:41 +0100 Original-Received: from localhost ([127.0.0.1]:43897 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8R7U-0003hz-SO for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 Mar 2019 11:02:36 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49023) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8R46-00011c-D0 for bug-gnu-emacs@gnu.org; Mon, 25 Mar 2019 10:59:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8R43-0005mW-Ad for bug-gnu-emacs@gnu.org; Mon, 25 Mar 2019 10:59:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44989) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h8R42-0005lw-Ce for bug-gnu-emacs@gnu.org; Mon, 25 Mar 2019 10:59:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h8R42-00013C-5z for bug-gnu-emacs@gnu.org; Mon, 25 Mar 2019 10:59:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eric Abrahamsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 25 Mar 2019 14:59:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34983 X-GNU-PR-Package: emacs Original-Received: via spool by 34983-submit@debbugs.gnu.org id=B34983.15535259384029 (code B ref 34983); Mon, 25 Mar 2019 14:59:02 +0000 Original-Received: (at 34983) by debbugs.gnu.org; 25 Mar 2019 14:58:58 +0000 Original-Received: from localhost ([127.0.0.1]:58533 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h8R3y-00012u-CO for submit@debbugs.gnu.org; Mon, 25 Mar 2019 10:58:58 -0400 Original-Received: from ericabrahamsen.net ([52.70.2.18]:40722 helo=mail.ericabrahamsen.net) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h8R3w-00012h-DH for 34983@debbugs.gnu.org; Mon, 25 Mar 2019 10:58:56 -0400 Original-Received: from localhost (97-113-60-14.tukw.qwest.net [97.113.60.14]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 9D69FFA02B; Mon, 25 Mar 2019 14:58:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ericabrahamsen.net; s=mail; t=1553525931; bh=zSatA4HmLf4DZ6LJRDYE0CwsffpsuQxMBnpZKUfqucs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=UOyc4KlUw4ZekikJR8xhMkHUAorW6LKC8GOBMVROwxkPQtuT5NpkEPCVUP5ztfDSD Hphn3wqORDxUo05cWaMMwiYZxfblE4Kjox7wE8qRkkIvOKcuQM3BxJMhiSYzR5jTNg gdtmZ8jAuCPLW/unWTdUGXVwsEsZ6RqiN53xkMvE= In-Reply-To: <87ftrbpije.fsf@bzg.fr> (Bastien's message of "Mon, 25 Mar 2019 07:36:21 +0100") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:156757 Archived-At: On 03/25/19 07:36 AM, Bastien wrote: > Hi Eric, > > good luck with fixing this. > > Eric Abrahamsen writes: > >> This is frustrating -- this was the most important part of the patch, >> and the part I thought I'd tested most thoroughly. At worst I think Gnus >> may be trying to read .newsrc.eld using the wrong encoding, so I don't >> think you will have lost anything permanently. (Still, I'm very sorry >> this is causing you Gnus outage.) >> >> First -- did you run "make bootstrap" before running this new version? > > No. I regularily build Emacs from the master branch but I only use > `make' to compile it then. I had no idea I had to `make bootstrap'. > Why was it necessary after your commit? My commit changed the definition of some macros, and some *elc files with the older definitions are still hanging around. This does happen from time to time when you're running master, though in this case it coincides with a real bug. You can also just delete all the *elc files in lisp/gnus and run regular "make". This will fix some of the problems you're seeing, though from the backtrace below and your previous report it looks like you've also maybe got a literal "nil" as a group name in your newsrc.eld. >> Second, can you tell me if your non-ascii group names are being saved in >> .newsrc.eld in utf-8, or if they have literal byte sequences in them? > > There is no literal byte sequence in the .newsrc.eld file that I was > able to backup, right after I got this Gnus initialization error. But there are group names with properly-encoded non-ascii names? There shouldn't be, which is why I'm curious. > Now I recompiled an Emacs from before your commit. Starting with my > backup does trigger this error: > > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > intern(nil [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ...]) > gnus-make-hashtable-from-newsrc-alist() > gnus-read-newsrc-el-file("/home/guerry/.newsrc.el") > gnus-read-newsrc-file(nil) > gnus-setup-news(nil nil nil) > #f(compiled-function () #)() > gnus-1(nil nil nil) > gnus(nil) > funcall-interactively(gnus nil) > call-interactively(gnus record nil) > command-execute(gnus record) > execute-extended-command(nil "gnus" "gnus") > funcall-interactively(execute-extended-command nil "gnus" "gnus") > call-interactively(execute-extended-command nil nil) > command-execute(execute-extended-command) > > ... so I suspect I did not save my .newsrc.eld in time to properly use > it with a stable Emacs (too bad). > > I hope I will be able to find my group subscriptions and my marks. I don't think you will have lost any data! There's probably just a bogus group name or two in your newsrc.eld file which is preventing Gnus from starting up. If you feel comfortable doing this, would you send me your .newsrc.eld file off list? Sorry for this train wreck... > I'm trying to better understand a few things, can you educate me? > > What is the Gnus "active" file? > Where is it on my computer? > What is the .newsrc.eld file? > What is the difference between .newsrc.eld and the active file? Basil's explanations are correct, I'll just add that you've only got one.newsrc.eld file, recording marks for all the groups you're subscribed to, but each of your backends produces its own active file, saying what groups it contains, and what the newest messages are. For nntp you request it from the server. For nnml it lives on your computer (I think it goes under (concat gnus-home-directory "News/")). For nnimap, the server sends Gnus a list of groups and Gnus munges the list into something that *looks* like an active file. Gnus knows if you have new mail by comparing the active file information with your.newsrc.eld information. Eric