Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[Jonathan Dowland]

On Wed Apr 24, 2024 at 1:50 PM BST, Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix for this or at least a way to handle this case with a much
> clearer error message. So I'll probably open a bug report for the package
> and the maintainer can decide if that should be forwarded upstream. Such a
> rather trivial case shouldn't be resulting in such fatal errors.

That's very interesting. I'd definitely suggest filing a bug for this,
if there isn't one already.

-- 
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[John Crawley]

On 26/04/2024 12:56, David Wright wrote:

On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:

Innocent question: what difference does the comment make vs just ending the 
file with an empty line?


Nothing for the computer, but visibility for me.

Say you print the file on paper. All you see is white space after
the end of the printed text. Is there an empty line?

Or take, for instance, my example above, and think back to those VDUs,
as we called them, where the firmware added a newline as soon as the
cursor reached the right side of the screen, without waiting to see
whether the next character was itself a newline or not.¹ So using an
empty line approach, you might find yourself looking at a screen like:

Last character position on the screen ---↓

swap LABEL= … … … … … … … … … … … … … … … … … … … … … =512

$

Now, is that an empty line before the prompt, or did the terminal
add the extra newline itself because the swap line was exactly
80 characters long?


Thanks!


And nano is worse: to know you've reached the bottom, you have to
check the cursor doesn't advance when you pound on the downarrow key.


Yes, that's what I usually do. :)

--
John

Last line [was: Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition]

[Max Nikulin]

On 26/04/2024 10:56, David Wright wrote:

Editor examples: a windowed emacs buffer has a ≣ decoration at the
extreme left edge after the last line of text, so that you can
distinguish an absence of lines from empty lines.


Perhaps that decoration should be explicitly enabled. However it 
reminded me the following:


(info "(elisp) Library-Headers")
https://www.gnu.org/software/emacs/manual/html_node/elisp/Library-Headers.html
"D.8 Conventional Headers for Emacs Libraries"

‘;;; filename ends here’

This is the footer line; it appears at the very end of the file.
Its purpose is to enable people to detect truncated versions of the file
from the lack of a footer line.


As to some ignored line at the end of a file:
https://mywiki.wooledge.org/BashFAQ/005#Handling_newlines_.28or_lack_thereof.29_at_the_end_of_a_file
"2.1.1. Handling newlines (or lack thereof) at the end of a file"
in BASH FAQ "How can I use array variables?"


`read` returns false when it reads the last line of a file. This
presents a problem: if the file contains a trailing newline, then
read will be false when reading/assigning that final line, otherwise,
it will be false when reading/assigning the last line of data.
Without a special check for these cases, no matter what logic is
used, you will always end up either with an extra blank element in
the resulting array, or a missing final element.

Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[David Wright]

On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
> On 24/04/2024 22:37, David Wright wrote:
> > On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> > > upon gathering my thoughts for answering to you I found the solution to
> > > this: update-initramfs can't handle the case that crypttab ends in the 
> > > line
> > > of the last entry and not in a new line character. I think there either
> > > should be a fix for this or at least a way to handle this case with a much
> > > clearer error message. So I'll probably open a bug report for the package
> > > and the maintainer can decide if that should be forwarded upstream. Such a
> > > rather trivial case shouldn't be resulting in such fatal errors.
> > 
> > Some time at the end of the last century, I remember some startup script
> > that cat'd its configuration file for that very reason. It taught me
> > the habit of always finishing files with a blank comment line:
> > 
> > $ cat /etc/crypttab
> > # 
> > swapLABEL=cryptswap /dev/urandom
> > swap,offset=2048,cipher=aes-xts-plain64,size=512
> > #
> > $
> > 
> 
> Innocent question: what difference does the comment make vs just ending the 
> file with an empty line?

Nothing for the computer, but visibility for me.

Say you print the file on paper. All you see is white space after
the end of the printed text. Is there an empty line?

Or take, for instance, my example above, and think back to those VDUs,
as we called them, where the firmware added a newline as soon as the
cursor reached the right side of the screen, without waiting to see
whether the next character was itself a newline or not.¹ So using an
empty line approach, you might find yourself looking at a screen like:

Last character position on the screen ---↓

swap LABEL= … … … … … … … … … … … … … … … … … … … … … =512

$ 

Now, is that an empty line before the prompt, or did the terminal
add the extra newline itself because the swap line was exactly
80 characters long?

Editor examples: a windowed emacs buffer has a ≣ decoration at the
extreme left edge after the last line of text, so that you can
distinguish an absence of lines from empty lines. However, a
non-windowed emacs in an xterm has no such decoration: you have to
provoke an "end of buffer" message to be certain where the file ends.
And nano is worse: to know you've reached the bottom, you have to
check the cursor doesn't advance when you pound on the downarrow key.

¹ IIRC, there's a terminfo capability, am, to work around this.

Cheers,
David.

Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[John Crawley]

On 24/04/2024 22:37, David Wright wrote:

On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:

upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character. I think there either
should be a fix for this or at least a way to handle this case with a much
clearer error message. So I'll probably open a bug report for the package
and the maintainer can decide if that should be forwarded upstream. Such a
rather trivial case shouldn't be resulting in such fatal errors.


Some time at the end of the last century, I remember some startup script
that cat'd its configuration file for that very reason. It taught me
the habit of always finishing files with a blank comment line:

$ cat /etc/crypttab
# 
swapLABEL=cryptswap /dev/urandom
swap,offset=2048,cipher=aes-xts-plain64,size=512
#
$



Innocent question: what difference does the comment make vs just ending the 
file with an empty line?

--
John

Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[David Wright]

On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix for this or at least a way to handle this case with a much
> clearer error message. So I'll probably open a bug report for the package
> and the maintainer can decide if that should be forwarded upstream. Such a
> rather trivial case shouldn't be resulting in such fatal errors.

Some time at the end of the last century, I remember some startup script
that cat'd its configuration file for that very reason. It taught me
the habit of always finishing files with a blank comment line:

$ cat /etc/crypttab 
# 
swapLABEL=cryptswap /dev/urandom
swap,offset=2048,cipher=aes-xts-plain64,size=512
#
$ 

Cheers,
David.

Re: [SOLVED] Trouble/bug with initramfs-tools adding encrypted swap partition

[Richard]

Hi Michel,
upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character. I think there either
should be a fix for this or at least a way to handle this case with a much
clearer error message. So I'll probably open a bug report for the package
and the maintainer can decide if that should be forwarded upstream. Such a
rather trivial case shouldn't be resulting in such fatal errors.

Best
Richard


On Wed, Apr 24, 2024, 14:23 Michel Verdier  wrote:

> On 2024-04-23, Richard wrote:
>
> > luks-775ea946-6797-4c4d-a042-72924309f3d2
> > UUID=775ea946-6797-4c4d-a042-72924309f3d2 /crypto_keyfile.bin
> > luks,keyscript=/bin/cat
> > luks-78362aa3-760c-41de-b911-6531b684e3f7
> > UUID=78362aa3-760c-41de-b911-6531b684e3f7 /crypto_keyfile.bin
> > luks,keyscript=/bin/cat
>
> initramfs extract line from /etc/crypttab to create its own crypttab
> as you have seen in main/cryptroot/crypttab, and only for rootfs, not for
> swap
>
> > Now, is this a bug in the package or am I missing something? And how do I
> > create a working initramfs now?
>
> swap is usually mounted after rootfs is mounted, thus using
> /etc/crypttab. If you want to resume from swap you have to follow
> paragraph 2.2.1 on
> https://wiki.archlinux.org/title/Dm-crypt/Swap_encryption
>
> If you don't need to resume you can follow the much easier chapter 1 on
> the same url, using /dev/urandom as a keyfile.
>
>
>

Re: Trouble/bug with initramfs-tools adding encrypted swap partition

[Richard]

Hello Hans,
this is exactly what I did. To be precise, I followed this guide [1], with
the difference that instead of "crypt" I used the actual name, luks-
(Disks thanksfully shows everything relevant). It's not the first time I'm
doing this. Yet I experience the errors mentioned. Sure, I'm not using the
-u flag with update-initramfs as I see no point in updating what's already
broken, I just use -ck all. But that shouldn't make a difference.

Best
Richard

[1]: https://wiki.debian.org/GrubEFIReinstall

Am Mi., 24. Apr. 2024 um 08:35 Uhr schrieb Hans :

> Am Dienstag, 23. April 2024, 22:26:17 CEST schrieb Richard:
>
> Hi Richard,
>
> this is, what I am doing when this happens:
>
> 1. booting into a live system (any new is working, I prefer kali-linux)
>
> 2. If you are using encrypted filesystems, open it. But you have to name
> it like it is named in /etc/crypttab of the defective system
>
> 3. Now mount the device with root-filesystem to /mnt
>
> 4. If you have /boot as a separated partition, mount it to /mnt/boot
>
> 5. Now mount needed system directories to /mnt
>
> mount --bind /sys /mnt/sys
>
> mount --bind /proc /mnt/proc
>
> mount --bind /dev /mnt/dev
>
> 6. If everything is mounted correct, you can chroot into the mounted system
>
> chroot /mnt
>
> 7. Now you can create a new initrd
>
> update-initramfs -u
>
>
>
> 8. exit the chroot and reboot.
>
>
> --
>
>
> Note:
>
> 1. if you have encrypted filesystems, check in the chroot the files
>
> /etc/crypttab
>
> /etc/cryptsetup-initramfs/conf-hook
>
> In conf-hook check the last line, the parm "ASKPASS=Y" should be commented
> out.
>
> 2. You can check the UUID of every partition with the command
>
> blkid /dev/sda1
>
> and compare it with the entries in /etc/fstab, /etc/crypttab and
> everywhere else it is used.
>
> 3. In chroot, you can of course also create a new initrd, using
>
> update-initramfs -c -k all
>
> 4. Please remember, when you have encrypted partitions, then the UUID of
> the device is other, than the partitions, you later mount. Example:
>
> blkid /dev/sda3
>
> UUID=1234556-dfre-3456.
>
> Now
>
> cryptsetup luksOpen /dev/sda3 crypt_sda3
>
> blkid /dev/mapper/crypt_sda3
>
> UUID=9876g54-765g-87hg
>
> Watch this, when changing any UUIDs in /etc/fstab or anywhere else.
>
> Last but not least: Hope this helps, good luck!
>
> Best
>
> Hans
>
>
>
>

Re: Trouble/bug with initramfs-tools adding encrypted swap partition

[Michel Verdier]

On 2024-04-23, Richard wrote:

> luks-775ea946-6797-4c4d-a042-72924309f3d2
> UUID=775ea946-6797-4c4d-a042-72924309f3d2 /crypto_keyfile.bin
> luks,keyscript=/bin/cat
> luks-78362aa3-760c-41de-b911-6531b684e3f7
> UUID=78362aa3-760c-41de-b911-6531b684e3f7 /crypto_keyfile.bin
> luks,keyscript=/bin/cat

initramfs extract line from /etc/crypttab to create its own crypttab
as you have seen in main/cryptroot/crypttab, and only for rootfs, not for
swap

> Now, is this a bug in the package or am I missing something? And how do I
> create a working initramfs now?

swap is usually mounted after rootfs is mounted, thus using
/etc/crypttab. If you want to resume from swap you have to follow
paragraph 2.2.1 on
https://wiki.archlinux.org/title/Dm-crypt/Swap_encryption

If you don't need to resume you can follow the much easier chapter 1 on
the same url, using /dev/urandom as a keyfile.

Re: Trouble/bug with initramfs-tools adding encrypted swap partition

[Hans]

Am Dienstag, 23. April 2024, 22:26:17 CEST schrieb Richard:
Hi Richard,

this is, what I am doing when this happens:

1. booting into a live system (any new is working, I prefer kali-linux)

2. If you are using encrypted filesystems, open it. But you have to name it 
like it is named in /
etc/crypttab of the defective system

3. Now mount the device with root-filesystem to /mnt 

4. If you have /boot as a separated partition, mount it to /mnt/boot

5. Now mount needed system directories to /mnt
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev

6. If everything is mounted correct, you can chroot into the mounted system
chroot /mnt

7. Now you can create a new initrd
update-initramfs -u
 
8. exit the chroot and reboot.





Note:

1. if you have encrypted filesystems, check in the chroot the files

/etc/crypttab
/etc/cryptsetup-initramfs/conf-hook 

In conf-hook check the last line, the parm "ASKPASS=Y" should be commented out.

2. You can check the UUID of every partition with the command
blkid /dev/sda1 
and compare it with the entries in /etc/fstab, /etc/crypttab and everywhere 
else it is used.

3. In chroot, you can of course also create a new initrd, using 
update-initramfs -c -k all

4. Please remember, when you have encrypted partitions, then the UUID of the 
device is other, 
than the partitions, you later mount. Example:

blkid /dev/sda3
UUID=1234556-dfre-3456.

Now
cryptsetup luksOpen /dev/sda3 crypt_sda3
blkid /dev/mapper/crypt_sda3
UUID=9876g54-765g-87hg

Watch this, when changing any UUIDs in /etc/fstab or anywhere else.

Last but not least: Hope this helps, good luck!

Best

Hans

   

Trouble/bug with initramfs-tools adding encrypted swap partition

[Richard]

Hi,
I've just set up a new computer with Debian Testing. I initially set it up
without a swap partition, but I want to add it now. The partition has
already been created as a LUKS2 partition, but I can't get update-initramfs
to add it so it will automatically be decrypted at boot (both have same
passphrase, but opposed to using the bootup passphrase or ask for a
separate one, I'm only asked much later by grub. Running update-initramfs
-ck all gives me this error:

update-initramfs: Generating /boot/initrd.img-6.6.15-amd64
cryptsetup: WARNING: target 'luks-78362aa3-760c-41de-b911-6531b684e3f7' not
found in /etc/crypttab


but /etc/crypttab has these two lines, just like I did on my old device:

luks-775ea946-6797-4c4d-a042-72924309f3d2
UUID=775ea946-6797-4c4d-a042-72924309f3d2 /crypto_keyfile.bin
luks,keyscript=/bin/cat
luks-78362aa3-760c-41de-b911-6531b684e3f7
UUID=78362aa3-760c-41de-b911-6531b684e3f7 /crypto_keyfile.bin
luks,keyscript=/bin/cat


So it clearly doesn't miss from the crypttab. Though I can'ft check if the
second partition has a crypto_keyfile.bin, as it is a swap partition and I
have no idea how to look inside. For completeness, that's the fstab:

UUID=F5D8-8C91/boot/efi  vfat
 defaults,noatime 0 2
/dev/mapper/luks-775ea946-6797-4c4d-a042-72924309f3d2 /  btrfs

subvol=/@,defaults,noatime,space_cache=v2,autodefrag,discard,compress=zstd:4
0 0
/dev/mapper/luks-775ea946-6797-4c4d-a042-72924309f3d2 /home  btrfs

subvol=/@home,defaults,noatime,space_cache=v2,autodefrag,discard,compress=zstd:4
0 0
/dev/mapper/luks-78362aa3-760c-41de-b911-6531b684e3f7 swap   swap
 defaults,noatime,discard   0 0
tmpfs /tmp   tmpfs
  defaults,noatime,mode=1777 0 0



and this is the command line in /etc/default/grub (of course I did run
update-grub afterward):

GRUB_CMDLINE_LINUX_DEFAULT="quiet
cryptdevice=UUID=775ea946-6797-4c4d-a042-72924309f3d2:luks-775ea946-6797-4c4d-a042-72924309f3d2
root=/dev/mapper/luks-775ea946-6797-4c4d-a042-72924309f3d2 splash
resume=/dev/mapper/luks-78362aa3-760c-41de-b911-6531b684e3f7"


I even created the file /etc/initramfs-tools/conf.d/resume containing the
line "RESUME=UUID=luks-78362aa3-760c-41de-b911-6531b684e3f7", also no
change.
In the meantime, I also tried adding the initramfs option in crypttab, yet
no change. Upon inspecting the created initramfs by unpacking it
with unmkinitramfs, I can see the initramfs does contain crypttab twice.
The one in main/etc/crypttab is identical to the one in my system, but the
one in main/cryptroot/crypttab is missing the second entry of the swap
partition.

Also, since then I've done a reboot and now when gdm would load I'm only
greeted by a strange white screen telling my something happened the system
can't recover from and that I should talk to my admin (or something like
that). I was still able to switch tty. So while I'm not sure if that's even
related, I tried to remove the swap partition from fstab, crypttab, grub
and the resume file. But the same error kept happening over and over again.
So I booted to a live USB (of 12.5), chrooted into the system without
mounting the swap partition to try to run "update-initramfs -ck all" from
there. But now it even refuses to find the root partition in crypttab.

Now, is this a bug in the package or am I missing something? And how do I
create a working initramfs now?

Best
Richard

Re: Trouble with OpenSMTPD

[Charles Curley]

On Sun, 7 Jan 2024 17:36:12 -0500
Paul M Foster  wrote:

> For reason(s) I don't understand, opensmtpd will not start via
> "systemctl start opensmtpd". According to "sudo smtpd -n", the
> configuration file passes, but it just won't start.

Have you looked to see what systemd has to say? After running
"systemctl start opensmtpd", run "systemctl status opensmtpd". You may
also find "journalctl -b -u opensmtpd" useful.

-- 
Does anybody read signatures any more?

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

Trouble with OpenSMTPD

[Paul M Foster]

Folks:

I'm running Debian Bookworm, and looking to switch from Exim4 to OpenSMTPd.
Here is my smtpd.conf file:

---

table aliases file:/etc/aliases
table secrets file:/etc/secrets

listen on lo
listen on eno1

# action name method options
action "local" mda maildrop virtual 
action "relay" relay host smtp+tls://pa...@smtp.dreamhost.com auth 

match from any for domain "yosemite.mars.lan" action "local"
match for local action "local"
match for any action "relay"

---

For reason(s) I don't understand, opensmtpd will not start via "systemctl
start opensmtpd". According to "sudo smtpd -n", the configuration file
passes, but it just won't start.

(For what it's worth, I've used this config back in 2021 running Debian and
it worked.)

I'm happy to supply whatever data needed in helping to resolve this.

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Trouble with KVM after upgrade to bookworm

[Niall O'Reilly]

Hello.

I use Debian as KVM host for the various VMs (Ubuntu, FreeBSD,
no Debian) which serve my home network.  I've been doing this
since Debian stretch.  Until bookworm, each release upgrade
has been tedious, but boringly unremarkable.

This upgrade seems to have broken KVM so as to cause one or other
guest VM to enter what seems to be a busy wait, and to do so
unpredictably and intermittently. According to virt-top, the affected guest 
seizes the full capacity of the CPU core where it is currently
running; on my 4-core unit, virt-top shows this as 25% CPU utilization.
When this happens, top shows zero idle time for the corresponding core,
and an aggregate of system and user utilization (the only non-zero
utilization values) closer to 50% than to 100%.  In normal operation,
I see each core busy for about 3% of the time, idle for 95% or more,
and an the remaining 2% or so unaccounted for.

When a VM goes busy like this, I find that it can be made unbusy
by use of the command, `virsh inject-nmi $GUEST`.

I think I have read the release notes for bookworm carefully, but
may have missed something.  I've repeatedly re-read chapters 4 and 5.

I'm baffled, and would appreciate any clue.

Thanks in advance.
Niall O'Reilly

Trouble with KVM after upgrade to bookworm

[Niall O'Reilly]

Hello.

I use Debian as KVM host for the various VMs (Ubuntu, FreeBSD,
no Debian) which serve my home network.  I've been doing this
since Debian stretch.  Until bookworm, each release upgrade
has been tedious, but boringly unremarkable.

This upgrade seems to have broken KVM so as to cause one or other
guest VM to enter what seems to be a busy wait, and to do so
unpredictably and intermittently. According to virt-top, the affected guest 
seizes the full capacity of the CPU core where it is currently
running; on my 4-core unit, virt-top shows this as 25% CPU utilization.
When this happens, top shows zero idle time for the corresponding core,
and an aggregate of system and user utilization (the only non-zero
utilization values) closer to 50% than to 100%.  In normal operation,
I see each core busy for about 3% of the time, idle for 95% or more,
and an the remaining 2% or so unaccounted for.

When a VM goes busy like this, I find that it can be made unbusy
by use of the command, `virsh inject-nmi $GUEST`.

I think I have read the release notes for bookworm carefully, but
may have missed something.  I've repeatedly re-read chapters 4 and 5.

I'm baffled, and would appreciate any clue.

Thanks in advance.
Niall O'Reilly

Re: Trouble with nvidia drivers in Debian 12 Bookworm

[Sam Clearman]

Solved my own problem: I had to do `apt install
linux-headers-cloud-amd64` instead of `apt install
linux-headers-amd64`

On Thu, Jul 13, 2023 at 2:28 PM Sam Clearman  wrote:
>
> Hi,
> I'm trying to get a Tesla T4 working under Debian 12.
>
> So far I've tried two approaches:
> 1. Using the Debian provided drivers, per
> https://wiki.debian.org/NvidiaGraphicsDrivers
> 2. Using the nVidia provided drivers installed via runfile, per
> https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html
>
> For 1 (installing the drivers in the debian nonfree repository),
> everything seems to install fine but the drivers don't load properly.
> Systemctl returns the following:
>
> $ systemctl status systemd-modules-load
> × systemd-modules-load.service - Load Kernel Modules
>  Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
>  Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08
> UTC; 18min ago
>Docs: man:systemd-modules-load.service(8)
>  man:modules-load.d(5)
> Process: 220 ExecStart=/lib/systemd/systemd-modules-load
> (code=exited, status=1/FAILURE)
>Main PID: 220 (code=exited, status=1/FAILURE)
> CPU: 29ms
>
> Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR:
> could not insert 'nvidia': Invalid argument
> Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL:
> Module nvidia-current-modeset not found in directory
> /lib/modules/6.1.0-10-cloud-amd64
> Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
> ../libkmod/libkmod-module.c:1047 command_do() Error running install
> command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m>
> Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
> could not insert 'nvidia_modeset': Invalid argument
> Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL:
> Module nvidia-current-drm not found in directory
> /lib/modules/6.1.0-10-cloud-amd64
> Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running
> install command 'modprobe nvidia-modeset ; modprobe -i
> nvidia-current-drm ' for module nvidia_drm: retcode 1
> Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert
> module 'nvidia_drm': Invalid argument
> Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
> Main process exited, code=exited, status=1/FAILURE
> Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
> Failed with result 'exit-code'.
> Jul 13 21:05:08 localhost systemd[1]: Failed to start
> systemd-modules-load.service - Load Kernel Modules.
>
> When I try to use the runfile (specifically, this file:
> https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run)
> it is unable to read the kernel headers that I have installed (if I
> don't specify a location, it says it can't find them, no matter which
> location I specify, it finds something unexpected about what's there).
>
> Any help is appreciated!
>
> PS: Secureboot is disabled, I get the following from mokutil:
> $ mokutil --sb-state
> SecureBoot disabled

Trouble with nvidia drivers in Debian 12 Bookworm

[Sam Clearman]

Hi,
I'm trying to get a Tesla T4 working under Debian 12.

So far I've tried two approaches:
1. Using the Debian provided drivers, per
https://wiki.debian.org/NvidiaGraphicsDrivers
2. Using the nVidia provided drivers installed via runfile, per
https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html

For 1 (installing the drivers in the debian nonfree repository),
everything seems to install fine but the drivers don't load properly.
Systemctl returns the following:

$ systemctl status systemd-modules-load
× systemd-modules-load.service - Load Kernel Modules
 Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
 Active: failed (Result: exit-code) since Thu 2023-07-13 21:05:08
UTC; 18min ago
   Docs: man:systemd-modules-load.service(8)
 man:modules-load.d(5)
Process: 220 ExecStart=/lib/systemd/systemd-modules-load
(code=exited, status=1/FAILURE)
   Main PID: 220 (code=exited, status=1/FAILURE)
CPU: 29ms

Jul 13 21:05:08 localhost systemd-modules-load[226]: modprobe: ERROR:
could not insert 'nvidia': Invalid argument
Jul 13 21:05:08 localhost systemd-modules-load[230]: modprobe: FATAL:
Module nvidia-current-modeset not found in directory
/lib/modules/6.1.0-10-cloud-amd64
Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
../libkmod/libkmod-module.c:1047 command_do() Error running install
command 'modprobe nvidia ; modprobe -i nvidia-current-modeset ' for m>
Jul 13 21:05:08 localhost systemd-modules-load[223]: modprobe: ERROR:
could not insert 'nvidia_modeset': Invalid argument
Jul 13 21:05:08 localhost systemd-modules-load[232]: modprobe: FATAL:
Module nvidia-current-drm not found in directory
/lib/modules/6.1.0-10-cloud-amd64
Jul 13 21:05:08 localhost systemd-modules-load[220]: Error running
install command 'modprobe nvidia-modeset ; modprobe -i
nvidia-current-drm ' for module nvidia_drm: retcode 1
Jul 13 21:05:08 localhost systemd-modules-load[220]: Failed to insert
module 'nvidia_drm': Invalid argument
Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
Jul 13 21:05:08 localhost systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
Jul 13 21:05:08 localhost systemd[1]: Failed to start
systemd-modules-load.service - Load Kernel Modules.

When I try to use the runfile (specifically, this file:
https://us.download.nvidia.com/tesla/535.54.03/NVIDIA-Linux-x86_64-535.54.03.run)
it is unable to read the kernel headers that I have installed (if I
don't specify a location, it says it can't find them, no matter which
location I specify, it finds something unexpected about what's there).

Any help is appreciated!

PS: Secureboot is disabled, I get the following from mokutil:
$ mokutil --sb-state
SecureBoot disabled

trouble with VPN deactivation

[Patrice Duroux]

Hi,

I am using a Debian Sid system with the GNOME desktop related packages from
experimental (GNOME 44). And:

$ id
uid=1001(patrice) gid=1001(patrice) 
groupes=1001(patrice),4(adm),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),109(netdev),113(bluetooth),117(scanner),135(sbuild),1000(lpadmin)

Activating a VPN configuration is working nicely. But when switching back to the
default network configuration it does not seem to not be ideal.
Also the network is working but seems to me somehow degraded. 

Here are the traces observed using journalctl:

-- Switching VPN on

juin 26 19:51:56 HOSTNAME NetworkManager[902]:   [1687801916.4276] 
vpn[0x55cb21ef7960,4d48a71a-ce3f-4cae-a421-ce0f17a0369d,"X"]: starting 
fortisslvpn
juin 26 19:51:56 HOSTNAME NetworkManager[902]:   [1687801916.4279] audit: 
op="connection-activate" uuid="4d48a71a-ce3f-4cae-a421-ce0f17a0369d" 
name="X" pid=2681 uid=1001 result="success"
juin 26 19:51:56 HOSTNAME NetworkManager[6178]: INFO:   Connected to gateway.
juin 26 19:51:56 HOSTNAME NetworkManager[6178]: INFO:   Authenticated.
juin 26 19:51:56 HOSTNAME NetworkManager[6178]: INFO:   Remote gateway has 
allocated a VPN.
juin 26 19:51:57 HOSTNAME pppd[6182]: Plugin 
/usr/lib/pppd/2.4.9/nm-fortisslvpn-pppd-plugin.so loaded.
juin 26 19:51:57 HOSTNAME NetworkManager[6182]: Plugin 
/usr/lib/pppd/2.4.9/nm-fortisslvpn-pppd-plugin.so loaded.
juin 26 19:51:57 HOSTNAME pppd[6182]: pppd 2.4.9 started by root, uid 0
juin 26 19:51:57 HOSTNAME kernel: PPP generic driver version 2.4.2
juin 26 19:51:57 HOSTNAME pppd[6182]: Using interface ppp0
juin 26 19:51:57 HOSTNAME NetworkManager[6182]: Using interface ppp0
juin 26 19:51:57 HOSTNAME NetworkManager[6182]: Connect: ppp0 <--> /dev/pts/1
juin 26 19:51:57 HOSTNAME pppd[6182]: Connect: ppp0 <--> /dev/pts/1
juin 26 19:51:57 HOSTNAME NetworkManager[6182]: {/tmp/.AY6261} {/tmp}
juin 26 19:51:57 HOSTNAME NetworkManager[6182]: {/tmp/.AY6261} {.AY6261}
juin 26 19:51:57 HOSTNAME NetworkManager[902]:   [1687801917.1194] 
manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/6)
juin 26 19:51:57 HOSTNAME kernel: PPP BSD Compression module registered
juin 26 19:51:57 HOSTNAME kernel: PPP Deflate Compression module registered
juin 26 19:51:57 HOSTNAME NetworkManager[6178]: INFO:   Got addresses: 
[X.X.X.X], ns [X.X.X.X, X.X.X.X]
juin 26 19:51:57 HOSTNAME NetworkManager[6178]: INFO:   Negotiation complete.
juin 26 19:52:00 HOSTNAME NetworkManager[6178]: INFO:   Got addresses: 
[X.X.X.X], ns [X.X.X.X, X.X.X.X]
juin 26 19:52:00 HOSTNAME NetworkManager[6178]: INFO:   Negotiation complete.
juin 26 19:52:00 HOSTNAME NetworkManager[6178]: INFO:   Negotiation complete.
juin 26 19:52:00 HOSTNAME pppd[6182]: local  IP address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[6182]: local  IP address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[6182]: remote IP address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[6182]: primary   DNS address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[6182]: secondary DNS address X.X.X.X
juin 26 19:52:00 HOSTNAME pppd[6182]: remote IP address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[902]:   [1687801920.5882] device 
(ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', 
sys-iface-state: 'external')
juin 26 19:52:00 HOSTNAME NetworkManager[6182]: Can't execute /etc/ppp/ip-up: 
Permission denied
juin 26 19:52:00 HOSTNAME pppd[6182]: primary   DNS address X.X.X.X
juin 26 19:52:00 HOSTNAME NetworkManager[902]:   [1687801920.5893] device 
(ppp0): state change: unavailable -> disconnected (reason 'none', 
sys-iface-state: 'external')
juin 26 19:52:00 HOSTNAME pppd[6182]: secondary DNS address X.X.X.X
juin 26 19:52:00 HOSTNAME pppd[6182]: Can't execute /etc/ppp/ip-up: Permission 
denied
juin 26 19:52:00 HOSTNAME dbus-daemon[827]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 
pid=902 comm="/usr/sbin/NetworkManager --no-daemon")
juin 26 19:52:00 HOSTNAME NetworkManager[6178]: INFO:   Interface ppp0 is UP.
juin 26 19:52:00 HOSTNAME NetworkManager[6178]: INFO:   Tunnel is up and 
running.
juin 26 19:52:00 HOSTNAME systemd[1]: Starting 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
░░ Subject: L'unité (unit) NetworkManager-dispatcher.service a commencé à 
démarrer
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ L'unité (unit) NetworkManager-dispatcher.service a commencé à démarrer.
juin 26 19:52:00 HOSTNAME dbus-daemon[827]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
juin 26 19:52:00 HOSTNAME systemd[1]: Started NetworkManager-dispatcher.service 
- Network Manager Script Dispatcher Service.
░░ Subject: L'unité (unit) NetworkManager-dispatcher.service a terminé son 
démarrage
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ L'unité (unit) 

Re: [SOLVED] Re: Mouse trouble on sid

[gene heskett]

On 5/18/23 01:29, to...@tuxteam.de wrote:

On Wed, May 17, 2023 at 07:01:30PM +0100, Joe wrote:


Oh dear, oh dear...

Very sorry for the wasted time.

When I tried the wired mouse I did not actually unplug the wireless
mouse receiver, so it was still generating scroll events every 200ms


\o/

No wasted time. Everyone got to sharpen their debugging tools.

The nicest part is, this person (it was Kent West, I think) who
suggested electromagnetic interference wasn't that off the mark
(I was one of those saying "nah, not the hardware..." :-)

Thanks for resolving the suspense.

Cheers


And Kent was probably right, the mouse battery died, the receiver upped 
the gain, and something in the environment was making enough noise it 
was being interpreted as a wheel related signal.

As a broadcast engineer I can easily visualize that.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: [SOLVED] Re: Mouse trouble on sid

[tomas]

On Wed, May 17, 2023 at 07:01:30PM +0100, Joe wrote:
> 
> Oh dear, oh dear...
> 
> Very sorry for the wasted time.
> 
> When I tried the wired mouse I did not actually unplug the wireless
> mouse receiver, so it was still generating scroll events every 200ms

\o/

No wasted time. Everyone got to sharpen their debugging tools.

The nicest part is, this person (it was Kent West, I think) who
suggested electromagnetic interference wasn't that off the mark
(I was one of those saying "nah, not the hardware..." :-)

Thanks for resolving the suspense.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: [SOLVED] Re: Mouse trouble on sid

[Charles Curley]

On Wed, 17 May 2023 19:01:30 +0100
Joe  wrote:

> Quick removal and replacement of mouse battery and problem solved.

Interesting. Usually when my rodent batteries fail, it simply stops
working.

XFCE's power monitor also see the batteries for my keyboards and
rodents. Logitech k330 and m215, respectively. You may need to install
it.

-- 
Does anybody read signatures any more?

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

Re: [SOLVED] Re: Mouse trouble on sid

[Christoph Brinkhaus]

Am Wed, May 17, 2023 at 07:01:30PM +0100 schrieb Joe:

Hello Joe,
> 
> Oh dear, oh dear...
> 
> Very sorry for the wasted time.
This has been no wasted time. You have found an additional root cause
for some unexpected behaviour all of us will be aware of from now on.
> 
> When I tried the wired mouse I did not actually unplug the wireless
> mouse receiver, so it was still generating scroll events every 200ms
> while over a window (presumably being ignored by the kernel when it was
> over unscrollable things like the background and panels.
> 
> Quick removal and replacement of mouse battery and problem solved.
And again we can blame the hardware :-).
> 
> As partial reparation, could I recommend evemu-tools to anyone who
> doesn't know about it? Cleans up that nasty raw output from cat
> /dev/input/mouseX and adds times. Problem solved immediately with its
> help.
This is good to know.
> 
> OK, I can't explain why Knoppix didn't also do it, the mouse was still
> generating masses of scroll events. That really messed up the
> troubleshooting. Knoppix doesn't have evemu-tools, but the raw mouse
> events were enough by that time.
It can be that the xinput of Knoppix is configured to do more
de-bouncing of scroll events than the Debian system. You reported that
Knoppix has been very slow. It could also be that Knoppix could not
handle all the mouse events and did the de-bouncing by unintended
throttling :-).

Thank you for reporting about the fix and for the recommendation!

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[Joe]

On Wed, 17 May 2023 12:18:17 +0200
Christoph Brinkhaus  wrote:

> Am Tue, May 16, 2023 at 07:26:41PM +0100 schrieb Joe:
> 
> Hello Joe,
> 
> > On Tue, 16 May 2023 12:29:02 +0200
> > Christoph Brinkhaus  wrote:
> >   
> > > Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe:
> > > 
> > > Hello Joe,
> > > 
> > > [...deleted a lot...]  
> > > > On Tue, 16 May 2023 10:44:03 +0100
> > > > Joe  wrote:
> > > > 
> > > > > > One idea is to try a minimalistic window manager as twm to
> > > > > > find out if the issue is related to xfce.  
> > > > > 
> > > > > OK, tried twm and fvvm. Both unusable, as a left-click brings
> > > > > up a menu for a fraction of a second. Couldn't log out of
> > > > > either, had to switch to console and uninstall them. But they
> > > > > confirm the mouse problem. It's obviously fairly fundamental.
> > > > > 
> > > > > Just tried previous kernel, but also bad. I can assume by now
> > > > > that nobody else has seen this problem.
> > > > 
> > > > Just as a sanity check, I booted Knoppix, and of course there's
> > > > no problem, it's just an order of magnitude too slow from USB
> > > > to do anything useful.
> > > 
> > > Now it seems as if the issue is related to X or the driver stuff.
> > > I have three ideas.
> > > 
> > > 1. Do you have any xorg.conf things in /etc or the related
> > > directories? Nowadays X is not so bad in guessing the hardware
> > > which makes xorg.conf and such obsolete. If there are X config
> > > files it might be worth to move them to a safe place and to try
> > > without them.  
> > 
> > I can't find anything. This is a relatively new sid (installed on
> > new hardware, opportunity to get rid of some junk) and I have never
> > needed to mess about with X.  
> > > 
> > > 2. It is unlikely, but it might be that some of the xinput related
> > > programs or libraries have been corrupted. It might help to
> > > reinstall them.  
> > 
> > I have nothing in the apt cache, so I'll need to locate debs. I
> > eventually gave up and copied out the (possibly) offending upgrade
> > log and added newlines so it was actually readable. What jumped out
> > then were three xserver packages (from a total of 118). I located
> > previous versions in the cache, installed them, rebooted and
> > confirmed they were now running, and... just the same.   
> 
> My only remaining idea is that packages have been corrupted during
> download. This is not likely but can have multiple root causes.
> 
> I do not know if apt or dpkg check the integrity of the packages
> before installation. I also do not know by heart how to check them
> manually.
> 
> If this does not help I am running out of ideas.

Me too.

> I do not think that it is a hardware issue because Knoppix works.
> I do not think that it is a general issue of sid because then the same
> issue would have been seen by other users.
> It should be related to "something" on your machine.

Yes, to all of that. I'm getting closer to reinstalling, which is an
admission of defeat.

Thank you for your time and efforts, and everyone else who responded.
If I do have any success I'll report back. As well as the bug report...

Joe

Re: Mouse trouble on sid

[Christoph Brinkhaus]

Am Tue, May 16, 2023 at 07:26:41PM +0100 schrieb Joe:

Hello Joe,

> On Tue, 16 May 2023 12:29:02 +0200
> Christoph Brinkhaus  wrote:
> 
> > Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe:
> > 
> > Hello Joe,
> > 
> > [...deleted a lot...]
> > > On Tue, 16 May 2023 10:44:03 +0100
> > > Joe  wrote:
> > >   
> > > > > One idea is to try a minimalistic window manager as twm to find
> > > > > out if the issue is related to xfce.
> > > > 
> > > > OK, tried twm and fvvm. Both unusable, as a left-click brings up a
> > > > menu for a fraction of a second. Couldn't log out of either, had
> > > > to switch to console and uninstall them. But they confirm the
> > > > mouse problem. It's obviously fairly fundamental.
> > > > 
> > > > Just tried previous kernel, but also bad. I can assume by now that
> > > > nobody else has seen this problem.  
> > > 
> > > Just as a sanity check, I booted Knoppix, and of course there's no
> > > problem, it's just an order of magnitude too slow from USB to do
> > > anything useful.  
> > 
> > Now it seems as if the issue is related to X or the driver stuff.
> > I have three ideas.
> > 
> > 1. Do you have any xorg.conf things in /etc or the related
> > directories? Nowadays X is not so bad in guessing the hardware which
> > makes xorg.conf and such obsolete. If there are X config files it
> > might be worth to move them to a safe place and to try without them.
> 
> I can't find anything. This is a relatively new sid (installed on new
> hardware, opportunity to get rid of some junk) and I have never needed
> to mess about with X.
> > 
> > 2. It is unlikely, but it might be that some of the xinput related
> > programs or libraries have been corrupted. It might help to reinstall
> > them.
> 
> I have nothing in the apt cache, so I'll need to locate debs. I
> eventually gave up and copied out the (possibly) offending upgrade log
> and added newlines so it was actually readable. What jumped out then
> were three xserver packages (from a total of 118). I located previous
> versions in the cache, installed them, rebooted and confirmed they were
> now running, and... just the same. 

My only remaining idea is that packages have been corrupted during
download. This is not likely but can have multiple root causes.

I do not know if apt or dpkg check the integrity of the packages
before installation. I also do not know by heart how to check them
manually.

If this does not help I am running out of ideas.
I do not think that it is a hardware issue because Knoppix works.
I do not think that it is a general issue of sid because then the same
issue would have been seen by other users.
It should be related to "something" on your machine.

> > 
> > 3. The comparison of Xorg.log of Debian and Knoppix may give some
> > indication.
> 
> They look broadly similar, although it is easy to miss things among
> that much output.

I wish you will find the issue. In case I will have new ideas or so
I will chime in again.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[Joe]

On Wed, 17 May 2023 10:07:42 +0100
Joe  wrote:


> > 
> > If you are able to get a terminal running under your
> > crippled X11 [1], then it'd be interesting to compare
> > the output of "xinput --list --long" between a working
> > and a non-working config.  
> 
> OK, done for sid, I'll boot into Knoppix when I have a moment.
> > 

There's only one difference, repeated in three places:

Sid version:

⎜   ↳ MOSART Semi. 2.4G Wireless Mouse  id=9
[slave  pointer  (2)] Reporting 7 classes:
Class originated from: 9. Type: XIButtonClass
Buttons supported: 9
Button labels: "Button Left" "Button Middle" "Button
Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left"
"Button Horiz Wheel Right" "Button Side" "Button Extra" Button state:
Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 120.00
  flags: 0x0
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: 120.00
  flags: 0x0


34c34
< increment: 120.00
---
> increment: 15.00

I don't know how significant this is. The scroll wheel in both distros
seems to work normally, and it's the interpretation of a mouseover as a
click or scroll which is the problem.

-- 
Joe

Re: Mouse trouble on sid

[Joe]

On Wed, 17 May 2023 06:35:54 +0200
 wrote:

> On Tue, May 16, 2023 at 08:07:51PM +0100, Joe wrote:
> > On Tue, 16 May 2023 13:43:26 -0500
> > Kent West  wrote:
> >   
> > > 
> > > 
> > > Just for kicks, unplug the keyboard and see if the mouse starts
> > > behaving.  
> > 
> > 
> > No, no change.  
> 
> No surprise. People still barking up the hardware tree,
> while all evidence is pointing up the software tree :)

I think so.
> 
>  - change came with an upgrade

Probably, nothing else was changed or installed around that time. I
have rolled back the kernel and the three xserver packages to no effect,
and there seem to be no other possible suspects. But there were 118
packages, including several libraries.

>  - change from wireless mouse to wired: no effect
>  - other distro: mouse works
> 
> If you are able to get a terminal running under your
> crippled X11 [1], then it'd be interesting to compare
> the output of "xinput --list --long" between a working
> and a non-working config.

OK, done for sid, I'll boot into Knoppix when I have a moment.
> 
> My hunch would be that something's rotten in the state
> of Sid.

Definitely. I'm hoping to avoid reinstalling, at least partly because I
may well just reinstall the problem, but GIMP and.some other things are
unusable at the moment. 
> 
>
Thanks for your help.

Joe

Re: Mouse trouble on sid

[tomas]

On Wed, May 17, 2023 at 06:35:54AM +0200, to...@tuxteam.de wrote:

[...]

> [1] Never tried it, but "setxkbmap -option keypad:pointerkeys"

Forgot the relevant link:

  https://en.wikipedia.org/wiki/Mouse_keys

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[tomas]

On Tue, May 16, 2023 at 08:07:51PM +0100, Joe wrote:
> On Tue, 16 May 2023 13:43:26 -0500
> Kent West  wrote:
> 
> > 
> > 
> > Just for kicks, unplug the keyboard and see if the mouse starts
> > behaving.
> 
> 
> No, no change.

No surprise. People still barking up the hardware tree,
while all evidence is pointing up the software tree :)

 - change came with an upgrade
 - change from wireless mouse to wired: no effect
 - other distro: mouse works

If you are able to get a terminal running under your
crippled X11 [1], then it'd be interesting to compare
the output of "xinput --list --long" between a working
and a non-working config.

My hunch would be that something's rotten in the state
of Sid.

Cheers

[1] Never tried it, but "setxkbmap -option keypad:pointerkeys"
   reportedly gives you a keyboard mouse:
   setxkbmap -option keypad:pointerkeys.
   Alternatively, you can always log into a Linux terminal
   and talk to your X like so:
   DISPLAY=:0 xinput --list --long
   (or whatever your DISPLAY var under X is).

-- 
tomás


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[Kent West]

Just for kicks, unplug the keyboard and see if the mouse starts behaving.

>
>

-- 
Kent West<")))><
IT Support / Client Support
Abilene Christian University
Westing Peacefully - http://kentwest.blogspot.com

Re: Mouse trouble on sid

[Joe]

On Tue, 16 May 2023 12:29:02 +0200
Christoph Brinkhaus  wrote:

> Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe:
> 
> Hello Joe,
> 
> [...deleted a lot...]
> > On Tue, 16 May 2023 10:44:03 +0100
> > Joe  wrote:
> >   
> > > > One idea is to try a minimalistic window manager as twm to find
> > > > out if the issue is related to xfce.
> > > 
> > > OK, tried twm and fvvm. Both unusable, as a left-click brings up a
> > > menu for a fraction of a second. Couldn't log out of either, had
> > > to switch to console and uninstall them. But they confirm the
> > > mouse problem. It's obviously fairly fundamental.
> > > 
> > > Just tried previous kernel, but also bad. I can assume by now that
> > > nobody else has seen this problem.  
> > 
> > Just as a sanity check, I booted Knoppix, and of course there's no
> > problem, it's just an order of magnitude too slow from USB to do
> > anything useful.  
> 
> Now it seems as if the issue is related to X or the driver stuff.
> I have three ideas.
> 
> 1. Do you have any xorg.conf things in /etc or the related
> directories? Nowadays X is not so bad in guessing the hardware which
> makes xorg.conf and such obsolete. If there are X config files it
> might be worth to move them to a safe place and to try without them.

I can't find anything. This is a relatively new sid (installed on new
hardware, opportunity to get rid of some junk) and I have never needed
to mess about with X.
> 
> 2. It is unlikely, but it might be that some of the xinput related
> programs or libraries have been corrupted. It might help to reinstall
> them.

I have nothing in the apt cache, so I'll need to locate debs. I
eventually gave up and copied out the (possibly) offending upgrade log
and added newlines so it was actually readable. What jumped out then
were three xserver packages (from a total of 118). I located previous
versions in the cache, installed them, rebooted and confirmed they were
now running, and... just the same. 
> 
> 3. The comparison of Xorg.log of Debian and Knoppix may give some
> indication.

They look broadly similar, although it is easy to miss things among
that much output.

-- 
Joe

Re: Mouse trouble on sid

[Christoph Brinkhaus]

Am Tue, May 16, 2023 at 11:02:50AM +0100 schrieb Joe:

Hello Joe,

[...deleted a lot...]
> On Tue, 16 May 2023 10:44:03 +0100
> Joe  wrote:
> 
> > > One idea is to try a minimalistic window manager as twm to find out
> > > if the issue is related to xfce.  
> > 
> > OK, tried twm and fvvm. Both unusable, as a left-click brings up a
> > menu for a fraction of a second. Couldn't log out of either, had to
> > switch to console and uninstall them. But they confirm the mouse
> > problem. It's obviously fairly fundamental.
> > 
> > Just tried previous kernel, but also bad. I can assume by now that
> > nobody else has seen this problem.
> 
> Just as a sanity check, I booted Knoppix, and of course there's no
> problem, it's just an order of magnitude too slow from USB to do
> anything useful.

Now it seems as if the issue is related to X or the driver stuff.
I have three ideas.

1. Do you have any xorg.conf things in /etc or the related
directories? Nowadays X is not so bad in guessing the hardware which
makes xorg.conf and such obsolete. If there are X config files it
might be worth to move them to a safe place and to try without them.

2. It is unlikely, but it might be that some of the xinput related
programs or libraries have been corrupted. It might help to reinstall
them.

3. The comparison of Xorg.log of Debian and Knoppix may give some
indication.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[Joe]

On Tue, 16 May 2023 10:44:03 +0100
Joe  wrote:

> On Mon, 15 May 2023 22:18:12 +0200
> Christoph Brinkhaus  wrote:
> 
> > Am Mon, May 15, 2023 at 08:57:38PM +0100 schrieb Joe:
> > 
> > Hello Joe,
> >   
> > > On Mon, 15 May 2023 19:35:23 +
> > > "Andrew M.A. Cater"  wrote:
> > > 
> > > > On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote:
> > > > > On Mon, 15 May 2023 13:26:06 -0500
> > > > > Kent West  wrote:
> > > > >   
> > > > > > On 5/15/23 11:57, Joe wrote:  
> > > > > > > Hi,
> > > > > > >  
> > > > > > 
> > > > > > Then go from there.
> > > > > >   
> > > > > Not much to go on so far. Thanks for your suggestions. This
> > > > > looks like a bug in an upgrade, but I can't see evidence of
> > > > > anyone else seeing it.
> > > > > 
> > > > > This is the real problem with running sid: not that things
> > > > > break, but that they only break for me.
> > > > >   
> > > > 
> > > > If you run sid, you are absolutely expected to be able to
> > > > resolve any problems you encounter. If it breaks, you get to
> > > > keep both pieces. That's the contract with sid, more than with
> > > > the other tranches of Debian (which comes with no overall
> > > > warranty).
> > > > 
> > > > If you want increased stability and less shiny new stuff, you
> > > > run stable or, if you feel able to help debug and develop it,
> > > > testing.
> > > > 
> > > > Them's the breaks: and, as ever, DontBreakDebian by mixing
> > > > different suites.
> > > > 
> > > 
> > > Yes, I know all that, I've been running sid since sarge was
> > > stable, and only had to reinstall twice in that time.
> > 
> > One idea is to try a minimalistic window manager as twm to find out
> > if the issue is related to xfce.  
> 
> OK, tried twm and fvvm. Both unusable, as a left-click brings up a
> menu for a fraction of a second. Couldn't log out of either, had to
> switch to console and uninstall them. But they confirm the mouse
> problem. It's obviously fairly fundamental.
> 
> Just tried previous kernel, but also bad. I can assume by now that
> nobody else has seen this problem.

Just as a sanity check, I booted Knoppix, and of course there's no
problem, it's just an order of magnitude too slow from USB to do
anything useful.

-- 
Joe

Re: Mouse trouble on sid

[Joe]

On Mon, 15 May 2023 22:18:12 +0200
Christoph Brinkhaus  wrote:

> Am Mon, May 15, 2023 at 08:57:38PM +0100 schrieb Joe:
> 
> Hello Joe,
> 
> > On Mon, 15 May 2023 19:35:23 +
> > "Andrew M.A. Cater"  wrote:
> >   
> > > On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote:  
> > > > On Mon, 15 May 2023 13:26:06 -0500
> > > > Kent West  wrote:
> > > > 
> > > > > On 5/15/23 11:57, Joe wrote:
> > > > > > Hi,
> > > > > >
> > > > > 
> > > > > Then go from there.
> > > > > 
> > > > Not much to go on so far. Thanks for your suggestions. This
> > > > looks like a bug in an upgrade, but I can't see evidence of
> > > > anyone else seeing it.
> > > > 
> > > > This is the real problem with running sid: not that things
> > > > break, but that they only break for me.
> > > > 
> > > 
> > > If you run sid, you are absolutely expected to be able to resolve
> > > any problems you encounter. If it breaks, you get to keep both
> > > pieces. That's the contract with sid, more than with the other
> > > tranches of Debian (which comes with no overall warranty).
> > > 
> > > If you want increased stability and less shiny new stuff, you run
> > > stable or, if you feel able to help debug and develop it, testing.
> > > 
> > > Them's the breaks: and, as ever, DontBreakDebian by mixing
> > > different suites.
> > >   
> > 
> > Yes, I know all that, I've been running sid since sarge was stable,
> > and only had to reinstall twice in that time.  
> 
> One idea is to try a minimalistic window manager as twm to find out if
> the issue is related to xfce.

OK, tried twm and fvvm. Both unusable, as a left-click brings up a menu
for a fraction of a second. Couldn't log out of either, had to switch
to console and uninstall them. But they confirm the mouse problem. It's
obviously fairly fundamental.

Just tried previous kernel, but also bad. I can assume by now that
nobody else has seen this problem.

Thanks for your help,
Joe

Re: Mouse trouble on sid

[Joe]

On Mon, 15 May 2023 22:18:12 +0200
Christoph Brinkhaus  wrote:

> Am Mon, May 15, 2023 at 08:57:38PM +0100 schrieb Joe:
> 
> Hello Joe,
> 
> > On Mon, 15 May 2023 19:35:23 +
> > "Andrew M.A. Cater"  wrote:
> >   
> > > On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote:  
> > > > On Mon, 15 May 2023 13:26:06 -0500
> > > > Kent West  wrote:
> > > > 
> > > > > On 5/15/23 11:57, Joe wrote:
> > > > > > Hi,
> > > > > >
> > > > > 
> > > > > Then go from there.
> > > > > 
> > > > Not much to go on so far. Thanks for your suggestions. This
> > > > looks like a bug in an upgrade, but I can't see evidence of
> > > > anyone else seeing it.
> > > > 
> > > > This is the real problem with running sid: not that things
> > > > break, but that they only break for me.
> > > > 
> > > 
> > > If you run sid, you are absolutely expected to be able to resolve
> > > any problems you encounter. If it breaks, you get to keep both
> > > pieces. That's the contract with sid, more than with the other
> > > tranches of Debian (which comes with no overall warranty).
> > > 
> > > If you want increased stability and less shiny new stuff, you run
> > > stable or, if you feel able to help debug and develop it, testing.
> > > 
> > > Them's the breaks: and, as ever, DontBreakDebian by mixing
> > > different suites.
> > >   
> > 
> > Yes, I know all that, I've been running sid since sarge was stable,
> > and only had to reinstall twice in that time.  
> 
> One idea is to try a minimalistic window manager as twm to find out if
> the issue is related to xfce.

OK, thank you, busy now, will try later.
> 
> The second idea could be to run apt-get autoremove - but I am not sure
> if this is a good idea for a non standard Debian installation. For the
> standard installations it is recommended to get rid of outdated
> libraries. But since you seem to be a long time Debian user I do not
> tell you anything new.
> 

I did that after the big update, as a kernel was involved and
significant space could be recovered.

Thanks.

-- 
Joe

Re: Mouse trouble on sid

[Kent West]

On Mon, May 15, 2023 at 2:16 PM Joe  wrote:

> On Mon, 15 May 2023 13:26:06 -0500
> Kent West  wrote:
>
> > On 5/15/23 11:57, Joe wrote:
> > > Hi,
> > >
> > > Upgraded sid two days ago for the first time for a week or so. Today
> > > have serious mouse problems. Xfce on AMD. First thing tried of
> > > course was another mouse, just the same.
> > >
> > > The computer is barely usable in this state. There were too many
> > > packages upgraded, including the kernel, to be able to narrow down
> > > the culprit or attempt a rollback, well over 100. Google tells me
> > > various things about making the mouse do things, but they all seem
> > > to involve some extra mouse tweak package, none of which I have
> > > installed.
> >
> >
> > I would boot into the CMOS/BIOS/System Setup, and make sure the mouse
> > works properly there (assuming your hardware has such a setup).
>
> No mouse pointer there.
> >
> > I would try a different (new) user.
>
> Exactly the same.
> >
> > I would try in console-mode only (may have to install 'gpm').
>
> Yes, mouse pointer present in console with gpm running, but I can't
> tell if there's any misbehaviour, it doesn't actually do much. It
> selects in mc, but not in aptitude.
> >
> > Then go from there.
> >
> Not much to go on so far. Thanks for your suggestions. This looks like
> a bug in an upgrade, but I can't see evidence of anyone else seeing it.
>
> This is the real problem with running sid: not that things break, but
> that they only break for me.
>
> --
> Joe
>
>
Do you have a new lamp on your computer desk that's putting out EM?

Is your mouse wireless or wired? Try a different USB port?

-- 
Kent West<")))><
IT Support / Client Support
Abilene Christian University
Westing Peacefully - http://kentwest.blogspot.com

Re: Mouse trouble on sid

[Kent West]

On Mon, May 15, 2023 at 2:16 PM Joe  wrote:

> On Mon, 15 May 2023 13:26:06 -0500
> Kent West  wrote:
>
> > On 5/15/23 11:57, Joe wrote:
> > > Hi,
> > >
> > > Upgraded sid two days ago for the first time for a week or so. Today
> > > have serious mouse problems. Xfce on AMD. First thing tried of
> > > course was another mouse, just the same.
> > >
> > > The computer is barely usable in this state. There were too many
> > > packages upgraded, including the kernel, to be able to narrow down
> > > the culprit or attempt a rollback, well over 100. Google tells me
> > > various things about making the mouse do things, but they all seem
> > > to involve some extra mouse tweak package, none of which I have
> > > installed.
> >
> >
> > I would boot into the CMOS/BIOS/System Setup, and make sure the mouse
> > works properly there (assuming your hardware has such a setup).
>
> No mouse pointer there.
> >
> > I would try a different (new) user.
>
> Exactly the same.
> >
> > I would try in console-mode only (may have to install 'gpm').
>
> Yes, mouse pointer present in console with gpm running, but I can't
> tell if there's any misbehaviour, it doesn't actually do much. It
> selects in mc, but not in aptitude.
> >
> > Then go from there.
> >
> Not much to go on so far. Thanks for your suggestions. This looks like
> a bug in an upgrade, but I can't see evidence of anyone else seeing it.
>
> This is the real problem with running sid: not that things break, but
> that they only break for me.
>
> --
> Joe
>
>
I should have also suggested a different window manager:

# taskselect

Another console-based app in which the mouse should function is links2.

-- 
Kent West<")))><
IT Support / Client Support
Abilene Christian University
Westing Peacefully - http://kentwest.blogspot.com

Re: Mouse trouble on sid

[Stefan Monnier]

> It's just the problems I get don't seem to happen to anyone else. But
> then I suppose, like Land Rovers, there's no two identical sid
> installations anywhere.

That's indeed a downside of Debian's package management where the set of
packages (and their versions) installed just before an upgrade can have
a vast impact on the set of packages you end up with.

In systems like Guix/Nix the set of packages you end up with is uniquely
determined by the "specification" of your system.  In such a system,
upgrading just computes the new set of packages that should be present
(regardless of those currently installed) and then figures out how to
change the current system to get there.


Stefan

Re: Mouse trouble on sid

[Christoph Brinkhaus]

Am Mon, May 15, 2023 at 08:57:38PM +0100 schrieb Joe:

Hello Joe,

> On Mon, 15 May 2023 19:35:23 +
> "Andrew M.A. Cater"  wrote:
> 
> > On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote:
> > > On Mon, 15 May 2023 13:26:06 -0500
> > > Kent West  wrote:
> > >   
> > > > On 5/15/23 11:57, Joe wrote:  
> > > > > Hi,
> > > > >  
> > > > 
> > > > Then go from there.
> > > >   
> > > Not much to go on so far. Thanks for your suggestions. This looks
> > > like a bug in an upgrade, but I can't see evidence of anyone else
> > > seeing it.
> > > 
> > > This is the real problem with running sid: not that things break,
> > > but that they only break for me.
> > >   
> > 
> > If you run sid, you are absolutely expected to be able to resolve any
> > problems you encounter. If it breaks, you get to keep both pieces.
> > That's the contract with sid, more than with the other tranches of
> > Debian (which comes with no overall warranty).
> > 
> > If you want increased stability and less shiny new stuff, you run
> > stable or, if you feel able to help debug and develop it, testing.
> > 
> > Them's the breaks: and, as ever, DontBreakDebian by mixing different
> > suites.
> > 
> 
> Yes, I know all that, I've been running sid since sarge was stable, and
> only had to reinstall twice in that time.

One idea is to try a minimalistic window manager as twm to find out if
the issue is related to xfce.

The second idea could be to run apt-get autoremove - but I am not sure
if this is a good idea for a non standard Debian installation. For the
standard installations it is recommended to get rid of outdated
libraries. But since you seem to be a long time Debian user I do not
tell you anything new.

> It's just the problems I get don't seem to happen to anyone else. But
> then I suppose, like Land Rovers, there's no two identical sid
> installations anywhere.

I like that image.
Land Rovers are the world best car for their purpose!
They are legends forever.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: Mouse trouble on sid

[Andrew M.A. Cater]

On Mon, May 15, 2023 at 08:15:42PM +0100, Joe wrote:
> On Mon, 15 May 2023 13:26:06 -0500
> Kent West  wrote:
> 
> > On 5/15/23 11:57, Joe wrote:
> > > Hi,
> > >
> > 
> > Then go from there.
> > 
> Not much to go on so far. Thanks for your suggestions. This looks like
> a bug in an upgrade, but I can't see evidence of anyone else seeing it.
> 
> This is the real problem with running sid: not that things break, but
> that they only break for me.
> 

If you run sid, you are absolutely expected to be able to resolve any
problems you encounter. If it breaks, you get to keep both pieces.
That's the contract with sid, more than with the other tranches of
Debian (which comes with no overall warranty).

If you want increased stability and less shiny new stuff, you run stable
or, if you feel able to help debug and develop it, testing.

Them's the breaks: and, as ever, DontBreakDebian by mixing different suites.

Andy Cater

> -- 
> Joe
> 

Re: Mouse trouble on sid

[Kent West]

On 5/15/23 11:57, Joe wrote:

Hi,

Upgraded sid two days ago for the first time for a week or so. Today
have serious mouse problems. Xfce on AMD. First thing tried of course
was another mouse, just the same.

The computer is barely usable in this state. There were too many
packages upgraded, including the kernel, to be able to narrow down the
culprit or attempt a rollback, well over 100. Google tells me various
things about making the mouse do things, but they all seem to involve
some extra mouse tweak package, none of which I have installed.



I would boot into the CMOS/BIOS/System Setup, and make sure the mouse 
works properly there (assuming your hardware has such a setup).


I would try a different (new) user.

I would try in console-mode only (may have to install 'gpm').

Then go from there.

--

Kent

Re: Trouble with ansible and apt. Is this a known problem?

[Nathanael Schweers]

David Wright  writes:

On Fri 25 Nov 2022 at 15:13:48 (+0100), Nathanael Schweers 
wrote:
> We need to know the versions of the (relevant) packages on 
> your system.


Sorry, I have the ones currently in bullseye.  I’m afraid I am 
not at
said machine at the moment and won’t be for the weekend.  I’ll 
post more

next week.


> BTW you started this thread with "I recently installed Debian 
> Bullseye
> on my desktop machine, having previously used Debian sid." We 
> need to
> know whether the last part of that sentence is of any 
> relevance, or

> just an aside.

That was just there to indicate that this works perfectly fine 
on sid.
I have another machine (which I’m using at the moment), which 
runs sid

without any of the problems I’ve described here.


What worried me was that you might, on the desktop machine, have
carried over configuration files in /home from the sid version
to bullseye. Your mentioning since, that there are some files
(I know not what) in ~/.local/bin/ make that a reasonable 
question

to ask.


I started writing a reply to this about how I checked and 
re-checked for any such files.  I was about to check the output of 
`ansible-playbook --version`, both in `$HOME/.local/bin` and in 
`/usr/bin`.  Then it hit me, that ansible is using more files than 
I anticipated.  Removing these fixed my issue!


Many many thousand thanks to you and everyone else who helped me 
with this!


Kind regards,
Nathanael

Re: Trouble with ansible and apt. Is this a known problem?

[David Wright]

On Fri 25 Nov 2022 at 15:13:48 (+0100), Nathanael Schweers wrote:
> > We need to know the versions of the (relevant) packages on your system.
> 
> Sorry, I have the ones currently in bullseye.  I’m afraid I am not at
> said machine at the moment and won’t be for the weekend.  I’ll post more
> next week.
> 
> 
> > BTW you started this thread with "I recently installed Debian Bullseye
> > on my desktop machine, having previously used Debian sid." We need to
> > know whether the last part of that sentence is of any relevance, or
> > just an aside.
> 
> That was just there to indicate that this works perfectly fine on sid.
> I have another machine (which I’m using at the moment), which runs sid
> without any of the problems I’ve described here.

What worried me was that you might, on the desktop machine, have
carried over configuration files in /home from the sid version
to bullseye. Your mentioning since, that there are some files
(I know not what) in ~/.local/bin/ make that a reasonable question
to ask.

Cheers,
David.

Re: Re: Trouble with ansible and apt. Is this a known problem?

[Nathanael Schweers]

> We also need to know what happened between the "I recently installed Debian" 
> statement and your "suddenly 2 days ago Ansible..." statement.

I’m not quite sure I follow.  I put that in my message to indicate that
it was running fine on sid.  It still is, in fact, on another machine.

Between installing Debian Bullseye and encountering said problems
ansible worked fine.  While debugging this (but before I posted to this
list) I realized that I had a pip installation in ~/.local/bin/.  I have
no idea where that came from.  Updating the pip installation eventually
fixed my issues, but removing it still causes the same problems.

> The python runtime messages probably indicate a missing variable. But have 
> you determined that is the actual error? And from where it is missing?

That python3-cryptography has the bug that this particular field is
missing is known.  I would have expected that to be in a version not in
Bullseye.  As I’ve mentioned in another answer I’ll take a look at the
exact versions installed when I get back to the machine in question next week.

Cheers,
Nathanael

Re: Re: Trouble with ansible and apt. Is this a known problem?

[Nathanael Schweers]

> We need to know the versions of the (relevant) packages on your system.

Sorry, I have the ones currently in bullseye.  I’m afraid I am not at
said machine at the moment and won’t be for the weekend.  I’ll post more
next week.


> BTW you started this thread with "I recently installed Debian Bullseye
> on my desktop machine, having previously used Debian sid." We need to
> know whether the last part of that sentence is of any relevance, or
> just an aside.

That was just there to indicate that this works perfectly fine on sid.
I have another machine (which I’m using at the moment), which runs sid
without any of the problems I’ve described here.

Cheers,
Nathanael.

Re: Trouble with ansible and apt. Is this a known problem?

[Nicholas Geovanis]

On Wed, Nov 23, 2022, 5:26 PM David Wright  wrote:

> On Wed 23 Nov 2022 at 20:18:43 (+0100), Nathanael Schweers wrote:
> > > It doesn't look like this exact problem is known at
> https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue=issues,
> but there are a few suggestions among the matching bugs.
> >
> > > One suggestion appears to be that your python module "cryptography" is
> too new for Ansible. You don't state how you installed Ansible, but you
> might find installing it into a virtualenv is more reliable.
> >
> > I installed ansible from apt.  I therefore wonder how the debian package
> > for `python3-cryptography` can be too new for ansible, which is also
> > installed via apt, not pip.
> >
> > I removed the pip installation from my user’s home directory and even
> > re-installed all already installed python packages on my system, but I
> > still have the same problem.  Is this actually broken on debian at the
> moment?
>
> We need to know the versions of the (relevant) packages on your system.
>
> BTW you started this thread with "I recently installed Debian Bullseye
> on my desktop machine, having previously used Debian sid." We need to
> know whether the last part of that sentence is of any relevance, or
> just an aside.
>

We also need to know what happened between the "I recently installed
Debian" statement and your "suddenly 2 days ago Ansible..." statement.

The python runtime messages probably indicate a missing variable. But have
you determined that is the actual error? And from where it is missing?

Cheers,
> David.
>

Re: Trouble with ansible and apt. Is this a known problem?

[David Wright]

On Wed 23 Nov 2022 at 20:18:43 (+0100), Nathanael Schweers wrote:
> > It doesn't look like this exact problem is known at 
> > https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue=issues,
> >  but there are a few suggestions among the matching bugs.
> 
> > One suggestion appears to be that your python module "cryptography" is too 
> > new for Ansible. You don't state how you installed Ansible, but you might 
> > find installing it into a virtualenv is more reliable.
> 
> I installed ansible from apt.  I therefore wonder how the debian package
> for `python3-cryptography` can be too new for ansible, which is also
> installed via apt, not pip.
> 
> I removed the pip installation from my user’s home directory and even
> re-installed all already installed python packages on my system, but I
> still have the same problem.  Is this actually broken on debian at the moment?

We need to know the versions of the (relevant) packages on your system.

BTW you started this thread with "I recently installed Debian Bullseye
on my desktop machine, having previously used Debian sid." We need to
know whether the last part of that sentence is of any relevance, or
just an aside.

Cheers,
David.

Re: Re: Trouble with ansible and apt. Is this a known problem?

[Nathanael Schweers]

> It doesn't look like this exact problem is known at 
> https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue=issues,
>  but there are a few suggestions among the matching bugs.

> One suggestion appears to be that your python module "cryptography" is too 
> new for Ansible. You don't state how you installed Ansible, but you might 
> find installing it into a virtualenv is more reliable.

I installed ansible from apt.  I therefore wonder how the debian package
for `python3-cryptography` can be too new for ansible, which is also
installed via apt, not pip.

I removed the pip installation from my user’s home directory and even
re-installed all already installed python packages on my system, but I
still have the same problem.  Is this actually broken on debian at the moment?

Kind regards,
Nathanael

Re: Trouble with ansible and apt. Is this a known problem?

[Darac Marjal]

On 21/11/2022 08:59, Nathanael Schweers wrote:

Hello people,

I recently installed Debian Bullseye on my desktop machine, having 
previously used Debian sid.


So far it all went well.  Yet two days ago, ansible suddenly reported 
the following message when attempting to use either the `apt` or 
`package` builtin.


fatal: [schweers-pc]: FAILED! => changed=false
 module_stderr: |-
   Shared connection to schweers-pc closed.
 module_stdout: |2-

   Traceback (most recent call last):
 File 
"/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 102, in 

   _ansiballz_main()
 File 
"/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 94, in _ansiballz_main

   invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
 File 
"/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 40, in invoke_module
   runpy.run_module(mod_name='ansible.modules.apt', 
init_globals=None, run_name='__main__', alter_sys=True)

 File "/usr/lib/python3.9/runpy.py", line 210, in run_module
   return _run_module_code(code, init_globals, run_name,    
mod_spec)

 File "/usr/lib/python3.9/runpy.py", line 97, in _run_module_code
   _run_code(code, mod_globals, init_globals,
 File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
   exec(code, run_globals)
 File 
"/tmp/ansible_ansible.legacy.apt_payload_og4qifjt/ansible_ansible.legacy.apt_payload.zip/ansible/modules/apt.py", 
 line 302, in 
 File "", line 1007, in  
_find_and_load
 File "", line 986, in 
_find_and_load_unlocked

 File "", line 664, in _load_unlocked
 File "", line 627, in 
_load_backward_compatible

 File "", line 259, in load_module
 File 
"/tmp/ansible_ansible.legacy.apt_payload_og4qifjt/ansible_ansible.legacy.apt_payload.zip/ansible/module_utils/urls.py", 
 line 115, in 
 File 
"/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",  
line 50, in 

   import OpenSSL.SSL
 File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py",  
line 8, in 

   from OpenSSL import crypto, SSL
 File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 
1556, in 

   class X509StoreFlags(object):
 File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 
1577, in X509StoreFlags

   CB_ISSUER_CHECK = _lib.X509_V_FLAG_CB_ISSUER_CHECK
   AttributeError: module 'lib' has no attribute 
'X509_V_FLAG_CB_ISSUER_CHECK'

 msg: |-
   MODULE FAILURE
   See stdout/stderr for the exact error
 rc: 1


Note that it does not matter that the package in question is already 
installed.


I have tried to reinstall `python3-urllibs`, `python3-apt` and 
`python3-openssl` yet to no avail.


Is this a known problem?


It doesn't look like this exact problem is known at 
https://github.com/search?q=org%3Aansible+X509_V_FLAG_CB_ISSUER_CHECK+is%3Aissue=issues, 
but there are a few suggestions among the matching bugs.


One suggestion appears to be that your python module "cryptography" is 
too new for Ansible. You don't state how you installed Ansible, but you 
might find installing it into a virtualenv is more reliable.





Kind regards,
Nathanael



OpenPGP_signature
Description: OpenPGP digital signature

Trouble with ansible and apt. Is this a known problem?

[Nathanael Schweers]

Hello people,

I recently installed Debian Bullseye on my desktop machine, having 
previously used Debian sid.


So far it all went well.  Yet two days ago, ansible suddenly 
reported the following message when attempting to use either the 
`apt` or `package` builtin.


fatal: [schweers-pc]: FAILED! => changed=false
 module_stderr: |-
   Shared connection to schweers-pc closed.
 module_stdout: |2-

   Traceback (most recent call last):
 File 
 "/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 102, in 

   _ansiballz_main()
 File 
 "/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 94, in _ansiballz_main

   invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
 File 
 "/home/schweers/.ansible/tmp/ansible-tmp-1669020286.4378655-35342-213285731346074/AnsiballZ_apt.py", 
 line 40, in invoke_module
   runpy.run_module(mod_name='ansible.modules.apt', 
   init_globals=None, run_name='__main__', alter_sys=True)

 File "/usr/lib/python3.9/runpy.py", line 210, in run_module
   return _run_module_code(code, init_globals, run_name, 
   mod_spec)
 File "/usr/lib/python3.9/runpy.py", line 97, in 
 _run_module_code

   _run_code(code, mod_globals, init_globals,
 File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
   exec(code, run_globals)
 File 
 "/tmp/ansible_ansible.legacy.apt_payload_og4qifjt/ansible_ansible.legacy.apt_payload.zip/ansible/modules/apt.py", 
 line 302, in 
 File "", line 1007, in 
 _find_and_load
 File "", line 986, in 
 _find_and_load_unlocked
 File "", line 664, in 
 _load_unlocked
 File "", line 627, in 
 _load_backward_compatible

 File "", line 259, in load_module
 File 
 "/tmp/ansible_ansible.legacy.apt_payload_og4qifjt/ansible_ansible.legacy.apt_payload.zip/ansible/module_utils/urls.py", 
 line 115, in 
 File 
 "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
 line 50, in 

   import OpenSSL.SSL
 File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", 
 line 8, in 

   from OpenSSL import crypto, SSL
 File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", 
 line 1556, in 

   class X509StoreFlags(object):
 File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", 
 line 1577, in X509StoreFlags

   CB_ISSUER_CHECK = _lib.X509_V_FLAG_CB_ISSUER_CHECK
   AttributeError: module 'lib' has no attribute 
   'X509_V_FLAG_CB_ISSUER_CHECK'

 msg: |-
   MODULE FAILURE
   See stdout/stderr for the exact error
 rc: 1


Note that it does not matter that the package in question is 
already installed.


I have tried to reinstall `python3-urllibs`, `python3-apt` and 
`python3-openssl` yet to no avail.


Is this a known problem?

Kind regards,
Nathanael

Re: pavucontrol configuration trouble

[Curt]

On 2022-07-16, Thomas George  wrote:
>   I set the GP107GL High Definition Audio Controller profile to off but 
> it continually reverts to High Definition HDMI Output which overrides 
> analog output to my external speakers.
>
> Today I found it impossible to turn this off. The off option is there 
> put when I try to scroll down to it the option window closes before I 
> can reach it.
>
> Is there some way to permanently turn off this controller?
>
>
>
>

"The option window closes before I can reach it" lies beyond the purview
of my intelligence but seems particularly infuriating (if somehow
*drôle* to the casual observer that is this humble correspondent).

I've read of people, confronted with similar problems to your own,
working around the unwanted switching of output devices by commenting
out

 load-module module-switch-on-port-available
 load-module module-switch-on-connect

in /etc/pulse/default.pa

Re: pavucontrol configuration trouble

[Hans]

Am Samstag, 16. Juli 2022, 17:30:57 CEST schrieb Thomas George:
Just an idea for a BAD workaround: Do set your configuration to you needs, if 
it works, just edit the rights of the confiuration file to read only, so that 
the application is no more able to change it. BAD trick, this is very clear to 
me, but sometimes it is working. 

Best

Hans
>   I set the GP107GL High Definition Audio Controller profile to off but
> it continually reverts to High Definition HDMI Output which overrides
> analog output to my external speakers.
> 
> Today I found it impossible to turn this off. The off option is there
> put when I try to scroll down to it the option window closes before I
> can reach it.
> 
> Is there some way to permanently turn off this controller?

pavucontrol configuration trouble

[Thomas George]

 I set the GP107GL High Definition Audio Controller profile to off but 
it continually reverts to High Definition HDMI Output which overrides 
analog output to my external speakers.


Today I found it impossible to turn this off. The off option is there 
put when I try to scroll down to it the option window closes before I 
can reach it.


Is there some way to permanently turn off this controller?

Re: adding trouble on the trouble (using apt upgrade)

[Patrice Duroux]

ps: sorry, on a Debian Sid system for sure.

Le lun. 14 mars 2022 à 19:41, Patrice Duroux  a
écrit :

>
> Hi,
>
> Since some versions ago, apt/dpkg(?) is stopping its process (upgrade
> here) whatever the packaging trouble it is facing. But in some cases, it
> may leave the system more broken than it would become just by 'skipping'
> the troubling package.
> For instance, in the upgrading transaction list were some ldap related
> packages that were left not working, mainly the sudo-ldap in my case was
> not functional before completing the process by  'apt -f install' or 'dpkg
> --configure --pending'. But for that I normally use sudo. By chance I can
> use 'su -' ;-)
>
> I suspect that I am not the only one to face such a situation.
> Is it something expected with new dpkg versions? Or is this already the
> subject of a bug report or have to be reported to dpkg?
>
> Regards,
> Patrice
>
> [...]
> Dépaquetage de xserver-xorg-input-wacom (1.0.0-1) sur (0.34.99.1-1+b1) ...
> Préparation du dépaquetage de .../106-gnupg-utils_2.2.27-3+b1_amd64.deb ...
> Dépaquetage de gnupg-utils (2.2.27-3+b1) sur (2.2.27-3) ...
> Des erreurs ont été rencontrées pendant l'exécution :
>  /tmp/apt-dpkg-install-wr0Tro/051-nodejs_12.22.10~dfsg-1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>

adding trouble on the trouble (using apt upgrade)

[Patrice Duroux]

Hi,

Since some versions ago, apt/dpkg(?) is stopping its process (upgrade here)
whatever the packaging trouble it is facing. But in some cases, it may
leave the system more broken than it would become just by 'skipping' the
troubling package.
For instance, in the upgrading transaction list were some ldap related
packages that were left not working, mainly the sudo-ldap in my case was
not functional before completing the process by  'apt -f install' or 'dpkg
--configure --pending'. But for that I normally use sudo. By chance I can
use 'su -' ;-)

I suspect that I am not the only one to face such a situation.
Is it something expected with new dpkg versions? Or is this already the
subject of a bug report or have to be reported to dpkg?

Regards,
Patrice

[...]
Dépaquetage de xserver-xorg-input-wacom (1.0.0-1) sur (0.34.99.1-1+b1) ...
Préparation du dépaquetage de .../106-gnupg-utils_2.2.27-3+b1_amd64.deb ...
Dépaquetage de gnupg-utils (2.2.27-3+b1) sur (2.2.27-3) ...
Des erreurs ont été rencontrées pendant l'exécution :
 /tmp/apt-dpkg-install-wr0Tro/051-nodejs_12.22.10~dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: Trouble using SDXC 128GB card

[Musbur]

Hello all, thanks for the replies to this issue. I currently don't have 
the time to delve into this any further, but I did format the card in my 
camera and took a few 100 MB of video on it. The video plays back fine 
on the camera itself, also after turning the camera off and removing and 
re-inserting the card. So the card is OK, it just doesn't work on my 
Lenovo T480s in both Debian 11 and Windows 10. I can write data to the 
raw device (i.e., /dev/hdb) but it reads back only garbage, without 
getting any I/O error. I suspect it has to do with the computer's 
hardware. Still weird, given that SDHC cards work fine, and this is a 
fairly recent machine with a brand-new BIOS update. I'll procure another 
card reader and report back.


Am 26.10.2021 20:08 schrieb Dan Ritter:

Musbur wrote:

Hello,

I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
Pro 128GB SDXC card for my digital camera, but I quickly found out 
that
the system can't work with that card. It show up as /dev/sdb, I can 
use

fdisk and everything without error, but when remove and re-insert the
card, the partition table is gone. When I boot the computer in Win10
(latest version), the card shows up as 'SDXC' but cannot be accessed.
The camera can format, read and write just fine.

According to the specs, the builtin card reader of the T480s is SDXC
compatible. Is there a driver for Linux that can make this card work?
The BIOS of the computer has just been updated a week ago. Is the
hardware just not compatible?

Needless to say, my SDHC cards (up to 32GB) work fine in this machine.


It's is quite plausible that you have a counterfeit card, with
an actual capacity of 8-16GB.

Try this (assuming it's still /dev/sdb when you plug it in):

mkfs.ext4 /dev/sdb
mkdir /mnt/tmpcrd
mount /dev/sdb /mnt/tmpcrd

Now download something big, like

wget
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.1.0-amd64-netinst.iso

which is 378MB.

for i in `seq 1 200`; do cp debian-11.1.0-amd64-netinst.iso \
/mnt/tmpcrd/file.$i; done

That will get you 200 files on the SD card, each 378MB, for a total of 
about

75,600 MB, which is more than half the capacity of the disk.

Next:

sync
umount /dev/sdb

pull the card out, pop it back in.

mount it at /mnt/tmpcrd again.

Debian says the SHA256 hash of that file is
02257c3ec27e45d9f022c181a69b59da67e5c72871cdb4f9a69db323a1fad58093f2e69702d29aa98f5f65e920e0b970d816475a5a936e1f3bf33832257b7e92

so let's calculate it for the last 20 files:

for i in `seq 180 200`; do sha256sum /mnt/tmpcrd/file.$i; done

You should get 20 copies of the same hash as above. If you don't
-- you have a a defective, possibly counterfeit card.

-dsr-

Re: Trouble using SDXC 128GB card

[Dieter Rohlfing]

Am Tue, 26 Oct 2021 15:41:33 +
schrieb Musbur :

>I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
>Pro 128GB SDXC card for my digital camera, but I quickly found out that
>the system can't work with that card.
>.
>The camera can format, read and write just fine.

Perhaps this link

https://github.com/ThomasKaiser/Knowledge/blob/master/articles/A1_and_A2_rated_SD_cards.md#application-performance-class-2-a2

may explain, why you have these problems.

Specially the following text is interesting:

>Application Performance Class 2 (A2)
>A2 promises even better performance with 4000/2000 read/write IOPS
>minimum but there's a problem since as outlined by the SD Association A2
>cards show "much higher performance than A1 performance by using
>functions of Command Queuing and Cache".
>
>Cache and Command Queuing require host (driver) support since the host
>needs to activate those new features first. The cache feature on A2 rated
>cards makes use of volatile RAM on the card requiring the host to learn
>new commands to issue flushing the cache (involving the risk of data
>losses -- for details see especially chapter 4.17 in Physical Layer
>Simplified Specification 6.0)

For my raspi-like hosts I avoid to buy A2 cards. With my A1 sdxc cards I
have no problems (neither with a built-in card reader nor an USB card
reader).

Re: Trouble using SDXC 128GB card

[Anssi Saari]

Musbur  writes:

> According to the specs, the builtin card reader of the T480s is SDXC
> compatible. Is there a driver for Linux that can make this card work?
> The BIOS of the computer has just been updated a week ago. Is the
> hardware just not compatible?

As Windows 10 can't access the card either then it seems likely your
hardware is not compatible. Curious though. For example,
https://www.notebookcheck.net/First-Impressions-Lenovo-ThinkPad-T480s-i5-WQHD-Laptop.284832.0.html
tested SDXC card performance on T480s. I guess it's possible your
specific T480s has a different card reader. Maybe you can check the
laptop's specific configuration with its serial number?

Well, external card readers are cheap and one assumes your camera can
connect to the PC with USB.

Re: Trouble using SDXC 128GB card

[David Christensen]

On 10/26/21 8:41 AM, Musbur wrote:

Hello,

I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
Pro 128GB SDXC card for my digital camera, but I quickly found out that
the system can't work with that card. It show up as /dev/sdb, I can use
fdisk and everything without error, but when remove and re-insert the
card, the partition table is gone. When I boot the computer in Win10
(latest version), the card shows up as 'SDXC' but cannot be accessed.
The camera can format, read and write just fine.

According to the specs, the builtin card reader of the T480s is SDXC
compatible. Is there a driver for Linux that can make this card work?
The BIOS of the computer has just been updated a week ago. Is the
hardware just not compatible?

Needless to say, my SDHC cards (up to 32GB) work fine in this machine.



Please post a complete console session (prompts displayed, commands 
entered, output displayed) that demonstrates the issues.



David

Re: Trouble using SDXC 128GB card

[David Wright]

On Tue 26 Oct 2021 at 15:41:33 (+), Musbur wrote:
> I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
> Pro 128GB SDXC card for my digital camera, but I quickly found out that
> the system can't work with that card. It show up as /dev/sdb, I can use
> fdisk and everything without error, but when remove and re-insert the
> card, the partition table is gone. When I boot the computer in Win10
> (latest version), the card shows up as 'SDXC' but cannot be accessed.
> The camera can format, read and write just fine.

Perhaps the first thing to figure out is the filesystem being used
by the camera, otherwise I assume the card is useless. The default fs
for such a card is exFAT, and the camera might just force that to
be the case if it dislikes what you feed it.

> According to the specs, the builtin card reader of the T480s is SDXC
> compatible. Is there a driver for Linux that can make this card work?
> The BIOS of the computer has just been updated a week ago. Is the
> hardware just not compatible?

The kernels in bullseye support exFAT, but older releases will require
the exfat-fuse and exfat-utils packages. Apparently bullseye can still
use exfat-fuse with the new exfatprogs package, but I've not tried
that.¹

> Needless to say, my SDHC cards (up to 32GB) work fine in this machine.

Yes, because they're probably formatted as vfat.

¹ I toyed with exFAT as a Windows/linux shared backup format, but the
  advantages weren't sufficient to counter the complications.

Cheers,
David.

Re: Trouble using SDXC 128GB card

[Dan Ritter]

Musbur wrote: 
> Hello,
> 
> I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
> Pro 128GB SDXC card for my digital camera, but I quickly found out that
> the system can't work with that card. It show up as /dev/sdb, I can use
> fdisk and everything without error, but when remove and re-insert the
> card, the partition table is gone. When I boot the computer in Win10
> (latest version), the card shows up as 'SDXC' but cannot be accessed.
> The camera can format, read and write just fine.
> 
> According to the specs, the builtin card reader of the T480s is SDXC
> compatible. Is there a driver for Linux that can make this card work?
> The BIOS of the computer has just been updated a week ago. Is the
> hardware just not compatible?
> 
> Needless to say, my SDHC cards (up to 32GB) work fine in this machine.

It's is quite plausible that you have a counterfeit card, with
an actual capacity of 8-16GB.

Try this (assuming it's still /dev/sdb when you plug it in):

mkfs.ext4 /dev/sdb
mkdir /mnt/tmpcrd
mount /dev/sdb /mnt/tmpcrd

Now download something big, like 

wget 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.1.0-amd64-netinst.iso

which is 378MB.

for i in `seq 1 200`; do cp debian-11.1.0-amd64-netinst.iso \
/mnt/tmpcrd/file.$i; done 

That will get you 200 files on the SD card, each 378MB, for a total of about
75,600 MB, which is more than half the capacity of the disk.

Next:

sync
umount /dev/sdb

pull the card out, pop it back in.

mount it at /mnt/tmpcrd again.

Debian says the SHA256 hash of that file is 
02257c3ec27e45d9f022c181a69b59da67e5c72871cdb4f9a69db323a1fad58093f2e69702d29aa98f5f65e920e0b970d816475a5a936e1f3bf33832257b7e92

so let's calculate it for the last 20 files:

for i in `seq 180 200`; do sha256sum /mnt/tmpcrd/file.$i; done

You should get 20 copies of the same hash as above. If you don't
-- you have a a defective, possibly counterfeit card.

-dsr-

Trouble using SDXC 128GB card

[Musbur]

Hello,

I'm using a Lenovo Thinkpad T480s. Recently I bought a SanDisk Extreme
Pro 128GB SDXC card for my digital camera, but I quickly found out that
the system can't work with that card. It show up as /dev/sdb, I can use
fdisk and everything without error, but when remove and re-insert the
card, the partition table is gone. When I boot the computer in Win10
(latest version), the card shows up as 'SDXC' but cannot be accessed.
The camera can format, read and write just fine.

According to the specs, the builtin card reader of the T480s is SDXC
compatible. Is there a driver for Linux that can make this card work?
The BIOS of the computer has just been updated a week ago. Is the
hardware just not compatible?

Needless to say, my SDHC cards (up to 32GB) work fine in this machine.

Re: Trouble connecting to wifi, Debian 11

[David]

On Thu, 14 Oct 2021 at 20:05, kaye n  wrote:

> I've downloaded this
> debian-live-11.1.0-amd64-lxqt+nonfree.iso

It would add useful information to the conversation if you
specify the URL (from where you downloaded it).
If you don't tell, we dont know.

> Are there no sha512sum for the non-free version?
> All I can find in Debian website is this:
> https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/SHA512SUMS

To find the SHA512SUMS, did you try looking in the
same directory from where you downloaded the iso file?

For example, the URL directory:
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/11.1.0-live+nonfree/amd64/iso-hybrid/
contains many files, including:
  debian-live-11.1.0-amd64-lxqt+nonfree.iso
  SHA512SUMS

Re: Trouble connecting to wifi, Debian 11

[kaye n]

On Thu, Oct 14, 2021 at 2:28 AM echo test  wrote:

> Maybe you should use it because that's where you will find a lot of non
> free firmwares.
>
> Check your kernel logs ($> sudo dmesg) , you may find an explicit reason
> why your adapter fails to run properly.
>
> Le mer. 13 oct. 2021 à 18:36, kaye n  a écrit :
>
>>
>>
>> On Wed, Oct 13, 2021, 21:26 Peter Ehlert,  wrote:
>>
>>>
>>> On 10/13/21 6:14 AM, kaye n wrote:
>>> > Hi Friends
>>> >
>>> > I've installed Debian 11 LXQT in my hard drive.
>>> > I noticed connman does not automatically run on startup, which is fine.
>>> >
>>> > I manually open Connman. It can detect my usb wifi adapter because
>>> > under Wireless tab, it says
>>> >
>>> > Wifi technologies: 1 Found,  1 powered
>>> >
>>> > However under the same tab, all these buttons after greyed out:
>>> > Connect, Disconnect, Remove, Rescan
>>> >
>>> > And I cannot see my router on the list below these buttons.
>>> >
>>> > Tried connecting and disconnecting the usb wifi adapter, no change.
>>> >
>>> > Tried using a pricier usb wifi adapter, same thing.
>>> >
>>> > Tried plugging in a different usb port, same thing.
>>> >
>>> > I had very little trouble connecting to wifi on Debian 10 xfce.
>>> >
>>> > Should i just install Debian 11 xfce or is there a solution to this?
>>> >
>>> > 64-bit Debian, by the way.
>>> >
>>> > Also, have the same issue on the live usb Debian 11 - cannot connect
>>> > to wifi.
>>> are you using the nonfree firmware ISO?
>>> >
>>> > Bit off topic, Debian live usb comes with complete libreoffice except
>>> > Base. The installed version on my hard drive has only libreoffice
>>> > Draw, i think.  Is this normal?
>>> >
>>> > Thank you for your time.
>>>
>>
>> No i am not using a non free firmware iso
>>
>
I've downloaded this

debian-live-11.1.0-amd64-lxqt+nonfree.iso

Are there no sha512sum for the non-free version?  All I can find in Debian
website is this:

https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/SHA512SUMS

which is the "free" version, correct?

Thank you

Re: Trouble connecting to wifi, Debian 11

[David Wright]

On Thu 14 Oct 2021 at 00:36:18 (+0800), kaye n wrote:
> On Wed, Oct 13, 2021, 21:26 Peter Ehlert,  wrote:
> > On 10/13/21 6:14 AM, kaye n wrote:
> > >
> > > I've installed Debian 11 LXQT in my hard drive.
> > > I noticed connman does not automatically run on startup, which is fine.

That wouldn't be fine for me.

> > > I manually open Connman. It can detect my usb wifi adapter because
> > > under Wireless tab, it says
> > >
> > > Wifi technologies: 1 Found,  1 powered
> > >
> > > However under the same tab, all these buttons after greyed out:
> > > Connect, Disconnect, Remove, Rescan
> > >
> > > And I cannot see my router on the list below these buttons.
> > >
> > > Tried connecting and disconnecting the usb wifi adapter, no change.
> > >
> > > Tried using a pricier usb wifi adapter, same thing.
> > >
> > > Tried plugging in a different usb port, same thing.
> > >
> > > I had very little trouble connecting to wifi on Debian 10 xfce.
> > >
> > > Should i just install Debian 11 xfce or is there a solution to this?
> > >
> > > 64-bit Debian, by the way.
> > >
> > > Also, have the same issue on the live usb Debian 11 - cannot connect
> > > to wifi.

> > are you using the nonfree firmware ISO?
> 
> No i am not using a non free firmware iso

I was under the impression, unless you've bought something,
that you were using:

 Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
  vendor: Wistron NeWeb driver: bcma-pci-bridge v: N/A port: 2000
  bus ID: 03:00.0 chip ID: 14e4:4727

which would require firmware. There's a wiki page:

https://wiki.debian.org/brcm80211

Most laptops' wifi will require firmware.

Cheers,
David.

Re: Trouble connecting to wifi, Debian 11

[echo test]

Maybe you should use it because that's where you will find a lot of non
free firmwares.

Check your kernel logs ($> sudo dmesg) , you may find an explicit reason
why your adapter fails to run properly.

Le mer. 13 oct. 2021 à 18:36, kaye n  a écrit :

>
>
> On Wed, Oct 13, 2021, 21:26 Peter Ehlert,  wrote:
>
>>
>> On 10/13/21 6:14 AM, kaye n wrote:
>> > Hi Friends
>> >
>> > I've installed Debian 11 LXQT in my hard drive.
>> > I noticed connman does not automatically run on startup, which is fine.
>> >
>> > I manually open Connman. It can detect my usb wifi adapter because
>> > under Wireless tab, it says
>> >
>> > Wifi technologies: 1 Found,  1 powered
>> >
>> > However under the same tab, all these buttons after greyed out:
>> > Connect, Disconnect, Remove, Rescan
>> >
>> > And I cannot see my router on the list below these buttons.
>> >
>> > Tried connecting and disconnecting the usb wifi adapter, no change.
>> >
>> > Tried using a pricier usb wifi adapter, same thing.
>> >
>> > Tried plugging in a different usb port, same thing.
>> >
>> > I had very little trouble connecting to wifi on Debian 10 xfce.
>> >
>> > Should i just install Debian 11 xfce or is there a solution to this?
>> >
>> > 64-bit Debian, by the way.
>> >
>> > Also, have the same issue on the live usb Debian 11 - cannot connect
>> > to wifi.
>> are you using the nonfree firmware ISO?
>> >
>> > Bit off topic, Debian live usb comes with complete libreoffice except
>> > Base. The installed version on my hard drive has only libreoffice
>> > Draw, i think.  Is this normal?
>> >
>> > Thank you for your time.
>>
>
> No i am not using a non free firmware iso
>
>>

Re: Trouble connecting to wifi, Debian 11

[kaye n]

On Wed, Oct 13, 2021, 21:26 Peter Ehlert,  wrote:

>
> On 10/13/21 6:14 AM, kaye n wrote:
> > Hi Friends
> >
> > I've installed Debian 11 LXQT in my hard drive.
> > I noticed connman does not automatically run on startup, which is fine.
> >
> > I manually open Connman. It can detect my usb wifi adapter because
> > under Wireless tab, it says
> >
> > Wifi technologies: 1 Found,  1 powered
> >
> > However under the same tab, all these buttons after greyed out:
> > Connect, Disconnect, Remove, Rescan
> >
> > And I cannot see my router on the list below these buttons.
> >
> > Tried connecting and disconnecting the usb wifi adapter, no change.
> >
> > Tried using a pricier usb wifi adapter, same thing.
> >
> > Tried plugging in a different usb port, same thing.
> >
> > I had very little trouble connecting to wifi on Debian 10 xfce.
> >
> > Should i just install Debian 11 xfce or is there a solution to this?
> >
> > 64-bit Debian, by the way.
> >
> > Also, have the same issue on the live usb Debian 11 - cannot connect
> > to wifi.
> are you using the nonfree firmware ISO?
> >
> > Bit off topic, Debian live usb comes with complete libreoffice except
> > Base. The installed version on my hard drive has only libreoffice
> > Draw, i think.  Is this normal?
> >
> > Thank you for your time.
>

No i am not using a non free firmware iso

>

Re: Trouble connecting to wifi, Debian 11

[Peter Ehlert]

On 10/13/21 6:14 AM, kaye n wrote:

Hi Friends

I've installed Debian 11 LXQT in my hard drive.
I noticed connman does not automatically run on startup, which is fine.

I manually open Connman. It can detect my usb wifi adapter because 
under Wireless tab, it says


Wifi technologies: 1 Found,  1 powered

However under the same tab, all these buttons after greyed out:
Connect, Disconnect, Remove, Rescan

And I cannot see my router on the list below these buttons.

Tried connecting and disconnecting the usb wifi adapter, no change.

Tried using a pricier usb wifi adapter, same thing.

Tried plugging in a different usb port, same thing.

I had very little trouble connecting to wifi on Debian 10 xfce.

Should i just install Debian 11 xfce or is there a solution to this?

64-bit Debian, by the way.

Also, have the same issue on the live usb Debian 11 - cannot connect 
to wifi.

are you using the nonfree firmware ISO?


Bit off topic, Debian live usb comes with complete libreoffice except 
Base. The installed version on my hard drive has only libreoffice 
Draw, i think.  Is this normal?


Thank you for your time.

Trouble connecting to wifi, Debian 11

[kaye n]

Hi Friends

I've installed Debian 11 LXQT in my hard drive.
I noticed connman does not automatically run on startup, which is fine.

I manually open Connman. It can detect my usb wifi adapter because under
Wireless tab, it says

Wifi technologies: 1 Found,  1 powered

However under the same tab, all these buttons after greyed out:
Connect, Disconnect, Remove, Rescan

And I cannot see my router on the list below these buttons.

Tried connecting and disconnecting the usb wifi adapter, no change.

Tried using a pricier usb wifi adapter, same thing.

Tried plugging in a different usb port, same thing.

I had very little trouble connecting to wifi on Debian 10 xfce.

Should i just install Debian 11 xfce or is there a solution to this?

64-bit Debian, by the way.

Also, have the same issue on the live usb Debian 11 - cannot connect to
wifi.

Bit off topic, Debian live usb comes with complete libreoffice except Base.
The installed version on my hard drive has only libreoffice Draw, i think.
Is this normal?

Thank you for your time.

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[tomas]

On Mon, Sep 13, 2021 at 10:59:28PM +0200, Thomas Amm wrote:
> On Mon, 2021-09-06 at 16:46 -0300, Dedeco Balaco wrote:
> 
> > If it is trivial to me setting my mail manager to use the dark
> >  [...]
> > Regards
> > 
> 
> Conrats! You have just made it into everybody's kill file.

A somewhat friendlier answer would go a longer way. Shouting contests
are unnecessary and futile. Moreover, they degrade the mailing list's
quality for everyone.

Maybe the OP really didn't know what they were doing. In any case,
their MUA was doing the correct thing: sending a text part along
with the HTML part as MIME alternative (although we discovered a
bug in the process as well).

You may put whomever you like into your kill file, but wehether
anyone is going to do it is their private business.

Cheers
 - t


signature.asc
Description: Digital signature

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Thomas Amm]

On Mon, 2021-09-06 at 16:46 -0300, Dedeco Balaco wrote:

> If it is trivial to me setting my mail manager to use the dark
>  [...]
> Regards
> 

Conrats! You have just made it into everybody's kill file.

Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright)

[Andrei POPESCU]

On Lu, 06 sep 21, 16:46:24, Dedeco Balaco wrote:
> 
> 
> Em 06/09/2021 14:25, John Hasler escreveu:
> > Curt writes:
> >> I suggest you follow the earlier advice, and set Thunderbird 
> >> to compose your email as plain text
> > Or even as "normal" HTML.
> 
> If it is trivial to me setting my mail manager to use the dark
> background i need, and to make it ignore the (usually default)
> background of color of all HTML messages, why the people in Debian User
> list cannot do it?

If your mail client is sending both html and plain text most subscribers 
will only see the plain text version (unless they go out of their way to 
look at the html version).

> I will not change my setting! I need it. Learn to
> deal with it. Things evolve. Being able to use *bold*, /italic/,
> _underscore_ is a minimum of "new" things that help a lot to compose
> good messages.

You mean like the markup in the text above? :)

(probably added by Thunderbird for the text version)

While I do agree with you somewhat, as far as I'm aware there is no 
agreed upon standard for HTML mail. How the receiving end will display 
your message is very much open to interpretation.

Some mail clients might even "lie" to you and show e.g. a sans font when 
composing, but the receiving end will display that message with a serif 
font (didn't bother to check the source to see which one of them is 
"wrong").

> If Thunderbird has a problem when writing the automatic
> text messages, together with the composed HTML ones, this is a reason to
> _**fix**_ it, not to never use anymore.

There should be a setting in Thunderbird to *not* remove "extra" line 
breaks (or similar) for the text version, please enable it.

> I have installed another mail
> manager in my computer: but it is bad, pretty horrible. It does not show
> HTML messages. It does not compose HTML messages. And it is pretty
> counter intuitive to configure, in several parts. It seems handy, have
> nice things. But if you do not know them, or are not familiar enough
> with "something", to be able to understand it, you cannot use them. Its
> name is Claws Mail. 

Last time I tried it Claws Mail could display (but not compose) HTML 
messages, you might need to enable it and/or install some plugin.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Trouble upgrading Debian (reply to David Wright)

[Richard Hector]

On 7/09/21 5:25 am, John Hasler wrote:

Curt writes:
I suggest you follow the earlier advice, and set Thunderbird 
to compose your email as plain text


Curt didn't write that; I did. Please be careful with your attributions.

I'm intrigued to know how this mistake happened, however. Were you 
perhaps replying to a digest message instead of a normal individual one?


Cheers,
Richard

Re: Partially Solved: OT: Why have I not received any messages from Dedeco (was: Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright))

[rhkramer]

On Tuesday, September 07, 2021 12:27:32 PM rhkra...@gmail.com wrote:
> > Can you add   Resent-From: debian-user@lists.debian.org   to your
> > whitelist? Or isn't it possible to use Resent-From?
> 
> Thanks, I'll have to look into that -- that would be something I have to do
> for / at google and I'm not familiar with what I can do there.  (I'll
> google for [gmail whitelist] and go from there...)

Turns out it was pretty easy to add debian-user to a whitelist (instructions 
below), but no obvious way to specify "Resent-from".  I have now received one 
post by Dedeco, so this might have done the job.



On your gmail webmail page:

   * Click on the gear in the upper right corner -- that should take you to 
the "Settings" page
   * Choose "Filters and Blocked Addresses"
   * Scroll to the bottom
   * Choose "Create a New Filter"
   * Enter the criteria (e.g., email address, ...)
   * Click "Create Filter"
   * Choose action, e.g., "Never send it to Spam"

You can also do things like forwarding an email to somewhere else.

Source:

   * [[https://downtimemonkey.com/blog/how-to-whitelist-an-email-address-in-
gmail.php][Whitelist Email Addresses In Gmail]]; 08 Nov 2018

Blocking IP addresses: there is a way to block IP addresses, but:

   * [[https://support.google.com/a/answer/60751][Google Workspace Admin 
Help]]
`
Add IP addresses to allowlists in Gmail

If you have the legacy free edition of G Suite, upgrade to Google Workspace to 
get this feature. 
'

Re: Partially Solved: OT: Why have I not received any messages from Dedeco (was: Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright))

[Dedeco Balaco]

One or two days after i tried to subscribe using the site, I received a
warning from this list saying that several messages were bounced by
Yahoo. It also said that if more bounces happen, i may be unsubscribed.
So, the subscribing messages i tried to make did not even arrived to my
spam folder - i checked this before trying the command subscription.


Em 07/09/2021 13:27, rhkra...@gmail.com escreveu:
> Thanks for the reply, some responses interspersed below:
> 
> On Tuesday, September 07, 2021 11:07:36 AM David Wright wrote:
>> On Tue 07 Sep 2021 at 08:49:19 (-0400), rhkra...@gmail.com wrote:
>>> -- I don't remember that message very well).
>>
>> Probably like:
>>
>>  "In the last seven days we've seen bounces for the following list:
>>   * debian-user
>>   1 bounce out of 32 mails in one day (3%, kick-score is 80%)
>>   (https://lists.debian.org/bounces/RnYmpd6xf_mNRHfzU2iUYA)
>>
>>   (The link above points to a copy of the latest bounce
>>   and will be valid for seven days.)
>>
>>   If the bounce-rate passes the kick-score, our bounce-detection will
>> forcibly remove your subscription.
> 
> Ahh, yes, that is the message I was thinking of, and the words "bounce" and 
> "kick-score".
> 
>>>  in this case, the messages were
>>> delivered but google decided they were spam.
>>
>> Can you add   Resent-From: debian-user@lists.debian.org   to your
>> whitelist? Or isn't it possible to use Resent-From?
> 
> Thanks, I'll have to look into that -- that would be something I have to do 
> for / at google and I'm not familiar with what I can do there.  (I'll google 
> for [gmail whitelist] and go from there...)
> 

Re: Partially Solved: OT: Why have I not received any messages from Dedeco (was: Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright))

[rhkramer]

Thanks for the reply, some responses interspersed below:

On Tuesday, September 07, 2021 11:07:36 AM David Wright wrote:
> On Tue 07 Sep 2021 at 08:49:19 (-0400), rhkra...@gmail.com wrote:
> > -- I don't remember that message very well).
> 
> Probably like:
> 
>  "In the last seven days we've seen bounces for the following list:
>   * debian-user
>   1 bounce out of 32 mails in one day (3%, kick-score is 80%)
>   (https://lists.debian.org/bounces/RnYmpd6xf_mNRHfzU2iUYA)
> 
>   (The link above points to a copy of the latest bounce
>   and will be valid for seven days.)
> 
>   If the bounce-rate passes the kick-score, our bounce-detection will
> forcibly remove your subscription.

Ahh, yes, that is the message I was thinking of, and the words "bounce" and 
"kick-score".

> >  in this case, the messages were
> > delivered but google decided they were spam.
> 
> Can you add   Resent-From: debian-user@lists.debian.org   to your
> whitelist? Or isn't it possible to use Resent-From?

Thanks, I'll have to look into that -- that would be something I have to do 
for / at google and I'm not familiar with what I can do there.  (I'll google 
for [gmail whitelist] and go from there...)

Re: Partially Solved: OT: Why have I not received any messages from Dedeco (was: Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright))

[David Wright]

On Tue 07 Sep 2021 at 08:49:19 (-0400), rhkra...@gmail.com wrote:

> I occasionally seem to lose other messages (I get the message from the debian-
> user lists about about some (small number of) messages beeing undeliverable  
> in the last day or so (can't remember the term used, and maybe there is a 
> threat to unsubscribe me if it gets worse and continues -- I don't remember 
> that message very well).

Probably like:

 "In the last seven days we've seen bounces for the following list:
  * debian-user
  1 bounce out of 32 mails in one day (3%, kick-score is 80%)
  (https://lists.debian.org/bounces/RnYmpd6xf_mNRHfzU2iUYA)

  (The link above points to a copy of the latest bounce
  and will be valid for seven days.)

  If the bounce-rate passes the kick-score, our bounce-detection will forcibly
  remove your subscription.

> But, my point here is that this is different -- the messages from the debian-
> user list indicate that they (it) got a notification that my message could 
> not 
> be delivered, in this case, the messages were delivered but google decided 
> they were spam.

> Ahh, I should check my gmail spam folder... ahh, there they are -- I guess 
> google decided they are spam

Can you add   Resent-From: debian-user@lists.debian.org   to your
whitelist? Or isn't it possible to use Resent-From?

Cheers,
David.

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[David Wright]

On Tue 07 Sep 2021 at 00:20:26 (-0300), Dedeco Balaco wrote:
> Em 06/09/2021 23:48, Kenneth Parker escreveu:
> > On Mon, Sep 6, 2021 at 7:58 PM Greg Wooledge wrote:
> > > On Mon, Sep 06, 2021 at 04:46:21PM -0300, Dedeco Balaco wrote:
> > > > If it is trivial to me setting my mail manager to use the dark
> > > > background i need, and to make it ignore the (usually default)
> > > > background of color of all HTML messages, why the people in Debian User
> > > > list cannot do it? I will not change my setting! I need it. Learn to
> > > > deal with it.

Perhaps the forums might suit you better than technical mailing lists.

> > > Many people will "deal with it" by deleting your messages and moving
> > > on.  Just so you know.
> > 
> > > For me, your messages seem OK.  Mutt is presenting me with readable
> > > text.  I don't know what other people are seeing.  However, if you're
> > > intentionally flaunting the guidelines and standards that make mailing
> > > lists work, you can expect a smaller audience for your requests.
> > 
> > Greg, what I saw is Rich Text Format [1], different from html.  I
> > suspect Mutt (as well as gmail) presents it as it, without issue.  But,
> > unfortunately, not all email reader software would see it properly.   

As one might expect, mutt can handle multipart/alternative in various
ways, according to how you configure it. AFAICT the emails in question
are sensibly constructed, with text/plain and text/html equivalents.

> My issue happened (this is my conclusion) because my Debian 9 was not
> updated when I followed the steps to change sources.list to those of
> Debian 10. This is something that should be added in Debian
> documentation, in my opinion.

It's already there, as I pointed out and gave the reference for.
In bullseye, it was given even greater prominence by being given
an individual section number.

> It is also important to note that third
> party sources should be disabled, to avoid possible conflicts or
> problems that should be addressed only after the OS upgrade ends
> successfully.

Ditto.

> I also made something much wrong by not rebooting the computer after
> each 'apt upgrade' for the next version. So, i ended up with a computer
> with packages and sources.list of Debian 11, but it was not quite
> that.

That is implicit, in that each upgrade is expected to be followed by a
period during which that version is used. Rebooting ensures that any
new kernel is being used.

It's also explicit, in that a system running the previous version's
kernel is not a "pure" system, and unprepared for the next upgrade.

> So, i remade all steps. And my first steps were to restore my Debian 9
> sources.list, 'apt update' and 'apt upgrade' it.

I don't see how that works. Once you've upgraded by one version,
downgrading it again is a non-trivial operation. But I found it
difficult to follow precisely the steps you took.

> A more detailed story is in the thread i pointed in my first message here:
> 
> https://www.linuxquestions.org/questions/linux-software-2/upgrading-debian-distribution-4175700202/#post6281677

I have already looked at that. There seem to be links to other forums,
debian.org, release notes for a different upgrade, etc. So my post,
later in the day, didn't add anything except emphasis: follow the
Release Notes in full. (It seemed that the mailing list was late in
being invited to the party.)

The problem with following random posts on the internet for upgrading
is that each one generally addresses a particular aspect where that OP
expressed some difficulty, but doesn't give the end-to-end method.

Cheers,
David.

Partially Solved: OT: Why have I not received any messages from Dedeco (was: Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright))

[rhkramer]

I asked and then answered my own question -- google decided the messages from 
Dedeco were spam, with this message when I open one (in google mail):


This message seems dangerous 
Similar messages were used to steal people's personal information. Avoid 
clicking links, downloading attachments, or replying with personal 
information.

Makes me wonder.
I occasionally seem to lose other messages (I get the message from the debian-
user lists about about some (small number of) messages beeing undeliverable  
in the last day or so (can't remember the term used, and maybe there is a 
threat to unsubscribe me if it gets worse and continues -- I don't remember 
that message very well).
But, my point here is that this is different -- the messages from the debian-
user list indicate that they (it) got a notification that my message could not 
be delivered, in this case, the messages were delivered but google decided 
they were spam.
I wonder what criteria google used to decide they were spam?  Do they know 
something we don't know, or is just because he used HTML and somehow google 
knows the list is intended to be plain text?
Draft start of old message below:

I am puzzled.  In my kmail client, I have not received any of the messages 
that people have replied to from Dedeco Balaco .

If I look in the archives, I see them (e.g., there are 4 on 
https://lists.debian.org/debian-user/2021/09/threads.html#00154).

I have never killfiled or blocked anyone.

Ahh, I should check my gmail spam folder... ahh, there they are -- I guess 
google decided they are spam

Interesting.


On Monday, September 06, 2021 10:36:03 PM Kenneth Parker wrote:
> On Mon, Sep 6, 2021 at 3:47 PM Dedeco Balaco 

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Dedeco Balaco]

Em 07/09/2021 03:28, Andrew M.A. Cater escreveu:
> It has been repeated a few times in different
> places that you can't jump a release straightforwardly, so it has to 
> be 9 -> 10 -> 11.
> 

Yes. People in the forum also told me this. But the problem was
something else.

> Having remade all the steps - do you now have a working system now?

Yes, everything seems finee.

Again, thank you all.

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Greg Wooledge]

On Tue, Sep 07, 2021 at 12:20:26AM -0300, Dedeco Balaco wrote:
> My issue happened (this is my conclusion) because my Debian 9 was not
> updated when I followed the steps to change sources.list to those of
> Debian 10. This is something that should be added in Debian
> documentation, in my opinion.

https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html#system-status

  4.2. Checking APT configuration status

  [...]

  This procedure also assumes your system has been updated to the latest
  point release of stretch. If you have not done this or are unsure,
  follow the instructions in Section A.1, “Upgrading your stretch
  system”.

Admittedly, it's a bit hard to find if you're only skimming, but you
should be reading the full release notes before upgrading.

> I also made something much wrong by not rebooting the computer after
> each 'apt upgrade' for the next version.

Well, after the full-upgrade, but this is a good point.  Some of the
services (dbus) require a reboot to restart them.  And of course, you'll
still be on the oldold...stable kernel until you reboot.

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Andrew M.A. Cater]

On Tue, Sep 07, 2021 at 12:20:26AM -0300, Dedeco Balaco wrote:
> 
> 
> Em 06/09/2021 23:48, Kenneth Parker escreveu:
> > 
> > 
> > On Mon, Sep 6, 2021 at 7:58 PM Greg Wooledge  > > wrote:
> > 
> > On Mon, Sep 06, 2021 at 04:46:21PM -0300, Dedeco Balaco wrote:
> > > If it is trivial to me setting my mail manager to use the dark
> > > background i need, and to make it ignore the (usually default)
> > > background of color of all HTML messages, why the people in Debian
> > User
> > > list cannot do it? I will not change my setting! I need it. Learn to
> > > deal with it.
> > 
> > Many people will "deal with it" by deleting your messages and moving
> > on.  Just so you know.
> > 
> > For me, your messages seem OK.  Mutt is presenting me with readable
> > text.  I don't know what other people are seeing.  However, if you're
> > intentionally flaunting the guidelines and standards that make mailing
> > lists work, you can expect a smaller audience for your requests.
> > 
> > Greg, what I saw is Rich Text Format [1], different from html.  I
> > suspect Mutt (as well as gmail) presents it as it, without issue.  But,
> > unfortunately, not all email reader software would see it properly.   
> > 
> > Kenneth Parker
> > 
> > [1] Rich Text Format.  https://en.wikipedia.org/wiki/Rich_Text_Format
> 
> My issue happened (this is my conclusion) because my Debian 9 was not
> updated when I followed the steps to change sources.list to those of
> Debian 10. This is something that should be added in Debian
> documentation, in my opinion. It is also important to note that third
> party sources should be disabled, to avoid possible conflicts or
> problems that should be addressed only after the OS upgrade ends
> successfully.
> 
> I also made something much wrong by not rebooting the computer after
> each 'apt upgrade' for the next version. So, i ended up with a computer
> with packages and sources.list of Debian 11, but it was not quite that.
> So, i remade all steps. And my first steps were to restore my Debian 9
> sources.list, 'apt update' and 'apt upgrade' it.
> 
> A more detailed story is in the thread i pointed in my first message here:
> 
> https://www.linuxquestions.org/questions/linux-software-2/upgrading-debian-distribution-4175700202/#post6281677
> 
> Thank you all.
> 

Hi Dedaco,

I _think_ that the issue of how to upgrade has been covered. 
The release notes cover new features / removed software: the installation
notes cover features of the installation.

https://www.debian.org/releases/bullseye/amd64/release-notes/ has
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#upgrade-to-debian-oldrelease
 
and section 4.2 covers this in detail. The instqallation guide is probably 
not so relevant once you have a running Debian system.

Since the release on June 14th or so, this has been extensively covered
in threads here on this list as people have hit problems but I agree, we
could always do more. It has been repeated a few times in different
places that you can't jump a release straightforwardly, so it has to 
be 9 -> 10 -> 11.

Having remade all the steps - do you now have a working system now?
[I'm busy fighting with a system that hasn't been upgraded in a while
and has flaky hardware at the moment: it's often hard to see where
problems are coming from when you are in the middle of them.]

All the very best, as ever,

Andy Cater

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Kenneth Parker]

On Mon, Sep 6, 2021 at 7:58 PM Greg Wooledge  wrote:

> On Mon, Sep 06, 2021 at 04:46:21PM -0300, Dedeco Balaco wrote:
> > If it is trivial to me setting my mail manager to use the dark
> > background i need, and to make it ignore the (usually default)
> > background of color of all HTML messages, why the people in Debian User
> > list cannot do it? I will not change my setting! I need it. Learn to
> > deal with it.
>
> Many people will "deal with it" by deleting your messages and moving
> on.  Just so you know.
>
> For me, your messages seem OK.  Mutt is presenting me with readable
> text.  I don't know what other people are seeing.  However, if you're
> intentionally flaunting the guidelines and standards that make mailing
> lists work, you can expect a smaller audience for your requests.
>
Greg, what I saw is Rich Text Format [1], different from html.  I suspect
Mutt (as well as gmail) presents it as it, without issue.  But,
unfortunately, not all email reader software would see it properly.

Kenneth Parker

[1] Rich Text Format.  https://en.wikipedia.org/wiki/Rich_Text_Format

Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright)

[Kenneth Parker]

On Mon, Sep 6, 2021 at 3:47 PM Dedeco Balaco 
wrote:

>
>
> Em 06/09/2021 14:25, John Hasler escreveu:
>
> Curt writes:
>
> I suggest you follow the earlier advice, and set Thunderbird
> to compose your email as plain text
>
> Or even as "normal" HTML.
>
> If it is trivial to me setting my mail manager to use the dark background
> i need, and to make it ignore the (usually default) background of color of
> all HTML messages, why the people in Debian User list cannot do it? I will
> not change my setting! I need it. Learn to deal with it. Things evolve.
> Being able to use *bold*, *italic*, *underscore* is a minimum of "new"
> things that help a lot to compose good messages. If Thunderbird has a
> problem when writing the automatic text messages, together with the
> composed HTML ones, this is a reason to **fix** it, not to never use
> anymore. I have installed another mail manager in my computer: but it is
> bad, pretty horrible. It does not show HTML messages. It does not compose
> HTML messages. And it is pretty counter intuitive to configure, in several
> parts. It seems handy, have nice things. But if you do not know them, or
> are not familiar enough with "something", to be able to understand it, you
> cannot use them. Its name is Claws Mail. I bet the most important people in
> this list love it. So, Thunderbird has some problems (and the HTML thing is
> not a problem to me), but it still the best mail manager for me.
>
This comes across as Rich Text Format, a precursor to Microsoft Word.
These files can be sent with a prefix of .rtf, and it is certainly
supported in LibreOffice Writer.  I am not sure how it works with email
lists, though.

Kenneth Parker

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Greg Wooledge]

On Mon, Sep 06, 2021 at 04:46:21PM -0300, Dedeco Balaco wrote:
> If it is trivial to me setting my mail manager to use the dark
> background i need, and to make it ignore the (usually default)
> background of color of all HTML messages, why the people in Debian User
> list cannot do it? I will not change my setting! I need it. Learn to
> deal with it.

Many people will "deal with it" by deleting your messages and moving
on.  Just so you know.

For me, your messages seem OK.  Mutt is presenting me with readable
text.  I don't know what other people are seeing.  However, if you're
intentionally flaunting the guidelines and standards that make mailing
lists work, you can expect a smaller audience for your requests.

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[piorunz]

On 06/09/2021 21:50, Dan Ritter wrote:


Here is reality:

Nobody here is obligated to help you. At all.
If we do, it's out of the goodness of our hearts.
If we don't, it could be:

because we don't know the answer
or
because you are being rude

This is a place where people send questions in plain text and
respond in plain text.

Your response is up to you.

Our responses are up to us.


I agree, we said enough. Good luck to Dedeco Balaco, and goodbye from
us, kind people.

--
With kindest regards, piorunz.

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

Re: (pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Dan Ritter]

Dedeco Balaco wrote: 
> 
> Em 06/09/2021 14:25, John Hasler escreveu:
> > Curt writes:
> >> I suggest you follow the earlier advice, and set Thunderbird 
> >> to compose your email as plain text
> > 
> > Or even as "normal" HTML.
> > 
> 
> If it is trivial to me setting my mail manager to use the dark
> background i need, and to make it ignore the (usually default)
> background of color of all HTML messages, why the people in Debian User
> list cannot do it? I will not change my setting! I need it. Learn to
> deal with it. Things evolve. Being able to use bold, italic, underscore

Here is reality:

Nobody here is obligated to help you. At all.
If we do, it's out of the goodness of our hearts.
If we don't, it could be:

because we don't know the answer
or
because you are being rude

This is a place where people send questions in plain text and
respond in plain text.

Your response is up to you.

Our responses are up to us.

-dsr-

(pure text) Re: Trouble upgrading Debian (reply to David Wright)

[Dedeco Balaco]

Em 06/09/2021 14:25, John Hasler escreveu:
> Curt writes:
>> I suggest you follow the earlier advice, and set Thunderbird 
>> to compose your email as plain text
> 
> Or even as "normal" HTML.
> 

If it is trivial to me setting my mail manager to use the dark
background i need, and to make it ignore the (usually default)
background of color of all HTML messages, why the people in Debian User
list cannot do it? I will not change my setting! I need it. Learn to
deal with it. Things evolve. Being able to use bold, italic, underscore
is a minimum of "new" things that help a lot to compose good messages.
If Thunderbird has a problem when writing the automatic text messages,
together with the composed HTML ones, this is a reason to *fix* it, not
to never use anymore. I have installed another mail manager in my
computer: but it is bad, pretty horrible. It does not show HTML
messages. It does not compose HTML messages. And it is pretty counter
intuitive to configure, in several parts. It seems handy, have nice
things. But if you do not know them, or are not familiar enough with
"something", to be able to understand it, you cannot use them. Its name
is Claws Mail. I bet the most important people in this list love it. So,
Thunderbird has some problems (and the HTML thing is not a problem to
me), but it still the best mail manager for me.

Regards

Re: Trouble upgrading Debian (reply to David Wright)

[John Hasler]

Curt writes:
> I suggest you follow the earlier advice, and set Thunderbird 
> to compose your email as plain text

Or even as "normal" HTML.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: Trouble upgrading Debian

[piorunz]

On 06/09/2021 01:01, Dedeco Balaco wrote:

No. I do not want to edit emails with the traditional "black over white"
area. And I have seen that the colors I send can be ignored. And
Thunderbird also sends a pure text message together with the HTML
messages I prefer to use.

Thank you


I will feel free to ignore your e-mails then, as I do not intend to tire
my eyes reading grey on red, just because you decided to use HTML in
your e-mails and you like these colours. I don't. Good luck with your
enquiry.

--
With kindest regards, piorunz.

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

Re: Trouble upgrading Debian (reply to David Wright)

[Curt]

On 2021-09-06, Dedeco Balaco  wrote:

>> manpage for repository creation and user configuration details. W: GPG
>> error: http://deb.debian.org/debian buster-updates InRelease: The
>> following signatures couldn't be verified because the public key is
>> not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
>> E: The repository 'http://deb.debian.org/debian buster-updates
>> InRelease' is not signed. N: Updating from such a repository can't be
>> done securely, and is therefore disabled by default. N: See
>> apt-secure(8) manpage for repository creation and user configuration
>> details. 21:46:50 [ 0] root@debian: /etc/apt #
>
> So, what can I do to fix this?
>

sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys 
648ACFD622F3D138  0E98404D386FA1D9

I think that's what you have to do (add the missing keys to your ring).
I'm unsure of the proper syntax for adding two keys at once. Maybe
wait for David or Greg for confirmation. Good luck.

Re: Trouble upgrading Debian (reply to David Wright)

[Richard Hector]

On 6/09/21 1:20 pm, Dedeco Balaco wrote:

3. Tried to do 'apt update' as root, but it does not work. GPG signature
error.


21:18:54 [ 0] root@compo: /etc/apt # apt-mark hold firefox-esr
firefox-esr-l10n-pt-br thunderbird thunderbird-l10n-pt-br firefox-esr
set on hold. firefox-esr-l10n-pt-br set on hold. thunderbird set on
hold. thunderbird-l10n-pt-br set on hold. 21:46:26 [ 0] root@debian:
/etc/apt # apt update Get:1http://security.debian.org  buster/updates
InRelease [65.4 kB] Err:1http://security.debian.org  buster/updates
InRelease The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY
54404762BBB6E853 Get:2http://deb.debian.org/debian  buster InRelease
[122 kB] Get:3http://deb.debian.org/debian  buster-updates InRelease
[51.9 kB] Err:3http://deb.debian.org/debian  buster-updates InRelease
The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY
0E98404D386FA1D9 Get:4http://deb.debian.org/debian  buster/main
Sources [7,836 kB] Get:5http://deb.debian.org/debian  buster/main
amd64 Packages [7,907 kB] Get:6http://deb.debian.org/debian
buster/main i386 Packages [7,863 kB] Get:7
http://deb.debian.org/debian  buster/main Translation-pt_BR [683 kB]
Get:8http://deb.debian.org/debian  buster/main Translation-en [5,968
kB] Get:9http://deb.debian.org/debian  buster/main Translation-pt [309
kB] Get:10http://deb.debian.org/debian  buster/main amd64 Contents
(deb) [37.3 MB] Get:11http://deb.debian.org/debian  buster/main i386
Contents (deb) [37.3 MB] Reading package lists... Done W: GPG error:
http://security.debian.org  buster/updates InRelease: The following
signatures couldn't be verified because the public key is not
available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853 E:
The repository 'http://security.debian.org  buster/updates InRelease'
is not signed. N: Updating from such a repository can't be done
securely, and is therefore disabled by default. N: See apt-secure(8)
manpage for repository creation and user configuration details. W: GPG
error:http://deb.debian.org/debian  buster-updates InRelease: The
following signatures couldn't be verified because the public key is
not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
E: The repository 'http://deb.debian.org/debian  buster-updates
InRelease' is not signed. N: Updating from such a repository can't be
done securely, and is therefore disabled by default. N: See
apt-secure(8) manpage for repository creation and user configuration
details. 21:46:50 [ 0] root@debian: /etc/apt #


As you can see, the plain text version of your email is not very 
readable. I suggest you follow the earlier advice, and set Thunderbird 
to compose your email as plain text, even if only for list mail.


Cheers,
Richard

Re: Trouble upgrading Debian

[tomas]

On Sun, Sep 05, 2021 at 09:01:22PM -0300, Dedeco Balaco wrote:

[...]

> I did not receive the Greg answer. The only 3 messages I have in my
> folder now are the 2 you sent, and the one I receive for my message:

Here's the start of the thread:

  https://lists.debian.org/debian-user/2021/09/threads.html#00154

Yes, it's quite possible that your mail takes a bit longer to
appear if you are not subscribed. But it /will/ appear. This
mailing list is open "by design".

Cheers
 - t


signature.asc
Description: Digital signature

Re: Trouble upgrading Debian

[Dedeco Balaco]

Em 05-09-2021 19:10, piorunz escreveu:
> On 05/09/2021 05:27, Dedeco Balaco wrote:
>
>> What should i do to solve this?
> You reposted your question two hours later, so I repost the solution and
> CC you as well.

I am sorry it was reposted. I had trouble subscribing to the list, using
the site, and I thought the first message would be rejected. After
several tries without success, I decided to subscribe using the mail
address command. I instantly received a confirmation of subscription,
and this showed me I was not subscribed before. I also did not see my
first message in the list (yes, I waited 20 minutes for the site
refreshing time). So, I resent my question.

> 1. Start by reading the error message.  If you can't understand it, then
> paste it here. As Greg Wooledge already said.

I did not receive the Greg answer. The only 3 messages I have in my
folder now are the 2 you sent, and the one I receive for my message:

I will search the Greg message in the archives, since you mention it.

> 2. Disable colouring e-mails in your Thunderbird. Or disable HTML
> e-mails all together, use plain text e-mail.

No. I do not want to edit emails with the traditional "black over white"
area. And I have seen that the colors I send can be ignored. And
Thunderbird also sends a pure text message together with the HTML
messages I prefer to use.

Thank you

Re: Trouble upgrading Debian

[piorunz]

On 05/09/2021 05:27, Dedeco Balaco wrote:


What should i do to solve this?


You reposted your question two hours later, so I repost the solution and
CC you as well.

1. Start by reading the error message.  If you can't understand it, then
paste it here. As Greg Wooledge already said.

2. Disable colouring e-mails in your Thunderbird. Or disable HTML
e-mails all together, use plain text e-mail.

--
With kindest regards, piorunz.

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

Re: Trouble upgrading Debian

[David Wright]

On Sat 04 Sep 2021 at 23:04:49 (-0300), Dedeco Balaco wrote:
> 
> today, i started to upgrade my computer from Debian 9 (Stretch) to
> Debian 11 (Bullseye). I had some trouble finding what i wanted to do, a
> completely internet based upgrade, if possible. In the Debian
> documention, i did not find this explanation. It says it can be done,
> but it does not explain how to do it.
> 
> So, i opened the following thread. Do not read it now, there are more
> things i will say here, first.
> 
> https://www.linuxquestions.org/questions/linux-software-2/upgrading-debian-distribution-4175700202/#post6281677
> 
> In the thread, I was advised to not upgrade from Debian 9 to 11 in one
> step, because "jumping 2 releases will probably result in MASSIVE
> breakage". This should be in the official documentation, no? If there is
> this risk, it must be.

Yes, in the Release Notes. You can download the appropriate version from
https://www.debian.org/releases/bullseye/releasenotes

The warning is in § 4.2.1. It's recursive, so when you go back to
buster's, it has the same warning (§ 4.2), and the same for stretch,
jessie, and so on.

> So, i should to 2 upgrades: one to Debian 10, and one more to Debian 11.
> Fine. And for each one, the steps are:
> 
> 1. Disable all third party repositories.
> 
> 2. Edit /etc/apt/sources.list to reflect the next distribution i will
> have. Directly, this is just changing all "stretch" occurencies to
> "buster"; or all "buster" to "bullseye", in the second upgrade.

No, follow the Release Notes. For example, you should update and
upgrade the current version before you change sources.list, as the
main upgrade should be made from the latest point-release.

> 3. apt update
> 
> 4. apt upgrade
> 
> 5. apt full-upgrade
> 
> But after my first edition to sources.list, apt update fails. I have
> tried apt-get update to, but it also fails for the apparently same reason.
> 
> What should i do to solve this?

Presumably you need help here, so posting the error message is needed.
But do read the Release Notes (buster's in the first instance):
if you follow them carefully, it's possible you won't get failures.

Cheers,
David.

Re: Trouble upgrading Debian

[Greg Wooledge]

On Sat, Sep 04, 2021 at 11:04:49PM -0300, Dedeco Balaco wrote:
> So, i should to 2 upgrades: one to Debian 10, and one more to Debian 11.
> Fine. And for each one, the steps are:

> But after my first edition to sources.list, apt update fails. I have
> tried apt-get update to, but it also fails for the apparently same reason.
> 
> What should i do to solve this?

Start by reading the error message.  If you can't understand it, then
paste it here.

Installation trouble

[Gunnar Gervin]

Hi again.
Happy to tell you that the installation went well. Because the dvd player
hung, the installation lost part of the process, but the settings made in
LVM were used for the automatic installation, obviously, because it
finished almost like in a flash.
Debian is jolly good `cause it instructs really well, & is focused on
finding solutions.
BR,
geg

Re: Root & Boot Trouble

[Gunnar Gervin]

But I liked your 'quarrel' and the funny stories.
geg

On Thu, 22 Jul 2021 at 19:02, Gunnar Gervin  wrote:

> I seem to sort it out (or done already in Gparted "Clearing" format to
> remove old rubbish)
> & then -probably- using LVM to set it up correctly using terminal instead
> of GUI.
> Maybe I'll test Bullseye later, cos Debian Buster is the worst distro I
> ever tried, Windows included..
>
> On Thu, 22 Jul 2021 at 11:10, Greg Wooledge  wrote:
>
>> On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
>> > Description of happenings when I tried to install LMDE4 after I had
>> Debian
>>
>> I had to Google this to see what it *is*.  Google says,
>>
>>  Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
>>  stands for "Linux Mint Debian Edition".
>>
>> So, LMDE (version 4 or whatever) is an entirely separate operating system.
>> It's not something you install on top of Debian.  It's something you
>> install *instead* of Debian.
>>
>> If you want to remove Debian and replace it with LMDE, and if the LMDE
>> installer isn't working correctly for you, then you will need to contact
>> an LMDE mailing list instead of debian-user.  We simply do not know how
>> LMDE's installer works.
>>
>>

Re: Root & Boot Trouble

[Gunnar Gervin]

I seem to sort it out (or done already in Gparted "Clearing" format to
remove old rubbish)
& then -probably- using LVM to set it up correctly using terminal instead
of GUI.
Maybe I'll test Bullseye later, cos Debian Buster is the worst distro I
ever tried, Windows included..

On Thu, 22 Jul 2021 at 11:10, Greg Wooledge  wrote:

> On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
> > Description of happenings when I tried to install LMDE4 after I had
> Debian
>
> I had to Google this to see what it *is*.  Google says,
>
>  Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
>  stands for "Linux Mint Debian Edition".
>
> So, LMDE (version 4 or whatever) is an entirely separate operating system.
> It's not something you install on top of Debian.  It's something you
> install *instead* of Debian.
>
> If you want to remove Debian and replace it with LMDE, and if the LMDE
> installer isn't working correctly for you, then you will need to contact
> an LMDE mailing list instead of debian-user.  We simply do not know how
> LMDE's installer works.
>
>

Re: Root & Boot Trouble

[Greg Wooledge]

On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
> Description of happenings when I tried to install LMDE4 after I had Debian

I had to Google this to see what it *is*.  Google says,

 Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
 stands for "Linux Mint Debian Edition".

So, LMDE (version 4 or whatever) is an entirely separate operating system.
It's not something you install on top of Debian.  It's something you
install *instead* of Debian.

If you want to remove Debian and replace it with LMDE, and if the LMDE
installer isn't working correctly for you, then you will need to contact
an LMDE mailing list instead of debian-user.  We simply do not know how
LMDE's installer works.