Bug#966286: Minor correction: xdg-email (as used in nemo-data, where 'Send by email' misbehaves when parent's folder name contains a comma.)

[Howard Johnson]

.. I had previously _incorrectly_ said:

Note that in our case there is only one path/filename, *so this
could be further simplified as follows*:

ATTACH=$(/bin/echo -e $(echo "$MAILTO" | grep '^attach='     | sed
's/^attach=//;s|^|file://|g'                                
                                         ))     #could also be


*This simplification only works if there is only 1 attachment.*  

I now realize that xdg-email is set up for multiple attachments, even
though the man page I'm seeing doesn't mention this.  So my first
suggestions for a fix still works.  In other words, this works for one
or multiple attachments:

    ATTACH=$(/bin/echo -e $(echo "$MAILTO" | grep '^attach='     | sed
's/^attach=//;s|^|file://|g'        | awk '{ printf "%s,",$0 }' | sed
's/,$//'    ))   


I've tested this with one and two attachments, as follows:

    $ xdg-email   --attach /usr/share/nemo/actions/foo,bar/x            
                
# one attachment file

and

 $ xdg-email   --attach /usr/share/nemo/actions/foo,bar/x   --attach
/usr/share/nemo/actions/foo,bar/y    # two attachment files

Bug#966286: xdg-email (as used in nemo-data, where 'Send by email' misbehaves when parent's folder name contains a comma.)

[Howard Johnson]

I'm happy to report that I think I found the problem and a solution for
966...@bugs.debian.org aka 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966286

When you call `/usr/bin/thunderbird`, one must separate optional
attachments with a comma.   See: 
http://kb.mozillazine.org/Command_line_arguments_%28Thunderbird%29 which
has this example:

  * /thunderbird -compose

"to='j...@example.com,ka...@example.com',cc='brit...@example.com',subject='dinner',body='How
about dinner
tonight?',attachment='C:\temp\info.doc*,*C:\temp\food.doc'" /

/Notice the comma in the last part:  ...
//'C:\temp\info.doc,C:\temp\food.doc/

This page also says that you can specify these attachment file(s) with
either absolute filenames or encoded URLs. 

But if you specify absolute filenames, then any comma, in any one of
these filenames, or in their paths, creates a problem because it's
unescaped. 


*So to fix this bug* the *xdg-email* shell script needs to be changed to
call Thunderbird with an encoded URL rather than an absolute filename. 
Fortunately this is fairly easy to do with the following single line
change which had incorrectly un-encoded the attachment name, rather than
keep and use the encoding to form a URL:

ATTACH=$(/bin/echo -e $(echo "$MAILTO" | grep '^attach='     | sed
's/^attach=//;s/%\(..\)/\\x\1/g'     | awk '{ printf "%s,",$0 }' | sed
's/,$//'    ))    #was
ATTACH=$(/bin/echo -e $(echo "$MAILTO" | grep '^attach='     | sed
's/^attach=//;s|^|file://|g'     | awk '{ printf "%s,",$0 }' |
sed 's/,$//'    ))    #should be


Note that in our case there is only one path/filename, *so this could be
further simplified as follows*:

ATTACH=$(/bin/echo -e $(echo "$MAILTO" | grep '^attach='     | sed
's/^attach=//;s|^|file://|g'                                    
                                     ))     #could also be//
//

//
//

//BTW, here's the line I'm using to test it:
//

//    $ xdg-email --attach /usr/share/nemo/actions/foo,bar/x
//

//where 'foo, bar' is a folder name with a file named x in it.//

//Hope this makes sense.
//

//Thanks for writing this Kevin and JWhite!
//

Bug#966286: nemo-data: 'Send by email' misbehaves when parent's folder name contains a comma.

[Howard Johnson]

I've tracked the bug back into /usr/bin/xdg-email I think.

Bug#966286: nemo-data: 'Send by email' misbehaves when parent's folder name contains a comma.

[Howard Johnson]

Package: nemo-data
Version: 3.8.5-1
Severity: normal

CreateCreate a folder named 'foo,bar'.  $ mkdir ~/'foo,bar'  #  <-- note
the comma here

Touch a file in it named y. touch Create~/'foo,bar'/y

Then in nemo right click on y and select Send by email.  This misbehaves.


 a folder named 'foobar'.   $ mkdir ~/'foobar'

Touch a file in it named x. touch ~/'foobar'/x

Then in nemo right click on x and select Send by email.  Without a comma in a
parent's foldername this works properly.



Notes:

* Am using Thunderbird as an email client.

* I 'think' these files are involved, but I'm not sure how to fix them:

/usr/share/meno/actions/send-by-mail.nemo_action
/usr/share/meno/actions/send-by-mail.py



-- System Information:
Debian Release: 10.4
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nemo-data depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  python3  3.7.3-1

nemo-data recommends no packages.

Versions of packages nemo-data suggests:
ii  nemo  3.8.5-1+b1

-- no debconf information

Bug#963785: gman: Search and viewing are inconsistant

[Howard Johnson]

Package: gman
Version: 0.9.3-5.3
Severity: normal

Hi

I've installed and tried both the normal Buster version and the most recent
version (both running on Buster).

I can't consistently enter a search word, e.g. 'tree' (without the quotes), and
get an index of man pages.  It may work.  And then it won't work.  And then it
can start to work again.  There seems to be some unknown thing going on.

Furthermore, if I do get an index, only some of the items in the index display.
And this is funky too.  You can't simply double click.  You must click to
select, then click again to open.  It's pretty primitive, and confusing.

Also I'm seeing error messages in monitor I started it in.  I would think that
I should not be seeing these.  (Example is below)

I'm just going to uninstall.  It seem this needs more work before it's ready
for the repo.


Some error messages I'm seeing:

$ gman
P
sh: $'0k\317G\265\177whatis': command not found
P
sh: $'0k\317G\265\177whatis': command not found
P
sh: $'0k\317G\265\177whatis': command not found

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*"
whatis -w "*ls*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*"
whatis -w "*ls*" whatis -w "*ls*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*"
whatis -w "*ls*" whatis -w "*ls*" whatis -w "*man*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*"
whatis -w "*ls*" whatis -w "*ls*" whatis -w "*man*" whatis -w "*man*" '

sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: `|whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*"
whatis -w "*tree*" whatis -w "*tree*" whatis -w "*tree*" whatis -w "*ls*"
whatis -w "*ls*" whatis -w "*ls*" whatis -w "*man*" whatis -w "*man*" whatis -w
"*man*" '
^C



-- System Information:
Debian Release: 10.4
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gman depends on:
ii  gnome-terminal [x-terminal-emulator]  3.30.2-2
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-6
ii  libglib2.0-0  2.58.3-2+deb10u2
ii  libgtk2.0-0   2.24.32-3
ii  libstdc++68.3.0-6
ii  man-db2.8.5-2
ii  terminator [x-terminal-emulator]  1.91-4
ii  xterm [x-terminal-emulator]   344-1

gman recommends no packages.

Versions of packages gman suggests:
ii  apache2 [httpd]   2.4.38-3+deb10u3
ii  evince3.30.2-3+deb10u1
pn  gv
ii  man2html  1.6g-11
pn  sensible-browser  

-- no debconf information

Bug#946617: Confirming the bug and fix. Suggesting also man2html

[Howard Johnson]

Hi,

I also observed this bug, and furthermore, also used the previously
suggested fix to correct it, i.e. adding


    $ENV{'MAN_DISABLE_SECCOMP'} = 1;

Also I think you might want to consider instead using *man2html* like
dpkg-www does, (or at least have it as an option), as I think it looks
much better in Firefox.

Thanks for a great tool!

Bug#963680: dwww: Coding error setting $mime_charset

[Howard Johnson]

Package: dwww
Version: 1.13.5
Severity: normal

Hi.  I discovered this code in dwww-convert that doesn't make sense.  Unless
I'm missing something, why test and set $mime_charset="UTF-8" again, when it's
already set that way.  Perhaps you had in mind setting something else.  Or
perhaps these tests are no longer needed.  Something is wrong.  It doesn't
affect output, rather it's just extra code which doesn't make any change in the
output.


Starts at line 504 in dwww-convert:

$mime_charset="UTF-8";
if ($file =~ /(^\/usr\/share\/doc\/[^\/]+\/)([^\/]+)$/o) {
if (($2 eq "changelog.Debian.gz") || ($2 eq "copyright") ||
($2 eq "changelog.gz" && ! -e "$1/changelog.Debian.gz")) {
$mime_charset="UTF-8";
}
}




-- System Information:
Debian Release: 10.4
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dwww depends on:
ii  apache2 [httpd-cgi]2.4.38-3+deb10u3
ii  debconf [debconf-2.0]  1.5.71
ii  debianutils4.8.6.1
ii  doc-base   0.10.8
ii  file   1:5.35-4+deb10u1
ii  libc6  2.28-10
ii  libfile-ncopy-perl 0.36-2
ii  libmime-types-perl 2.17-1
ii  man-db 2.8.5-2
ii  mime-support   3.62
ii  perl   5.28.1-6
ii  sensible-utils 0.0.12
ii  ucf3.0038+nmu1

Versions of packages dwww recommends:
ii  apache2 [httpd]  2.4.38-3+deb10u3
ii  apt  1.8.2.1
ii  dlocate  1.07+nmu1
ii  info2www 1.2.2.9-24
ii  swish++  6.1.5-5

Versions of packages dwww suggests:
ii  chromium [www-browser]  80.0.3987.162-1~deb10u1
ii  doc-debian  6.4
ii  dpkg-www2.59
ii  google-chrome-stable [www-browser]  83.0.4103.106-1
ii  lynx [www-browser]  2.8.9rel.1-3
ii  w3m [www-browser]   0.5.3-37

-- Configuration Files:
/etc/apache2/conf-available/dwww.conf changed [not included]

-- debconf information:
  dwww/nosuchdir:
* dwww/index_docs: true
  dwww/nosuchuser:
* dwww/cgidir: /usr/lib/cgi-bin
* dwww/serverport: 80
* dwww/servername: localhost
  dwww/badport:
* dwww/docrootdir: /var/www/html
* dwww/cgiuser: www-data

Bug#963169: minor correction to my initial report

[Howard Johnson]

I wrote:

3) Furthermore, you can run `# /usr/sbin/dwww-find mysql` and you can see that
the man page for the mysql COMMAND is actually contained in the html.


More correctly:

3) Furthermore, you can run `# /usr/sbin/dwww-find mysql` and you can see that
the *_a man page LINK for the mysql command is now available*_ in the html.


Thanks!

Bug#963169: dwww: `--package` should be `--program` in usage: to agree with manpage and actual function

[Howard Johnson]

Package: dwww
Version: 1.13.5
Severity: normal

Hi.

I believe that the `usage:` message for dwww-find has an error.


Here is how you observe and confirm this:

1) Run `$ man dwww-find` and observe that dwww-find only spells out a
`--program` option, not a `--package` option.

2) Run `# /usr/sbin/dwww-find` and observe that the usage message says:

usage: dwww-find [--package  ...

It doesn't make sense to get a man page for a package.  In fact a package could
have more than one man page.

3) Furthermore, you can run `# /usr/sbin/dwww-find mysql` and you can see that
the man page for the mysql COMMAND is actually contained in the html.

4) Finally, you can run `# /usr/sbin/dwww-find mariadb-client-core | grep 'Not
found!'`, and although this is a valid package, no content for the html man
page is found.





To fix replace the word 'package' with 'program' in

dwww-1.13.5/scripts/dwww-find .



-- System Information:
Debian Release: 10.4
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dwww depends on:
ii  apache2 [httpd-cgi]2.4.38-3+deb10u3
ii  debconf [debconf-2.0]  1.5.71
ii  debianutils4.8.6.1
ii  doc-base   0.10.8
ii  file   1:5.35-4+deb10u1
ii  libc6  2.28-10
ii  libfile-ncopy-perl 0.36-2
ii  libmime-types-perl 2.17-1
ii  man-db 2.8.5-2
ii  mime-support   3.62
ii  perl   5.28.1-6
ii  sensible-utils 0.0.12
ii  ucf3.0038+nmu1

Versions of packages dwww recommends:
ii  apache2 [httpd]  2.4.38-3+deb10u3
ii  apt  1.8.2.1
ii  dlocate  1.07+nmu1
ii  info2www 1.2.2.9-24
ii  swish++  6.1.5-5

Versions of packages dwww suggests:
ii  chromium [www-browser]  80.0.3987.162-1~deb10u1
ii  doc-debian  6.4
pn  dpkg-www
ii  google-chrome-stable [www-browser]  83.0.4103.106-1
ii  lynx [www-browser]  2.8.9rel.1-3
ii  w3m [www-browser]   0.5.3-37

-- Configuration Files:
/etc/apache2/conf-available/dwww.conf changed [not included]

-- debconf information excluded

Bug#963031: man2html: `hman` "executable rejected due to location or path"

[Howard Johnson]

Package: man2html
Version: 1.6g-12
Severity: normal
Tags: patch

The problem:

1) Install and configure man2html package.
2) Make sure that MANHTMLPAGER is not set.
3) Run `hman` command (script) to view man pages in the default
browser: lynx.

3) Bug:  Get red lynx error:  "executable rejected due to location or
path"


Proposed fix:

Change line# 70 in /usr/bin/hman from:

CG="lynxcgi:/usr/lib/cgi-bin/man"

to

CG="http://$HOST/cgi-bin/man;


With fix in place `hman` runs as expected.


A temporary workaround, to avoid this problem rather than fixing it:

Set `MANHTMLPAGER=sensible-browser` prior to starting `hman`.



-- System Information:
Debian Release: 10.4
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages man2html depends on:
ii  apache2 [httpd-cgi]2.4.38-3+deb10u3
ii  debconf [debconf-2.0]  1.5.71
ii  gawk   1:4.2.1+dfsg-1
ii  libc6  2.28-10
ii  lynx   2.8.9rel.1-3
ii  man-db 2.8.5-2
ii  man2html-base  1.6g-11
ii  sensible-utils 0.0.12

man2html recommends no packages.

Versions of packages man2html suggests:
ii  chromium [www-browser]  80.0.3987.162-1~deb10u1
ii  google-chrome-stable [www-browser]  83.0.4103.106-1
ii  lynx [www-browser]  2.8.9rel.1-3
ii  swish++ 6.1.5-5
ii  w3m [www-browser]   0.5.3-37

-- debconf information:
  man2html/index_manpages: true

Bug#954191: vbackup homepage is bad

[Howard Johnson]

Package: vbackup
Version: 7.5.3

On https://tracker.debian.org/pkg/vbackup under "links" clicking on
"homepage " is broken.

It properly goes to URL https://www.v13.gr/ but this only displays:

PANIC: Failed to connect to the database.

Bug#954188: `reportbug` is a mess and should not be recommended as a method of sending Debian bug reports.

[Howard Johnson]

Package: reportbug
Version: 7.5.3

https://www.debian.org/Bugs/Reporting says:

    "We strongly recommend that you report bugs in Debian using the
reportbug program."


I'm using Buster 10.3 now.  But when I was using Jessie, I reported to
Debian that *reportbug* was not working.

So a few years later, reportbug is still not working.


Excuse me, but isn't this a very important Debian program? 

Without bug reports, nothing else gets fixed!, for example, the
*vbackup* package appears to have lost it's maintainer, but Debian don't
seem to know about that, possibly because reportbug isn't working.


And reportbug is broken in so many ways.  :-(  I'm not even going to go
into it again.  If someone dosn't care to test it and fix it, then I
can't help that.

I'm about to remove it from my system.


I just thought I'd write and tell you one last time of this most
important Debian program, that is really so badly broken.


*Please test it yourself.  *

I can't get it to send you a bug report.  I don't have a full emailer on
my laptop, and the emailer in reportbug doesn't work.  (see *reportbug
--configure* log below)

And the backup feature (the 'back' button) doesn't really work. 

And if you do backup, you can't copy your typed text into a paste buffer.

And finally, you can't save your typed bug report into a file, at least
I can't find the file, and then it doesn't tell me where the file is.


I guess I'm extra frustrated, because I took the time to report on these
issues before, several years ago, and NOTHING was ever done. 

So I'm wondering today if ANYTHING will ever be done about this.

Please prove me wrong,

:-)


==

# *reportbug --configure*
Please choose the default operating mode for reportbug.

1 novice    Offer simple prompts, bypassing technical questions.

2 standard  Offer more extensive prompts, including asking about things
that a moderately sophisticated user would be expected to
    know about Debian.

3 advanced  Like standard, but assumes you know a bit more about Debian,
including "incoming".

4 expert    Bypass most handholding measures and preliminary triage
routines. This mode should not be used by people unfamiliar
    with Debian's policies and operating procedures.

Select mode: [novice] *2*
Please choose the default interface for reportbug.

1 text   A text-oriented console user interface

2 gtk    A graphical (GTK+) user interface.

3 urwid  A menu-based console user interface

Select interface: *2*
Will reportbug often have direct Internet access? (You should answer yes
to this question unless you know what you are doing and
plan to check whether duplicate reports have been filed via some other
channel.) [Y|n|q|?]? *y*
What real name should be used for sending bug reports?
[root]> *H Johnson*
Which of your email addresses should be used when sending bug reports?
(Note that this address will be visible in the bug tracking
system, so you may want to use a webmail address or another address with
good spam filtering capabilities.)
[r...@love2d.ddns.net]> *bridgeportcontrac...@gmail.com*
Do you have a "mail transport agent" (MTA) like Exim, Postfix or SSMTP
configured on this computer to send mail to the Internet?
[y|N|q|?]? *n*
Please enter the name of your SMTP host. Usually it's called something
like "mail.example.org" or "smtp.example.org". If you need
to use a different port than default, use the : alternative
format. Just press ENTER if you don't have one or don't
know, and so a Debian SMTP host will be used.
> *mail.BridgeportContractor.com*
If you need to use a user name to send email via
"mail.BridgeportContractor.com" on your computer, please enter that user
name.
Just press ENTER if you don't need a user name.
> *h...@bridgeportcontractor.com*
Do you want to encrypt the SMTP connection with TLS (only available if
the SMTP host supports it)? [y|N|q|?]? y
Please enter the name of your proxy server. It should only use this
parameter if you are behind a firewall. The PROXY argument
should be formatted as a valid HTTP URL, including (if necessary) a port
number; for example, http://192.168.1.1:3128/. Just press
ENTER if you don't have one or don't know.
>
Default preferences file written. To reconfigure, re-run reportbug with
the "--configure" option.


=

Then when I try to submit a bug it asks me this which doesn't make any
sense:

    Enter SMTP password for bridgeportcontrac...@gmail.com@smtp.gmail.com:

Bug#885928: (no subject)

[Howard Johnson]

For me fixed with this:

sudo chown -R _apt:root /var/lib/apt/lists

Bug#903552: /var/lib/apt/lists must be owned by '_apt'.

[Howard Johnson]

|/var/lib/apt/lists must be owned by '_apt'. |

**

*So for me this fix worked:
*

|sudo chown -R _apt:root /var/lib/apt/lists |

Bug#921037: typo correction

[Howard Johnson]

I accidentally left out the Types: line.   Should be:

--- start of code ---
#NOTE: Most preferred source listed first!

#=== NEW MULTI-LINE FORMAT ===
Types:  deb deb-src
URIs:http://ftp.uk.debian.org/debian/
Suites: stretch
Components: main contrib non-free
--- end of code --


But note that the bug occurs both with that missing line, and without it.

So this follow-up is just so, you the maintainer, don't look at this and jump 
to the conclusion that the missing Types line has anything to do with this bug. 
 It does not.


In fact, this even more simple example with a single comment line followed by 
two blank lines, also demonstrates this bug:

--- start of code ---
#NOTE: Most preferred source listed first!


--- end of code --

Bug#921037: apt: Additional empty lines not ignored in multi-line format

[Howard Johnson]

Package: apt
Version: 1.4.9
Severity: normal
Tags: newcomer

In  `man sources.list`,  under the heading: "DEB822-STYLE FORMAT",  it says,

"Individual entries are separated by an empty line; additional empty
lines are ignored".

However, additional empty lines are not being ignored.  Consider this from my
/etc/apt/source.list.d/sources.sources:

--- start of code ---
#NOTE:  Most preferred source listed first!


#=== NEW MULTI-LINE FORMAT ===
URIs:   http://ftp.uk.debian.org/debian/
Suites: stretch
Components: main contrib non-free
--- end of code --


When I run `apt update` it gives this unexpected error message:

E: Malformed stanza 1 in source list
/etc/apt/sources.list.d/sources.sources (type)


If I remove one of the two blank lines the error goes away.

I would expect that two blank lines in succession would act as a single blank
line.

___
Apt v 1.4.9 (amd64)

OS: GNU/Linux Debian 9.6 (x86-64);
Cinnamon desktop: 3.2.7;
Linux Kernel: 4.9.0-8-amd64;
Processor: Intel Core 2 Duo P8800;
Graphics Card: AMD/ATI RV710/M92 Mobility Radeon HD 4530/4570/545v



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-8-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-7-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-8-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";

Bug#919634: wiki.debian.org: https://wiki.debian.org/ down

[Howard Johnson]

Package: wiki.debian.org
Severity: grave
Justification: renders package unusable

wiki web server is mis-configured.

When I browse to:

https://wiki.debian.org/

The web page returned says:

Forbidden

You are not allowed to access this!"


OR when viewed as source, I see this:



403 Forbidden
Forbidden
pYou are not allowed to access this!/p



-- System Information:
Debian Release: 9.6
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#881232: xserver-xorg-input-libinput package: Depends: xorg-input-abi-* but is not installable

[Howard Johnson]

Package: xserver-xorg-input-libinput
Version: 0.23.0-2
Severity: important

Dear Maintainer,

I was looking for version numbers for all packages for xserver (to work on a
different bug), when I noticed this non-existing xserver package dependency.

I also noticed that this bug almost got fixed in
https://lists.debian.org/debian-x/2016/11/msg00259.html, but it went away there
for the bug reporter, so never really got fixed at that point.

It appears that this dependency might be accidentally loaded elsewhere, so
hidden.

I would expect this dependency to be named something like xserver-xorg-input-
abi-24, or perhaps removed altogether if another dependent package already
loaded requires it.

Thanks for looking at this.

-- Howard



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jul 30  2016 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 14 01:36 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 44497 Nov  8 14:30 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 6.450] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 6.450] X Protocol Version 11, Revision 0
[ 6.450] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[ 6.450] Current Operating System: Linux Love2d 4.9.0-4-amd64 #1 SMP Debian 
4.9.51-1 (2017-09-28) x86_64
[ 6.450] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 
root=UUID=9875621b-e4df-416a-92a5-dba64a0f3f41 ro initrd=/install/initrd.gz 
quiet
[ 6.451] Build Date: 16 October 2017  08:19:45AM
[ 6.451] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) 
[ 6.451] Current version of pixman: 0.34.0
[ 6.451]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.451] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.451] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov  8 14:29:52 
2017
[ 6.452] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.453] (==) No Layout section.  Using the first Screen section.
[ 6.453] (==) No screen section available. Using defaults.
[ 6.453] (**) |-->Screen "Default Screen Section" (0)
[ 6.453] (**) |   |-->Monitor ""
[ 6.453] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.453] (==) Automatically adding devices
[ 6.453] (==) Automatically enabling devices
[ 6.453] (==) Automatically adding GPU devices
[ 6.453] (==) Max clients allowed: 256, resource mask: 0x1f
[ 6.454] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 6.454]Entry deleted from font path.
[ 6.456] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 6.456] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.456] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 6.456] (II) Loader magic: 0x560299c02e00
[ 6.456] (II) Module ABI versions:
[ 6.456]X.Org ANSI C Emulation: 0.4
[ 6.456]X.Org Video Driver: 23.0
[ 6.456]X.Org XInput driver : 24.1
[ 6.456]X.Org Server Extension : 10.0
[ 6.457] (++) using VT number 7

[ 6.457] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 6.457] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.460] (--) PCI:*(0:1:0:0) 1002:9553:103c:3624 rev 0, Mem @ 
0xc000/268435456, 0xda00/65536, I/O @ 0x7000/256, BIOS @ 
0x/131072
[ 6.460] (II) LoadModule: "glx"
[ 6.462] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.477] (II) Module glx: vendor="X.Org Foundation"
[ 6.477]compiled for 1.19.2, module version = 1.0.0
[ 6.477]ABI class: X.Org 

Bug#800643: I think I'm seeing the same issue

[Howard Johnson]

Been looking through my journal for errors, and noticed this.

I assume I'm seeing the same bug.


A few additional pieces of info for you (that may or may not be helpful):

-
From my journal:
...
Jul  2 22:04:41 Love2d avahi-daemon[621]: avahi-daemon 0.6.32 starting up.
Jul  2 22:04:41 Love2d avahi-daemon[621]: Successfully called chroot().
Jul  2 22:04:41 Love2d avahi-daemon[621]: Successfully dropped 
remaining capabilities.


Jul  2 22:04:41 Love2d avahi-daemon[630]: chroot.c: open() failed: 
No such file or directory
Jul  2 22:04:41 Love2d avahi-daemon[621]: Failed to open 
/etc/resolv.conf: Invalid argument


Jul  2 22:04:41 Love2d avahi-daemon[621]: No service file found in 
/etc/avahi/services.



-
/etc/resolv.conf is linked like this:
resolv.conf -> /var/run/NetworkManager/resolv.conf

cat resolv.conf gives:
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4

From man pages:
  nameserver Name server IP address
  Internet address of a name server that the resolver 
should query, either an IPv4 address  (in  dot  notation),  or an  IPv6
  address in colon (and possibly dot) notation as per RFC 
2373.  Up to MAXNS (currently 3, see ) name servers may be
  listed, one per keyword.  If there are multiple servers, 
the resolver library queries them in the order listed. If no name‐
  server  entries  are  present,  the default is to use the 
name server on the local machine.  (The algorithm used is to try a
  name server, and if the query times out, try the next, 
until out of name servers, then repeat trying all  the name  servers

  until a maximum number of retries are made.)



-
avahi.org is temporarily unavailavable, a couple of quick links are 
available below


 * doxygen documentation 
 * avahi 0.6.32
   

 * github: lathiat 
 * mailing list 

Bug#297485: libwvstreams4.0-extras: WvModem class does not work on ptys (SmartLink software modem daemon)

[Howard Johnson]

Package: libwvstreams4.0-extras
Version: 4.0.1-1.3
Severity: normal
Tags: patch

The SmartLink software modem (sl-modem-daemon) presents it's modem
interface on a pty, but the WvModem class's dependency on TIOCGSERIAL
prevents it's use on ptys such as /dev/pts/0.  This renders wvdial
unusable from SmartLink software modems.  The patch shown below has
been tested successfully on my laptop.

--- wvmodem-401-13.cc   2005-02-08 00:02:00 -0800
+++ wvmodem.cc  2005-02-28 02:53:00 -0800
@@ -189,29 +189,28 @@
 
 drain();
 
 #if HAVE_LINUX_SERIAL_H
 struct serial_struct old_sinfo, sinfo;
 sinfo.reserved_char[0] = 0;
-if (ioctl(getrfd(), TIOCGSERIAL, old_sinfo)  0) 
+if (ioctl(getrfd(), TIOCGSERIAL, old_sinfo) = 0) 
 {
-   seterr(Cannot get information for serial port.);
-   return;
-}
+   // No need to set information if we're a pty (software modem).
sinfo = old_sinfo;
// Why there are two closing wait timeouts, is beyond me
// but there are... apparently the second one is deprecated
// but why take a chance...
sinfo.closing_wait = ASYNC_CLOSING_WAIT_NONE;
sinfo.closing_wait2 = ASYNC_CLOSING_WAIT_NONE;
 
if (ioctl(getrfd(), TIOCSSERIAL, sinfo)  0  getuid() == 0) 
{
seterr(Cannot set information for serial port.);
return;
}
+}
 #endif
 
 // set up the terminal characteristics.
 // see man tcsetattr for more information about these options.
 t.c_iflag = ~(BRKINT | ISTRIP | IUCLC | IXON | IXANY | IXOFF | IMAXBEL);
 t.c_iflag |= (IGNBRK | IGNPAR);

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages libwvstreams4.0-extras depends on:
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libfam0c102 2.7.0-6  client library to control the FAM 
ii  libpam0g0.76-22  Pluggable Authentication Modules l
ii  libslp1 1.0.11a-1OpenSLP libraries
ii  libssl0.9.7 0.9.7e-2 SSL shared libraries
ii  libwvstreams4.0-base4.0.1-1.3C++ network libraries for rapid ap
ii  libxplc0.3.10   0.3.10-3.1   Light weight component system
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#296945: installation-reports

[Howard Johnson]

Package: installation-reports
Debian-installer-version: 2004-11-21 (sarge rc2) from cdimage.debian.org
uname -a: Linux hoto 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux
Date: 2005-01-05 08:30 PST
Method: cdrom
Machine: Toshiba Satellite A45-S150
Processor: Mobile Intel(R) Pentium(R) 4  2.40 GHz
Memory: 512 MB
Root Device: /dev/hda: IC25N060ATMR04-0 (60 GB, /proc/ide/ide0/hda/model)
Root Size/partition table:
Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/hda1   1 892 7164958+  1b  Hidden W95 FAT32
Windows 2000 SP4 on FAT32 (for kodakimg.exe, Boot Magic, safe boot)
/dev/hda2 893344220482875   17  Hidden HPFS/NTFS
Windows XP SP2 on NTFS (primary Windows partition)
/dev/hda3   *3443729630957255f  W95 Ext'd (LBA)
/dev/hda534434334 7164958+   b  W95 FAT32
FAT32 for data, exchanges between Windows and Linux
/dev/hda64335640416627243+   7  HPFS/NTFS
NTFS for data
/dev/hda764057296 7164958+  83  Linux
Debian Linux (sarge)
Output of lspci and lspci -n:
:00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
:00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control 
Registers (rev 02)
:00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration 
Process Registers (rev 02)
:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated 
Graphics Device (rev 02)
:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics 
Device (rev 02)
:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #1 (rev 03)
:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #2 (rev 03)
:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI 
Controller (rev 03)
:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83)
:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage 
Controller (rev 03)
:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 
Modem Controller (rev 03)
:01:05.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg 
NIC (rev 01)
:01:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet 
Controller (rev 83)
:01:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to 
Cardbus Bridge with ZV Support (rev 33)
:00:00.0 0600: 8086:3580 (rev 02)
:00:00.1 0880: 8086:3584 (rev 02)
:00:00.3 0880: 8086:3585 (rev 02)
:00:02.0 0300: 8086:3582 (rev 02)
:00:02.1 0380: 8086:3582 (rev 02)
:00:1d.0 0c03: 8086:24c2 (rev 03)
:00:1d.1 0c03: 8086:24c4 (rev 03)
:00:1d.7 0c03: 8086:24cd (rev 03)
:00:1e.0 0604: 8086:2448 (rev 83)
:00:1f.0 0601: 8086:24cc (rev 03)
:00:1f.1 0101: 8086:24ca (rev 03)
:00:1f.5 0401: 8086:24c5 (rev 03)
:00:1f.6 0703: 8086:24c6 (rev 03)
:01:05.0 0200: 168c:0013 (rev 01)
:01:08.0 0200: 8086:103d (rev 83)
:01:0b.0 0607: 1179:0617 (rev 33)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [E]
Comments/Problems:
It took a few tries to get LILO to live on /dev/hda3 instead of
/dev/hda.  I like to mark the extended partition active when booting
to Linux.  Can grub do this?
Installed kernel 2.4.27 first with netinstall, then added 2.6.8 kernel.
Was able to get ACPI working with 2.6.8 to monitor battery level.
X video was surprisingly easy to get working.  Used i810 driver.
ALSA failed to detect/install sound driver.  On a lark, put i810_audio
in /etc/modules and sound works without building custom kernel modules.
sl-modem-daemon allows me to access internal modem with minicom, but
not with wvdial.  Did not have to compile a kernel module, but may
try it anyway.  Modem speaker integration does not work.
Compiled and installed madwifi-modules-*-386_20041023-1_i386 for
Atheros 5212 wifi network interface.  Eventually got wpasupplicant
(with resolvconf) to work reasonably well.  Documentation is very
sketchy.  About 4 (expert) man-days of effort to get this working.
toshset and toshutils packages do not work.  toshset complained that
ACPI was detected and