gmane is always closed.

gmane is always closed.

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hello

I have the following setting:

(setq gnus-secondary-select-methods
      '(
		(nnimap "UCMgmail"
				(nnimap-address "imap.gmail.com")
				(nnimap-server-port 993)
				(nnimap-authinfo-file "~/.authinfo")
				(nnimap-stream ssl))
		(nnimap "gmail"
				(nnimap-address "imap.gmail.com")
				(nnimap-server-port 993)
				(nnimap-authinfo-file "~/.authinfo")
				(nnimap-stream ssl))
 		(nntp "news.gmane.org")))

However since a couple of weeks when starting gnus the server list looks
as:

     {nndiary:diary} (closed)
     {nnml:archive} (opened)
     {nnvirtual:Test} (closed)
     {nndraft:} (opened)
     {nntp:news.gmane.org} (denied) (cloud)
     {nnimap:gmail} (opened) (agent)
     {nnimap:UCMgmail} (opened) (agent)


So I have always to open manually gmane.

What is wrong with my setting? Did gmane change his settings?

thanks

Uwe Brauer 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]

Re: gmane is always closed.

[Alberto Luaces]

Uwe Brauer writes:

> What is wrong with my setting? Did gmane change his settings?

I don't think so; my settings are the same as yours, but I didn't set
gmane in gnus.el; I created it directly from the server buffer:

(nntp "news.gmane.org")

-- 
Alberto

Re: gmane is always closed.

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

>> "Alberto" == Alberto Luaces <aluaces@udc.es> writes:

   > Uwe Brauer writes:
   >> What is wrong with my setting? Did gmane change his settings?

   > I don't think so; my settings are the same as yours, but I didn't set
   > gmane in gnus.el; I created it directly from the server buffer:

   > (nntp "news.gmane.org")
I deleted even my .newsrc.el file and restarted, same behavior.

So I set debug-on-signal to t

And this is what I got.


[-- Attachment #2: server-error --]
[-- Type: text/plain, Size: 1382 bytes --]

Debugger entered--Lisp error: (file-error "Opening input file" "No such file or directory" "/home/oub/News/agent/lib/categories")
  insert-file-contents-internal("~/News/agent/lib/categories" nil nil nil nil raw-text used-codesys)
  byte-code("..." [buffer-file-coding-system-for-read coding-system-for-read return-val visit filename coding-system run-hook-with-args insert-file-contents-access-hook run-hook-with-args-until-success insert-file-contents-pre-hook find-file-coding-system-for-read-from-filename raw-text find-coding-system lwarn notice "Invalid coding-system (%s), using 'undecided" undecided insert-file-contents-internal used-codesys start end replace] 9)
  insert-file-contents("~/News/agent/lib/categories" nil nil nil nil)
  mm-insert-file-contents("~/News/agent/lib/categories" nil nil nil nil)
  nnheader-insert-file-contents("~/News/agent/lib/categories")
  byte-code("..." [gnus-agent-directory new-list old-list nnheader-insert-file-contents nnheader-concat "lib/categories" read nil (byte-code "Àp!‡" [read] 2) ((error)) mapcar #<compiled-function (from "/home/oub/xemacs/site-lisp/packages/ma-gnus-09/lisp/gnus-agent.elc") (c) "...(59)" [symb #:result c #:result-tail #:head2 #:head1 delete* nil ... valu] 7 0x42ee>] 5)
  gnus-category-read()
  gnus-open-agent()
  gnus-agentize()
  gnus-1(nil nil nil)
  gnus(nil)
  call-interactively(gnus)

Re: gmane is always closed.

[Alberto Luaces]

Uwe Brauer <oub@mat.ucm.es> writes:

>>> "Alberto" == Alberto Luaces <aluaces@udc.es> writes:
>
>    > Uwe Brauer writes:
>    >> What is wrong with my setting? Did gmane change his settings?
>
>    > I don't think so; my settings are the same as yours, but I didn't set
>    > gmane in gnus.el; I created it directly from the server buffer:
>
>    > (nntp "news.gmane.org")
> I deleted even my .newsrc.el file and restarted, same behavior.
>
> So I set debug-on-signal to t
>
> And this is what I got.

[...]

The backtrace mentions the agent.  Can you disable it to see if it
behaves differently?

-- 
Alberto

Re: gmane is always closed.

[Uwe Brauer]

   > Uwe Brauer <oub@mat.ucm.es> writes:

   > [...]

   > The backtrace mentions the agent.  Can you disable it to see if it
   > behaves differently?
Yes I noticed as well, the agent is disabled since a while. I will
submit a bug report.