Re: Default date output format changed after an upgrade to buster

[Curt]

On 2019-09-10, Sven Joachim  wrote:
> On 2019-09-10 22:06 +0200, Rainer Dorsch wrote:
>
>> Hi,
>>
>> after an upgrade from stretch to buster, the date default output changed on 
>> my
>> system
>>
>> As an example:
>>
>> Tue Sep 10 19:50:26 CEST 2019   (stretch)
>> Tue 10 Sep 2019 09:26:33 PM CEST  (buster)
>>
>> I am just wondering if this is a known issue or if another configuration 
>> change
>> during the upgrade caused this.
>
> The default format very much depends on your locale.  In the en_US.UTF-8
> locale I also see the difference, but I think it's a bug fix.  The
> buster output looks more like what an American user would expect.  If
> you don't like it, set LC_TIME to something else, e.g. en_GB.UTF-8.

You'd assume Americans would be less bewildered without the
"military-style" 24 clock (I remember old dad quizzing me when I was a
kid: "What time's 1700 hours?"), but then again our rather unique
habit of putting the month before the day (as in mm-dd-) is reversed
by the upgrade, so it seems to be a tie cultural imperialism-wise. 

> Cheers,
>Sven
>
>


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

Re: Default date output format changed after an upgrade to buster

[Curt]

On 2019-09-11, Curt  wrote:
> On 2019-09-10, Sven Joachim  wrote:
>> On 2019-09-10 22:06 +0200, Rainer Dorsch wrote:
>>
>>> Hi,
>>>
>>> after an upgrade from stretch to buster, the date default output changed on 
>>> my
>>> system
>>>
>>> As an example:
>>>
>>> Tue Sep 10 19:50:26 CEST 2019   (stretch)
>>> Tue 10 Sep 2019 09:26:33 PM CEST  (buster)
>>>
>>> I am just wondering if this is a known issue or if another configuration 
>>> change
>>> during the upgrade caused this.
>>
>> The default format very much depends on your locale.  In the en_US.UTF-8
>> locale I also see the difference, but I think it's a bug fix.  The
>> buster output looks more like what an American user would expect.  If
>> you don't like it, set LC_TIME to something else, e.g. en_GB.UTF-8.
>
> You'd assume Americans would be less bewildered without the
> "military-style" 24 clock (I remember old dad quizzing me when I was a
   24-hour clock
> kid: "What time's 1700 hours?"), but then again our rather unique
> habit of putting the month before the day (as in mm-dd-) is reversed
> by the upgrade, so it seems to be a tie cultural imperialism-wise. 
>
>> Cheers,
>>Sven
>>
>>
>
>


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

crc16

[Grzesiek Sójka]

Hi there,

Is there any utility to calculate crc16 (not the crc32) in Debian?

Thanks in advance for any help

Re: crc16

[Curt]

On 2019-09-11, Grzesiek Sójka  wrote:
> Hi there,
>
> Is there any utility to calculate crc16 (not the crc32) in Debian?


curty@einstein:~$ apt-cache search crc16
node-crc - module for calculating Cyclic Redundancy Check (CRC)

> Thanks in advance for any help
>
>


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

Re: crc16

[Curt]

On 2019-09-11, Curt  wrote:
> On 2019-09-11, Grzesiek Sójka  wrote:
>> Hi there,
>>
>> Is there any utility to calculate crc16 (not the crc32) in Debian?
>
>
> curty@einstein:~$ apt-cache search crc16
> node-crc - module for calculating Cyclic Redundancy Check (CRC)

On second thought, maybe it's wiser to install 'python-crcmod'
(available from the repositories, I believe).

http://crcmod.sourceforge.net/crcmod.html


>> Thanks in advance for any help
>>
>>
>
>


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

Re: Default date output format changed after an upgrade to buster

[Michael Stone]

On Wed, Sep 11, 2019 at 08:36:49AM +0200, Rainer Dorsch wrote:

Am Dienstag, 10. September 2019, 22:52:03 CEST schrieb Greg Wooledge:

On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote:
> after an upgrade from stretch to buster, the date default output changed
> on my system
>
> As an example:
>
> Tue Sep 10 19:50:26 CEST 2019   (stretch)
> Tue 10 Sep 2019 09:26:33 PM CEST  (buster)
>
> I am just wondering if this is a known issue or if another configuration
> change during the upgrade caused this.

https://www.mail-archive.com/debian-user@lists.debian.org/msg741032.html


Many thanks for all the replies. Greg, the perfect explanation you already
gave here

https://www.mail-archive.com/debian-user@lists.debian.org/msg741096.html

(that explains why buster behaves differently).

I think it would have been worth an entry for apt-listchanges, since it might
at least change the output of some local scripts (like it did here).


apt-listchanges in what? If you run the stretch date on buster, you'll 
get the same output. The change is that the localized string changed to 
something more sensible and date uses the localized string. If a script 
is relying on the output of a program like date without specifying 
either the C locale or a date format, it's almost certainly doing 
something wrong--those strings are expected to change depending on 
things like locale settings, and are for humans to read, not programs. 

Re: Default date output format changed after an upgrade to buster

[The Wanderer]

On 2019-09-11 at 07:57, Michael Stone wrote:

> On Wed, Sep 11, 2019 at 08:36:49AM +0200, Rainer Dorsch wrote:
> 
>> Am Dienstag, 10. September 2019, 22:52:03 CEST schrieb Greg 
>> Wooledge:

>>> https://www.mail-archive.com/debian-user@lists.debian.org/msg741032.html
>> 
>> Many thanks for all the replies. Greg, the perfect explanation you 
>> already gave here
>> 
>> https://www.mail-archive.com/debian-user@lists.debian.org/msg741096.html
>> 
>> (that explains why buster behaves differently).
>> 
>> I think it would have been worth an entry for apt-listchanges,
>> since it might at least change the output of some local scripts
>> (like it did here).
> 
> apt-listchanges in what?

Given that (as far as I'm aware) apt-listchanges just reports the
changelog and NEWS entries from the various packages, the question
should really be: a changelog or NEWS entry in what package, and what
version of that package?

In this case, the relevant package appears to be libc6, from the source
package glibc.

The changelog entry for glibc 2.28-5 mentions a backport of what looks
to my eye like the patch which makes this change, albeit without
mentioning what effect the change itself will have; to figure that out,
you have to read the referenced (Debian) bug report, #877900. That patch
appears to have been released upstream in glibc 2.29, which doesn't seem
to have hit Debian testing yet.

So I think the suggestion would have been that either the changelog or
the NEWS entry from the Debian-packaged version of glibc which first
included the patch which makes this change should have had a comment
pointing out that the default date format for this common locale would
change.

> If a script is relying on the output of a program like date without 
> specifying either the C locale or a date format, it's almost 
> certainly doing something wrong--those strings are expected to
> change depending on things like locale settings, and are for humans
> to read, not programs.

This is quite true, however.

-- 
The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Default date output format changed after an upgrade to buster

[Rainer Dorsch]

Am Mittwoch, 11. September 2019, 13:57:37 CEST schrieb Michael Stone:
> On Wed, Sep 11, 2019 at 08:36:49AM +0200, Rainer Dorsch wrote:
> >Am Dienstag, 10. September 2019, 22:52:03 CEST schrieb Greg Wooledge:
> >> On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote:
> >> > after an upgrade from stretch to buster, the date default output
> >> > changed
> >> > on my system
> >> > 
> >> > As an example:
> >> > 
> >> > Tue Sep 10 19:50:26 CEST 2019   (stretch)
> >> > Tue 10 Sep 2019 09:26:33 PM CEST  (buster)
> >> > 
> >> > I am just wondering if this is a known issue or if another
> >> > configuration
> >> > change during the upgrade caused this.
> >> 
> >> https://www.mail-archive.com/debian-user@lists.debian.org/msg741032.html
> >
> >Many thanks for all the replies. Greg, the perfect explanation you already
> >gave here
> >
> >https://www.mail-archive.com/debian-user@lists.debian.org/msg741096.html
> >
> >(that explains why buster behaves differently).
> >
> >I think it would have been worth an entry for apt-listchanges, since it
> >might at least change the output of some local scripts (like it did here).
> apt-listchanges in what? If you run the stretch date on buster, you'll
> get the same output. The change is that the localized string changed to
> something more sensible and date uses the localized string. If a script
> is relying on the output of a program like date without specifying
> either the C locale or a date format, it's almost certainly doing
> something wrong--those strings are expected to change depending on
> things like locale settings, and are for humans to read, not programs.

Don't expect that all my scripts are perfect ... there are quick and dirty 
ones;-) In a logfile a human readable output sounds not a too bad idea 
though...but I understand attaching that change to date does not make sense.

Nevermind, all good for me, I hope that if others are affected by the change 
they find the topic in the list archive.

Thanks again
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: crc16

[Andy Smith]

Hello,

On Wed, Sep 11, 2019 at 11:37:11AM +0200, Grzesiek Sójka wrote:
> Is there any utility to calculate crc16 (not the crc32) in Debian?

It should be trivial in almost any scripting language available in
Debian. Here is a Perl example.

$ sudo apt install libdigest-crc-perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  libdigest-crc-perl
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 14.2 kB of archives.
After this operation, 51.2 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 libdigest-crc-perl amd64 
0.22.2-1+b1 [14.2 kB]
Fetched 14.2 kB in 0s (93.0 kB/s)
Selecting previously unselected package libdigest-crc-perl.
(Reading database ... 127754 files and directories currently installed.)
Preparing to unpack .../libdigest-crc-perl_0.22.2-1+b1_amd64.deb ...
Unpacking libdigest-crc-perl (0.22.2-1+b1) ...
Setting up libdigest-crc-perl (0.22.2-1+b1) ...
Processing triggers for man-db (2.8.5-2) ...

$ perl -MDigest::CRC -e '$ctx = Digest::CRC->new(type=>"crc16"); 
$ctx->addfile(*STDIN); print $ctx->b64digest' < /etc/os-release 
lzA=

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Default date output format changed after an upgrade to buster

[rhkramer]

On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote:
> apt-listchanges in what? If you run the stretch date on buster, you'll
> get the same output. The change is that the localized string changed to
> something more sensible and date uses the localized string. If a script
> is relying on the output of a program like date without specifying
> either the C locale or a date format, it's almost certainly doing
> something wrong--


> those strings are expected to change depending on
> things like locale settings, and are for humans to read, not programs.

Interesting!  I have no argument with what you say, it makes perfect sense, 
but it must be one of those things that "goes without saying" -- I can't claim 
to be a Linux guru, but in the years I've spent with Linux and with a fair 
amount of reading, I never saw that stated, nor was it ever implied enough for 
me to infer that (nor did I ever have occasion to run into a problem because 
of it (I am not the OP).)

(I had a colleague who often felt that contracts included things that "go 
without saying" -- I tried to make it a practice to write those things into 
the contract. ;-)  (Well, within reason, at least -- there are things like 
laws that govern contracts, and maybe well known conventions. ;-)

Re: Default date output format changed after an upgrade to buster

[Greg Wooledge]

On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote:
> On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote:
> > those strings are expected to change depending on
> > things like locale settings, and are for humans to read, not programs.
> 
> Interesting!  I have no argument with what you say, it makes perfect sense, 
> but it must be one of those things that "goes without saying" -- I can't 
> claim 
> to be a Linux guru, but in the years I've spent with Linux and with a fair 
> amount of reading, I never saw that stated, nor was it ever implied enough 
> for 
> me to infer that (nor did I ever have occasion to run into a problem because 
> of it (I am not the OP).)

https://mywiki.wooledge.org/locale
https://wiki.debian.org/Locale

If you're writing a program that parses the output of a command, you
typically will need to set LANG or LC_ALL to C somewhere in your
program, in order to get output in a predictable format.

Re: crc16

[Jonas Smedegaard]

Quoting Grzesiek Sójka (2019-09-11 11:37:11)
> Is there any utility to calculate crc16 (not the crc32) in Debian?

Yes.

For command-line use:

  jacksum
  radare2

  node-crc
  libdigest-crc-perl: 
  python3-crcelk
  python3-crcmod
  tcllib

Latter part above are not really utilities, but can probably all of them 
be used for oneliners - like this:

echo foobar|perl -MDigest::CRC=crc16 -nE'chomp;say "$_: ", crc16($_)'


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

black screen (only mouse visible) after resume with xfce4 on kernel 5.2.0

[Andrea Borgia]

Hi.

On two systens with fairly different hardware (a 6yr old laptop I am using 
now on holiday and my new home desktop), with kernel 5.2.0 (and possibly 
as low as 5.0.11) the following happens: boot, login X, hibernate (ok), 
resume (also ok), unlock xfce4, stare at mouse pointer alone on a black 
screen. The pointer can move, there is sound (Telegram notifications, for 
example), and only keycombo that works is the one to go back to console.


Additionally, I noticed that this tends to happen only after the system 
was suspended for quite a while, i.e. if I hibernate it and soon 
afterwards resume it nothing strange happens. If I let it sleep for the 
night, the next morning it will surely give me a black screen. When I say 
that hibernate and resume are OK, I mean that the text console works just 
fine and the system is in no way thrashing.


Very important: on the same laptop, if I reboot with an older kernel, say 
5.0.2, after unlocking it I can use X just fine even after many cycles. I 
don't have the desktop at hand until I'm back home, but I first observed 
this issue around 5.0.11 (see [1])


Now the question: should I file this as a bug against the kernel package 
or against xfce4?


On one hand, the fact that changing kernel creates or prevents the issue 
seems to me a very strong indication this is a kernel bug, on the other 
hand I am not really able to try a different desktop environment at the 
moment (lack of time, lack of RAM and CPU power) and cannot completely 
rule out a userspace issue (some change in the kernel not properly 
accepted by the application)


Has anyone else experienced something similar? I've had a look at the logs 
and I don't see anything obviously wrong or different from one case to the 
other.


Thanks,
Andrea.

[1] 
https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/81#issuecomment-489403571)

Re: Default date output format changed after an upgrade to buster

[Michael Stone]

On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote:

Interesting!  I have no argument with what you say, it makes perfect sense,
but it must be one of those things that "goes without saying" -- I can't claim
to be a Linux guru, but in the years I've spent with Linux and with a fair
amount of reading, I never saw that stated, nor was it ever implied enough for
me to infer that (nor did I ever have occasion to run into a problem because
of it (I am not the OP).)


It's pretty clearly defined in the standards, but few people read them. :-)

Support zum Druckerankauf - printer to buy difficulties

[li . vog]

Sent today / Eingesandt heute (11. Sept. 2019) 
to/anhttps://developers.hp.com/hp-linux-imagingand printing


I need a new printerfor my computers at home since my Brother printer has 
stopped workingwhen the new Debian Buster came out, but it seems impossible for 
meto find out which printer works  without any difficulty with my twoFujitsu 
computers and Tuxedo laptop on Debian Buster, all of them onUSB2. Without the 
possibility to print out your list on this websiteis much too voluminous and 
confusing, calling your 'contact' leads toan Ubuntu site I am not interested 
in, and main HP support - as wellas Brother support - I do not want to call any 
more because the waythe arrogant louts there utter their ' no support for 
Linux' becomesmore and more insulting and impudent.
I think of anall-in-one (OfficeJet ?) ink, - not laser - printer with double 
sidedcolour printing and scanning, if possible  not above € 100.-- foronly 
occasionally more than 200 pages a month.   Let's see if you can- and want to - 
help.

Ich brauche einen neuen Drucker fürmeine Computer daheim, weil mein 
Brotherdrucker beim Release desneuen Debian Buster den Geist aufgegeben hat, 
aber es scheint fürmich unmöglich herauszufinden, welcher Drucker anstandslos 
mitmeinen zwei Fujitsu-Computern und meinem Tuxedo-Laptop unter DebianBuster, 
alle USB2, läuft. Ohne die Möglichkeit, sie auszudrucken,ist Ihre Liste auf 
dieser Website viel zu umfangreich und verwirrend,ein Aufruf Ihres ‚Kontaktes‘ 
führt zu einer Ubuntu-Seite, diemich nicht interessiert, und den Hauptsupport 
von HP – ebenso wieden von Brother – mag ich ganz einfach nicht mehr aufrufen, 
weildie Art, wie die arroganten Lümmel dort ihr ‚kein Support fürLinux‘ 
ausdrücken, immer beleidigender und unverschämter wird.Ich denke an einen 
all-in-one(OfficeJet?)Tinten-, nichtLaserdrucker mit doppelseitigem Farbdruck 
und Scannen, wenn möglichnicht über € 100,-- für nur gelegentlich mehr als 200 
Seiten proMonat. Schaun, ob Sie helfen können – und wollen.


Yours/Ihr
OSR.Hans Vogelsberger

Re: Default date output format changed after an upgrade to buster

[rhkramer]

On Wednesday, September 11, 2019 09:14:19 AM Greg Wooledge wrote:
> On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote:
> > On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote:
> > > those strings are expected to change depending on
> > > things like locale settings, and are for humans to read, not programs.
> > 
> > Interesting!  I have no argument with what you say, it makes perfect
> > sense, but it must be one of those things that "goes without saying" --
> > I can't claim to be a Linux guru, but in the years I've spent with Linux
> > and with a fair amount of reading, I never saw that stated, nor was it
> > ever implied enough for me to infer that (nor did I ever have occasion
> > to run into a problem because of it (I am not the OP).)
> 
> https://mywiki.wooledge.org/locale
> https://wiki.debian.org/Locale
> 
> If you're writing a program that parses the output of a command, you
> typically will need to set LANG or LC_ALL to C somewhere in your
> program, in order to get output in a predictable format.

That's the sentence that would have been most meaningful / useful to me, and I 
would have needed to find that in all (or at least many of) the sources of 
documentation on how to write scripts or programs.  (Now, sometimes I have 
selective attention, maybe it is there and I just glossed over it...)

I'd need something to make me think there was a reason to look at locale when 
writing a script or program.

(The only reason I found (that I can recall) to set a locale was to get a sort 
order that met my needs (usually meaning one that sorted uppercase and 
lowercase words and letters in a common sort order (not separated, uppercase 
in one place, lowercase in another).  (Hmm, I vaguely recally that I once had 
to change the locale for some other reason, but that reason escapes me atm.)

merkaartor: annoying merkaartor.log in HOME

[Jerome BENOIT]

Hello List,

each time I read an OSM data file with merkaartor,
a (very) annoying merkaartor.log is let in my HOME directory.
How can we get rid of it ? or get it elsewhere ?

Thanks in advance,
Jerome

Buster Problem - No Sound

[Thomas George]

After upgrading from Stretch to Buster no sound

Rebooted to Stretch, sound works fine

The difference: Choice of outputs in Stretch includes lineout- built in 
audio. This option is missing in Buster


How can I correct this?

Re: merkaartor: annoying merkaartor.log in HOME

[Reco]

Hi.

On Wed, Sep 11, 2019 at 06:40:24PM +0400, Jerome BENOIT wrote:
> Hello List,
> 
> each time I read an OSM data file with merkaartor,
> a (very) annoying merkaartor.log is let in my HOME directory.
> How can we get rid of it ? or get it elsewhere ?

Create an apparmor profile for it, deny it creating the offending file.
Update a profile as needed. Problem solved.

Sample merkaartor profile attached, took me a minute to make it.

Reco
#include 

/usr/bin/merkaartor {
  #include 
  #include 
  #include 
  #include 
  #include 

  deny owner /home/*/merkaartor.log w,

  /proc/sys/kernel/random/boot_id r,
  owner /home/*/.Xauthority r,
  owner /home/*/.cache/fontconfig/* r,
  owner /home/*/.config/** rwl,
  owner /home/*/.config/Merkaartor/* rwk,
  owner /home/*/.config/Merkaartor/Merkaartor.conf rw,
  owner /home/*/.config/fontconfig/fonts.conf r,
  owner /home/*/.merkaartor/* rw,

}

Trapped in Gnome

[Thomas George]

At login after booting up there is a symbol like a gear below the 
password entry line. I moved the mouse and clicked on this symbol. 
Several options appeared and I decided to try Classic Gnome. This worked 
but the next time I booted up the mouse was frozen. The symbol to change 
desktops is there but there is no way to reach it, the mouse is stuck in 
the lower right side of the screen


How can I escape? I don't like the version of Gnome I an stuck in

Re: merkaartor: annoying merkaartor.log in HOME

[Charles Curley]

On Wed, 11 Sep 2019 18:40:24 +0400
Jerome BENOIT  wrote:

> each time I read an OSM data file with merkaartor,
> a (very) annoying merkaartor.log is let in my HOME directory.
> How can we get rid of it ? or get it elsewhere ?

That's probably a question for the merkaartor folks.

Short of that, that sounds like a job for logrotate. Or if you just
want to get rid of or move them, a cron job. Or both: a cron job to
move them, and a logrotate job to manage them.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = 38DD CE9F 9725 42DD E29A  EB11 7514 6D37 A332 10CB
https://charlescurley.com

Re: Linux Journal epub files

[Jonathan Dowland]

On Mon, Sep 09, 2019 at 07:15:16AM -0500, Nate Bargmann wrote:

I did manage to grab all of the available PDF files and then grabbed
everything in HTML for good measure in my personal archive.  I could
pass along the needed PDF files if that would help you.  Note that I
have no expressed permission from Linux Journal to do so.


That's a kind offer, Nate. In the event that archive.org do *not* have
these all already (and I'm trying to verify), then it would be best IMHO
to arrange to get the PDFs to them. I can facilitate that, if you want.
Please contact me off-list if you are happy to proceed.


--
👱🏻  Jonathan Dowland
✎   j...@dow.land
🔗   https://jmtd.net

Re: Problem enabling IOMMU with Buster and Xen

[Intense Red]

> Have you enabled SR-IOV in the bios?

   I love how the various BIOS entries have zero help even though AMI has an 
empty help/description field. No, that was not enabled -- thanks! -- but even 
enabling it, doing a cold/poweroff boot cycle does nothing. It still gives the 
exact same error message.

> I also suspect that Xen doesnt allow to PCI passthrough host device
> right?

   I actually haven't tried that. All of the various Xen "docs"/how-tos I've 
read say that each preceding step must be done or it won't work. (Based on 
your input, I'll try that but I'm not hopeful.)

   At this point I've read that Xen's passthrough might not work with some 
motherboard chipsets, so I'm wondering if Xen is a bit too cutting edge for 
what I want to do.

   What I want to do is to run multiple secure/separated VMs on a machine. One 
of those VMs will be to handle an Internet connection and firewall. Another VM 
will do filesharing via NFS and Samba; another VM is to run Kodi and output 
videos/TV via HDMI to a TV/monitor.

   From everything I've read, Xen is the ideal choice -- but only if I can get 
it to run. :)

-- 
The first known legal proclamation in the history of the world is on display in 
Paris, in the Louvre. It was given about 2400 B.C. by Enmetena, ruler of the 
Sumerian city-state of Lagash. It was a decree of debt cancellation.

Re: Buster: Konqueror as File Manager

[R.Lewis]

Update about a sidebar for Konqueror

More searching on the web has lead me to this thread:

https://bugs.kde.org/show_bug.cgi?id=373824

and to comment no. 27.

Using David Faure's suggestion I did the following to create a sidebar:

. launch krunner (alt-F2)
. enter "/" 
. click on "Locations Open /"
. this will open konqueror as file manager
. put a check mark next to "View / Lock to current location"
. do "Window / Split view Left/Right"
. re-size the left pane to look like a sidebar
. from either pane, put a check mark next to "View / Link view"
. go to "File / Session / Save as ..." and save this session

When you click on a folder in the left pane, it will be show up in the right 
pane.

Tips:

. Only these two panes are linked, so if you do "Split view Left/Right" from 
the right pane, any selection you make in the far left pane will only affect 
the pane to its immediate right.

. I suggest you display the bookmarks toolbar and use bookmarks, it's 
especially helpful with a split view.

. To launch your file manager
. go to Application Launcher / Edit Applications...
. create a New Item in the folder of your choice, e.g. System or 
Utilities
. give it a Name and Description, and select an icon
. in the Command field, put "konqueror --open-session 
"
. Save
. add this new application to Favourites, the panel, or the desktop

. To make a global shortcut
. go to System Settings / Workspace / Shortcuts / Edit / New / Global 
Shortcut / Command/URL
. give the New Action a name; e.g. KonquerorFM
. enter a comment in the Comment tab, if you wish
. enter your shortcut key in the Trigger tab
. enter the same command in the Action tab that you entered to create 
the application
. click "Apply"


Although this method doesn't replace the full-functioning sidebar of 
Konqueror that's in Stretch, it does help, a bit, in Buster.


Regards,
Robert

Re: OT: Missing sidebar; was buster: multiple instances of konqueror?

[R. Lewis]

Hello,

Étienne Mollier wrote:

> On 07/09/2019 18.00, R. Lewis wrote:
>> Hi,
>> 
>> D. R. Evans wrote:
>> 
>>> R.Lewis wrote on 9/7/19 8:14 AM:
>>>
 I'm glad to see that you have solved your problem with konqueror, and
 I'm wondering if you can help me with mine.

 Do you have a sidebar (F9)?  If you do, how did you get it?

>>>
>>> Nope. I saw your original question, and have no solution for you, I'm
>>> afraid.
>>>
>>>   Doc
>>>
>> 
>> Thanks very much for replying.
>> 
>> Robert
>> 
> 
> Hi,
> 
> I managed to get something looking like a side bar (side tool
> bar might be a more appropriate naming perhaps), even with F9 to
> switch it on and off.  But I had to configure it myself to get
> it to work, and it is quite possible that is does not achieve
> the convenience of the way it worked in previous Konqueror
> versions.
> 
> I worked with the "Bookmark Toolbar", but steps would be similar
> when using any other custom toolbar.  Here are the steps I
> followed:
> 
> 1. I made sure the "Bookmark Toolbar" was enabled in the menu
>showing up when right clicking over the menu bar.
> 
> 2. Right click over the Bookmark Toolbar shows a menu in which I
>made sure the "Lock Toolbar Positions" entry was unchecked.
> 
> 3. Using the handle which just spawned, I dragged the Bookmark
>Toolbar to the side, until a shadow filling the whole height
>of the window show up.
> 
> 4. To setup the F9 switch, I went to the menu:
> Settings
> -> Configure Shortcuts…
>then searched for "bookmark", and created the "F9" shortcut
>for the "Bookmark Toolbar".
> 
> 5. And hit "OK" to validate.
> 
> I fear it is kind of a very hack-ish way of bringing this option
> back to Konqueror, but hope it will open interesting
> perspectives nevertheless.  Don't hesitate to play with the
> "Text Position" and "Icon size": the bar tends to use as much
> space as it requires, without a handle to reduce its width.
> 
> Kind Regards,  :)

Thank you for the reply, and the handy tips.  I never realized that the 
toolbars could be repositioned.  There's always something new to learn. :-)

More searching on the web lead me to a method for creating a tree-style 
sidebar.  I've posted it in my original thread "Buster: Konqueror as File 
Manager", rather than to this OT thread, so that  others may find more 
easily.

Thanks again.

Regards,
Robert

Re: relational database tracking of packages and updates

[Matt Zagrabelny]

On Tue, Sep 10, 2019 at 9:38 PM Greg Wooledge  wrote:

> On Tue, Sep 10, 2019 at 02:55:20PM -0500, Matt Zagrabelny wrote:
> > Does anyone know of a "software inventory" solution for Debian (or other
> > GNU/Linux OSes) ?
> >
> > I'm thinking something that keeps track of packages. I.e. when various
> > package versions become available and when upgrades happen to said
> packages.
> >
> > There are a variety of ways of attacking this problem and I'm wondering
> if
> > anyone has already had some success in the domain?
>
> https://wiki.debian.org/UltimateDebianDatabase/


Thanks for the pointer, Greg.

I was hoping to have some sort of package I could install on each system I
admin. There would be a script or something that would keep a database
updated of what is happening with packages on that system.

I could then interact with the database. In pseudo-SQL:

select * from hosts, packages, etc. where package_name = 'apache2' and
package_state = 'installed' and package_version <= '2.4';

Not sure if anyone has done something like this or not.

-m

Re: relational database tracking of packages and updates

[Greg Wooledge]

On Wed, Sep 11, 2019 at 01:23:20PM -0500, Matt Zagrabelny wrote:
> I was hoping to have some sort of package I could install on each system I
> admin. There would be a script or something that would keep a database
> updated of what is happening with packages on that system.

The closest equivalent of that is dpkg's log files.

/var/log/dpkg.log*

You could write something that parses them and stores information
in an sqlite database, or whatever.  I don't know of any existing
implementations.

Re: Problem enabling IOMMU with Buster and Xen

[Dan Ritter]

Intense Red wrote: 
> 
>What I want to do is to run multiple secure/separated VMs on a machine. 
> One 
> of those VMs will be to handle an Internet connection and firewall. Another 
> VM 
> will do filesharing via NFS and Samba; another VM is to run Kodi and output 
> videos/TV via HDMI to a TV/monitor.
> 
>From everything I've read, Xen is the ideal choice -- but only if I can 
> get 
> it to run. :)

You might want Proxmox, which is a virtualization management
distro built on top of Debian.

Or, maybe KVM/QEMU with libvirt management.

In any case, remember that VMs generally don't provide much
security from each other -- they're billed that way, but new
escapes keep being found.

-dsr-

Gnu sieve vs Dovecot sieve-filter - sieve-filter extremely slow at lda (writing emails to local mbox files)

[Zenaan Harkness]

Why is Gnu sieve so extremely fast to batch process an mbox file, but
while Dovecot's sieve-filter is an order of magnitude slower?

Sequence:

 - mpop or getmail to pipeline download emails into temp mbox file
 - filter that file

Gnu sieve just flies through a local mbox file and saving emails to
other local mbox files.

Gnu sieve rejects too many emails with "malformed" errors, so after a
few years I bit the bullet and upgraded to Dovecot's sieve-filter.

Dovecot's sieve-filter, at present, is an order of magnitude slower.

Here's my filter command (one line):

/usr/bin/sieve-filter -veW -c $HOME/etc/email/sieve-dovecot-config.conf -o 
mail_location=mbox:~/mail:INBOX=~/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions
 ~/etc/email/sieve.rc email-incoming-unsorted

The sieve script is fine now that I have the correct "require"
clauses (hint: "capability strings").

File ~/etc/email/sieve-dovecot-config.conf:

  protocols = pop
  lda_mailbox_autocreate = yes
  lda_mailbox_autosubscribe = yes
  mail_fsync = never

There's no re-sending of emails into my local Postfix SMTP server - I
checked the system logs and confirmed this (journalctl -f).

I suspect that Gnu sieve was directly writing each email to the
appropriate sieve-determined mbox file (perhaps with only a sync at
the end of a single batch process - what I've attempted to achieve
above with sieve-filter), and that sieve-filter is instead passing
each email through some (dovecot) lda?

Here's the output for a sieve-filter batch processing of 11 emails:

$ /usr/bin/sieve-filter -veW -c /home/zen/etc/email/sieve-dovecot-config.conf 
-o 
mail_location=mbox:/home/zen/mail:INBOX=/home/zen/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions
 /home/zen/etc/email/sieve.rc email-incoming-unsorted
# PS0 Timestamp: 20190912@07:02:23
info: filtering: [Tue, 3 Sep 2019 05:17:16 -0500; 10240 bytes] `Re: 
VentureBeat: The death of disk? H...'.
info: 
msgid=: 
stored mail into mailbox 'l/cp/cp'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 07:29:53 -0400; 12968 bytes] `[zfs-devel] 
xattr naming format in Zo...'.
info: msgid=<15675101930.d5ba2e.12...@composer.zfsonlinux.topicbox.com>: stored 
mail into mailbox 'l/z/zdev'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 03 Sep 2019 15:29:09 +0300; 20461 bytes] `Re: 
[zfs-devel] xattr naming format i...'.
info: msgid=<23955051567513...@sas1-02732547ccc0.qloud-c.yandex.net>: stored 
mail into mailbox 'l/z/zdev'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 18:20:42 +0530; 18065 bytes] `Re: 
[Gluster-users] Issues with Geo-r...'.
info: 
msgid=: 
stored mail into mailbox 'l/gl/user'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 09:34:20 -0400; 13342 bytes] `Re: tasksel'.
info: msgid=<20190903133420.gs6...@eeg.ccf.org>: stored mail into mailbox 
'l/deb/user'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 06:56:07 -0700 (PDT); 12390 bytes] 
`[awx-project] Re: AWX on Kubernetes m...'.
info: msgid=<0715adb7-540f-4cff-9282-e1252c53c...@googlegroups.com>: stored 
mail into mailbox 'l/ansible/awx'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 07:01:27 -0700 (PDT); 12220 bytes] 
`[awx-project] Re: AWX on Kubernetes m...'.
info: msgid=<949b2c17-4254-49f1-83b4-cd54d15aa...@googlegroups.com>: stored 
mail into mailbox 'l/ansible/awx'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 10:14:58 -0400; 25313 bytes] `Re: [zfs-devel] 
xattr naming format i...'.
info: 
msgid=: 
stored mail into mailbox 'l/z/zdev'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 17:10:22 +0200; 7567 bytes] `Re: 
[asterisk-users] Playing MP3's in...'.
info: msgid=<20190903151022.354xpe6ds2vglher@red.localdomain>: stored mail into 
mailbox 'l/as/users'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Wed, 4 Sep 2019 01:04:49 +0900; 14858 bytes] `Re: 
[Hyperledger Fabric] a primitive ...'.
info: msgid=<160901d8-b903-9e9a-91ac-267571b0e...@gmx.com>: stored mail into 
mailbox 'l/hl/fabric'.
info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 09:55:22 -0700 (PDT); 13337 bytes] 
`[awx-project] Re: AWX on Kubernetes m...'.
info: msgid=: stored 
mail into mailbox 'l/ansible/awx'.
info: message expunged from source mailbox upon successful move.
2 ▶︎️ zen@eye 20190912@07:02:30 ~ $


So about 3/4 of a second is spent by dovecot's sieve-filter, on each
email that it processes - watching it is painful given how fast Gnu
sieve has been for the last few years - it's almost (but not 

Re: Gnu sieve vs Dovecot sieve-filter - sieve-filter extremely slow at lda (writing emails to local mbox files)

[Zenaan Harkness]

On Thu, Sep 12, 2019 at 07:55:23AM +1000, Zenaan Harkness wrote:
> Why is Gnu sieve so extremely fast to batch process an mbox file, but
> while Dovecot's sieve-filter is an order of magnitude slower?
> 
> Sequence:
> 
>  - mpop or getmail to pipeline download emails into temp mbox file
>  - filter that file
> 
> Gnu sieve just flies through a local mbox file and saving emails to
> other local mbox files.
> 
> Gnu sieve rejects too many emails with "malformed" errors, so after a
> few years I bit the bullet and upgraded to Dovecot's sieve-filter.
> 
> Dovecot's sieve-filter, at present, is an order of magnitude slower.
> 
> Here's my filter command (one line):
> 
> /usr/bin/sieve-filter -veW -c $HOME/etc/email/sieve-dovecot-config.conf -o 
> mail_location=mbox:~/mail:INBOX=~/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions
>  ~/etc/email/sieve.rc email-incoming-unsorted
> 
> The sieve script is fine now that I have the correct "require"
> clauses (hint: "capability strings").
> 
> File ~/etc/email/sieve-dovecot-config.conf:
> 
>   protocols = pop
>   lda_mailbox_autocreate = yes
>   lda_mailbox_autosubscribe = yes
>   mail_fsync = never
> 
> There's no re-sending of emails into my local Postfix SMTP server - I
> checked the system logs and confirmed this (journalctl -f).
> 
> I suspect that Gnu sieve was directly writing each email to the
> appropriate sieve-determined mbox file (perhaps with only a sync at
> the end of a single batch process - what I've attempted to achieve
> above with sieve-filter), and that sieve-filter is instead passing
> each email through some (dovecot) lda?
> 
> Here's the output for a sieve-filter batch processing of 11 emails:
> 
> $ /usr/bin/sieve-filter -veW -c /home/zen/etc/email/sieve-dovecot-config.conf 
> -o 
> mail_location=mbox:/home/zen/mail:INBOX=/home/zen/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions
>  /home/zen/etc/email/sieve.rc email-incoming-unsorted
> # PS0 Timestamp: 20190912@07:02:23
> info: filtering: [Tue, 3 Sep 2019 05:17:16 -0500; 10240 bytes] `Re: 
> VentureBeat: The death of disk? H...'.
> info: 
> msgid=: 
> stored mail into mailbox 'l/cp/cp'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 07:29:53 -0400; 12968 bytes] `[zfs-devel] 
> xattr naming format in Zo...'.
> info: msgid=<15675101930.d5ba2e.12...@composer.zfsonlinux.topicbox.com>: 
> stored mail into mailbox 'l/z/zdev'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 03 Sep 2019 15:29:09 +0300; 20461 bytes] `Re: 
> [zfs-devel] xattr naming format i...'.
> info: msgid=<23955051567513...@sas1-02732547ccc0.qloud-c.yandex.net>: stored 
> mail into mailbox 'l/z/zdev'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 18:20:42 +0530; 18065 bytes] `Re: 
> [Gluster-users] Issues with Geo-r...'.
> info: 
> msgid=: 
> stored mail into mailbox 'l/gl/user'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 09:34:20 -0400; 13342 bytes] `Re: tasksel'.
> info: msgid=<20190903133420.gs6...@eeg.ccf.org>: stored mail into mailbox 
> 'l/deb/user'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 06:56:07 -0700 (PDT); 12390 bytes] 
> `[awx-project] Re: AWX on Kubernetes m...'.
> info: msgid=<0715adb7-540f-4cff-9282-e1252c53c...@googlegroups.com>: stored 
> mail into mailbox 'l/ansible/awx'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 07:01:27 -0700 (PDT); 12220 bytes] 
> `[awx-project] Re: AWX on Kubernetes m...'.
> info: msgid=<949b2c17-4254-49f1-83b4-cd54d15aa...@googlegroups.com>: stored 
> mail into mailbox 'l/ansible/awx'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 10:14:58 -0400; 25313 bytes] `Re: 
> [zfs-devel] xattr naming format i...'.
> info: 
> msgid=: 
> stored mail into mailbox 'l/z/zdev'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 17:10:22 +0200; 7567 bytes] `Re: 
> [asterisk-users] Playing MP3's in...'.
> info: msgid=<20190903151022.354xpe6ds2vglher@red.localdomain>: stored mail 
> into mailbox 'l/as/users'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Wed, 4 Sep 2019 01:04:49 +0900; 14858 bytes] `Re: 
> [Hyperledger Fabric] a primitive ...'.
> info: msgid=<160901d8-b903-9e9a-91ac-267571b0e...@gmx.com>: stored mail into 
> mailbox 'l/hl/fabric'.
> info: message expunged from source mailbox upon successful move.
> info: filtering: [Tue, 3 Sep 2019 09:55:22 -0700 (PDT); 13337 bytes] 
> `[awx-project] Re: AWX on Kubernetes m...'.
> info: msgid=: stored 
> mail into mailbox 'l/ansible/awx'.
> info: message expunged fro

Re: Screensaver issues after distro upgrade (SOLVED)

[Miroslav Skoric]

On 9/10/19 8:11 PM, Christopher David Howie wrote:


On 9/10/19 4:30 AM, Miroslav Skoric wrote:

After upgrading the old laptop from Jessie to Stretch, I noticed that
the screensaver in Mate environment does not work for me as before. For
example, when the screen goes black after some time of inactivity, for
returning back it is not enough just to touch the touchpad or press any
key. Instead, pressing any key or touching the touchpad makes the screen
just some 1% lighter than the full black (or better to say, it remains
99% black). However, the last working GUI does not return.


I have this same issue with the default configuration of XFCE on Buster,
where the problem was not present on Stretch.



Hi Chris,

Well, I noticed that issue after I recently upgraded to Stretch, but not 
had it in Jessie. Whatever. Having in mind that Stretch is oldstable for 
a while, and you had the issue in Buster, it seems that the issue goes 
through the versions intact :-)



Is light-locker installed, and do you use lightdm?  light-locker appears
to be the source of this issue.  Googling "light-locker black screen"
returns dozens of posts across many sites complaining about the same
problem.



Yes, light-locker was installed, and as soon as I removed it the problem 
disappeared. By the way, lightdm is still there, however I am unsure 
about the display manager in current use because it is the system that 
started initially from Squeeze several years ago, and included Gnome, 
KDE, LXDE, and XFCE (and I added MATE in Wheezy I think). Before the 
last dist-upgrade I removed KDE because I used it at least.



I resolved this issue by removing light-locker and installing
xscreensaver instead.  Note that this required removing a few
metapackages, and then marking the dependent packages that I wanted to
keep as manually installed to prevent apt from removing most of my
desktop tools.



Well, in trying solution for this issue, I removed xscreensaver 
yesterday. So it disappeared from MATE's menu System > Preferences > ... 
but that did not solve the problem.


Nevertheless now I only have one instance of screensaver preferences in 
MATE's System > Preferences > Look and Feel > Screensaver. It works well 
for now. I'll observe its behaviour, and report again if it is not good.


Thank you for help!

Misko

Re: Screensaver issues after distro upgrade

[Miroslav Skoric]

On 9/11/19 12:12 AM, Ben Caradoc-Davies wrote:



I saw the same problem when I tried lightlocker after upgrading to XFCE 
4.14, so I went back to good old xscreensaver. Ugly bitmaps fonts and no 
theming, but secure and reliable. There is a new locker in XFCE, but 
there have been reports of segfaults causing uncommanded unlock, so I 
consider it too vulnerable for use. There is a bug report.


Kind regards,



Ben, I just removed light-locker, and the problem disappeared. I did not 
reinstall xscreensaver (yet). Looks as if it is not required in my 
environment (MATE).


Regards,

Misko

Re: black screen (only mouse visible) after resume with xfce4 on kernel 5.2.0

[Christopher David Howie]

On 9/11/2019 9:58 AM, Andrea Borgia wrote:
> unlock xfce4, stare at mouse pointer alone on a black screen

If this is the same problem I had (and discussed prior on this list),
there is a bug in light-locker that seems to cause this behavior
randomly even without hibernation.  Consider switching from light-locker
to xscreensaver; this resolved the problem for me.

If it resolves the problem for you as well then I would hesitate to say
immediately that it's a kernel bug, even if the kernel version is
somehow related to the problem.

See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913062

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Re: Screensaver issues after distro upgrade (SOLVED)

[Christopher David Howie]

On 9/11/2019 7:01 PM, Miroslav Skoric wrote:
> Well, I noticed that issue after I recently upgraded to Stretch, but not
> had it in Jessie. Whatever. Having in mind that Stretch is oldstable for
> a while, and you had the issue in Buster, it seems that the issue goes
> through the versions intact :-)

Yes, light-locker has not changed much recently and the threads I was
able to find on the issue spanned many years and Linux distributions.
Debian is not unique to have this problem.

I believe this is the relevant bug.  It may be useful to add any
additional information beyond what has already been reported there:

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

Perhaps the problem is hardware-specific.  It doesn't seem like everyone
has this problem, so there must be something our systems all have in
common to trigger this.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Re: Default date output format changed after an upgrade to buster

[David Wright]

On Wed 11 Sep 2019 at 07:26:33 (-), Curt wrote:
> On 2019-09-10, Sven Joachim  wrote:
> > On 2019-09-10 22:06 +0200, Rainer Dorsch wrote:
> >>
> >> after an upgrade from stretch to buster, the date default output changed 
> >> on my
> >> system
> >>
> >> As an example:
> >>
> >> Tue Sep 10 19:50:26 CEST 2019   (stretch)
> >> Tue 10 Sep 2019 09:26:33 PM CEST  (buster)
> >>
> >> I am just wondering if this is a known issue or if another configuration 
> >> change
> >> during the upgrade caused this.
> >
> > The default format very much depends on your locale.  In the en_US.UTF-8
> > locale I also see the difference, but I think it's a bug fix.  The
> > buster output looks more like what an American user would expect.  If
> > you don't like it, set LC_TIME to something else, e.g. en_GB.UTF-8.
> 
> You'd assume Americans would be less bewildered without the
> "military-style" 24 clock (I remember old dad quizzing me when I was a
> kid: "What time's 1700 hours?"), but then again our rather unique
> habit of putting the month before the day (as in mm-dd-) is reversed
> by the upgrade, so it seems to be a tie cultural imperialism-wise. 

What surprised me is the use of 12am and 12pm in the States. When
I was at grammar school (in the days of 12hour times), you lost
marks for writing either of these contradictions. It was either
12 noon, 12 midnight, or 12 o'clock (where there's no ambiguity).

Even more astonishing is the fact that the US Government switched
their am/pm meanings sometime between 2000 and 2008, which shows
just how ambiguous they are.

Cheers,
David.

PRoblems uninstalling nvidia

[Carlos Kosloff]

Hello list,

Running buster + backports.

Instaled nvidia from an alternate source an ran into problems because 
not packaged for Debian.


Probem is I cannot uninstall old version because dpkg halts:

|Welcome to the NVIDIA Software Installer for Unix/Linux

Detected 8 CPUs online; setting concurrency level to 8.

If you plan to no longer use the NVIDIA driver, you should make sure 
that no X screens
are configured to use the NVIDIA X driver in your X configuration file. 
If you used

nvidia-xconfig to configure X, it may have created a backup of your original
configuration. Would you like to run `nvidia-xconfig 
--restore-original-backup` to

attempt restoration of the original X configuration file?
  [default: (N)o]: N

Progress: [  0%] 
[..]

|

|this does not even return the prompt.|

|After this I can no longer update system apt refuses to run dist-upgrade.|

|SO, how can I uninstall old version of nvidia?
|

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

>> https://wiki.debian.org/RaspberryPiImages
>> https://www.raspberrypi.org/documentation/installation/
> 
> Potential timeline?
> 
> Cheers, Gene Heskett

My RPI4 arrived as well - need to pick up also power supply and cables,
which arrived too. Excited to see how it performs.

Re: Display resolution 3840x2160@24rb stopped working after Upgrade from Stretch to Buster

[Jan Michael Greiner]

Dear Charles,

On Monday, September 9, 2019, 1:55:06 PM GMT+2, Charles Curley wrote:

>> On Mon, 9 Sep 2019 10:20:37+ (UTC) Jan Michael Greiner wrote:
>> With Debian Stretch (9.8) I had the display running with 3840x2160
>> resolution at 24Hz reduced blank.


>> [What worked with Debian Stretch (9.9)]
>> export modename="3840x2160_24.00_rb"
 >> xrandr --newmode $modename 209.75 3840 3888 3920 4000 2160 2163 2168 2185 
 >> +HSync -Vsync
 >> xrandr --addmode HDMI-1 $modename
 >> xrandr --output HDMI-1 --mode $modename

 >> [Problem with Debian Buster (10.1)]
 >> xrandr --output XWAYLAND1 --mode $modename
 >> xrandr: Configure crtc0 failed

 >And I take it you want to reproduce that on Debian 10 (buster). I
 > suggest you:
 > * Install arandr.
 >[...]

 Thank you for making me aware of arandr. However, from what I learned:

- arandr is merely a graphical tool for xrandr, so if something does not work 
with xrandr, arandr will not be able to help 

- I did not see any option in the arandr gui to add a non yet existing 
resolution (and I would like to add a 24Hz reduced blank resolution)

 To rephrase my question: How can I enable a custom screen resolution and 
refresh rate (with my specific modeline) with Debian Buster (Wayland)?


 Thank you and best regards

 JM 

AW: PRoblems uninstalling nvidia

[01793666059]

What is alsways helping me was

apt-get --purge remove `nvidia-*`

or alternatively

aptitude purge ~nnvidia-*

(not a typo, it is ~nnvidia-*)

Hope this helps. Good luck!

Best Hans


Am Wed, 11 Sep 2019 22:44:50 -0400, Carlos Kosloff  
schrieb:


Hello list,

Running buster + backports.

Instaled nvidia from an alternate source an ran into problems because not 
packaged for Debian.

Probem is I cannot uninstall old version because dpkg halts:

Welcome to the NVIDIA Software Installer for Unix/Linux

Detected 8 CPUs online; setting concurrency level to 8.

If you plan to no longer use the NVIDIA driver, you should make sure that no X 
screens
are configured to use the NVIDIA X driver in your X configuration file. If you 
used
nvidia-xconfig to configure X, it may have created a backup of your original
configuration. Would you like to run `nvidia-xconfig --restore-original-backup` 
to
attempt restoration of the original X configuration file?
  [default: (N)o]: N

Progress: [  0%] 
[..] 

this does not even return the prompt.

After this I can no longer update system apt refuses to run dist-upgrade.

SO, how can I uninstall old version of nvidia?