Re: PATH question

[Charles Kroeger]

> apt-get -f install

dpkg --configure -a 

I had to use that this morning after the many nvidia related updates that
failed to build the module required to set up the packages in waiting. 

-- 
CK

Re: unexplained crash

[Jeffrey Walton]

On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk  wrote:
>
> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
>
> The machine was responding to ping and "telnet 22" was briefly
> connecting before connection closed.
>
> The graphical login prompt was visible, but when I tried to log in, it
> threw me to the text console. No login prompt on any virtual consoles
> and Ctrl-Alt-Del did nothing.
>
> There is no information logged in wtmp, kern.log and dmesg. Nothing
> interesting in auth.log
>
> The last 40 lines from syslog look as below:
>
> Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0...
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths.
> Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger
> for Ubuntu Report.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers.
> Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus
> Socket.
> Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate
> management daemon.
> Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent
> and passphrase cache (access for web browsers).
> Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent
> and passphrase cache (restricted).
> Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent
> (ssh-agent emulation).
> Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent
> and passphrase cache.
> Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket.
> Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket:
> Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd
> user session agent.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown.
> Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session.
> Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session.
> Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0.
> Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory
> /run/user/0...
> Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded.
> Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory
> /run/user/0.
> Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0.
>
> Does anybody have an idea what could have happened?

Whenever I see Snap, I get suspicious. You should probably ask on the
ubuntu-users list. The list has a person that answers Snap questions.
.

You should also show the SSH connection log for the client and server.
I think that's 'ssh -vvv' for the client, and 'journalctl -u ssh' for
the server.

Jeff

Re: Why is bullseye-backports recommended on bookworm?

[David Wright]

On Fri 17 Nov 2023 at 14:07:54 (+), Tixy wrote:
> On Thu, 2023-11-16 at 14:04 -0600, David Wright wrote:
> > On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote:
> > > On 2023-11-15 13:54:51 -0600, David Wright wrote:
> > > > On Wed 15 Nov 2023 at 20:01:20 (+0100), Vincent Lefevre wrote:
> > > > > On 2023-11-15 18:06:45 +, Tixy wrote:
> > > > > > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote:
> > > > > > > On 2023-11-15 16:39:15 -, Curt wrote:
> > > > > > > > On 2023-11-14, Vincent Lefevre  wrote:
> > > > > > > > > 
> > > > > > > > > The base number is the same, but I would have thought that 
> > > > > > > > > this other
> > > > > > > > > kernel might have additional patches.
> > > > > > > > > 
> > > > > > > > > > That's why I suggested ignoring the message.
> > > > > > > > > 
> > > > > > > > > Then why does reportbug mention the bullseye-backports kernel?
> > > > > > > > 
> > > > > > > > Because it kind of looks newer if you're a not very bright 
> > > > > > > > software
> > > > > > > > construct, he opined.
> > > > > > > 
> > > > > > > But the bookworm-backports kernel is even newer.
> > > > > > > So why not this one?
> > > > > > 
> > > > > > Because it's a different package?
> > > > > 
> > > > > There is no guarantee that a package with the same name in a
> > > > > different distribution has the same meaning (because packages
> > > > > get renamed...).

This is the bit I don't agree with. Perhaps just terminology…

> > > > > So I would say that this is not a good reason.
> > > > Well, it would seem strange to provide a backport for a package
> > > > and call it by a different name. But with kernels, there's always
> > > > the problem of a myriad of slightly different versions, so a
> > > > fuzzy name match might be appropriate.
> > > 
> > > In any case, if a package is renamed (which particularly applies to
> > > unstable, I don't know about backports), I would expect reportbug
> > > to also consider the new name for a newer version of the package.
> > > In short, its search for newer versions should be based on the
> > > source package rather than the binary package.
> > 
> > As I said above, I don't know whether they apply any fuzziness to the
> > version numbers in view of the multiplicity of linux-image versions
> > (and sources). As far as a 'rename' is concerned, I don't think that
> > linux-image has changed name since it was kernel-image in sarge.
> 
> There is no binary package called 'linux-image'.

Of course, the names of Debian packaged binary kernel images are an
agglomeration of 'linux-image', flavour, upstream version, and a
Debian version counter, incremented AIUI when the internal interfaces
change (so that the modules will stay in step).

> My PC has 'linux-
> image-amd64' installed which is a meta package who's description says
> 'This package depends on the latest Linux kernel and modules for use on
> PCs with AMD64'.
> 
> At time of writing, that depended on package in stable is called
> 'linux-image-6.1.0-13-amd64' and the version of that package is
> '6.1.55-1'. This is the kernel installed on my machine.

And AIUI that version is the upstream source version, and a Debian
counter for that source. The counter is rarely used, AFAICT, and can
cause consternation when it is, because it means the kernel gets
upgraded 'in place', making it tricky to revert if you wanted to.
(That shouldn't normally be necessary.) And I'm sure you know all
this, or something like it.

> In the original post that sparked this thread, Vincent showed reportbug
> saying that same binary package (linux-image-6.1.0-13-amd64) had a
> newer version available in backports, with the version number
> 6.1.55+1~bpo11+1.
> 
> Report bug is correct, that is a newer version by Debian versioning
> rules, there is no 'fuzzy' matching involved...
> 
if↘
> $ dpkg --compare-versions 6.1.55+1~bpo11+1 gt 6.1.55-1; then echo True; else 
> echo False; fi
> True
> 
> Now, I admit, looking in a prior releases backports for a newer version
> seems wrong, assuming the machine in question didn't have that release
> in it's source.list.

It is fuzzy in one sense. When APT and dpkg compare versions, they use
the version numbers exposed in the name of the .deb file, which in
your case above, are 6.1.55-1~bpo11+1 and 6.1.55-1:

  $ if dpkg --compare-versions 6.1.55-1~bpo11+1 gt 6.1.55-1; then echo True; 
else echo False; fi
  False
  $ 

This is caused by the use of ~bpo rather than -bpo, to make sure that
backports get replaced, similar to the ~rc trick for release candidates.
Otherwise you would get:

  $ if dpkg --compare-versions 6.1.55-1-bpo11+1 gt 6.1.55-1; then echo True; 
else echo False; fi
  True
  $ 

The 'fuzziness' is that your comparison is made using the /source/
version, which is why I included the Source field (src) in my listing.
What I can't answer is why the top half of the list has their sources
only specified as plain "linux". It's very easy to extract the source
version from the 

Re: Why is bullseye-backports recommended on bookworm?

[David Wright]

On Fri 17 Nov 2023 at 13:30:32 (+0100), Vincent Lefevre wrote:
> On 2023-11-16 14:04:29 -0600, David Wright wrote:
> > On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote:
> > > In any case, if a package is renamed (which particularly applies to
> > > unstable, I don't know about backports), I would expect reportbug
> > > to also consider the new name for a newer version of the package.
> > > In short, its search for newer versions should be based on the
> > > source package rather than the binary package.
> > 
> > As I said above, I don't know whether they apply any fuzziness to the
> > version numbers in view of the multiplicity of linux-image versions
> > (and sources). As far as a 'rename' is concerned, I don't think that
> > linux-image has changed name since it was kernel-image in sarge.
> 
> The name of the binary package frequently changes. This is why Tixy
> said "Because it's a different package?".

Tixy said that because the bookworm-backports packages are
called "linux-image-6.4.0…" which are all from a different kernel
source. I would call linux-image-x.y.z-386 → linux-image-x.y.z-486
and suchlike a name change.

> > > Note that for the Packages files, reportbug just uses the files from
> > > the /var/lib/apt/lists directory, but I don't have anything matching
> > > *bullseye* there.
> > 
> > I didn't know that, and at least one post in this thread suggests
> > otherwise.
> 
> I'm wondering why you think that.

Only because Greg wrote ‘What it said was "Hey, I looked on the
internets and I saw this other kernel that might be newer than the
one you're running, so maybe you wanna check this other kernel first
and see if it's still got the same bug, before you report this."’

Cheers,
David.

Re: unexplained crash

[David Wright]

On Sat 18 Nov 2023 at 07:06:49 (+0100), to...@tuxteam.de wrote:
> On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote:
> > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
> > 
> > The machine was responding to ping and "telnet 22" was briefly connecting
> > before connection closed.
> 
> Guessing from the context, you tried to ssh into your desktop and
> something went wrong ("became unresponsive"). What /exactly/ did
> your ssh client say?
> 
> I'd guess along the lines of "connection closed by foreign host",
> which would mean the ssh daemon is listening on the other side
> but closes the connection shortly after establishing it.
> 
> You can gather a bit more of info by adding one (or more) -v options
> to your ssh client invocation.
> 
> > The graphical login prompt was visible, but when I tried to log in, it threw
> > me to the text console. No login prompt on any virtual consoles and
> > Ctrl-Alt-Del did nothing.



> > 
> > There is no information logged in wtmp, kern.log and dmesg. Nothing
> > interesting in auth.log
> > 
> > The last 40 lines from syslog look as below:
> 
> [...]
> 
> I'm not a systemd expert by a long shot, so I'll have to leave
> this to others, but my first impression of the log is that of
> a system shutting down (which is kind of strange).

They did say they tried Ctrl-Alt-Del. That shuts down (and reboots)
on my systems.

Cheers,
David.

Re: unexplained crash

[tomas]

On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote:
> Hello,
> 
> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
> 
> The machine was responding to ping and "telnet 22" was briefly connecting
> before connection closed.

Guessing from the context, you tried to ssh into your desktop and
something went wrong ("became unresponsive"). What /exactly/ did
your ssh client say?

I'd guess along the lines of "connection closed by foreign host",
which would mean the ssh daemon is listening on the other side
but closes the connection shortly after establishing it.

You can gather a bit more of info by adding one (or more) -v options
to your ssh client invocation.

> The graphical login prompt was visible, but when I tried to log in, it threw
> me to the text console. No login prompt on any virtual consoles and
> Ctrl-Alt-Del did nothing.
> 
> There is no information logged in wtmp, kern.log and dmesg. Nothing
> interesting in auth.log
> 
> The last 40 lines from syslog look as below:

[...]

I'm not a systemd expert by a long shot, so I'll have to leave
this to others, but my first impression of the log is that of
a system shutting down (which is kind of strange).

Perhaps you've had a file system (or underlying drive media)
error and your root FS is mounted read only?

I understand that you managed to log into a console: what does
"mount" say?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Upgrade my distribution

[Ryan Nowakowski]

On Thu, Nov 16, 2023 at 09:09:08PM +, Michael Kjörling wrote:
> On 16 Nov 2023 14:27 -0600, from willitc9...@gmail.com (William Torrez Corea):
> > I have Debian 11 bullseye. I want have Debian 12 "bookworm"
> > 
> > I execute the command:
> > 
> > apt-get update
> >> apt upgrade
> >> apt dist-upgrade
> > 
> > But I don't get any change in my distribution.
> 
> In addition to what has already been said about updating your apt
> sources list, _please_ first read the Bookworm release notes:
> 
> https://www.debian.org/releases/bookworm/amd64/release-notes/index.en.html
> 
> and _particularly_ the chapter on upgrading:
> 
> https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html

+1 here.  There are sometimes nuances between releases and I always follow the 
release upgrade guide to catch them.

Re: le bluez de la doc de bluez (+wireplumber)

[Marc Chantreux]

hello!

> Avertissement: je ne connais rien à Bluetooth, jamais utilisé. Je me
> demande aussi si dans ton cas de casque USB (que tu raccordes en USB?)
> c'est nécessaire de passer par Bluetooth en cas de raccordement USB (ça
> devrait être vu comme périphérique audio USB?)

merde … j'ai parlé de USB. Il fallait bien comprendre blutooth! désolé
et merci pour ta vigilance!

> Sinon le wiki Archlinux a des pages intéressantes sur Bluetooth en général
> et l'utilisation d'un combiné micro-casque en particulier:
> https://wiki.archlinux.org/title/Bluetooth
> https://wiki.archlinux.org/title/Bluetooth_headset
> je m'aperçois qu'il y a grosso-modo la même chose dans le wiki Debian:
> https://wiki.debian.org/BluetoothUser
> https://wiki.debian.org/BluetoothUser/a2dp

Je vais potasser ces liens pendant le WE.

cordialement,
marc

bluetooth Re: le bluez de la doc de bluez (+wireplumber)

[Marc Chantreux]

salut,

> > Je tente de connecter un casque USB. Pour le moment, j'ai réussi
> > à enregistrer le périphérique

> Dans mon cas ou je n'utilise pas Gnome3 mais blueman-applet et
> pulseaudio, j'installe pulseaudio-module-bluetooth et désinstalle tout
> ce qui ressemble à pipewire qui m'enschtroumphe.

Je n'utilise pas gnome3: je suis sous dwm.

Pulseaudio vs wireplumber ne me semble pas être un sujet puisque j'en
suis simplement à vouloir pairer.

Et pour parler de mon problème effectivement:

[bluetooth]# devices Paired
Device 08:21:EF:03:05:BC marc
Device 14:3F:A6:71:C7:92 LE_WH-XB900N
[bluetooth]# devices Connected
[bluetooth]# connect 14:3F:A6:71:C7:92
Attempting to connect to 14:3F:A6:71:C7:92
Failed to connect: org.bluez.Error.Failed Operation already in progress


Je n'ai pas de message plus explicite. J'ai fais un

journalctl -xfen0

Mais il reste silencieux et je cherche donc à augmenter le niveau de
verbosité.

Mais c'est pe un autre outils qu'il faut utiliser par exemple pour
dumper le traffic USB et tenter de comprendre ce qu'il se passe?

D'avance merci pour toute aide.

cordialement,
marc

Re: approx in debian 12

[Russell L. Harris]

On Fri, Nov 17, 2023 at 02:02:10PM -0500, Greg Wooledge wrote:

On Fri, Nov 17, 2023 at 05:18:02PM +, Russell L. Harris wrote:

Should we report an error regarding the approx man page which states:


I would not bother filing any cosmetic bug reports against a 12-year-old
upstream man page.


Agreed on that point.  But I suspect that the maintainer is going to
become involved to get approx working in Debian-12.

I searched for "Debian approx apt-cache" and found several users of
apt-cache and apt-cache-ng who reported the packages buggy and
several who expressed appreciation for the stability of approx.

Whatever release of approx I have running on the Debian-9 machine
works flawlessly, but I do hope to upgrade the Debian version on that
machine.  I suppose I could reinstall on my planned replacement, and
see whether approx still works with Debian-11, or go back to
Debian-10, if necessary.

RLH

Re: le bluez de la doc de bluez (+wireplumber)

[didier gaumet]

Bonjour,

Avertissement: je ne connais rien à Bluetooth, jamais utilisé. Je me 
demande aussi si dans ton cas de casque USB (que tu raccordes en USB?) 
c'est nécessaire de passer par Bluetooth en cas de raccordement USB (ça 
devrait être vu comme périphérique audio USB?)


Sinon le wiki Archlinux a des pages intéressantes sur Bluetooth en 
général et l'utilisation d'un combiné micro-casque en particulier:

https://wiki.archlinux.org/title/Bluetooth
https://wiki.archlinux.org/title/Bluetooth_headset

je m'aperçois qu'il y a grosso-modo la même chose dans le wiki Debian:
https://wiki.debian.org/BluetoothUser
https://wiki.debian.org/BluetoothUser/a2dp

Re: le bluez de la doc de bluez (+wireplumber)

[Haricophile]

Le Fri, 17 Nov 2023 19:49:59 +0100,
Marc Chantreux  a écrit :

> Je tente de connecter un casque USB. Pour le moment, j'ai réussi
> à enregistrer le périphérique

Dans mon cas ou je n'utilise pas Gnome3 mais blueman-applet et
pulseaudio, j'installe pulseaudio-module-bluetooth et désinstalle tout
ce qui ressemble à pipewire qui m'enschtroumphe.

Debian-user!

[Kimberly Thompson]

Debian-user, it's me again, are you ok?

unexplained crash

[Adam Weremczuk]

Hello,

Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.

The machine was responding to ping and "telnet 22" was briefly 
connecting before connection closed.


The graphical login prompt was visible, but when I tried to log in, it 
threw me to the text console. No login prompt on any virtual consoles 
and Ctrl-Alt-Del did nothing.


There is no information logged in wtmp, kern.log and dmesg. Nothing 
interesting in auth.log


The last 40 lines from syslog look as below:

Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0...
Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target.
Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System.
Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths.
Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger 
for Ubuntu Report.

Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets.
Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers.
Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus 
Socket.

Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate 
management daemon.

Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent 
and passphrase cache (access for web browsers).

Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent 
and passphrase cache (restricted).

Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent 
(ssh-agent emulation).

Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent 
and passphrase cache.

Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket.
Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket: 
Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd 
user session agent.

Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown.
Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session.
Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session.
Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0.
Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory 
/run/user/0...

Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded.
Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory 
/run/user/0.

Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0.

Does anybody have an idea what could have happened?

Regards,
Adam

Re: le bluez de la doc de bluez (+wireplumber)

[NoSpam]

Debian bookworm également

Le 17/11/2023 à 20:03, NoSpam a écrit :

Ubuntu 22.04 pas de soucis avec bluetoothctl --help et les man

ii  bluez  5.64-0ubuntu1 amd64    Bluetooth tools and daemons

Le 17/11/2023 à 19:49, Marc Chantreux a écrit :

salut à tous,

Je tente de connecter un casque USB. Pour le moment, j'ai réussi
à enregistrer le périphérique

# bluetoothctl devices |grep W
Device 14:XX:XX:XX:XX:XX WH-XB900N

et il me faut maintenant le pairer. Et là surprise: toutes ces
commandes ne servent à peu pret à rien:

man bluetoothctl
bluetoothctl --help
apropos bluetoothctl
apropos bluez
info

"il me manque un paquet de doc", me dis-je, mais

# aptitude search '~nbluez ~ndoc'
libkf5bluezqt-doc - documentation files for bluez-qt

bon ... je me résigne:

apt-cache show bluez |
sed '/^Homepage: /!d;s///;q' |
xargs chromium

ce qui me fait visiter http://www.bluez.org. Sauf que même ici

* pas d'onglet doc.
* la FAQ est moins longue que celle de la WTFPL 
(http://www.wtfpl.net/faq/)


dans la page download, je trouve "User Space BlueZ Package". Cool!

curl http://www.kernel.org/pub/linux/bluetooth/bluez-5.66.tar.xz |
tar xz
grep -F bluetoothctl blu*/doc

et là encore je ne trouve rien (ou plutôt une ligne).

Y'a pas de docs ou c'est moi qui ne sais plut chercher?

cordialement,
marc

Re: le bluez de la doc de bluez (+wireplumber)

[NoSpam]

Ubuntu 22.04 pas de soucis avec bluetoothctl --help et les man

ii  bluez  5.64-0ubuntu1 amd64    Bluetooth tools and daemons

Le 17/11/2023 à 19:49, Marc Chantreux a écrit :

salut à tous,

Je tente de connecter un casque USB. Pour le moment, j'ai réussi
à enregistrer le périphérique

# bluetoothctl devices |grep W
Device 14:XX:XX:XX:XX:XX WH-XB900N

et il me faut maintenant le pairer. Et là surprise: toutes ces
commandes ne servent à peu pret à rien:

man bluetoothctl
bluetoothctl --help
apropos bluetoothctl
apropos bluez
info

"il me manque un paquet de doc", me dis-je, mais

# aptitude search '~nbluez ~ndoc'
libkf5bluezqt-doc - documentation files for bluez-qt

bon ... je me résigne:

apt-cache show bluez |
sed '/^Homepage: /!d;s///;q' |
xargs chromium

ce qui me fait visiter http://www.bluez.org. Sauf que même ici

* pas d'onglet doc.
* la FAQ est moins longue que celle de la WTFPL (http://www.wtfpl.net/faq/)

dans la page download, je trouve "User Space BlueZ Package". Cool!

curl http://www.kernel.org/pub/linux/bluetooth/bluez-5.66.tar.xz |
tar xz
grep -F bluetoothctl blu*/doc

et là encore je ne trouve rien (ou plutôt une ligne).

Y'a pas de docs ou c'est moi qui ne sais plut chercher?

cordialement,
marc

Re: approx in debian 12

[Greg Wooledge]

On Fri, Nov 17, 2023 at 05:18:02PM +, Russell L. Harris wrote:
> Should we report an error regarding the approx man page which states:
> 
> USEAGE
> approx is invoked by inetd(8)

I assume you're looking at the approx(8) man page as shown
here: 

This is upstream's man page, dated May 2011.  It's clearly not going
to be *literally* true on every system, as there are plenty of
alternatives to inetd (xinetd, systemd, and so on).  One may read it
as meaning "inetd or something which fulfills the same role".

I would not bother filing any cosmetic bug reports against a 12-year-old
upstream man page.

le bluez de la doc de bluez (+wireplumber)

[Marc Chantreux]

salut à tous,

Je tente de connecter un casque USB. Pour le moment, j'ai réussi
à enregistrer le périphérique

# bluetoothctl devices |grep W
Device 14:XX:XX:XX:XX:XX WH-XB900N

et il me faut maintenant le pairer. Et là surprise: toutes ces
commandes ne servent à peu pret à rien:

man bluetoothctl
bluetoothctl --help
apropos bluetoothctl
apropos bluez
info

"il me manque un paquet de doc", me dis-je, mais

# aptitude search '~nbluez ~ndoc'
libkf5bluezqt-doc - documentation files for bluez-qt

bon ... je me résigne:

apt-cache show bluez |
sed '/^Homepage: /!d;s///;q' |
xargs chromium

ce qui me fait visiter http://www.bluez.org. Sauf que même ici

* pas d'onglet doc.
* la FAQ est moins longue que celle de la WTFPL (http://www.wtfpl.net/faq/)

dans la page download, je trouve "User Space BlueZ Package". Cool!

curl http://www.kernel.org/pub/linux/bluetooth/bluez-5.66.tar.xz |
tar xz
grep -F bluetoothctl blu*/doc

et là encore je ne trouve rien (ou plutôt une ligne).

Y'a pas de docs ou c'est moi qui ne sais plut chercher?

cordialement,
marc

Re: Mission Center can't create graphs on bookworm OS

[Jeffrey Walton]

On Fri, Nov 17, 2023 at 11:21 AM Steven Friedrich
 wrote:
>
> It says can't create Open GL context.  What package should I report this
> against?
>
> I am running latest raspberry os(bookworm) on a Pi4B.

I don't see mission-center in Debian's packages. It may be there, but
I have not found it.

I do see flatpak versions of mission center. Cf.,
.

Maybe flatpak would be the place?

Jeff

Re: approx in debian 12

[Russell L. Harris]

On Fri, Nov 17, 2023 at 11:57:44AM +0300, Reco wrote:

Hi.

On Fri, Nov 17, 2023 at 08:03:15AM +, Russell L. Harris wrote:

On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:
> Looks good. What about this one:
>
> apt update -o Acquire::http::Proxy=http://localhost:

root@mollydew:/etc/approx# apt update -o 
Acquire::http::Proxy=http://localhost:
Ign:1 http://security.debian.org/debian-security bookworm-security InRelease


Hm. I have this in my approx.conf for debian-security:

debian-security http://deb.debian.org/debian-security

Try changing it, I guess.


The red screen still appears.

Should we report an error regarding the approx man page which states:

USEAGE
approx is invoked by inetd(8)

RLH

Re: touchpad buttons sometimes stop working for several seconds

[Max Nikulin]

On 17/11/2023 19:54, Vincent Lefevre wrote:

BTW, what model of touchpad do you have?


Device:   SYNA30AC:00 06CB:CDEB Touchpad
Kernel:   /dev/input/event11
Group:9
Seat: seat0, default
Size: 106x61mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock:disabled
Left-handed:  disabled
Nat.scrolling:disabled
Middle emulation: disabled
Calibration:  n/a
Scroll methods:   *two-finger edge
Click methods:*button-areas clickfinger
Disable-w-typing: enabled
Disable-w-trackpointing: enabled
Accel profiles:   flat *adaptive
Rotation: n/a

Re: Why is bullseye-backports recommended on bookworm?

[Tixy]

On Thu, 2023-11-16 at 14:04 -0600, David Wright wrote:
> On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote:
> > On 2023-11-15 13:54:51 -0600, David Wright wrote:
> > > On Wed 15 Nov 2023 at 20:01:20 (+0100), Vincent Lefevre wrote:
> > > > On 2023-11-15 18:06:45 +, Tixy wrote:
> > > > > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote:
> > > > > > On 2023-11-15 16:39:15 -, Curt wrote:
> > > > > > > On 2023-11-14, Vincent Lefevre  wrote:
> > > > > > > > 
> > > > > > > > The base number is the same, but I would have thought that this 
> > > > > > > > other
> > > > > > > > kernel might have additional patches.
> > > > > > > > 
> > > > > > > > > That's why I suggested ignoring the message.
> > > > > > > > 
> > > > > > > > Then why does reportbug mention the bullseye-backports kernel?
> > > > > > > 
> > > > > > > Because it kind of looks newer if you're a not very bright 
> > > > > > > software
> > > > > > > construct, he opined.
> > > > > > 
> > > > > > But the bookworm-backports kernel is even newer.
> > > > > > So why not this one?
> > > > > 
> > > > > Because it's a different package?
> > > > 
> > > > There is no guarantee that a package with the same name in a
> > > > different distribution has the same meaning (because packages
> > > > get renamed...). So I would say that this is not a good reason.
> > > 
> > > Well, it would seem strange to provide a backport for a package
> > > and call it by a different name. But with kernels, there's always
> > > the problem of a myriad of slightly different versions, so a
> > > fuzzy name match might be appropriate.
> > 
> > In any case, if a package is renamed (which particularly applies to
> > unstable, I don't know about backports), I would expect reportbug
> > to also consider the new name for a newer version of the package.
> > In short, its search for newer versions should be based on the
> > source package rather than the binary package.
> 
> As I said above, I don't know whether they apply any fuzziness to the
> version numbers in view of the multiplicity of linux-image versions
> (and sources). As far as a 'rename' is concerned, I don't think that
> linux-image has changed name since it was kernel-image in sarge.

There is no binary package called 'linux-image'. My PC has 'linux-
image-amd64' installed which is a meta package who's description says
'This package depends on the latest Linux kernel and modules for use on
PCs with AMD64'.

At time of writing, that depended on package in stable is called
'linux-image-6.1.0-13-amd64' and the version of that package is
'6.1.55-1'. This is the kernel installed on my machine.

In the original post that sparked this thread, Vincent showed reportbug
saying that same binary package (linux-image-6.1.0-13-amd64) had a
newer version available in backports, with the version number
6.1.55+1~bpo11+1.

Report bug is correct, that is a newer version by Debian versioning
rules, there is no 'fuzzy' matching involved...

$ dpkg --compare-versions 6.1.55+1~bpo11+1 gt 6.1.55-1; then echo True; else 
echo False; fi
True

Now, I admit, looking in a prior releases backports for a newer version
seems wrong, assuming the machine in question didn't have that release
in it's source.list.

-- 
Tixy

Re: touchpad buttons sometimes stop working for several seconds

[Vincent Lefevre]

On 2023-11-16 23:53:51 +0700, Max Nikulin wrote:
> On 16/11/2023 20:59, Vincent Lefevre wrote:
> > The question is what suppresses software buttons. If this is libinput
> > that suppresses them (just like it suppressed pointer moves when
> > typing, while pointer moves are still reported by the kernel), then
> > this is unrelated to my issue.
> 
> I am unsure if kernel is involved at all. It may be device firmware (have
> you checked for firmware updates?),

Yes, firmware is up-to-date (/etc/update-motd.d/85-fwupd signals
when new versions are available).

> it may be libinput as the device driver. Perhaps libinput may send
> some commands to touchpad to suppress generation of events for some
> interval of time.

I would have expected something in the log in such a case.

In the next few days, I'll try to look at issues more closely with
tools from libinput-tools.

> > BTW, I often accidentally touch the bottom of the touchpad with the
> > palm of my hand
> 
> I am unsure if you have read relevant parts of libinput docs
> https://wayland.freedesktop.org/libinput/doc/latest/palm-detection.html

Just a note to say that palm detection is either disabled or it does
not work (I'll try to see whether MT_TOOL_PALM can be generated).

> I hope I solved my variant of "buttons does not work for some period of
> time" by dropping a snippet into xorg.conf.d that enables tap-to-click.

I don't like tap-to-click (I don't want accidental clicks).

> For me it is more convenient than clicks in the bottom area. My
> observation is that hardware click works more reliable if I raise
> the finger for a moment after moving cursor. However in my case
> period of clickbuttons inactivity is usually just a few seconds
> (unless prolonged by repeating clicks). Sometimes clicks are ignored
> when a finger is at the bottom touchpad edge.

When I tried, I tested clicks on various parts of the touchpad.
But I would say that even if clicks are to be ignored, an event
is normally generated by the kernel. I could see that the kernel
generates a BTN_LEFT event even when it doesn't know where the
click has been done; in such a case, I get no clicks at the X11
level (obviously).

BTW, what model of touchpad do you have?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Why is bullseye-backports recommended on bookworm?

[Vincent Lefevre]

On 2023-11-16 14:04:29 -0600, David Wright wrote:
> On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote:
> > In any case, if a package is renamed (which particularly applies to
> > unstable, I don't know about backports), I would expect reportbug
> > to also consider the new name for a newer version of the package.
> > In short, its search for newer versions should be based on the
> > source package rather than the binary package.
> 
> As I said above, I don't know whether they apply any fuzziness to the
> version numbers in view of the multiplicity of linux-image versions
> (and sources). As far as a 'rename' is concerned, I don't think that
> linux-image has changed name since it was kernel-image in sarge.

The name of the binary package frequently changes. This is why Tixy
said "Because it's a different package?".

> > Note that for the Packages files, reportbug just uses the files from
> > the /var/lib/apt/lists directory, but I don't have anything matching
> > *bullseye* there.
> 
> I didn't know that, and at least one post in this thread suggests
> otherwise.

I'm wondering why you think that. Earlier in this thread:


On 2023-11-14 23:54:31 +0700, Max Nikulin wrote:
> On 14/11/2023 19:00, Vincent Lefevre wrote:
> > To my surprise, reportbug asks me to use bullseye-backports
> > (= oldstable-backports) on my bookworm (= stable) machine:
>
> Might it happen that you have bullseye-backports in apt sources.list?

No, and this is actually the complaint of reportbug, which wants
me to add it.


In my bug report (bug 1055931), Nis Martensen found where
6.1.55+1~bpo11+1 came from. As a summary from

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055931#34


On 2023-11-16 17:31:13 +0100, Nis Martensen wrote:
> I can find "6.1.55+1~bpo11+1" in https://ftp-master.debian.org/new.822
> so it must come from there.

Thanks. I had first looked at

  https://ftp-master.debian.org/new.html

(as output by reportbug), and it doesn't appear on this page
(I searched for both "linux" and "6.1.55"). Note that clicking
on "Click to toggle all/binary-NEW packages" does not make this
kernel appear either.

FYI, I later looked at https://ftp-master.debian.org/new.822 too
(as I could see it in the strace output), but only searched for
linux-image there, explaining that I didn't find it either (it
actually appears as linux-signed-amd64).

At the bottom of the new.html page:
"You can also look at the RFC822 version."

But why are the contents different? (linux-signed-amd64 appears
only in the RFC822 version.)


-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Mission Center can't create graphs on bookworm OS

[Steven Friedrich]

It says can't create Open GL context.  What package should I report this 
against?


I am running latest raspberry os(bookworm) on a Pi4B.

Re: Upgrade my distribution

[Ralf Doering]

William Torrez Corea  writes:

> How can I upgrade my distribution?
> I have Debian 11 bullseye. I want have Debian 12 "bookworm"

The release notes answer this in depth.

https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html

Ralf

Re: Request advice on Optimal Combo-usage of Gmail and Mailman, as mentioned in Msg-Id. "2023/11/msg00443"

[Charles Kroeger]

> If you ever do find one, please let me know. The lack of such a thing is
> the primary reason why I don't do E-mail on Android *at all*.

https://github.com/M66B/FairEmail

I use this. It is what you want.

-- 
CK

Szkolenia menedżerskie

[Karol Czychiel]

Dzień dobry, 

dostarczamy kompleksowe usług doradczych w obszarze strategicznego zarządzania 
zasobami ludzkimi – outsourcingu HR. 

Nasze usługi dedykowana są firmom ze wszystkich branż, które nie posiadają 
wewnętrznego działu HR, dzięki czemu zapewniamy ciągłość polityki personalnej 
bez konieczności utrzymywania etatu HR. 

Jeżeli są Państwo zainteresowani pozyskaniem oferty i szerszym zapoznaniem się 
z naszymi usługami, będę wdzięczny za kontakt. 


Pozdrawiam
Karol Czychiel

Re: approx in debian 12

[Reco]

Hi.

On Fri, Nov 17, 2023 at 08:03:15AM +, Russell L. Harris wrote:
> On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:
> > Looks good. What about this one:
> > 
> > apt update -o Acquire::http::Proxy=http://localhost:
> 
> root@mollydew:/etc/approx# apt update -o 
> Acquire::http::Proxy=http://localhost:
> Ign:1 http://security.debian.org/debian-security bookworm-security InRelease

Hm. I have this in my approx.conf for debian-security:

debian-security http://deb.debian.org/debian-security

Try changing it, I guess.

Reco

Re: MySQL Workbench

[Camaleón]

El 2023-11-16 a las 17:22 -0300, Carlos Villiere escribió:

> ¡¡Hola Comunidad Debian!!
> 
> Estoy tratando de instalar mysql-workbench-community_8.0.34 en miPc Debian
> desde un paquete .deb obtenido de la Web Page de MySQL, pero los únicos
> para Sistemas Debian son
> mysql-workbench-community_8.0.34-1ubuntu23.04_amd64 y
> mysql-workbench-community_8.0.34-1ubuntu22.04_amd64.

Descarga la versión del paquete deb para la versión de Ubuntu más 
parecida a tu versión Debian, es decir, si tienes instalada la versión 
oldstable de Debian (bullseye), que salió en el año 2021, prueba con el 
paquete para ubuntu22 o incluso con una versión más antigua (la 8.0.28
desde los archivos¹, para intentar minimizar problemas con las 
dependencias.

¹https://downloads.mysql.com/archives/workbench/

> También tengo la versión del código fuente.
> Al querer instalarla mysql-workbench-community_8.0.34-1ubuntu23.04_amd64
> con el procedimiento estándar.
> sudo apt-get update
> sudo apt-get upgrade
> sudo apt-get install
> ./mysql-workbench-community_8.0.34-1ubuntu23.04_amd64.deb
> Tengo un problema de dependencias que me informa apt-get
> "Los siguientes paquetes tienen dependencias incumplidas:
>  mysql-workbench-community : Depende: libatkmm-1.6-1v5 (>= 2.28.3) pero 
> 2.28.0-3 va a ser instalado
>  Depende: libc6 (>= 2.35) pero 2.31-13+deb11u7 va 
> a ser instalado
>  Depende: libglib2.0-0 (>= 2.70.0) pero 2.66.8-1 
> va a ser instalado
>  Depende: libglibmm-2.4-1v5 (>= 2.66.6) pero 
> 2.64.2-2 va a ser instalado
>  Depende: libgtkmm-3.0-1v5 (>= 3.24.7) pero 
> 3.24.2-2 va a ser instalado
>  Depende: libjpeg8 (>= 8c) pero no es instalable
>  Depende: liblerc4 (>= 3.0) pero no es instalable
>  Depende: libmysqlclient21 (>= 8.0.11) pero no es 
> instalable
>  Depende: libproj25 (>= 8.2.0) pero no es 
> instalable
>  Depende: libpython3.11 (>= 3.11.0) pero no es 
> instalable
>  Depende: libsasl2-2 (>= 2.1.28+dfsg) pero 
> 2.1.27+dfsg-2.1+deb11u1 va a ser instalado
>  Depende: libssl3 (>= 3.0.0) pero no es instalable
>  Depende: libstdc++6 (>= 12) pero 10.2.1-6 va a 
> ser instalado
>  Depende: libwebp7 (>= 1.2.4) pero no es 
> instalable
> E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.
> " (sic.)

Lo que quiere decir es que el paquete que vas a instalar es demasiado 
moderno para tu sistema, que no tiene todos los paquetes disponibles en 
la versión requerida.

> El paquete mysql-workbench-community no se encuentra en los repositorios de
> Debian, por esa razon lo baje de la Web Page.

Bueno, está en Sid pero es mejor que pruebes antes con la versión de WB 
8.0.28, o anteriores.

https://packages.debian.org/sid/mysql-workbench

> La cuestion aqui es, ¿resuelvo las dependencias incumplidas y vuelvo a
> intentar instalarlo 

Si tienes Debian 11 no vas a poder :-P

> o pruebo instalar desde las fuentes con Cmake, el que tengo ya 
> instalado, y es como indica la documentación que incluye el
> mysql-workbench-community-8.0.33-src.tar.gz?

Yo probaría antes a instalar otro deb para Ubuntu (8.0.28), que salió en 
el año 2021.

> ¿La primera opción podría producir algún inconveniente en mi sistema?

No vas a poder :-)

> Desde ya les agradezco su tiempo y sugerencias al respecto.

Por aquí tienes más info:

Instalar MySQL Workbench en Debian 10
https://hotsechu.wordpress.com/2021/03/02/instalar-mysql-workbench-en-debian-10/

Saludos,

-- 
Camaleón 

Re: approx in debian 12

[Russell L. Harris]

On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:

Looks good. What about this one:

apt update -o Acquire::http::Proxy=http://localhost:


root@mollydew:/etc/approx# apt update -o Acquire::http::Proxy=http://localhost: 
Ign:1 http://security.debian.org/debian-security bookworm-security InRelease

Err:2 http://security.debian.org/debian-security bookworm-security Release
 404  Not Found [IP: ::1 ]
Hit:3 http://192.168.1.40:/debian bookworm InRelease
Get:4 http://192.168.1.40:/debian bookworm-updates InRelease [52.1 kB]
Reading package lists... Done   
E: The repository 'http://security.debian.org/debian-security bookworm-security Release' no longer has a Release file.

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.
root@mollydew:/etc/approx#