My name, Norton Cater, email address: norton.ca...@gmail.com, is on your mailing list in error- Please remove it

[Norton Caterq1qb]

Thank you

Sent from my iPad

Re: My name, Norton Cater, email address: norton.ca...@gmail.com, is on your mailing list in error- Please remove it

[Floris]

Op Tue, 05 Dec 2017 10:39:07 +0100 schreef Norton Caterq1qb  
:



Thank you

Sent from my iPad



Please read:
https://www.debian.org/MailingLists/#subunsub

bugreport - reportbug 7.1.7 on Debian 9.1

[Sophie Loewenthal]

Hi,

Submitting a bug report via reportbug 7.1.7 programme produced:

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2234, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1225, in user_interface
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2150, in user_interface
package, severity, mode, charset=charset, tags=tags)
  File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in 
spawn_editor
newmessage = open(filename).read()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780: 
ordinal not in range(128)


# cat .reportbugrc 
# reportbug preferences file
# character encoding: us-ascii
# Version of reportbug this preferences file was written by
reportbug_version "7.1.7"
# default operating mode: one of: novice, standard, advanced, expert
mode standard
# default user interface
ui text
# offline setting - comment out to be online
#offline
# name and email setting (if non-default)
realname "Sophie L"
email "withh...@klunky.co.uk"
# Suppress user ID check for this user
no-check-uid
# If nothing else works, remove the # at the beginning
# of the following three lines:
#no-cc
#header "X-Debbugs-CC: withh...@klunky.co.uk"
#smtphost reportbug.debian.org
# You can add other settings after this line.  See
# /etc/reportbug.conf for a full listing of options.



Full copy and paste from session, but the vi entries are missed:

# reportbug
Welcome to reportbug! Since it looks like this is the first time you have used 
reportbug, we are configuring its behavior. These
settings will be saved to the file "/root/.reportbugrc", which you will be free 
to edit further.
Please choose the default operating mode for reportbug.

1 noviceOffer 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 expertBypass 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
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]> Sophie L
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...@cmx12.klunky.co.uk]> withh...@klunky.co.uk
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|?]? 
reportbug: exiting due to user interrupt.
root@cmx12:/etc# reportbug
Welcome to reportbug! Since it looks like this is the first time you have used 
reportbug, we are configuring its behavior. These
settings will be saved to the file "/root/.reportbugrc", which you will be free 
to edit further.
Please choose the default operating mode for reportbug.

1 noviceOffer 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 expertBypass 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
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]> Sophie L
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...@cmx12.klunky.co.uk]> withh...@klunky.co.uk
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|?]? y
Please enter the name of your proxy serv

bugreport : redis-server - debian 9.1

[Sophie Loewenthal]

Hi, 

The post install scripts for redis-server did not run well on a freshly 
installed Debian 9.1 server.  Because bugreport did not work on my debian 9 
install I'd like to seek help here.  I’ll email a separate email for the 
bugreport bugreport :)


Kind regards, Sophie


# cat /etc/debian_version 
9.1
# uname -a
Linux mx12 2.6.32-042stab125.5 #1 SMP Tue Oct 17 12:48:22 MSK 2017 x86_64 
GNU/Linux

# apt-get install redis-server
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libaio1 libcgi-fast-perl libcgi-pm-perl libdbi-perl libencode-locale-perl 
libfcgi-perl libhtml-parser-perl libhtml-tagset-perl
  libhtml-template-perl libhttp-date-perl libhttp-message-perl libio-html-perl 
liblwp-mediatypes-perl libopts25 libreadline5
  libterm-readkey-perl libtimedate-perl liburi-perl socat
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  redis-server
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 413 kB of archives.
After this operation, 1063 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian  
stretch/main amd64 redis-server amd64 3:3.2.6-1 [413 kB]
Fetched 413 kB in 0s (3127 kB/s) 
Selecting previously unselected package redis-server.
(Reading database ... 34119 files and directories currently installed.)
Preparing to unpack .../redis-server_3%3a3.2.6-1_amd64.deb ...
Unpacking redis-server (3:3.2.6-1) ...
Processing triggers for systemd (232-25+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up redis-server (3:3.2.6-1) ...
Created symlink /etc/systemd/system/redis.service → 
/lib/systemd/system/redis-server.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/redis-server.service → 
/lib/systemd/system/redis-server.service.
Job for redis-server.service failed because the control process exited with 
error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript redis-server, action "start" failed.
● redis-server.service - Advanced key-value store
   Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2017-12-05 
09:52:12 UTC; 19ms ago
 Docs: http://redis.io/documentation ,
   man:redis-server(1)
  Process: 21728 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf 
(code=exited, status=226/NAMESPACE)
  Process: 21725 ExecStartPre=/bin/run-parts --verbose 
/etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE)

Dec 05 09:52:12 mx12 systemd[1]: Failed to start Advanced key-value store.
Dec 05 09:52:12 mx12 systemd[1]: redis-server.service: Unit entered failed 
state.
Dec 05 09:52:12 mx12 systemd[1]: redis-server.service: Failed with result 
'exit-code'.
dpkg: error processing package redis-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
 redis-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: bugreport - reportbug 7.1.7 on Debian 9.1

[Sophie Loewenthal]

Submitted to bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577 


> On 5 Dec 2017, at 11:34, Sophie Loewenthal  wrote:
> 
> Hi,
> 
> Submitting a bug report via reportbug 7.1.7 programme produced:
> 
> Traceback (most recent call last):
>  File "/usr/bin/reportbug", line 2234, in 
>main()
>  File "/usr/bin/reportbug", line 1107, in main
>return iface.user_interface()
>  File "/usr/bin/reportbug", line 1225, in user_interface
>main()
>  File "/usr/bin/reportbug", line 1107, in main
>return iface.user_interface()
>  File "/usr/bin/reportbug", line 2150, in user_interface
>package, severity, mode, charset=charset, tags=tags)
>  File "/usr/bin/reportbug", line 182, in handle_editing
>editor, charset)
>  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in 
> spawn_editor
>newmessage = open(filename).read()
>  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
>return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780: 
> ordinal not in range(128)
> 
> 
> # cat .reportbugrc 
> # reportbug preferences file
> # character encoding: us-ascii
> # Version of reportbug this preferences file was written by
> reportbug_version "7.1.7"
> # default operating mode: one of: novice, standard, advanced, expert
> mode standard
> # default user interface
> ui text
> # offline setting - comment out to be online
> #offline
> # name and email setting (if non-default)
> realname "Sophie L"
> email "withh...@klunky.co.uk"
> # Suppress user ID check for this user
> no-check-uid
> # If nothing else works, remove the # at the beginning
> # of the following three lines:
> #no-cc
> #header "X-Debbugs-CC: withh...@klunky.co.uk"
> #smtphost reportbug.debian.org
> # You can add other settings after this line.  See
> # /etc/reportbug.conf for a full listing of options.
> 
> 
> 
> Full copy and paste from session, but the vi entries are missed:
> 
> # reportbug
> Welcome to reportbug! Since it looks like this is the first time you have 
> used reportbug, we are configuring its behavior. These
> settings will be saved to the file "/root/.reportbugrc", which you will be 
> free to edit further.
> Please choose the default operating mode for reportbug.
> 
> 1 noviceOffer 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 expertBypass 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
> 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]> Sophie L
> 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...@cmx12.klunky.co.uk]> withh...@klunky.co.uk
> 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|?]? 
> reportbug: exiting due to user interrupt.
> root@cmx12:/etc# reportbug
> Welcome to reportbug! Since it looks like this is the first time you have 
> used reportbug, we are configuring its behavior. These
> settings will be saved to the file "/root/.reportbugrc", which you will be 
> free to edit further.
> Please choose the default operating mode for reportbug.
> 
> 1 noviceOffer 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 expertBypass 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
> 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]> Sophie L
> Which of your email addresses should be used when sending

Re: bugreport : redis-server - debian 9.1

[Sophie Loewenthal]

Submitted to bug tracker

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883576 



> On 5 Dec 2017, at 11:29, Sophie Loewenthal  wrote:
> 
> Hi, 
> 
> The post install scripts for redis-server did not run well on a freshly 
> installed Debian 9.1 server.  Because bugreport did not work on my debian 9 
> install I'd like to seek help here.  I’ll email a separate email for the 
> bugreport bugreport :)
> 
> 
> Kind regards, Sophie
> 
> 
> # cat /etc/debian_version 
> 9.1
> # uname -a
> Linux mx12 2.6.32-042stab125.5 #1 SMP Tue Oct 17 12:48:22 MSK 2017 x86_64 
> GNU/Linux
> 
> # apt-get install redis-server
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> The following packages were automatically installed and are no longer 
> required:
>   libaio1 libcgi-fast-perl libcgi-pm-perl libdbi-perl libencode-locale-perl 
> libfcgi-perl libhtml-parser-perl libhtml-tagset-perl
>   libhtml-template-perl libhttp-date-perl libhttp-message-perl 
> libio-html-perl liblwp-mediatypes-perl libopts25 libreadline5
>   libterm-readkey-perl libtimedate-perl liburi-perl socat
> Use 'apt autoremove' to remove them.
> The following NEW packages will be installed:
>   redis-server
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 413 kB of archives.
> After this operation, 1063 kB of additional disk space will be used.
> Get:1 http://ftp.us.debian.org/debian  
> stretch/main amd64 redis-server amd64 3:3.2.6-1 [413 kB]
> Fetched 413 kB in 0s (3127 kB/s) 
> Selecting previously unselected package redis-server.
> (Reading database ... 34119 files and directories currently installed.)
> Preparing to unpack .../redis-server_3%3a3.2.6-1_amd64.deb ...
> Unpacking redis-server (3:3.2.6-1) ...
> Processing triggers for systemd (232-25+deb9u1) ...
> Processing triggers for man-db (2.7.6.1-2) ...
> Setting up redis-server (3:3.2.6-1) ...
> Created symlink /etc/systemd/system/redis.service → 
> /lib/systemd/system/redis-server.service.
> Created symlink 
> /etc/systemd/system/multi-user.target.wants/redis-server.service → 
> /lib/systemd/system/redis-server.service.
> Job for redis-server.service failed because the control process exited with 
> error code.
> See "systemctl status redis-server.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript redis-server, action "start" failed.
> ● redis-server.service - Advanced key-value store
>Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor 
> preset: enabled)
>Active: activating (auto-restart) (Result: exit-code) since Tue 2017-12-05 
> 09:52:12 UTC; 19ms ago
>  Docs: http://redis.io/documentation ,
>man:redis-server(1)
>   Process: 21728 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf 
> (code=exited, status=226/NAMESPACE)
>   Process: 21725 ExecStartPre=/bin/run-parts --verbose 
> /etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE)
> 
> Dec 05 09:52:12 mx12 systemd[1]: Failed to start Advanced key-value store.
> Dec 05 09:52:12 mx12 systemd[1]: redis-server.service: Unit entered failed 
> state.
> Dec 05 09:52:12 mx12 systemd[1]: redis-server.service: Failed with result 
> 'exit-code'.
> dpkg: error processing package redis-server (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (232-25+deb9u1) ...
> Errors were encountered while processing:
>  redis-server
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
> 

Re: My name, Norton Cater, email address: norton.ca...@gmail.com, is on your mailing list in error- Please remove it

[Roberto C . Sánchez]

On Tue, Dec 05, 2017 at 10:47:01AM +0100, Floris wrote:
> Op Tue, 05 Dec 2017 10:39:07 +0100 schreef Norton Caterq1qb
> :
> 
> > Thank you
> > 
> > Sent from my iPad
> > 
> 
> Please read:
> https://www.debian.org/MailingLists/#subunsub
> 
He is probably not subscribed, but receiving spam with forged headers.
Sadly, unsubscribing from the list won't fix that.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: My name, Norton Cater, email address: norton.ca...@gmail.com, is on your mailing list in error- Please remove it

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Dec 05, 2017 at 07:47:51AM -0500, Roberto C. Sánchez wrote:
> On Tue, Dec 05, 2017 at 10:47:01AM +0100, Floris wrote:
> > Op Tue, 05 Dec 2017 10:39:07 +0100 schreef Norton Caterq1qb
> > :
> > 
> > > Thank you
> > > 
> > > Sent from my iPad
> > > 
> > 
> > Please read:
> > https://www.debian.org/MailingLists/#subunsub
> > 
> He is probably not subscribed, but receiving spam with forged headers.
> Sadly, unsubscribing from the list won't fix that.

Posting to the list, since everyone now is chiming in.

Typically, if one of those posts seems legit, I try to answer
directly, and not to list:

 - because I don't want disturbing the ~3000 subscribers
   even more than they've already been
 - because should be the message be spam, its spam score
   probably falls when there are answers to it

I try to explain politely, but in no unmistakable terms that
only the subscriber can cancel his/her subscription, and that
(s)he just incommodated around 3k people with a request they
can't do much about. And I give hints on how to do it, and
on how to find those hints in the mails themselves (the set
of headers beginning with X-List...).

In this case, the OP seems[1] to be subscribed, as the spam
status header suggests:

  X-Spam-Status: No, score=-10.0 required=4.0 tests=GMAIL,LDOSUBSCRIBER,
  LDO_WHITELIST autolearn=unavailable autolearn_force=no version=3.4.1

(this extracted from *your* posting. Notice the LDOSUBSCRIBER
test up there).

I generally hope the poster has a chance to learn
from this, and don't blow up the thread unnecessarily.

There's some risk that the OP gets a bunch of this type
of mail, but hey, (s)he has just done something where
3000 other people carry the burden, so this small risk
seems balanced to me.

In the current case, the OP actually answered (which is
more I hoped for), and I hope I could help him getting
unsubscribed.

Does that make sense? Is there a policy on that? Dunno.

Cheers

[1] Of course, these are just hints. Mail headers can
   be spoofed (I don't know how one could get that
   one past the mailing list software unnoticed, but
   there ya go)

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlomoHsACgkQBcgs9XrR2kbVPgCfana7lVYXyOmz6UOAW35s0DVs
qJAAn2pZLu+QPabi4HqNDzhb3qMYGGRz
=wIbZ
-END PGP SIGNATURE-

Re: bugreport : redis-server - debian 9.1

[Glenn English]

On Tue, Dec 5, 2017 at 10:29 AM, Sophie Loewenthal  wrote:
> Hi,

Hi, Sophie

> The post install scripts for redis-server did not run well on a freshly
> installed Debian 9.1 server.

I ran into trouble with that release as well. I installed Buster, and
things went back to normal.

--
Glenn English

Re: bugreport - reportbug 7.1.7 on Debian 9.1

[Michael Lange]

Hi,

On Tue, 5 Dec 2017 11:34:57 +0100
Sophie Loewenthal  wrote:

> Hi,
> 
> Submitting a bug report via reportbug 7.1.7 programme produced:
> 
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 2234, in 
> main()
>   File "/usr/bin/reportbug", line 1107, in main
> return iface.user_interface()
>   File "/usr/bin/reportbug", line 1225, in user_interface
> main()
>   File "/usr/bin/reportbug", line 1107, in main
> return iface.user_interface()
>   File "/usr/bin/reportbug", line 2150, in user_interface
> package, severity, mode, charset=charset, tags=tags)
>   File "/usr/bin/reportbug", line 182, in handle_editing
> editor, charset)
>   File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line
> 1064, in spawn_editor newmessage = open(filename).read()
>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
> 1780: ordinal not in range(128)

not sure, but maybe this happens because there is something misconfigured
with your system's locale settings.
The reportbug UI tries to guess the system encoding and if nothing good
is detected falls back to "us-ascii", which seems to be what happens
here. When then some non-ascii character is used (here apparently "â") it
cannot be decoded and causes the above error.
The code snippet reportbug uses for the encoding detection can be run as
a one-line command, which produces here:

$ python3 -c "import locale; print(locale.nl_langinfo(locale.CODESET))"
UTF-8

If you get "us-ascii" instead, you might want to check your locale
settings.

Best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Uncontrolled power will turn even saints into savages.  And we can all
be counted on to live down to our lowest impulses.
-- Parmen, "Plato's Stepchildren", stardate 5784.3

Re: [OT] Relavant mailing list or USENET group

[Richard Owlett]

On 12/04/2017 05:00 AM, Eric S Fraga wrote:

On Saturday,  2 Dec 2017 at 11:17, Richard Owlett wrote:

This is part of my search for a LINUX PDA. [1] [2]


OpenPandora and it's replacement, the Pyra (not yet ready, mind you).

https://pyra-handheld.com/boards/

I have the former with Debian but awaiting the latter with eagerness...



I had been to https://pyra-handheld.com/boards/pages/pyra/ but there was 
no indication of where they were on the "initial design"/"product 
available" timeline.


As to web based fora, I've not discovered a way to efficiently read/find 
posts of interest. In mailing lists and USENET I make extensiveness use 
of the tagging and marking options of SeaMonkey. [I date from era of 
"paper tape"/"high speed paper tape. ;]

Re: Re: Thunderbird no longer opens links

[Vincas Dargis]

On 2017-12-04 20:42, Alexander V. Makartsev wrote:
Thanks for the information. It felt like there should be some way to gracefully override profiles. Definitely gonna test 
that.


There is a current discussion [0] for using AppArmor profile variables for ever more customization points, as (again) 
advanced Thunderbird use cases shows us.



Also will eventually go through whole AppArmor documentation as well at 
http://wiki.apparmor.net/index.php/Documentation


`man apparmor.d` looks like a good read too.

[0] https://lists.ubuntu.com/archives/apparmor/2017-December/011350.html

Re: [OT] Relavant mailing list or USENET group

[Eric S Fraga]

On Tuesday,  5 Dec 2017 at 10:24, Richard Owlett wrote:
> I had been to https://pyra-handheld.com/boards/pages/pyra/ but there
> was no indication of where they were on the "initial design"/"product
> available" timeline.

Hard to say.  All the bits are mostly there.  Some final snagging on
cases with a few prototypes out in the wild.  Many of us are hoping
(waiting impatiently ;-)) for mid-2018 but this is a very small
endeavour so difficult to estimate.  The whole process from scratch to
date is openly discussed on the boards and in itself is interesting!

> As to web based fora, I've not discovered a way to efficiently
> read/find posts of interest.

I use gnus in Emacs for RSS feeds which can give you summaries of
activities on some fora (but not all).  Web-based fora are lacking in
functionality when compared with USENET unfortunately.  Step
backwards.  My current pet peeve is discourse based systems (e.g. Julia
language forum).

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.3


signature.asc
Description: PGP signature

Re: bugreport - reportbug 7.1.7 on Debian 9.1

[Michael Lange]

Hi,

On Tue, 5 Dec 2017 19:20:45 +0100
Sophie Loewenthal  wrote:

> Hi Michael,
> 
> Thanks for the info.
> 
> $  python3 -c "import locale; print(locale.nl_langinfo(locale.CODESET))"
> ANSI_X3.4-1968
> 
> I’ve not set this Bizarre
> 

this looks like somehow LANG is set to C (or maybe something that
Python does not know).
ANSI_X3.4-1968 appears to be a synonym for ASCII

You can change this temporarily by preceding the program call with an
explicitely defined locale:

$ python3 -c "import locale; print(locale.nl_langinfo(locale.CODESET))"
UTF-8
$ LANG=C python3 -c "import locale; print(locale.nl_langinfo(locale.CODESET))"
ANSI_X3.4-1968
$ LANG=en_US python3 -c "import locale; 
print(locale.nl_langinfo(locale.CODESET))"
ISO-8859-1
$ LANG=en_US.UTF8 python3 -c "import locale; 
print(locale.nl_langinfo(locale.CODESET))"
UTF-8

Maybe your terminal emulator is misconfigured, did you try
a different one? Or is there something suspicious looking in the
output of env ?

> 
> Sophie 
> ( ͡° ͜ʖ ͡°)

(ó.ò)

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Genius doesn't work on an assembly line basis.  You can't simply say,
"Today I will be brilliant."
-- Kirk, "The Ultimate Computer", stardate 4731.3

Nvidia driver installing newer releases from SVN

[Benny Simonsen]

Hi,

System: Fresh Debian 9
I have a Nvidia GT 1030, that needs 384 (or newer), and I have followed the
guide listed here:
https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_releases_from_SVN
Last step: svn-buildpackage --svn-ignore -us -uc -rfakeroot

But whats next, have tried cd to buid-area folder, containg the deb files,
and "dpkg -i *.deb", but leaves unconfigured packages and other issues.

Note:
As a prerequsite I did the same as required for 375.66 (above on the page)

Add "contrib" and "non-free" components to /etc/apt/sources.list, for
example:

# Debian 9 "Stretch"deb http://httpredir.debian.org/debian/ stretch
main contrib non-free

And also on deb-src

Br,
Benny

Re: [OT] Relavant mailing list or USENET group

[Richard Owlett]

On 12/05/2017 12:59 PM, Eric S Fraga wrote:

On Tuesday,  5 Dec 2017 at 10:24, Richard Owlett wrote:

I had been to https://pyra-handheld.com/boards/pages/pyra/ but there
was no indication of where they were on the "initial design"/"product
available" timeline.


Hard to say.  All the bits are mostly there.  Some final snagging on
cases with a few prototypes out in the wild.  Many of us are hoping
(waiting impatiently ;-)) for mid-2018 but this is a very small
endeavour so difficult to estimate.  The whole process from scratch to
date is openly discussed on the boards and in itself is interesting!


I understand completely. Back in the 70's I was a junior engineer in 
Power Supply Engineering at Digital Equipement involved from first 
prototype  past what was supposed to have been EOL for H720-E. (Any DEC 
people out there ;)





As to web based fora, I've not discovered a way to efficiently
read/find posts of interest.


I use gnus in Emacs for RSS feeds


I've seen the term "RSS", but never had any contact with it. Not sure if 
SeaMonkey 2.48 can use it.



which can give you summaries of
activities on some fora (but not all).  Web-based fora are lacking in
functionality when compared with USENET unfortunately.  Step
backwards.  My current pet peeve is discourse based systems (e.g. Julia
language forum).

Re: BIOS Can Not Find Disk

[Dan Norton]

On 12/04/2017 12:17 AM, David Christensen wrote:

On 12/03/17 13:44, Dan Norton wrote:

On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT. 
The disk is 1T and it was handled by the extended partition scheme 
before this experiment and it probably can again. I still want to do 
LVM and multiboot a few systems though.




[...]



When I mount /dev/sda1, I see:

# mount -o ro /dev/sda1 /mnt/sda1

# mount | grep /mnt/sda1
/dev/sda1 on /mnt/sda1 type vfat 
(ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)


# df /dev/sda1
Filesystem 1K-blocks  Used Available Use% Mounted on
/dev/sda1 973952   188    973764   1% /mnt/sda1

# tree -a /mnt/sda1
/mnt/sda1
`-- EFI
    `-- debian
    `-- grubx64.efi

# ls -l /mnt/sda1/EFI/debian/grubx64.efi
-rwxr-xr-x 1 root root 178688 Dec  2 23:33 
/mnt/sda1/EFI/debian/grubx64.efi


# file /mnt/sda1/EFI/debian/grubx64.efi
/mnt/sda1/EFI/debian/grubx64.efi: PE32+ executable (EFI application) 
x86-64 (stripped to external PDB), for MS Windows



I can run various LVM commands to confirm that d-i/partman did what I 
told it to do.



The next time I try this, I think I'll go the opposite extreme, feed a 
blank disk to d-i, let partman automagically format the whole disk, 
and see if GRUB installs, if the installation completes without error, 
if the disk boots, and what the SSD contains.




This post is being sent from a fresh netinst:

dan@mydeb:~$ uname -v
#1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19)

root@mydeb:/# fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x29f6f73a

Device Boot Start   End   Sectors   Size Id Type
/dev/sda1  * 2048    976895    974848   476M ef EFI (FAT-12/16/32)
/dev/sda2  976896  16601087  15624192   7.5G 83 Linux
/dev/sda3    16603134 532223999 515620866 245.9G  5 Extended
/dev/sda5    16603136 141600767 124997632  59.6G 8e Linux LVM
/dev/sda6   141602816 266600447 124997632  59.6G 83 Linux
/dev/sda7   266602496 391600127 124997632  59.6G 83 Linux
/dev/sda8   391602176 516599807 124997632  59.6G 83 Linux
/dev/sda9   516601856 532223999  15622144   7.5G 82 Linux swap / Solaris

[...]

As you can see, the partitioning scheme is primary/logical. Needed to 
get some work done. I'm in the process of restoring stuff from backup, 
but at least the saved emails are OK.


The installer was involved in all partitioning. At the start of this 
thread and another, fdisk had been used to define sda1 and sda2. This 
time I tried not to over-think it.


First, manual partitioning in the installer was used to remove the LVs 
and VGs. Then the physical partitions were removed, resulting in 1TB 
free space (the whole disk). There were lots of false starts, but I 
learned that you can reboot the installer and run it repeated through 
partitioning and eventually get things corrected. I lost count. 
Partitioning dread subsided and I began to relax.


Next, primary partitions were defined for sda1 and sda2. Logical 
partitions for sda5-9. The installer automagically did sda3 Extended. 
When it complained that there was no EFI, sda1 was removed and the EFI 
put in its place.


Now you are looking at this and thinking, "Boy, that is really sloppy. 
Wasting disk space like that." That's OK, I don't mind. Obviously sda1 
is much bigger than needed and sda2 is not used at all but it boots 
*normally* at last. Onward to installing another Debian and I may try 
GPT again, too.


Many thanks for your help, everyone.

 - Dan

Re: BIOS Can Not Find Disk

[David Wright]

On Mon 04 Dec 2017 at 17:34:52 (-0800), David Christensen wrote:
> On 12/04/17 07:21, David Wright wrote:
> >I recently reformatted a disk thus:
> >
> >puck:   GPT-style, master
> >
> >Part #  filesys sizecoderôle
> >puck-   1007KiB partition tables and alignment space
> >puck01  -   3MiBEF02bios-boot for Grub (bios_grub flag)
> >puck02  FAT32   496MiB  EF00EFI (boot flag)
> >puck03  ext2500MiB  8300/boot (unencrypted)
> >…
> 
> Your console session is incomplete -- you did not copy/paste your command.

That isn't a console session, it's taken from the File (in the MI5/FBI
sense) that I keep on each significant piece of hardware that I have.
"Puck" is what's written in magic marker on the drive.
"Part #" is the filesystem LABEL where there is such a thing,
otherwise it's a human label by which to refer to it (as I did
when I wrote puck01 later in the post).
"code" is the abbreviated code of the type used by gdisk.
"rôle" is the use that the area/partition is put to, written
in human language.

I don't know of a command that can print out a line like
puck-   1007KiB partition tables and alignment space
which is why I write it into the file myself.

> >which gdisk shows as
> >
> >Number  Start (sector)End (sector)  Size   Code  Name
> >120488191   3.0 MiB EF02  BIOS boot partition
> >28192 1023999   496.0 MiB   EF00  EFI System
> >3 1024000 2047999   500.0 MiB   8300  Linux filesystem
> >…
> 
> As above; but at least you dropped a clue, "gdisk".

That *is* a copy/paste. I didn't think the command relevant: my
question is about the absence of this sort of partition in the
disk that you formatted:

120488191   3.0 MiB EF02  BIOS boot partition

I was under the impression (correct me if this is wrong) that Grub
put its 1st stage in the first sector along with the "fake" MBR
partition table, and the 2nd stage into the BIOS boot partition
which is an area that nothing else takes any interest in.

AFAICT (again, correct me if this is wrong) your disk has nowhere
for Grub to place its 2nd stage, so it fails. Perhaps that's what you
were deliberately trying to show?

> >Is the absence of a partition like puck01 on your disk a significant
> >factor in your failure to install grub?
> >ie where's grub going to place itself?
> 
> I initially let d-i/partman automagically partition the SSD, looked
> at the table it generated, and saw a ESP partition, a swap
> partition, and a root partition.  I then wipe the first and last
> megabyte, created the GPT partition with parted, and then proceeded
> with the complex disk layout I really wanted.  Unfortunately,
> debian-9.1.0-amd64-xfce-CD-1 d-i blew up trying to install GRUB, so
> I don't know where GRUB ends up when UEFI firmware and GPT
> partitioning is done correctly.  That's why I plan to try again with
> the simplest automagic partitioning and see what happens.

I don't know anything about UEFI firmware. I'm only just inheriting
a UEFI laptop with W10 on it and hope to split a partition for linux,
but I've only booted linux from a USB stick just to have a poke about.

The OP/Subject line says "BIOS Can Not Find Disk" so I'm posting info
from a BIOS computer booting from a SATA GPT disk. I installed stretch
onto it from a USB stick. Here's the full output from gdisk if you
think it helps:

✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂

GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Disk /dev/sdb: 15625 sectors, 74.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3443D1C7-75D1-44BB-B438-18F912FEC2DA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 156249966
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)End (sector)  Size   Code  Name
   120488191   3.0 MiB EF02  BIOS boot partition
   28192 1023999   496.0 MiB   EF00  EFI System
   3 1024000 2047999   500.0 MiB   8300  Linux filesystem
   4 204800079140863   36.8 GiB8300  Linux filesystem
   579140864   156249966   36.8 GiB8300  Linux filesystem

✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂

And here is how it boots, as seen by bootinfoscript:

✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂

  Boot Info Script 0.61  [1 April 2012]


= Boot Info Summary: ===

 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 2048 
of the same hard drive for core.img, but core.img can not be found at this 
location.
 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 2048 
of the same hard drive for core

Re: BIOS Can Not Find Disk

[Pascal Hambourg]

Le 05/12/2017 à 06:55, David Christensen a écrit :


I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided - 
use entire disk and set up encrypted LVM", which produced:


     LVM VG debian-vg, LV home - 3.5 GB Linux device-mapper (linear)
  #1  3.5 GB f  ext4  /home
     LVM VG debian-vg, LV root - 2.0 GB Linux device-mapper (linear)
  #1  2.0 GB f  ext4  /
     LVM VG debian-vg, LV swap_1 - 8.5 GB Linux device-mapper (linear)
  #1  8.5 GB f  swap  swap
     LVM VG debian-vg, LV tmp - 255.9 MB Linux device-mapper (linear)
  #1    255.9 MB f  ext4  /tmp
     LVM VG debian-vg, LV tmp - 998.2 MB Linux device-mapper (linear)
  #1    998.2 MB f  ext4  /var
 Encrypted volume (sda3_crypt) - 15.2 GB Linux device-mapper (crypt)
  #1 15.2 GB K  lvm
 SCSI3 (0,0,0) (sda) - 16.0 GB ATA SAMSUNG SSD UM41
  1.0 MB    FREE SPACE
  #1    536.9 MB  B  F  ESP
  #2    255.9 MB F  ext2  /boot
  #3 15.2 GB K  crypto    (sda3_crypt)
     73.2 kB    FREE SPACE

(...)

d-i completed without errors.  :-)


ESP means that you ran the installer in EFI mode. If you did that with 
the initial partitioning (BIOS boot partition), the installation of GRUB 
could not work because there was no ESP partition.



As for "how does it boot with UEFI, GPT, and GRUB?", my vague guess is:

1.  There is no 16-bit 8086 first stage boot loader code in sector 0 of 
the SSD -- see 'gpart -d -vvv /dev/sda' output, below.  The motherboard 
firmware doesn't use this in UEFI mode.


Correct.

2.  There is a "protective MBR" in sector 0 of the SSD -- see 'fdisk -t 
mbr -l /dev/sda' output, below.  I don't know if UEFI firmware looks at 
this.


It may, in order to check that it contains a valid protective MBR.


3.  The firmware finds and reads the GPT partition table on the SSD.


Correct.

4.  The firmware finds the first GPT partition and file system, which 
look "right" for EFI boot images.


No.

5.  The firmware reads this file system and finds only one file, which 
it loads and runs (starting GRUB):


     /EFI/debian/grubx64.efi


No.

(If there were more than one choice, my guess is that I'd have to 
pre-select one in the CMOS setup, or perhaps have to select one from a 
menu at the end of POST?)


No.

First, a compliant UEFI firmware should look up its EFI boot variables 
and try each boot entry Boot* in the order defined in the BootOrder 
variable. The text description associated to theses entries is usually 
displayed in the EFI boot menu. If no entry is defined or works, then 
the firmware should look for a partition with the "EFI system partition" 
type GUID and look for an /EFI/Boot/bootx64.efi file (default path used 
on removable devices).


GRUB can be installed in such a path with

grub-install --removable

6.  GRUB finds the second GPT partition and file system, which looks 
"right" for GRUB, reads the file system, locates the appropriate files 
(notably /boot/grub/grub.cfg), and boots the system.


When /boot/grub is in a plain partition on the same drive as GRUB's core 
image (grubx64.efi here), the partition number is hardcoded in the core 
image.


Again -- are there any other commands I should run that readers might 
find interesting?


You can print the EFI boot variables with

efibootmgr -v

Re: playing blurays with vlc (or other)

[davidson]

On Sat, 2 Dec 2017, Pierre Frenkiel wrote:


  the information about vm0 was useful for vlc, but as I said, the
  problem is not actually solved, as I'm unable to use vlc with any
  audio track other than 1.


In vlc, 'b' seems to be the shortcut key for switching audio tracks
(and 'v' the shortcut for switching subtitles).

Re: inotifywait in bash script: space

[davidson]

On Sat, 2 Dec 2017, B.M. wrote:


Dear all,

not a Debian specific question, but I hope to get an answer here...

I try to use inotifywait in a bash script to block until a file in a directory
gets changed. Then the script should continue. That's working well unless the
path I hand over to inotifywait contains spaces.

I already tried to escape them like so:

 MYCOMMAND = "inotifywait  -qqr -e create \"$MYDIR\""

where MYDIR is something like "/tmp/test dir" but although echo shows the
command correctly and putting the very same command in a shell just works, as
part of my script it doesn't work. (I don't want to get paths back from
inotifywait.)

Thanks for any pointers towards clarification and help.


I don't know anything about inotifywait. Maybe that doesn't matter?

  $ foo="filename with spaces"
  $ echo content > "$foo"
  $ command=(cat "$foo")
  $ "${command[@]}"# This will work:
  content
  $ ${command[@]}  # but do notice that this will not work:
  cat: filename: No such file or directory
  cat: with: No such file or directory
  cat: spaces: No such file or directory



Best,
Bernd

Re: [OT] Relavant mailing list or USENET group

[Eric S Fraga]

On Tuesday,  5 Dec 2017 at 14:53, Richard Owlett wrote:

[...]

> I've seen the term "RSS", but never had any contact with it. Not sure
> if SeaMonkey 2.48 can use it.

No idea.  Never used SeaMonkey...

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.3


signature.asc
Description: PGP signature