Hello:

Please do.

Not that you know of.

Indeed ...

I think that what is annoying is that something (unknown to you) is creating a .config dir in /.

And from what I have been told, it should not be happening.
Unless at some time your $HOME was set to /.
Which does not seem to be the case.

Granted, it may not be a big deal, but it should not be happening.

My idea of things like these is that they should be investigated and fixed.
If it is a bug or an oversight, it should be squashed/fixed.

All those "won't fix because it is harmless" issues, warnings and/or bug reports which end up being swept under the rug will are not healthy.
I see it as lousy coding and may (eventually) end up causing issues somewhere in the system.

Of course, YMMV.

Best,

A.

Hello:

Hmm ...
No idea.
Have not tried it but I don't see (?) why it shouldn't.

Yes, I guess I could pin it.
ie: the same way I do with pulseaudio and see what happens on the next upgrade.

Bear in mind that there are other apparmor related libraries which are/may be needed by other packages.

eg: libapparmor1

~$ aptitude why libapparmor1
i   stress-ng Depends libapparmor1 (>= 2.10)
~$ 

Edit:

It seems that there's more than stress-ng involved with libapparmor1.

~$ aptitude why libapparmor1
i   slim Depends dbus                    
i A dbus Depends libapparmor1 (>= 2.8.94)
~$

---> Very strange all this did not show up on my previous query to aptitude. <---

I have not used stress-ng in years, so I might as well get rid of it. and solve the issue.

We'll see how the pinning goes.

Best,

A.

Hello:

Yes, but do remember to check the link I posted.
You don't want pulseaudio pulled in again by some uncouth package.

~$ cat /etc/apt/preferences.d/avoid_pulseaudio
Package: pulseaudio:*
Pin: version *
Pin-Priority: -1
~$ 

Best,

A.

Hello:

Some Nvidia cards can no longer be used in Linux systems as Nvidia dropped support for them.
In my specific case, the 340.108 driver I use for my two perfectly working FX580 cards.

That is the main reason I am still on Devuan Beowulf running a backported kernel till I am forced to move on and use the Nouveau drivers.
Hopefully, they may work better than the last time I tried them.

You may want to have a read here and see if you find the answer you are looking for.

Best,

A.

Hello:

So ...
It's a bug in the grub installer?

Best,

A.

Hello:

Haven't come across this but ...

I don't think there's any magic or wonder of any sort going on here.

The fact that lsusb does not show the connected device only means that.
ie: that it does not show/detect it.

But it does not mean that the SP Flash Tool cannot read the processor information belonging to the Android device.
ie: after all, it is the SP Flash Tool app that is doing the reading.

The thing is that (from what you are saying) the only place the SP Flash Tool can check the processor data is on the Android device.
And the only way the SP Flash Tool can do that is through the USB connection you established by plugging in the device.

That is, unless I am missing some new and recently develped tech.

Best,

A.

Hello:

Have you seen this article in The Register?

-----
How to get Linux onto a non-approved laptop
Dell certifies certain models for Linux, but if yours isn't, all is not lost
Liam Proven
Fri 22 Jul 2022 // 16:00 UTC
-----

Best,

A.

Hello:

You should check that then.

Yes, install with the --no-install-recommends flag.

eg:

apt install --no-install-recommends [package_name_here]

See https://superuser.com/questions/615565/ … recommends for how to make that permanent in apt.

Best,

A.

Hello:

Run this in a terminal:

~$ aptitude why libcups3

I run Devuan Beowulf with a backported kernel:

~$ uname -a
Linux devuan 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
~$ 

I have cups installed:

~$ apt list | grep installed | grep -i cups
---
cups-bsd/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-client/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-common/oldstable,oldstable,oldstable-security,oldstable-security,now 2.2.10-6+deb10u6 all [installed,automatic]
cups-core-drivers/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-daemon/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-filters-core-drivers/oldstable,now 1.21.6-5 amd64 [installed,automatic]
cups-filters/oldstable,now 1.21.6-5 amd64 [installed,automatic]
cups-ipp-utils/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-ppdc/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
cups-server-common/oldstable,oldstable,oldstable-security,oldstable-security,now 2.2.10-6+deb10u6 all [installed,automatic]
cups/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed]
libcups2/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
libcups2/oldstable,oldstable-security,now 2.2.10-6+deb10u6 i386 [installed]
libcupsfilters1/oldstable,now 1.21.6-5 amd64 [installed,automatic]
libcupsimage2/oldstable,oldstable-security,now 2.2.10-6+deb10u6 amd64 [installed,automatic]
printer-driver-hpcups/oldstable,now 3.18.12+dfsg0-2 amd64 [installed,automatic]
~$ 

But the library you referr to is not installed in my system:

~$ apt list | grep installed | grep -i libcups3
---
~$ 

~$ aptitude why libcups3
E: No package named "libcups3" exists.
~$ 

Maybe it is just a chimaera thing?

Best,

A.

Hello:

Glad you were able to work it out.

I see that there are only 36 open issues at the CUPS GitHub page and only 3 have not been looked at/sorted/classified yet.
The last 2 being from this month and one from less than a month ago.

Not bad at all, I've seen much worse.
eg: LibreOffice, XFCE and others.

Hopefully you'll get a request for more information or feedback of some sort within a fortnight.
Please keep us posted.

Best,

A.

Hello:

Hmm ...

You may want to have a read here and here.
ie: Enter BIOS during power on (before Windows loads)

The first page is for the first L14 series (type 20U1, 20U2) and the second is for the following L14 series (type 20U5, 20U6) ThinkPads.
The BIOS seem to be the same.

I don't have one of those laptops so I really cannot say, but it seems to me that you may not be accessing the whole of the BIOS settings.

Best,

A.

Hello:

Hmm ...
No.

It's

For fuck's sake why?

Seriously, just who comes up with these dumb ideas?

which is one of the smartest and most useful Linux commands.

A.