Bug#804751: gnus-agent-regenerate-group crashes => Invalid read syntax: ". in wrong context"

Package: emacs24 Version: 24.4+1-5 Severity: important Dear Maintainer, A particular newsgroup breaks gnus in an irrecoverable way. Gnus cannot open a group with content from "gwene.com.fatwallet.hotdeals" from the news.gmane.org server (filed in bug# 797409). Two other gnus functions fail when

Bug#799895: qpdf: Please make owner passwords optional

Package: qpdf Version: 5.1.2-2 Severity: wishlist Dear Maintainer, The "--encrypt" command must be followed by this sequence of options: user-password owner-password key-length [restrictions] -- The owner-password is not for encryption, and only useful when applying (the probably infrequent)

Bug#797409: emacs: gnus reports "Invalid read syntax" on a particular newsgroup

Package: emacs Version: 46.1 Severity: normal Dear Maintainer, For years Gnus has had no problem reading the newsgroup "gwene.com.fatwallet.hotdeals" from the news.gmane.org server. Suddenly it's no longer possible to even enter the summary buffer for this particular group. After attempting to e

Bug#792234: w3m: see other browsers approaches

Package: w3m Version: 0.5.3-19 Followup-For: Bug #792234 Dear Maintainer, The same suggestion is mirrored for lynx. I recommend looking at this report to see how other browsers implement this option: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792532 -- System Information: Debian Release

Bug#792532: lynx: w3m consistency would be nice

Package: lynx Version: 2.8.9dev1-2 Followup-For: Bug #792532 Andy, Thanks for the reply. In principle, I would not be fussy about how the fail-safe is implemented, so long as there is a means to fail safely. But I suggest that whatever the syntax is, it would be useful if it were consistent wit

Bug#792532: lynx: Add a CLI fail-safe option to specify a proxy (e.g. "--proxy")

Package: lynx Version: 2.8.9dev1-2 Severity: wishlist Dear Maintainer, It is risky to rely on an environment variable to specify a proxy. Any number of things can wrong, as we know from bug 791452. E.g., a user may think incorrectly that a proxy will be used, and have no idea of any failure. Ha

Bug#791452: lynx: more cases

Package: lynx Version: 2.8.9dev1-2 Followup-For: Bug #791452 I am the submitter. After more tests, there are perhaps multiple bugs here. I attempted to change test sites, because torstatus.blutmagie.de is a large document. These commands cause lynx to hang: env http_proxy=http://127.0.0.1:81

Bug#790250: iceweasel: first search from about:home hangs (goes to lunch)

Package: iceweasel Version: 31.7.0esr-1~deb8u1 Severity: normal Dear Maintainer, When "about:home" is the default home page, the first search after launching always goes to lunch. The timer wheel spins forever. If another tab is opened, then that search works instantly, but only if another sear

Bug#759341: use a separate tor circuit for each sources.list line

Package: apt-transport-tor Version: 0.2.1-1 Severity: wishlist apt-transport-tor should use a separate tor circuit for each line in sources.list. Otherwise it may be possible for exit nodes to fingerprint systems based on the set of sources.lists lines they use. -- To UNSUBSCRIBE, email to debi