Re: Bullseye: setting and using $DISPLAY after su -

[David Wright]

On Thu 31 Dec 2020 at 17:49:02 (-0700), Charles Curley wrote:
> On Thu, 31 Dec 2020 17:15:40 -0500 Greg Wooledge wrote:
> 
> > It's worth pointing out that even on buster, "su -" does in fact clear
> > the value of DISPLAY, which is not really a surprise, since you
> > explicitly requested a "clean" login session as the new user.
> > Perhaps you are mis-remembering what you used to do.  Perhaps you
> > used to use regular "su" without the infernal Red Hat "-" option.
> 
> I still have a small herd of buster boxen available, and 'su -' is
> exactly what I have been doing for at least a decade.

Same here, since the 1990s. In fact, I posted this dialogue on the
Corel mailing list in March 2000:

  ahost!auser 14:13 ~
  $ echo $DISPLAY
  :0.0 < the name of the display
  ahost!auser 14:13 ~
  $ xeyes -display :0.0< now I close the new window
  ahost!auser 14:13 ~
  $ /bin/su -
  Password:
  ahost ~# xeyes -display :0.0
  Xlib: connection to ":0.0" refused by server
  Xlib: Client is not authorized to connect to Server
  Error: Can't open display: :0.0
  ahost ~# ln -s ~auser/.Xauthority .Xauthority
  ahost ~# xeyes -display :0.0 < now I close the new window
  ahost ~# logout
  ahost!auser 14:14 ~
  $ 

> Also, if I want to run as root, I want access to all the rootty system
> administrator things like fdisk and fsck. Plain vanilla su leaves one
> with the unprivileged user's PATH.
> 
> > 
> > unicorn:~$ su
> > Password: 
> > root@unicorn:/home/greg# env | grep DISPLAY=
> > HOSTDISPLAY=unicorn:0
> > DISPLAY=:0
> > root@unicorn:/home/greg# exit
> > unicorn:~$ su -
> > Password: 
> > root@unicorn:~# env | grep DISPLAY=
> > root@unicorn:~# 
> 
> Also on buster:
> 
> charles@hawk:~$ su
> Password: 
> root@hawk:/home/charles# env | grep DISPLAY
> DISPLAY=:0.0
> root@hawk:/home/charles# exit
> exit
> charles@hawk:~$ su -
> Password: 
> 
> Today is Setting Orange, the 73rd of The Aftermath, 3186. All Hail Discordia! 
> root@hawk:~# env | grep DISPLAY
> DISPLAY=:0
> root@hawk:~# xclock &
> [1] 3550
> root@hawk:~# 
> 
> (xclock ran successfully.)
> 
> > 
> > Quite a difference, eh?  Almost certainly this is not a thing that
> > has changed during bullseye's run as testing.
> 
> Yup, quite a difference. But something has changed.

Well, for a start, the value of DISPLAY changes for you—that's never
happened to me (though I realise they both point to the same place).

Whitelisting with -w should do nothing for you—knowing the display's
location doesn't authorise you to use it.

The only suggestions I can come up with are:

Look at these files on buster (has PAM been modified?):

$ TZ=America/Phoenix ls --full-time /etc/pam.d/su*
-rw-r--r-- 1 root root 2257 2019-01-10 01:30:43.0 -0700 /etc/pam.d/su
-rw-r--r-- 1 root root  137 2019-01-10 01:30:43.0 -0700 /etc/pam.d/su-l
-rw-r--r-- 1 root root   95 2020-02-02 00:41:42.0 -0700 /etc/pam.d/sudo
$ apt-cache policy util-linux
util-linux:
  Installed: 2.33.1-0.1
  Candidate: 2.33.1-0.1
  Version table:
 *** 2.33.1-0.1 990
990 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
$ 

Is wayland involved? (I have no idea what you're able to do with
PAM, wayland, or with XFCE either.)

Cheers,
David.

Re: Label printer Debian compatible

[Russell L. Harris]

On Thu, Dec 31, 2020 at 04:12:25PM -0600, Tom Browder wrote:

Has anyone had any success driving a mailing label printer for mailing labels
from either a LAN or direct connection with a Linux box? 


I can print sheets of mailing labels from my main printer, but I would love to
be able to print single labels from my adress db with a suitable specialty
printer and a suitable Linux driver.


OKI Microline 320 Turbo via USB

CUPS ("raw" = no driver)

tractor-feed labels

RLH

Re: Bullseye: setting and using $DISPLAY after su -

[Mark Neyhart]

On 12/31/20 12:50 PM, Charles Curley wrote:
> I am using Bullseye as updated to yesterday. It is my custom to log in
> to XFCE as my regular user, then "su -" in order to run as root,
> including GUI programs. In the process, in the past $DISPLAY has been
> set.
> 
> I now find on bullseye that $DISPLAY is not being set. However, even if
> I set DISPLAY manually or run 'su -w DISPLAY -', programs like xclock
> complain that they cannot open the display.
> 
> How do I allow root to use the display?
> 

Before the su try

xhost SI:localuser:root

or just

xhost +

You will still have to set $DISPLAY manually

Re: Bullseye: setting and using $DISPLAY after su -

[Charles Curley]

On Thu, 31 Dec 2020 23:02:18 +0100
 wrote:

> > 
> > How do I allow root to use the display?  
> 
> Most probably you have to copy  the user's [1] ~/.Xauthority file to
> root's home.

No go. But thanks for the thought.

I also tried moving .Xauthority aside, logging out of the regular
account, logging in as root (which would create a new one), logging
out, and logging back in again. No go.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


pgpKet6lt6svw.pgp
Description: OpenPGP digital signature

Re: Bullseye: setting and using $DISPLAY after su -

[Charles Curley]

On Thu, 31 Dec 2020 17:15:40 -0500
Greg Wooledge  wrote:

> It's worth pointing out that even on buster, "su -" does in fact clear
> the value of DISPLAY, which is not really a surprise, since you
> explicitly requested a "clean" login session as the new user.
> Perhaps you are mis-remembering what you used to do.  Perhaps you
> used to use regular "su" without the infernal Red Hat "-" option.

I still have a small herd of buster boxen available, and 'su -' is
exactly what I have been doing for at least a decade.

Also, if I want to run as root, I want access to all the rootty system
administrator things like fdisk and fsck. Plain vanilla su leaves one
with the unprivileged user's PATH.

> 
> unicorn:~$ su
> Password: 
> root@unicorn:/home/greg# env | grep DISPLAY=
> HOSTDISPLAY=unicorn:0
> DISPLAY=:0
> root@unicorn:/home/greg# exit
> unicorn:~$ su -
> Password: 
> root@unicorn:~# env | grep DISPLAY=
> root@unicorn:~# 

Also on buster:

charles@hawk:~$ su
Password: 
root@hawk:/home/charles# env | grep DISPLAY
DISPLAY=:0.0
root@hawk:/home/charles# exit
exit
charles@hawk:~$ su -
Password: 

Today is Setting Orange, the 73rd of The Aftermath, 3186. All Hail Discordia! 
root@hawk:~# env | grep DISPLAY
DISPLAY=:0
root@hawk:~# xclock &
[1] 3550
root@hawk:~# 

(xclock ran successfully.)

> 
> Quite a difference, eh?  Almost certainly this is not a thing that
> has changed during bullseye's run as testing.

Yup, quite a difference. But something has changed.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Unresolved mime type.............

[Charlie]

Thoughts from my Keyboard:

Hello Debian viwers,

Using Debian Bullseye 5.9.0-4-amd64 Dell Inspiron 15 3000
laptop, updated and upgraded this morning with geoclue-2.0 on
hold

Have received this whenever gwenview was brought up:

$ gwenview
org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type
"image/x-nikon-nrw"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type
"image/x-samsung-srw"

Gwenview does open the image so it is nothing really important, just
curious if someone has any information regarding this and would like to
share.

Be well,
Charlie

East Gippsland Wildlife Rehabilitators Inc..
http://www.egwildlife.com.au/

-- 
Registered Linux User:- 329524

***

A rational person can find peace by cultivating indifference to
things outside of their control. ---Naval Ravikant

***
Debian GNU/Linux - Magic indeed.

-

Re: Label printer Debian compatible

[Jeremy Ardley]

On 1/1/21 6:12 am, Tom Browder wrote:
Has anyone had any success driving a mailing label printer for mailing 
labels from either a LAN or direct connection with a Linux box?


I can print sheets of mailing labels from my main printer, but I would 
love to be able to print single labels from my adress db with a 
suitable specialty printer and a suitable Linux driver.


Thanks, and Happy New Year to all!

-Tom



I have a label printer running under cups on my Debian linux system. I 
wrote the driver myself and added the CUPS definitions so it could be 
shared to other systems across the LAN. In particular it can be accessed 
by windows machines.


The CUPS system allows two modes. Either using the host driver, where 
the printer is effectively a postscript device that uses the driver to 
do the final render, or it operates in pass-through mode where a remote 
driver - say on a windows machine - generates the device commands and 
image data and these are transparently sent to the printer un-modified 
by CUPS.


I wrote the driver because my particular printer has a different command 
set to most. In the real world, many label printers use the Zebra 
command set and CUPS has that built in, so it's simply a matter of 
configuration.


My printer is in the GPrinter family which shares its command set with a 
number of other brands



--
Jeremy


OpenPGP_signature
Description: OpenPGP digital signature

Re: Bullseye: setting and using $DISPLAY after su -

[Greg Wooledge]

On Thu, Dec 31, 2020 at 11:02:18PM +0100, to...@tuxteam.de wrote:
> On Thu, Dec 31, 2020 at 02:50:18PM -0700, Charles Curley wrote:
> > I am using Bullseye as updated to yesterday. It is my custom to log in
> > to XFCE as my regular user, then "su -" in order to run as root,
> > including GUI programs. In the process, in the past $DISPLAY has been
> > set.
> > 
> > I now find on bullseye that $DISPLAY is not being set.

It's worth pointing out that even on buster, "su -" does in fact clear
the value of DISPLAY, which is not really a surprise, since you explicitly
requested a "clean" login session as the new user.  Perhaps you are
mis-remembering what you used to do.  Perhaps you used to use regular
"su" without the infernal Red Hat "-" option.

unicorn:~$ su
Password: 
root@unicorn:/home/greg# env | grep DISPLAY=
HOSTDISPLAY=unicorn:0
DISPLAY=:0
root@unicorn:/home/greg# exit
unicorn:~$ su -
Password: 
root@unicorn:~# env | grep DISPLAY=
root@unicorn:~# 

Quite a difference, eh?  Almost certainly this is not a thing that
has changed during bullseye's run as testing.

> > I set DISPLAY manually or run 'su -w DISPLAY -', programs like xclock
> > complain that they cannot open the display.
> > 
> > How do I allow root to use the display?
> 
> Most probably you have to copy  the user's [1] ~/.Xauthority file to
> root's home.

More typically, since root can usually read the user's files,[2] all
that's needed is to export the XAUTHORITY variable with the full pathname
of the user's .Xauthority file.

[2] Unless of course the user's home directory is on a network file system.

Label printer Debian compatible

[Tom Browder]

Has anyone had any success driving a mailing label printer for mailing
labels from either a LAN or direct connection with a Linux box?

I can print sheets of mailing labels from my main printer, but I would love
to be able to print single labels from my adress db with a suitable
specialty printer and a suitable Linux driver.

Thanks, and Happy New Year to all!

-Tom

Re: Bullseye: setting and using $DISPLAY after su -

[tomas]

On Thu, Dec 31, 2020 at 02:50:18PM -0700, Charles Curley wrote:
> I am using Bullseye as updated to yesterday. It is my custom to log in
> to XFCE as my regular user, then "su -" in order to run as root,
> including GUI programs. In the process, in the past $DISPLAY has been
> set.
> 
> I now find on bullseye that $DISPLAY is not being set. However, even if
> I set DISPLAY manually or run 'su -w DISPLAY -', programs like xclock
> complain that they cannot open the display.
> 
> How do I allow root to use the display?

Most probably you have to copy  the user's [1] ~/.Xauthority file to
root's home.

Cheers

[1] on behalf of which the X server runs.

> Does anybody read signatures any more?

Yes, I do :)
 - t


signature.asc
Description: Digital signature

Bullseye: setting and using $DISPLAY after su -

[Charles Curley]

I am using Bullseye as updated to yesterday. It is my custom to log in
to XFCE as my regular user, then "su -" in order to run as root,
including GUI programs. In the process, in the past $DISPLAY has been
set.

I now find on bullseye that $DISPLAY is not being set. However, even if
I set DISPLAY manually or run 'su -w DISPLAY -', programs like xclock
complain that they cannot open the display.

How do I allow root to use the display?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Webcam resolution in VLC (and elsewhere)

[Eugen Dedu]

Hi Celejar,

To find out the capabilities of your camera, you can install v4l-utils 
and execute:

v4l2-ctl --list-devices
v4l2-ctl -d /dev/video0 --list-formats
v4l2-ctl -d /dev/video0 --list-formats-ext
Check also the other /dev/video* files.

Another method is to use qv4l2 (provided by the homonym package), which 
is very user-friendly and I think it uses v4l2-ctl to find information.


The above information comes from 
https://wiki.archlinux.org/index.php/webcam_setup.


Cheese and vlc must not be used to find out available resolutions.  On 
my Dell built-in webcam both show 640x480 and below, whereas my camera 
supports 1280x720, as given by the laptop specification and 
v4l2-ctl/qv4l2.  As about why do these applications use this resolution, 
I do not have any idea.


Best regards.

Re: Totally on topic

[Peter Ehlert]

On 12/31/20 11:33 AM, mick crane wrote:
Happy New Year to all concerned and thanks for the handy tips and 
information on Debian users in 2020


mick

and my Best to you Sir

Totally on topic

[mick crane]

Happy New Year to all concerned and thanks for the handy tips and 
information on Debian users in 2020


mick
--
Key ID4BFEBB31

Re: Webcam resolution in VLC (and elsewhere)

[Gene Heskett]

On Thursday 31 December 2020 10:59:36 Celejar wrote:

> On Wed, 30 Dec 2020 10:53:37 -0800 (PST)
>
> didier gaumet  wrote:
> > Le mercredi 30 décembre 2020 à 16:40:06 UTC+1, Celejar a écrit :
> > [...]
> >
> > > 1) Why does VLC default to the lower resolution? Incidentally, I
> > > see that Cheese also opens the camera by default at a lower
> > > resolution - but a different one: 960x540. Why? Is this to save
> > > space when recording?
> >
> > I don't know: one possibility is that either Linux or VLC/Cheese
> > incorrectly detects the webcam resolution? Another possibility could
> > be
>
> The manufacturer claims that it's 720p HD:
>
> https://www.lenovo.com/us/en/laptops/thinkpad/w-series/w550s/
>
> > a marketing trick: an higher resolution is claimed through
> > interpolation  while actual optical resolution is lower.
>
> I don't know how to evaluate this. But still, if the camera is
> reporting 720p, shouldn't the applications default to that? Do they
> somehow figure out that the 720p mode is cheating and therefore ignore
> it by default?
>
> > > 2) VLC's GUI doesn't seem to offer any way to set the resolution.
> > > I see all kind of references on the internet to knobs to turn to
> > > set resolution, but none of them seem available in my VLC when
> > > using a v4l2 camera. Why?
> >
> > I use VLC from Buster. the following is the rough english
> > translation of my VLC that is in french.
> >
> > - To set up the resolution of the webcam for a session and begin the
> > session:  Media>Open a capture device, then set up the capture mode
> > to video camera, click on advanced options button and fill the width
> > and height fields. - To set up the default resolution of the webcam:
> > Tools>Preferences, then click on display parameters: all, then
> > input/codecs>access modules>v4l, fill the width and height fields
>
> You're right, I was mistaken. The Advanced option do contain height
> and width fields (parelleling the height and width CLI parameters I
> mentioned).
>
> But I still think it's ridiculous that a) VLC doesn't provide a list
> of supported resolutions to choose from, instead making the user
> figure these out using other tools, and then enter the values manually
> and b) hides these fields under the Advanced options, which, as I
> noted, the documentation describes as "useful in some rare cases"
>
> Celejar


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Webcam resolution in VLC (and elsewhere)

[Michael Stone]

On Thu, Dec 31, 2020 at 10:59:36AM -0500, Celejar wrote:

I don't know how to evaluate this. But still, if the camera is
reporting 720p, shouldn't the applications default to that?


The optical quality on most small web cams is so bad that increasing the 
resolution just means significantly more bandwidth is used to produce a 
picture that's visually indistinguishable from the lower resolution 
version. Most video chat applications will downsample a high res image 
anyway, so generating a high res stream is just making more work. There 
are cameras and applications where the increased resolution matter, but 
they're the exception IME.

Re: Webcam resolution in VLC (and elsewhere)

[Celejar]

On Wed, 30 Dec 2020 10:53:37 -0800 (PST)
didier gaumet  wrote:

> Le mercredi 30 décembre 2020 à 16:40:06 UTC+1, Celejar a écrit :
> [...]
> > 1) Why does VLC default to the lower resolution? Incidentally, I see 
> > that Cheese also opens the camera by default at a lower resolution - 
> > but a different one: 960x540. Why? Is this to save space when recording? 
> 
> I don't know: one possibility is that either Linux or VLC/Cheese
> incorrectly detects the webcam resolution? Another possibility could be

The manufacturer claims that it's 720p HD:

https://www.lenovo.com/us/en/laptops/thinkpad/w-series/w550s/

> a marketing trick: an higher resolution is claimed through
> interpolation  while actual optical resolution is lower.

I don't know how to evaluate this. But still, if the camera is
reporting 720p, shouldn't the applications default to that? Do they
somehow figure out that the 720p mode is cheating and therefore ignore
it by default?

> > 2) VLC's GUI doesn't seem to offer any way to set the resolution. 
> > I see all kind of references on the internet to knobs to turn to set 
> > resolution, but none of them seem available in my VLC when using a v4l2 
> > camera. Why? 
> 
> I use VLC from Buster. the following is the rough english translation of my 
> VLC that is in french.
> 
> - To set up the resolution of the webcam for a session and begin the session: 
>  Media>Open a capture device, then set up the capture mode to video camera, 
> click on advanced options button and fill the width and height fields.
> - To set up the default resolution of the webcam: Tools>Preferences, then 
> click on display parameters: all, then input/codecs>access modules>v4l, fill 
> the width and height fields

You're right, I was mistaken. The Advanced option do contain height and
width fields (parelleling the height and width CLI parameters I
mentioned).

But I still think it's ridiculous that a) VLC doesn't provide a list of
supported resolutions to choose from, instead making the user figure
these out using other tools, and then enter the values manually and b)
hides these fields under the Advanced options, which, as I noted, the
documentation describes as "useful in some rare cases"

Celejar

Re: Webcam resolution in VLC (and elsewhere)

[Celejar]

On Wed, 30 Dec 2020 11:02:31 -0800 (PST)
didier gaumet  wrote:

> Le mercredi 30 décembre 2020 à 16:40:06 UTC+1, Celejar a écrit :
> [...]
> > 1) Why does VLC default to the lower resolution? Incidentally, I see 
> > that Cheese also opens the camera by default at a lower resolution - 
> > but a different one: 960x540. Why? Is this to save space when recording? 
> 
> to set up the default video resolution of your webcam in Cheese, install 
> dconf editor, launch it and set up the the video-x-resolution and 
> video-y-resolution in /org/gnome/cheese/

Thanks. Once I set it once, the setting seems to survive restarts of
the program, and I'm currently only using Cheese for testing anyway ;)

Celejar

Re: mdadm usage

[Andy Smith]

Hello,

On Thu, Dec 31, 2020 at 06:18:29PM +0300, Reco wrote:
> On Thu, Dec 31, 2020 at 03:06:34PM +, Andy Smith wrote:
> > Datasheet says:
> > 
> > * Enhanced Power-Loss Data Protection with Tantal capacitors
> 
> It does not have a battery = it does not have a BBU.
> Samsung can dance around that fact all they want, but it won't change.

That is a really strange comment to me. No SSDs have batteries.
Almost no RAID cards have batteries anymore. Supercapacitors have
obsoleted the battery for such purposes. All SSD power loss
protection is supercaps. And if you try to buy a modern RAID card
with a BBU you will mostly just find cards with supercaps instead.
But OP was asking about SSDs not RAID cards so even that nuance
doesn't make much sense.

But okay, your SSD doesn't have pink elephants either. Samsung can
dance around that fact all they want.

Andy

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

Re: mdadm usage

[Reco]

On Thu, Dec 31, 2020 at 03:06:34PM +, Andy Smith wrote:
> On Thu, Dec 31, 2020 at 05:42:35PM +0300, Reco wrote:
> > It's a cheap model (relatively), and lack all those fancy BBU features,
> > but it works for my employer:
> > 
> > # smartctl -a /dev/sdj
> > ...
> > Vendor:   SAMSUNG
> > Product:  MZILT1T9HAJQ/007
> 
> Datasheet says:
> 
> * Enhanced Power-Loss Data Protection with Tantal capacitors

It does not have a battery = it does not have a BBU.
Samsung can dance around that fact all they want, but it won't change.

The lack of BBU does not bother me though (there are backups for
worst-case scenarios), and that server is on UPS anyway. Possible
firmware bugs (these things are new, this unit was produced about a year
ago), and, of course, the scourge of modern Enterprise SSDs -
temperature loss - these I'm wary of.

Reco

Minitube in the stable branch

[Davide Lombardo]

What is the point of packaging such software for the stable release ? 
Doesn't the package maintainer know the application stop working after 
some time because Google is constantly changing things on their side. I 
think would be a better policy doesn't packaging such software for the 
stable branch, at least the program doesn't get bad reviews from angry 
users who doesn't understand such thing.

Re: mdadm usage

[Andy Smith]

Hello,

On Thu, Dec 31, 2020 at 05:42:35PM +0300, Reco wrote:
> It's a cheap model (relatively), and lack all those fancy BBU features,
> but it works for my employer:
> 
> # smartctl -a /dev/sdj
> ...
> Vendor:   SAMSUNG
> Product:  MZILT1T9HAJQ/007

Datasheet says:

* Enhanced Power-Loss Data Protection with Tantal capacitors

https://www.hyperscalers.com/image/catalog/!Petar/PM1643%202.5%20SAS%20SSD%20Datasheet_v1.0_for%20General%20(002).pdf

Also corroborated at:


https://www.anandtech.com/show/12448/samsung-begins-mass-production-of-pm1643-sas-ssds-with-3072-tb-capacity

"Some of the features of the PM1643 that Samsung is willing to
discuss right now (metadata protection, power loss protection,
data recovery, end-to-end data protection, encryption, etc.)
confirm that the drives are indeed aimed at servers that require
advanced reliability."

Cheers,
Andy

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

Re: mdadm usage

[Reco]

Hi.

On Wed, Dec 30, 2020 at 11:14:37PM +0100, deloptes wrote:
> Can someone recommend server or NAS grade (SATA) SSD - a reliable one
> for RAID use?

It's a cheap model (relatively), and lack all those fancy BBU features,
but it works for my employer:

# smartctl -a /dev/sdj
...
Vendor:   SAMSUNG
Product:  MZILT1T9HAJQ/007
Revision: GXF2
Compliance:   SPC-5
User Capacity:1,920,383,410,176 bytes [1.92 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:Solid State Device
Form Factor:  2.5 inches
Transport protocol:   SAS (SPL-3)
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning:  Enabled
...


Note that it's a SAS drive, not SATA.

Reco

Re: mdadm usage

[Andy Smith]

Hello,

On Thu, Dec 31, 2020 at 09:17:03AM -0500, Michael Stone wrote:
> On Thu, Dec 31, 2020 at 07:25:54AM -0500, rhkra...@gmail.com wrote:
> >What do you mean by power loss protection -- do you mean, for example, that
> >the host computer is on a UPS, or is that a feature of some SSDs?
> 
> It's a feature of server SSDs. I wouldn't worry about it on a consumer
> device, especially if you have a UPS.

Though OP did ask about NAS-quality SSDs for RAID use.

Cheers,
Andy

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

Re: mdadm usage

[Michael Stone]

On Thu, Dec 31, 2020 at 07:25:54AM -0500, rhkra...@gmail.com wrote:

What do you mean by power loss protection -- do you mean, for example, that
the host computer is on a UPS, or is that a feature of some SSDs?


It's a feature of server SSDs. I wouldn't worry about it on a consumer 
device, especially if you have a UPS.

Re: Sound does not work on Debian 10

[Alexander V. Makartsev]

On 31.12.2020 18:06, Hassans Tech wrote:

In addition, the output of aplay -l
 Is: List of PLAYBACK Hardware Devices 
card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audi]

  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audi]

  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audi]

  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: bytchtes8316 [bytcht-es8316], device 0: Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: bytchtes8316 [bytcht-es8316], device 1: Deep-Buffer Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
haf@UNKNOWN:~$
It looks like sound card is detected, but enumerated in wrong order. Try 
to set card 1 as default [1] and see if that will solve your problem.

If not send output from commands below:
    $ aplay -L | grep -e ':CARD'
    $ lshw -c multimedia


[1] 
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#Set_the_default_sound_card


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: graphical session in LXC automatically started at boot and reachable via VNC/RDP/X2GO

[Linux-Fan]

Yvan Masson writes:

[...]

I glanced over /etc/vnc.conf and it seems communication can be easily  
secured with self-signed X509 certificate: this might be simpler to setup  
than SSH tunneling, especially with a Windows client. Has someone already  
tried that? Anyway, I will let you know.


I do not have any personal experience with the X509 certificates in the case  
of VNC. From my experience, TLS is more difficult to configure than SSH,  
mostly because of (1) the necessity for a PKI and (2) time-based certificate  
expiration by default. The other point is the more difficult process of  
generating all the necessary files (host certificate). The manpage for  
`vnc.conf` seems to indicate that this is automated for the VNC usage to  
some extent -- possibly worth trying :)


My cheatsheet for openssl commands to prepare all the necessary TLS keys  
(for stunnel, but VNC may be similar) is here:

https://masysma.lima-city.de/37/dashboards_with_docker.xhtml

At a glance, the `vnc.conf` manpage does not hint towards private-key-based  
client authentication, whereas SSH private key files serve this purpose.


The new SSH client on Windows is straight-forward to configure:  
Just store the id_rsa file and configure the Windows equivalent of "chmod  
600" for it. Afterwards, use command `ssh` (or optionally

%USERPROFILE%/.ssh/config) as you would on Linux.

HTH and YMMV
Linux-Fan

öö


pgp_WESvwwFNs.pgp
Description: PGP signature

Re: Sound does not work on Debian 10

[Hassans Tech]

In addition, the output of aplay -l
 Is: List of PLAYBACK Hardware Devices 
card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel
HDMI/DP LPE Audi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel
HDMI/DP LPE Audi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel
HDMI/DP LPE Audi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: bytchtes8316 [bytcht-es8316], device 0: Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: bytchtes8316 [bytcht-es8316], device 1: Deep-Buffer Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
haf@UNKNOWN:~$

Re: Problems with loadlin.exe

[shadowmaker]

El 2020-12-29 16:48, Andrew M.A. Cater escribió:
On Mon, Dec 28, 2020 at 09:19:58PM +, shadowma...@logorroici.org 
wrote:

El 2020-12-26 16:18, Andrew M.A. Cater escribió:
> On Sat, Dec 26, 2020 at 04:05:50PM +, shadowma...@logorroici.org
> wrote:
> > Hello everybody:
> > I am new to this forum, but not to GNU/Linux. I am in a Windows 10
> > Machine
> > with an AMD x64 architecture. I am unable to install from a distro
> > image
> > (firmware-10.7.0-amd64-netinst.iso) because loadlin.exe is not working
> > anymore in my OS. I want to dual boot the computer, but I am not
> > sure of how
> > to do it. I tried installing the OS from the USB. Everything was OK,
> > but the
> > system didn't boot... It was weird because I solved all the problems
> > that it
> > gave to me: a problem loading "uefi:db x.509 certificate (-65)" that
> > was
> > fixed by disabling Fast Boot and Secure Boot (it is impossible to
> > use Legacy
> > mode in new computers). There was a problem with IOMMU that was fixed
> > disabling it too. Now I want to try to install it from the Windows
> > system to
> > avoid the weird problems it gave because of GRUB (I had GRUB already
> > installed and it conflict somehow with the other installed by Debian).
> > Please, help me!!!
> > Thanks in advance ;)

> Reenable Secure Boot - Debian 10 should be able to boot with Secure Boot
> now.

I tried with it reenabled but it didn't work.

> How was Windows installed initially - if it was installed in UEFI mode
> and you are attempting to boot Debian in legacy mode, it will fail and
> vice versa.

The computer doesn't have a Legacy mode. All the OS are installed 
under the

UEFI

> What had you installed previously using Grub?

Nothing important. Windows.

> Are you booting from a USB stick?

I installed from a USB stick. Now the Debian is in my disk

> How did you write the Debian image to the USB stick?

I used Win32DiskImager

> Do you know what firmware your system is likely to need?

The PCI. I have a GPU so maybe that's why it doesn't load the desktop.

OK - So you now have a working Windows system and a part installed 
Debian.

I would suggest that you install the firmware-linux-nonfree and
firmware-misc-nonfree packages to get firmware onto the machine.


The first time I used an image without non-free firmware. It nothing 
worked and I had the same problem. With this version with firmware it 
gives no errors, but the OS doesn't begin (as I said the GRUB works and 
the rescue mode gives no errors. The only thing that keeps wrong is the 
pci, that shows unknown messages... I will try with the packages you've 
said an retry.


Other question... How do I write to the ext4 filesystem without a GNU 
system? I have some .deb packages I want to install (downloaded from the 
AMD webpage) and I don't know to mount it in the rescue-mode (I try with 
the `sudo mount /dev/sda1` but it was unable to mount it. I tried with 
`umount` too.



What GPU do you have?


It's an AMD Radeon Vega Graphics

In the install, are you sure that you selected a desktop. If you are 
not sure,
then, as root, execute the command tasksel and see which desktop is 
selected.


I think GNOME was correctly installed... I will check as you say.


All the very best,



Andy C


Thanks for your answer :)

Happy hacking!


> Getting a Windows system to dual boot Debian is (relatively)
> straightforward but knowing the answer to some of the above questions
> may help us narrow down useful suggestions as to what to try next.
> All the very best, as ever,
>
> Andy

Re: Sound does not work on Debian 10

[Hassans Tech]

Additional info that I forgot to add:
The output of lspci -knn
 Is: 00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280]
(rev
36)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:7270]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
Controller [808
6:22b0] (rev 36)
DeviceName:  Onboard IGD
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Multimedia controller [0480]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit
[8086:22b8] (rev 36
)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series Imaging Unit [8086:7270]
Kernel driver in use: intel_atomisp2_pm
Kernel modules: intel_atomisp2_pm
00:0b.0 Signal processing controller [1180]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management
Controll
er [8086:22dc] (rev 36)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:7270]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev
36
)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:7270]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:1a.0 Encryption controller [1080]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted
Execution Engine [8086:2
298] (rev 36)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:7270]
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 36)
Subsystem: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCU [8086:7270]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
again, thanks for your time.

Re: mdadm usage

[rhkramer]

On Wednesday, December 30, 2020 06:20:09 PM Andy Smith wrote:
> On Wed, Dec 30, 2020 at 11:14:37PM +0100, deloptes wrote:
> > Can someone recommend server or NAS grade (SATA) SSD - a reliable one for
> > RAID use?

...

> Then make sure it has power loss protection.

What do you mean by power loss protection -- do you mean, for example, that 
the host computer is on a UPS, or is that a feature of some SSDs?

Sound does not work on Debian 10

[Hassans Tech]

Hi, so I have successfully installed Debian 10 (testing) and I am
experiencing audio issues.
The output of lspci is as follows:
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 36)
00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 36)
00:0b.0 Signal processing controller: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management
Controller (rev
 36)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCU (rev 36)

And the output of  pacmd list-sinks
 Is as follows:
1 sink(s) available.
  * index: 0
name: 
driver: 
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause: (none)
priority: 1000
volume: front-left: 32768 /  50% / -18.06 dB,   front-right: 32768
/  50% / -18.06 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 2.28 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 2
linked by: 2
configured latency: 2.49 ms; range is 0.50 .. 2000.00 ms
module: 13
properties:
device.description = "Dummy Output"
device.class = "abstract"
device.icon_name = "audio-card"

The output of amixer is:
 Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 65536
  Mono:
  Front Left: Playback 32768 [50%] [on]
  Front Right: Playback 32768 [50%] [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch cswitch-joined
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 65536
  Front Left: Capture 65536 [100%] [on]
  Front Right: Capture 65536 [100%] [on]

Additional information,
The version was installed through the non-free image and it is using KDE.
Thank you for your time.

Re: graphical session in LXC automatically started at boot and reachable via VNC/RDP/X2GO

[Yvan Masson]

Le 30/12/2020 à 23:46, Linux-Fan a écrit :

Yvan Masson writes:

[...]

What I did not understand from your answers (sorry maybe I missed 
something) is how to start the graphical session automatically when 
the container starts, so that the software can be started and 
listening on the network, and then later someone can attach to this 
session with VNC/RDP/X2GO. It seems your script Linux-Fan starts a VNC 
server, but does it start a session in it?


I did not mention it explicitly, because with the VNC server I am using 
(`tightvncserver`) does this automatically.


The trick most important steps are as follows:

* Prepare a configuration for the session of interest to start, I have 
these

   lines in my "Dockerfile" (i.e. image preparation stage):

 echo \$vncStartup = \"exec /usr/bin/icewm\" > $HOME/.vncrc; \
 [...]
 printf "%s\n\n%s\n" "#!/bin/sh -e" "/usr/bin/megasync &" \
     > /etc/X11/icewm/startup; \

   This way, it configures `icewm` to be the window manager to use and
   uses IceWM's autorun facility to start my program of interest 
(`megasync`).


* In the container's startup script, run the VNC server.

 /usr/bin/vncserver -geometry 1024x768 :0

   This will start `icewm` (as configured in `.vncrc`) which (by 
configuration

   in `/etc/X11/icewm/startup`) runs `megasync`.

   See also: vncserver(1) --
   
https://manpages.debian.org/buster/tightvncserver/tightvncserver.1.en.html


* To automatically start the container upon OS boot, I use Docker's
   `--restart=unless-stopped`. This will be different for LXC of course!

* For the gory details of setting passwords, making the right files
   executable or resuming from "crashed" sesions (i.e. delete temp files)
   check the respective source codes:

   https://github.com/m7a/lo-megasync/blob/master/megasync_ctrl.sh
   https://github.com/m7a/lo-megasync/blob/master/Dockerfile

Thanks for the detailed explanations, this looks perfect! The command 
`vncserver` was exactly what I could not find with xrdp and x2go. 
Unfortunately I do not have time to test this solution today.


I glanced over /etc/vnc.conf and it seems communication can be easily 
secured with self-signed X509 certificate: this might be simpler to 
setup than SSH tunneling, especially with a Windows client. Has someone 
already tried that? Anyway, I will let you know.


Regards,
Yvan