Sounds

[Gunnar Gervin]

Hi gals & guys,
sounds are back!

Gunnar

Re: If the variable has its 'integer' attribute set,

[Greg Wooledge]

On Sun, Nov 21, 2021 at 01:37:14AM +, sim sim wrote:
> I do not understand  "If the variable has its 'integer' attribute set," where 
> the variable has an 'integer' attribute, after all, this is not a function?

They're talking about "declare -i".  Which is really a stupid thing
and I wish it didn't exist, but it does, and people are silly enough
to use it, and I cannot stop them.

For those who don't understand the context of the question, this is
about bash, and variables in bash.

All variables in bash hold string values.  Even if you use "declare -i",
the value that is stored in memory is a string.  What "declare -i" does
is make it so that when you assign new strings to the variable, dark
magic occurs.  The value that gets assigned will be interpreted by the
shell's math context parser, and the result will be a value that looks
like a number, or else an error.

unicorn:~$ bash
unicorn:~$ declare -i foo
unicorn:~$ foo=bar
unicorn:~$ declare -p foo
declare -i foo="0"

So... what happened here?  We tried to assign the string "bar" to a
variable with the "-i" flag set.  Since bar doesn't look like a number,
it was sent into the math context parser.  The math context parser saw
that "bar" looks like a variable name, so it recursively evaluated "bar"
in a math context, retrieve the value from the variable "bar".  Which
did not exist.  So that value was assigned as "0".  Which is a string that
looks like a number.  Because, as I said, all bash variables hold strings.

unicorn:~$ bar='hello world'
unicorn:~$ foo=bar
bash: hello world: syntax error in expression (error token is "world")

Here, we got an error, because "hello world" could not be evaluated by
the shell's math parser.

unicorn:~$ bar=7*9
unicorn:~$ foo=bar
unicorn:~$ declare -p foo bar
declare -i foo="63"
declare -- bar="7*9"

Here, bar which is an ordinary value holds the string value "7*9", which
happens to be a valid expression in the eyes of the shell's math parser.
When we assigned "bar" to "foo", which has the "-i" flag set, the string
value was fed to the math parser, and "7" and "9" were temporarily
turned into integers, and a multiplication was performed, and then the
resulting number 63 was turned back into a string, and the string "63"
was stored in "foo".

Why people think this is a good idea is utterly beyond me.  I can only
advise you never to use this thing.  It's confusing and dumb.  If you want
to perform arithmetic while assigning a value to a variable, I advise
you to use an *explicit* arithmetic expression:

foo=$(( math stuff here ))

That way you can see what's happening when you read the script, and there
won't be as many surprises.

Bash is full of enough landmines without introducing more.

Volume control disabled?

[Gunnar Gervin]

Hi.
Volume is gone in Bullseye version, too.

In Multimedia > Pulse Audio Volume control :
Speaker has red cross on the speaker in System Volume & Firefox Volume
control.
As a recall it has not been the case before.
I ask you please instruct how remove the 2 red crosses. Using Terminal
commands or whatever I need to do.
(If not I must reinstall to Bionicpup Linux, ugly & w/sound, but extremely
slow.
A script slowed down Youtube, and if I turned it off Youtube did not work.
Hacking or malware, maybe? I doubt Youtube would throw out a potential
customer.)
I will try remove and reinstall Pulse Audio Volume control.
Gunnar

If the variable has its 'integer' attribute set,

[sim sim]

Hi, all.
My question may be in the wrong place but I'm already exhausted. Started 
reading https://www.gnu.org/software/bash/manual/bash.pdf.

3.4 Shell Parameters
.

A parameter is set if it has been assigned a value.  The null string is a valid 
value.  Once a variable is set, it may be unset only by using the 'unset' 
builtin command.
   A variable may be assigned to by a statement of the form
 NAME=[VALUE]
If VALUE is not given, the variable is assigned the null string.  All VALUEs 
undergo tilde expansion, parameter and variable expansion, command 
substitution, arithmetic expansion, and quote removal (detailed below).  If the 
variable has its 'integer' attribute set, then VALUE is evaluated as an 
arithmetic expression even if the '$((...))' expansion is not used.  
.
..
I do not understand  "If the variable has its 'integer' attribute set," where 
the variable has an 'integer' attribute, after all, this is not a function?
I do not ask to explain in detail, because it is long and I will not understand 
because of my poor English, but if you can just write a simple variable for:
 name=[value] 
where "If the variable has its 'integer' attribute set",
for example it will help a lot. This manual is difficult for a beginner to 
read. The same concept in different places denotes: either an attribute or a 
parameter or an option.
And advise a smart forum on this topic, where you can ask questions, Google 
found trash.
Thanks,
Sim. 

Re: How to rotate screen AND input (consistently)

[riveravaldez]

On 11/20/21, Dan Ritter  wrote:
> riveravaldez wrote:
>> Hi,
>>
>> I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
>> and I need to rotate the display (both physically and GUI)
>> which I do with:
>>
>> $ xrandr --output LVDS-1 --rotate inverted
>>
>> But then the input (trackpad/mouse, stylus, touchscreen, etc.)
>> doesn't rotate accordingly, so it gets unusable...
>
> Right, because for most cases, rotating a monitor doesn't mean
> picking up your mouse and rotating it, too.
>
> If you've got an external mouse, you'll see that works just
> fine, but that defeats the point of a tablet.

Absolutely right. Thanks a lot for the information.

>> I've been reading different recommendations online
>> but can't figure out which would be the best/proper/simpler
>> approach to achieve this reliably (that hardware input
>> stays consistent with the GUI in display when rotated).
>>
>> What should I do? Any hint?
>
> I haven't done this, but I believe xinput is going to be your
> friend. It can list devices, list properties, and set whatever
> needs to be set.

Thanks, Dan, I'm going to check it.

> The older way of doing this is to get into the Mouse section of
> your xorg.conf.
>
> Wayland has its own ways, which perhaps someone else can
> explain.

Thanks a lot again.
Just to avoid any waste of help, there's nothing/no wayland package
in this box, pure X.

Regards!

Sounds disappeared

[Gunnar Gervin]

Hi again.
Upgraded to Bullseye in hope it will give me sound.
BR,
Gunnar G.
(PS.
Mal apropos:
System refused let me save replacements in sources.list:

deb https://deb.debian.org/debian-security/ bullseye-security main
deb-src https://deb.debian.org/debian-security/ bullseye-security main

So the text will probably say "bullseye-updates" instead of
"bullseye-security",
the rest of the text is the same (I think). Suppose it does not matter very
much.)

Re: Sound

[Andrew M.A. Cater]

On Sun, Nov 21, 2021 at 12:03:20AM +0200, Gunnar Gervin wrote:
> Hi again. Please help me get sound.
> Installed Debian again in my 2,1 Macbook from 2017, works, but no sound in
> internal speakers, or in headphones.
> Plugged in external speakers, which worked, but then disappeared.
> Pulse audio program is installed, but does not give response in the form of
> sound..
> BR,
> Gunnar G

Hi Gunnar,

OK. Not really enough information here to go on. 

1. What version of Debian

2. What does Lspci report for the chipset / audio

3. Do you have a desktop environment loaded? 

4. Shich one?

5. Does it have a settings app?

6. Does it work at all if you play, say, a YouTube video / has it ever worked?

If you can help us with information, we may be better able to help you.

All the very best, as ever,

Andy Cater

Sound

[Gunnar Gervin]

Hi again. Please help me get sound.
Installed Debian again in my 2,1 Macbook from 2017, works, but no sound in
internal speakers, or in headphones.
Plugged in external speakers, which worked, but then disappeared.
Pulse audio program is installed, but does not give response in the form of
sound..
BR,
Gunnar G

Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

[Greg Wooledge]

On Sat, Nov 20, 2021 at 09:46:24PM +0100, Arkadiusz Dabrowski wrote:
> Unfortunately, the solution with .xsession file doesn't work.
> I resorted to something very simplistic:
> 
> 
> exec /usr/bin/marco
> 
> 
> Note: I use mate desktop with marco wm.

I doubt very much that this is the correct command for starting MATE.
Unfortunately, I am not a MATE user, so I don't know what the correct
command *is*.  But this doesn't look like it'll be the one.

Have you considered using my suggestion?  Put these two lines in .xsession:

. /etc/X11/Xsession
pkill unison

Keep your .xsessionrc which starts the unison program.  (Or you could
move it here, later, but for now I'm simply trying to do the bare
minimum needed to achieve a working setup.)

> Started with "exec" according to Debian documentation:
> https://wiki.debian.org/Xsession

You're cargo-culting stuff with zero understanding.  That's not going
to help.

If you don't know how shell scripts work, if you don't know what the
"exec" command does... then this is going to be quite difficult for you.

Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

[Arkadiusz Dabrowski]

Unfortunately, the solution with .xsession file doesn't work.
I resorted to something very simplistic:


exec /usr/bin/marco


Note: I use mate desktop with marco wm.
Started with "exec" according to Debian documentation:
https://wiki.debian.org/Xsession
They also use some other stuff, I'm not sure if I need any of these lines:

xsetroot -solid grayxmodmap -e "keysym Super_L = Multi_key"xset s off;
xset dpms 0 1800 0exec fvwm


...and my session doesn't start at all - login popup disappears and nothing
else happens on the screen.
I see that marco is started and ssh-agent is the only process under it.
I have no idea why my .xsession file name appears in the command line where
ssh-agent is started but it looks suspicious. Another x-session is started?

root   17474  0.0  0.1 165776  9604 ?Sl   21:23   0:00  \_
lightdm --session-child 12 21
arek   17484  0.0  0.3 274164 27188 ?Ssl  21:23   0:00  \_
/usr/bin/marco
arek   17572  0.0  0.0   5964   468 ?Ss   21:23   0:00
 \_ /usr/bin/ssh-agent env TMPDIR=/tmp/0_arek /usr/bin/im-launch /bin/bash
/home/arek/.xsession


What could happen here?

Re: reportbug fail

[Lee]

On 11/20/21, Ulf Volmer  wrote:
>
> On 20.11.21 15:04, Lee wrote:
>> I wanted to create a bug report for meld but couldn't find any info on
>> how to other than "use reportbug" :(
>>
>> I've got a brand new install of debian 11 & reportbug dies:
>
>>  conn = self._connect_tls_proxy(hostname, conn)
>>File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
>> 500, in _connect_tls_proxy
  <.. snip ..>
> Sounds like a poxy issue for me. Do you have one defined?

Yup - that was it.
$ unset https_proxy
$ unset http_proxy

and reportbug works!

Thanks
Lee

Re: reportbug fail

[Thomas Schmitt]

Hi,

> I've got a brand new install of debian 11 & reportbug dies:

It is possible to report bugs via plain mail, as described in:
  https://www.debian.org/Bugs/Reporting
  "Sending the bug report via e-mail"

Quick tour:

Use your intended bug title as mail "Subject:".

In the mail body write Pseudo-Headers "Package:", "Version:", and maybe
"Severity:" like in the following template (which initially stems from
a working reportbug):
==

Package: [... package for which to report the bug ...]
Version: [... package version which you use ...]
Severity: [... minor / normal / important /serious ...]

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: [... what you have ...]
Architecture: [... e.g. amd64 ...]

Kernel: [... the version which you get from uname -a ...]
Locale: [... output of command locale, if related to the problem ...]
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

==

Have a nice day :)

Thomas

Re: Re : Plus d'accès port USB après mise en veille

[Thierry]

Non, il n'est pas installé


Le 20/11/2021 à 00:09, benoit a écrit :

Tu n'aurais pas installé  laptop-mode-tools ?

apt search laptop-mode-tools

laptop-mode-tools coupe entre autre (par défaut de configuration) 
l'alimentation des usb

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

Le vendredi 19 novembre 2021 à 14:24, thierry_j  a écrit :


Bonjour à tous

petit souci: après retour de mise en veille, les ports USB sont inactifs

et les matériel n'est pas reconnu. Je suppose qu'il faut regarder du

côté systemd ou udev, mais je ne pas suis expert sur le sujet.

Auriez-vous une idée?

Je suis (encore) sous Buster.

Merci

Re: aboutdebian.com

[Bob Weber]

On 11/19/21 22:38, A_Man_Without_Clue wrote:



On 11/20/21 12:07 AM, Peter Ehlert wrote:

On 11/19/21 6:52 AM, Nicholas Geovanis wrote:

On Fri, Nov 19, 2021, 1:05 AM Nate Bargmann mailto:n...@n0nb.us>> wrote:

 * On 2021 18 Nov 23:00 -0600, A_Man_Without_Clue wrote:
 > Does anyone remember the site existed in the past,
 aboutdebian.com?

 I can't say that I do.


I do remember it and it was a good resource at one time. My
recollection is that the relevant contents were moved to the Debian
wiki. But I can't support that.

I also remember it as being a topic of conversation...

 > I wonder if the contents are moved to somewhere else or they are not
 > available at all?

 It looks like the last time it was online with content was
 approximately
 29 Feb 2020:

 https://web.archive.org/web/20200229050405/http://www.aboutdebian.com/
 


something is odd, I see a post on thehttps://aboutdebian.com/  page
dated 2021-10-10


 I see that as of that date, the site had not been updated for Buster
 which by that time had been released nearly half a year earlier.

 After that the Web archive shows a blank page and captures from last
 month show nothing Debian related.

 - Nate

 --
 "The optimist proclaims that we live in the best of all
 possible worlds.  The pessimist fears this is true."
 Web:https://www.n0nb.us  
 Projects:https://github.com/N0NB  
 GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



Sad, it's long gone and the contents are virtually lost. It was very
tutorial resource so, I just miss. I have several page printed out on
the paper, I still use for basic tutorial.


Thanks everybody.


Its on internet archive at least back to about 2018 and before.

--


*...Bob*

Re: How to rotate screen AND input (consistently)

[Loïc Grenié]

Le sam. 20 nov. 2021 à 13:03, Dan Ritter  a écrit :

> riveravaldez wrote:
> > Hi,
> >
> > I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
> > and I need to rotate the display (both physically and GUI)
> > which I do with:
> >
> > $ xrandr --output LVDS-1 --rotate inverted
> >
> > But then the input (trackpad/mouse, stylus, touchscreen, etc.)
> > doesn't rotate accordingly, so it gets unusable...
>
> Right, because for most cases, rotating a monitor doesn't mean
> picking up your mouse and rotating it, too.
>
> If you've got an external mouse, you'll see that works just
> fine, but that defeats the point of a tablet.
>
> > I've been reading different recommendations online
> > but can't figure out which would be the best/proper/simpler
> > approach to achieve this reliably (that hardware input
> > stays consistent with the GUI in display when rotated).
> >
> > What should I do? Any hint?
>
> I haven't done this, but I believe xinput is going to be your
> friend. It can list devices, list properties, and set whatever
> needs to be set.


I do something like that. In my script the two corresponding
  lines are:

TOUCHPAD=`xinput --list --short | grep Synaptics | grep -i pointer | sed -e
's/.*id=//' -e 's/[^0-9].*//'`
xinput set-prop $TOUCHPAD 169 0 -1 0 1 0 0 0 0 1

169 is the "coordinate transformation matrix" for my touchpad.

Hope this helps,

 Loïc

Re: How to rotate screen AND input (consistently)

[David Wright]

On Sat 20 Nov 2021 at 06:46:45 (-0500), Dan Ritter wrote:
> riveravaldez wrote: 
> > 
> > I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
> > and I need to rotate the display (both physically and GUI)
> > which I do with:
> > 
> > $ xrandr --output LVDS-1 --rotate inverted
> > 
> > But then the input (trackpad/mouse, stylus, touchscreen, etc.)
> > doesn't rotate accordingly, so it gets unusable...
> 
> Right, because for most cases, rotating a monitor doesn't mean
> picking up your mouse and rotating it, too.
> 
> If you've got an external mouse, you'll see that works just
> fine, but that defeats the point of a tablet.
> 
> > I've been reading different recommendations online
> > but can't figure out which would be the best/proper/simpler
> > approach to achieve this reliably (that hardware input
> > stays consistent with the GUI in display when rotated).
> > 
> > What should I do? Any hint?
> 
> I haven't done this, but I believe xinput is going to be your
> friend. It can list devices, list properties, and set whatever
> needs to be set.
> 
> The older way of doing this is to get into the Mouse section of 
> your xorg.conf.
> 
> Wayland has its own ways, which perhaps someone else can
> explain.

Indeed, I do this with xinput in X. My function is called
synaps for historical reasons. The xinput is extracted from
my bin/xinput-xsession, which itself is called from .xsession
because keeping it separate allows you to call it at any time,
nut just when X starts.

Anyway, they're both attached, lightly anonymised, The
reference to viewports may only make sense if you use fvwm.

Cheers,
David.
function synaps {
[ "$1" = "-?" ] && printf '%s\n' "Usage:${FUNCNAME[0]} [ l | r | u | i 
| m ]
rotates the screen left, right, or upside down, or inverted or
mirrored, and takes account of the touchpad and touchpoint.
Normality is restored with no argument (or anything else).
The only remaining confusion is that the viewports keys don't 
correspond." >&2 && return 1
local Matrix="X 0 0 0 X 0 0 0 1"
case "$1" in
l)
xrandr -o 1
Matrix="0 -X 0 X 0 0 0 0 1"
;;
r)
xrandr -o 3
Matrix="0 X 0 -X 0 0 0 0 1"
;;
u)
xrandr -o 2
Matrix="-X 0 0 0 -X 0 0 0 1"
;;
i)
xrandr -y --q1
Matrix="-X 0 0 0 -X 0 0 0 1"
;;
m)
xrandr -x --q1
Matrix="-X 0 0 0 -X 0 0 0 1"
;;
*)
xrandr -o 0
;;
esac
xinput --set-prop "AlpsPS/2 ALPS DualPoint TouchPad" "Coordinate 
Transformation Matrix" ${Matrix//X/.8} 2>/dev/null # west
xinput --set-prop "DualPoint Stick" "Coordinate Transformation Matrix" 
${Matrix//X/.2} 2>/dev/null # west
xinput --set-prop "SynPS/2 Synaptics TouchPad" "Coordinate Transformation 
Matrix" ${Matrix//X/.4} 2>/dev/null # wren
xinput --set-prop "Logitech M325" "Coordinate Transformation Matrix" 
${Matrix//X/.3} 2>/dev/null
xinput --set-prop "Logitech M310" "Coordinate Transformation Matrix" 
${Matrix//X/.3} 2>/dev/null
xinput --set-prop "Logitech M510" "Coordinate Transformation Matrix" 
${Matrix//X/.3} 2>/dev/null
xinput --set-prop "USB Wheel Mouse" "Coordinate Transformation Matrix" 
${Matrix//X/.4} 2>/dev/null
}
#!/bin/bash
#
# ~/bin/xinput-xsession last edited 2021-10-11
# Normally called from .xsession but is made available separately so that it can
# be called easily after, say, the mouse/keyboard dongle is removed and 
reinserted.

[ -n "$1" ] && set -x

Unique="$(mktemp --suffix .list ${Uniquetrash:-/tmp}/xinput-"$(date +%s)"-)"
xinput | tee "$Unique"

# Pointers tend to be too sensitive.
# Leave the last number as 1: the other numbers are ratio'd with it.
# My M325 mouse wheel is unreliable and unsafe for button 2, so use buttons 1&3.
# Set the same for most other mice, because my fingers are wired for it.

Matrix="X 0 0 0 X 0 0 0 1"

Devicetype="pointer"

Device="Logitech M325" # purple wireless
Id="$(grep "$Device[[:space:]]*id.*$Devicetype" "$Unique" | sed 
's/^[^=]\+=//;s/\t.*//;')"
[ -n "$Id" ] && printf '\nXID %2s %s ' "$Id" "$Devicetype" && xinput 
--list-props "$Id" && xinput --set-prop "$Id" "Coordinate Transformation 
Matrix" ${Matrix//X/.3} && xinput --set-prop "$Id" "libinput Middle Emulation 
Enabled" 1

Device="Logitech M310" # not sure, might be a mistake
Id="$(grep "$Device[[:space:]]*id.*$Devicetype" "$Unique" | sed 
's/^[^=]\+=//;s/\t.*//;')"
[ -n "$Id" ] && printf '\nXID %2s %s ' "$Id" "$Devicetype" && xinput 
--list-props "$Id" && xinput --set-prop "$Id" "Coordinate Transformation 
Matrix" ${Matrix//X/.3} && xinput --set-prop "$Id" "libinput Middle Emulation 
Enabled" 1

Device="Logitech M510" # Xyz's and its evil twin
Id="$(grep "$Device[[:space:]]*id.*$Devicetype" "$Unique" | sed 
's/^[^=]\+=//;s/\t.*//;')"
[ -n "$Id" ] && printf '\nXID %2s %s ' "$Id" "$Devicetype" 

Re: reportbug fail

[Ulf Volmer]

On 20.11.21 15:04, Lee wrote:

I wanted to create a bug report for meld but couldn't find any info on
how to other than "use reportbug" :(

I've got a brand new install of debian 11 & reportbug dies:



 conn = self._connect_tls_proxy(hostname, conn)
   File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
500, in _connect_tls_proxy
 return ssl_wrap_socket(
   File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line
453, in ssl_wrap_socket
 ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls)
   File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line
495, in _ssl_wrap_socket_impl
 return ssl_context.wrap_socket(sock)
   File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
 return self.sslsocket_class._create(
   File "/usr/lib/python3.9/ssl.py", line 997, in _create
 raise ValueError("check_hostname requires server_hostname")
ValueError: check_hostname requires server_hostname



Sounds like a poxy issue for me. Do you have one defined?

Best regards
Ulf

reportbug fail

[Lee]

I wanted to create a bug report for meld but couldn't find any info on
how to other than "use reportbug" :(

I've got a brand new install of debian 11 & reportbug dies:
  ...
Default preferences file written.  To reconfigure, re-run reportbug
with the "--configure" option.
Please enter the name of the package in which you have found a
problem, or type 'other' to report a more general
problem. If you don't know what package the bug is in, please contact
debian-user@lists.debian.org for assistance.
> meld
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address
of the submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Lee ' as your from address.
Getting status for meld...
Checking for newer versions at madison...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2381, in 
main()
  File "/usr/bin/reportbug", line 1120, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1697, in user_interface
(avail, toonew) = checkversions.check_available(
  File "/usr/lib/python3/dist-packages/reportbug/checkversions.py",
line 294, in check_available
stuff = get_versions_available(package, timeout, dists, http_proxy, arch)
  File "/usr/lib/python3/dist-packages/reportbug/checkversions.py",
line 135, in get_versions_available
page = open_url(url, http_proxy, timeout)
  File "/usr/lib/python3/dist-packages/reportbug/urlutils.py", line
183, in open_url
page = urlopen(url, proxies, timeout)
  File "/usr/lib/python3/dist-packages/reportbug/urlutils.py", line
127, in urlopen
return requests.get(url, headers=headers, proxies=proxies,
timeout=timeout).text
  File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line
542, in request
resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py",
line 696, in urlopen
self._prepare_proxy(conn)
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py",
line 966, in _prepare_proxy
conn.connect()
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
359, in connect
conn = self._connect_tls_proxy(hostname, conn)
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
500, in _connect_tls_proxy
return ssl_wrap_socket(
  File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line
453, in ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls)
  File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line
495, in _ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock)
  File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
return self.sslsocket_class._create(
  File "/usr/lib/python3.9/ssl.py", line 997, in _create
raise ValueError("check_hostname requires server_hostname")
ValueError: check_hostname requires server_hostname

Re: How to rotate screen AND input (consistently)

[Dan Ritter]

riveravaldez wrote: 
> Hi,
> 
> I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
> and I need to rotate the display (both physically and GUI)
> which I do with:
> 
> $ xrandr --output LVDS-1 --rotate inverted
> 
> But then the input (trackpad/mouse, stylus, touchscreen, etc.)
> doesn't rotate accordingly, so it gets unusable...

Right, because for most cases, rotating a monitor doesn't mean
picking up your mouse and rotating it, too.

If you've got an external mouse, you'll see that works just
fine, but that defeats the point of a tablet.

> I've been reading different recommendations online
> but can't figure out which would be the best/proper/simpler
> approach to achieve this reliably (that hardware input
> stays consistent with the GUI in display when rotated).
> 
> What should I do? Any hint?

I haven't done this, but I believe xinput is going to be your
friend. It can list devices, list properties, and set whatever
needs to be set.

The older way of doing this is to get into the Mouse section of 
your xorg.conf.

Wayland has its own ways, which perhaps someone else can
explain.


-dsr-

Re: (ssh-1 ongefixst maar probleem anders opgelost) Re: Debian 11, openssh server, ssh-1 toegang voor 1 client, hoe?

[Richard Lucassen]

On Thu, 18 Nov 2021 15:33:46 +0100
Gijs Hillenius  wrote:

> Wellicht wijst iemand me binnenkort terecht terecht dat ik niet moet
> peuteren aan de veiligheidsknoppen van SSH.
> 
> Ik heb mijn onderliggende probleem (met een legacy Android app)
> inmiddels op een andere manier opgelost.

Het blijft ook een eeuwig probleem. Net zoals browsers die niet meer
willen connecten met bijv een oudere versie ILO van een HP server. Oude
spullen gebruiken, al dan niet in een VM is dan de oplossing. Voor
Debian is er het pakket openssh-client-ssh1 (dat is dan voor jou wel in
de andere richting):

secure shell (SSH) client for legacy SSH1 protocol

Nadeeltje is wel dat-ie out of the box de "normale" ssh_config
gebruikt en daardoor gaat zeuren, je zult dus een ssh1_config moeten
aanmaken en die specifiek moeten gebruiken.

Maar kun je sshd in de configs niet zo maken dat-ie toch die oude
ciphers accepteert?

Er is zo te zien geen pakket openssh-server-ssh1 die je op een andere
poort kan laten draaien met een firewall ervoor.

-- 
richard lucassen
http://contact.xaq.nl/