Re: package managers problem

[tomas]

On Fri, Jun 16, 2023 at 03:33:23PM -0400, Felix Miata wrote:
> gene heskett composed on 2023-06-16 14:32 (UTC-0400):
> 
> > greetings, just had to reinstall bullseye. from an 11.2 netinstall.
> 
> > Sudo -E cannot run synaptic, and cannot run it from menu pulldown after 
> > entering my pw. So what package manager with a gui for selection is 
> > compatible with wayland?
> 
> Switching to Wayland at 90 years old to run CRCs and other machinery, really? 
> I
> have yet to open a Wayland session. Hopefully I won't live long enough to be
> forced to switch, and I'm younger than you by at least a decade.

That makes two of us :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: package managers problem

[tomas]

On Fri, Jun 16, 2023 at 11:03:59PM -0400, pa...@quillandmouse.com wrote:

[...]

> Please forgive my ignorance. But from what I've heard, apt and apt-get
> manage packages differently, and aptitude does it differently as well.
> Why isn't there a ONE WAY for packages to be managed?

Actually they all share the database holding the package state (OK,
some add some extra bits and pieces, but basically that is it).

Some are just frontends which bundle functionality, to take from you
the burden of remembering whether you have to say "apt-get install"
or "apt-cache search" -- you just say "apt install" or "apt search".

See, with projects which are around for a while you don't just change
interfaces of basic utilities willy-nilly. This takes some planning
and sometimes quite a bit of pain to strike a balance between moving
forward (for some value of forward) and not throwing too many users
under the bus.

>You'd think this
> would a high priority for the Debian team. If the answer is, "We don't
> want to break stuff from long ago", why not just deprecate things over
> time?

Debian does have its deprecation policies. That's why.

> And why hasn't anyone made a Wayland-native port of Synaptic? Is it
> planned? If not, why not?

Have at it :-)

I'll stay with X [1] thankyouverymuch.

Cheers

[1] Of course, this is irrelevant. It only wants to illustrate
   the problem. For a feature to come forward, you need some
   enthusiastic devels and some users for it.
-- 
t


signature.asc
Description: PGP signature

Re: package managers problem

[gene heskett]

On 6/16/23 23:04, pa...@quillandmouse.com wrote:
[...]

Please forgive my ignorance. But from what I've heard, apt and apt-get
manage packages differently, and aptitude does it differently as well.
Why isn't there a ONE WAY for packages to be managed? You'd think this
would a high priority for the Debian team. If the answer is, "We don't
want to break stuff from long ago", why not just deprecate things over
time?

And why hasn't anyone made a Wayland-native port of Synaptic? Is it
planned? If not, why not?

Paul


Heck of a good question Paul, but I really don't expect to get an answer 
that makes sense on THIS list.


Come on debian, can't this be fixed? The lack of a good graphical 
program that works like synaptic is a major PITA.  Somebody suggested 
apper but ask apt to install it and it drags in 164 other dependencies, 
stuff I've never heard of before with what to me are 100% non-sensical 
names.


So how about a justifiable explanation?

How many 3 letter back doors are in that stuff?

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: package managers problem

[John Hasler]

Paul writes:
> Please forgive my ignorance. But from what I've heard, apt and apt-get
> manage packages differently, and aptitude does it differently as well.


Apt-get:

DESCRIPTION

apt-get is the command-line tool for handling packages, and may be
considered the user's "back-end" to other tools using the APT
library. Several "front-end" interfaces exist, such as
aptitude(8), synaptic(8) and wajig(1).

Apt:

DESCRIPTION

apt provides a high-level commandline interface for the package
   management system. It is intended as an end user interface and
   enables some options better suited for interactive usage by
   default compared to more specialized APT tools like apt-get(8)
   and apt-cache(8).

All of these tools are front-ends for the apt library, which is what
actually manages packages.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: Strange message

[Maureen L Thomas]

I followed the instructions but they did not work.  Now what?


On 6/15/23 8:27 AM, ogis wrote:

Hello. Just check this:

https://forums.debian.net/viewtopic.php?t=150193


15.06.2023 08:09, Maureen L Thomas пишет:
Failed to receive portal pid: org.freedesktop.DBus, error, 
NameHasNoOwner

Re: package managers problem

[John Hasler]

Paul writes:
> Here's a reason to use a GUI package manager (or even aptitude): you
> want a package which does X, and you don't know which packages do
> that.

And therefor I use apt-cache search to find it.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: package managers problem

[Stefan Monnier]

> I really don't understand why people want a GUI package manager at all.

I always use the plain "batch command line" tools like `apt` or
`aptitude`, indeed (and not the ncurses UI of `aptitude` which I found
difficult to use when I tried it).

But I think the reason is quite simple: while most people are very
familiar with the "GUI language" (i.e. the conventions of what means
what and how you interact with the various elements) because it's quite
standardized across most devices nowadays, most computer users are not
familiar with the unix command line language nor with the ncurses UI
language (which is not even standardized, so every ncurses application
has to be learned individually).


Stefan

Re: package managers problem

[paulf]

On Fri, 16 Jun 2023 15:14:43 -0400
gene heskett  wrote:

> On 6/16/23 14:38, Jeffrey Walton wrote:
> > On Fri, Jun 16, 2023 at 2:32 PM gene heskett 
> > wrote:
> >>
> >> greetings, just had to reinstall bullseye. from an 11.2 netinstall.
> >>
> >> Sudo -E cannot run synaptic, and cannot run it from menu pulldown
> >> after entering my pw. So what package manager with a gui for
> >> selection is compatible with wayland? Something I can get apt to
> >> install from a sudo -i shell?
> > 
> > For Debian, the official package manager is Apt and Aptitude. See
> > https://wiki.debian.org/Aptitude .
> > 
> > Jeff
> > .
> Has aptitude been tamed?
> 
> I've stayed away from it now for years because its torn the system
> down with its idea of dependencies, to doing a reinstall 4 times in
> the decade passed. I do not trust it at all, been burned to the
> ground too many times.  With apt, I was able to remove cups-browsed
> all by itself with apt so the brother factory drivers could actually
> run my pair of brother printers just now. I have serious doubts
> aptitude would have allowed that without nuking 300 other files too.
> Like the kernel thats running once.  That is not an ooops but nobody
> seemed to notice at the time. The arm version seems to be ok, but x86
> stuff?
> 
> Cheers, Gene Heskett.

Please forgive my ignorance. But from what I've heard, apt and apt-get
manage packages differently, and aptitude does it differently as well.
Why isn't there a ONE WAY for packages to be managed? You'd think this
would a high priority for the Debian team. If the answer is, "We don't
want to break stuff from long ago", why not just deprecate things over
time?

And why hasn't anyone made a Wayland-native port of Synaptic? Is it
planned? If not, why not?

Paul


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

Re: package managers problem

[paulf]

On Fri, 16 Jun 2023 18:17:07 -0400
gene heskett  wrote:

[snip]

> So all my cnc machines are still on buster, and will stay there until 
> wayland CAN replace X11.  wayland is just barely able to run a simple 
> gui, and until it can transparently do everything X11 has done for 
> decades, its not open for discussion. Wayland is a cripple, and will 
> remain so until I can ssh -Y into one of my buster machines and 
> everything in its gui works just as if I was at that machines
> keyboard, mouse and monitor.  Until then wayland is still knocking on
> the door begging to be let in.

Wayland's not bad, it just doesn't work for you. I sympathize. I look
forward to the day when Wayland can replace the creaky Xorg system. But
the problem is that so many programs we take for granted haven't been
ported to Wayland; they have to run in Xwayland if they'll run at all.
I'd love to embrace Wayland, but like you, I believe there are just too
many programs I need which Wayland won't support natively.

Paul

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

Re: package managers problem

[paulf]

On Fri, 16 Jun 2023 19:40:54 -0400
gene heskett  wrote:

> On 6/16/23 18:41, Greg Wooledge wrote:
> > On Fri, Jun 16, 2023 at 06:35:48PM -0400, gene heskett wrote:
> >> 0 upgraded, 164 newly installed, 0 to remove and 0 not upgraded.
> >> Need to get 44.5 MB of archives.
> >> After this operation, 206 MB of additional disk space will be used.
> > 
> > I really don't understand why people want a GUI package manager at
> > all. The last time I used anything even remotely *close* to a GUI
> > package manager was dselect, back in the previous century.  And
> > that was a curses (terminal) interface, not an X11 one.
> > 
> > In the last two decades, I haven't used or wanted anything fancier
> > than apt(-get).
> > 
> > Now, granted, this is just my personal stance.  I may be atypical.
> > That said, what exactly does a GUI package manager offer you, that
> > you can't get from "apt install thing-i-want"?
> > 
> > .
> Like looking at the menu in a fancy restaurant, if you don't have a
> menu to read, how that heck are you supposed to know what you want?
> 
> Cheers, Gene Heskett.

+1

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

Re: package managers problem

[paulf]

On Fri, 16 Jun 2023 18:41:08 -0400
Greg Wooledge  wrote:

> On Fri, Jun 16, 2023 at 06:35:48PM -0400, gene heskett wrote:
> > 0 upgraded, 164 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 44.5 MB of archives.
> > After this operation, 206 MB of additional disk space will be used.
> 
> I really don't understand why people want a GUI package manager at
> all. The last time I used anything even remotely *close* to a GUI
> package manager was dselect, back in the previous century.  And that
> was a curses (terminal) interface, not an X11 one.
> 
> In the last two decades, I haven't used or wanted anything fancier
> than apt(-get).
> 
> Now, granted, this is just my personal stance.  I may be atypical.
> That said, what exactly does a GUI package manager offer you, that
> you can't get from "apt install thing-i-want"?
> 

Here's a reason to use a GUI package manager (or even aptitude): you
want a package which does X, and you don't know which packages do that.
I install stuff with apt and apt-get all the time, but only once I know
the package name.

Synaptic is easier to "navigate" because, in a terminal, aptitude is
all the same size text in different colors. Things sort of jumble
together, at least for me. The synaptic GUI separates things out and
it's easier to pick out what you want to focus on on screen.

Paul

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

pilote nvidia propriétaire et noyau 6.3

[F. Dubois]

Bonsoir,

Je suis en unstable, lors de la construction des modules du pilote 
nvidia (avec dkms), pour le tout récent noyau 
linux-headers-6.3.0-1-amd64 et linux-image-6.3.0-1-amd64 une erreur se 
produit.


Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j4 modules 
KERNEL_UNAME=6.3.0-1-amd64..(bad exit status: 2)

Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log for 
more information.

dkms autoinstall on 6.3.0-1-amd64/x86_64 failed for nvidia-tesla-470(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.3.0-1-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

Pas de rapport de bug, d'info...

La fin de /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log

/usr/src/linux-headers-6.3.0-1-common/scripts/check-local-export 
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-p2p.o
# cmd_gen_symversions_c 
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-p2p.o
  if nm /var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-p2p.o 
2>/dev/null | grep -q __ksymtab; then  gcc-12 -E -D__GENKSYMS__ 
-Wp,-MMD,/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/.nv-p2p.o.d 
-nostdinc -I/usr/src/linux-headers-6.3.0-1-common/arch/x86/include 
-I./arch/x86/include/generated 
-I/usr/src/linux-headers-6.3.0-1-common/include -I./include 
-I/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-6.3.0-1-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-6.3.0-1-common/include/linux/compiler-version.h 
-include /usr/src/linux-headers-6.3.0-1-common/include/linux/kconfig.h 
-include 
/usr/src/linux-headers-6.3.0-1-common/include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-6.3.0-1-common/= 
-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int 
-Werror=return-type -Wno-format-security -funsigned-char -std=gnu11 
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=branch 
-fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup 
-mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -mindirect-branch-cs-prefix 
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all 
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks 
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow 
-Wno-address-of-packed-member -O2 -fno-allow-store-data-races 
-Wframe-larger-than=2048 -fstack-protector-strong -Wno-main 
-Wno-unused-but-set-variable -Wno-unused-const-variable 
-Wno-dangling-pointer -ftrivial-auto-var-init=zero 
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry 
-DCC_USING_FENTRY -falign-functions=16 -Wdeclaration-after-statement 
-Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation 
-Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized 
-Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 
-fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time 
-Werror=incompatible-pointer-types -Werror=designated-init 
-Wno-packed-not-aligned -g 
-I/var/lib/dkms/nvidia-tesla-470/470.182.03/build/common/inc 
-I/var/lib/dkms/nvidia-tesla-470/470.182.03/build -Wall -MD 
-Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE 
-DNVRM -DNV_VERSION_STRING=\"470.182.03\" -Wno-unused-function 
-Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel 
-DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 
-DNV_KERNEL_INTERFACE_LAYER 
-I/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia 
-DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -DMODULE  
-DKBUILD_BASENAME='"nv_p2p"' -DKBUILD_MODNAME='"nvidia"' 
-D__KBUILD_MODNAME=kmod_nvidia 
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-p2p.c | 
scripts/genksyms/genksyms   -r /dev/null >> 
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/.nv-p2p.o.cmd; fi
make[2]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050 : 
/var/lib/dkms/nvidia-tesla-470/470.182.03/build] Erreur 2

make[2] : on quitte le répertoire « /usr/src/linux-headers-6.3.0-1-amd64 »
make[1]: *** [Makefile:238 : __sub-make] Erreur 2
make[1] : on quitte le répertoire « /usr/src/linux-headers-6.3.0-1-common »
make: *** [Makefile:80 : modules] Erreur 2

Cela est-il arrivé chez quelqu'un  ?

Librement,

Fabien

Re: package managers problem

[Greg Wooledge]

On Fri, Jun 16, 2023 at 07:40:54PM -0400, gene heskett wrote:
> On 6/16/23 18:41, Greg Wooledge wrote:
> > Now, granted, this is just my personal stance.  I may be atypical.
> > That said, what exactly does a GUI package manager offer you, that
> > you can't get from "apt install thing-i-want"?
> > 
> > .
> Like looking at the menu in a fancy restaurant, if you don't have a menu to
> read, how that heck are you supposed to know what you want?

I agree that discovering the *package name* of the thing-u-want is
often the hard part.  I'm not sure how much easier it is to learn the
package name with a GUI application vs. "apt search" or similar
commands.  In lots of cases, there are just a slew of false positive
results (libraries/modules to interface with the thing-u-want in some
obscure language, etc.), but I don't think sifting through those is
any easier in a GUI than in a terminal.  Maybe I'm wrong about that.

In any case, for people who've been using Debian as long as we have,
one would think we have a pretty good idea which packages we want,
when we're installing a new system.

Re: package managers problem

[gene heskett]

On 6/16/23 18:41, Greg Wooledge wrote:

On Fri, Jun 16, 2023 at 06:35:48PM -0400, gene heskett wrote:

0 upgraded, 164 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.5 MB of archives.
After this operation, 206 MB of additional disk space will be used.


I really don't understand why people want a GUI package manager at all.
The last time I used anything even remotely *close* to a GUI package
manager was dselect, back in the previous century.  And that was a curses
(terminal) interface, not an X11 one.

In the last two decades, I haven't used or wanted anything fancier
than apt(-get).

Now, granted, this is just my personal stance.  I may be atypical.
That said, what exactly does a GUI package manager offer you, that
you can't get from "apt install thing-i-want"?

.
Like looking at the menu in a fancy restaurant, if you don't have a menu 
to read, how that heck are you supposed to know what you want?


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: package managers problem

[David]

On Fri, 2023-06-16 at 18:41 -0400, Greg Wooledge wrote:
> On Fri, Jun 16, 2023 at 06:35:48PM -0400, gene heskett wrote:
> > 0 upgraded, 164 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 44.5 MB of archives.
> > After this operation, 206 MB of additional disk space will be used.
> 
> I really don't understand why people want a GUI package manager at
> all.
> The last time I used anything even remotely *close* to a GUI package
> manager was dselect, back in the previous century.  And that was a
> curses
> (terminal) interface, not an X11 one.
> 
> In the last two decades, I haven't used or wanted anything fancier
> than apt(-get).
> 
> Now, granted, this is just my personal stance.  I may be atypical.
> That said, what exactly does a GUI package manager offer you, that
> you can't get from "apt install thing-i-want"?

Why I use aptitude is exactly because of the curses interface.
I can run it from the terminal, but if I want to search for a package
or gain some other information on it, such as dependencies, it's all
there at a glance.
Aptitude install/remove ... whatever, does it all, but I have that
information resource there if required.
Cheers!

-- 
A Kiwi in Australia,
doing my bit toward raising the national standard.

Re: package managers problem

[Greg Wooledge]

On Fri, Jun 16, 2023 at 06:35:48PM -0400, gene heskett wrote:
> 0 upgraded, 164 newly installed, 0 to remove and 0 not upgraded.
> Need to get 44.5 MB of archives.
> After this operation, 206 MB of additional disk space will be used.

I really don't understand why people want a GUI package manager at all.
The last time I used anything even remotely *close* to a GUI package
manager was dselect, back in the previous century.  And that was a curses
(terminal) interface, not an X11 one.

In the last two decades, I haven't used or wanted anything fancier
than apt(-get).

Now, granted, this is just my personal stance.  I may be atypical.
That said, what exactly does a GUI package manager offer you, that
you can't get from "apt install thing-i-want"?

Re: package managers problem

[gene heskett]

On 6/16/23 17:49, Antonio Russo wrote:


On 2023-06-16 13:14, gene heskett wrote:

Has aptitude been tamed?

I've stayed away from it now for years because its torn the system down with 
its idea of dependencies, to doing a reinstall 4 times in the decade passed. I 
do not trust it at all, been burned to the ground too many times.  With apt, I 
was able to remove cups-browsed all by itself with apt so the brother factory 
drivers could actually run my pair of brother printers just now. I have serious 
doubts aptitude would have allowed that without nuking 300 other files too. 
Like the kernel thats running once.  That is not an ooops but nobody seemed to 
notice at the time. The arm version seems to be ok, but x86 stuff?

Cheers, Gene Heskett.



If anything gets even a tiny bit hairy, I work in aptitude. That said, I 
disabled
"automatically fix broken packages before installing or removing" under 
"dependency
handling" in options->preferences .  I always review what exactly is being done 
(in
those situations) by looking over what is expressed after hitting "g" and making
sure I'm happy with it.

I (personally) use this.  It's extremely powerful if used correctly, but can be
tricky.  Force a package installation by highlighting something and pressing 
"+".
You can mark things manually installed with "m" (and auto-installed/removable 
with
"M"). If things go south after one action, press "Control-u" to undo that. 
Things
can get tangled here, but you always see what happens before you do it!  You may
have to review suggested resolutions of things ("!" will apply the 
recommendation,
sometimes this does NOTHING, which is a little counter-intuitive at first).  Set
a package to be kept in the original state with ":", and force-hold to it's 
current
version (and pin it there) with "=".  Notice that ":" may still uninstall a 
package
if it is automatically installed and nothing depends on it (anymore)!

I just tried to get apper working, and could not get it to ask for authorization
through polkit.  That might be a trixie bug, a "I locked polkit down too tight"
bug, or a wayland bug.  If you *really* want a gui, I'd at least try apper. I
wasn't willing to try synaptic (GTK dependencies and all).

I have a ott session going but the response to tell apt to install apper 
is scary:


he following NEW packages will be installed:
  apper apper-data appstream apt-config-icons debconf-kde-data 
debconf-kde-helper kded5 kio kwayland-data kwayland-integration 
libappstreamqt2 libaribb24-0 libcddb2
  libdbusmenu-qt5-2 libdebconf-kde1 libdouble-conversion3 libdvbpsi10 
libebml5 libfam0 libgles2 libhfstospell11 libixml10 libkf5archive5 
libkf5attica5 libkf5auth-data
  libkf5authcore5 libkf5codecs-data libkf5codecs5 libkf5completion-data 
libkf5completion5 libkf5config-bin libkf5config-data libkf5configcore5 
libkf5configgui5
  libkf5configwidgets-data libkf5configwidgets5 libkf5coreaddons-data 
libkf5coreaddons5 libkf5crash5 libkf5dbusaddons-bin 
libkf5dbusaddons-data libkf5dbusaddons5
  libkf5doctools5 libkf5globalaccel-bin libkf5globalaccel-data 
libkf5globalaccel5 libkf5globalaccelprivate5 libkf5guiaddons5 
libkf5i18n-data libkf5i18n5
  libkf5iconthemes-bin libkf5iconthemes-data libkf5iconthemes5 
libkf5idletime5 libkf5itemviews-data libkf5itemviews5 
libkf5jobwidgets-data libkf5jobwidgets5 libkf5kiocore5
  libkf5kiogui5 libkf5kiontlm5 libkf5kiowidgets5 
libkf5notifications-data libkf5notifications5 libkf5service-bin 
libkf5service-data libkf5service5 libkf5solid5
  libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 
libkf5sonnetui5 libkf5textwidgets-data libkf5textwidgets5 
libkf5wallet-bin libkf5wallet-data libkf5wallet5
  libkf5waylandclient5 libkf5widgetsaddons-data libkf5widgetsaddons5 
libkf5windowsystem-data libkf5windowsystem5 libkf5xmlgui-bin 
libkf5xmlgui-data libkf5xmlgui5
  libkwalletbackend5-5 libkworkspace5-5 liblua5.2-0 libmad0 
libmatroska7 libmd4c0 libmtp-common libmtp-runtime libmtp9 libnfs13 
libopenmpt-modplug1 libpackagekitqt5-1
  libpcre2-16-0 libphonon4qt5-4 libphonon4qt5-data libplacebo72 
libpolkit-qt5-1-1 libprotobuf-lite23 libproxy-tools libqt5core5a 
libqt5dbus5 libqt5designer5 libqt5gui5
  libqt5help5 libqt5network5 libqt5printsupport5 libqt5qml5 
libqt5qmlmodels5 libqt5quick5 libqt5sql5 libqt5sql5-sqlite libqt5svg5 
libqt5test5 libqt5texttospeech5
  libqt5waylandclient5 libqt5waylandcompositor5 libqt5widgets5 
libqt5x11extras5 libqt5xml5 libqt5xmlpatterns5 libresid-builder0c2a 
libsdl-image1.2 libsdl1.2debian
  libsidplay2 libspatialaudio0 libupnp13 libva-wayland2 libvlc-bin 
libvlc5 libvlccore9 libvoikko1 libxcb-icccm4 libxcb-image0 
libxcb-keysyms1 libxcb-render-util0
  libxcb-res0 libxcb-xinerama0 libxcb-xinput0 libxcb-xkb1 libxcb-xv0 
libxkbcommon-x11-0 media-player-info phonon4qt5 phonon4qt5-backend-vlc 
python3-distro-info
  python3-pyqt5 python3-pyqt5.sip python3-software-properties 
qt5-gtk-platformtheme qtspeech5-speechd-plugin qttranslations5-l10n 
qtwayland5 

Re: package managers problem

[gene heskett]

On 6/16/23 15:33, Felix Miata wrote:

gene heskett composed on 2023-06-16 14:32 (UTC-0400):


greetings, just had to reinstall bullseye. from an 11.2 netinstall.



Sudo -E cannot run synaptic, and cannot run it from menu pulldown after
entering my pw. So what package manager with a gui for selection is
compatible with wayland?


Switching to Wayland at 90 years old to run CRCs and other machinery, really? I
have yet to open a Wayland session. Hopefully I won't live long enough to be
forced to switch, and I'm younger than you by at least a decade.


It not my choice. I tried to fix a 6 month old udev bug debian refuses 
to fix, even bokworm is said to have it yet, and the fix-it script 
pulled in by way of an apt session 39 security fixes and recommended I 
reboot, but when I did, my passwd had been nulled or something, so I 
could not get past the login. 5 re-install attempts later because I had 
to unplug everything, including the 6 drives I wanted to save.


I finally got a single disk install that was safe and I still had my 
/home which is on a separate raid10 of 4 samsung 1T ssd's with 900G of 
each drive as md0p1, 60G's remaining is swap, and a few remaining megs 
is md2. Not in use but...


After this 3 day debacle I should compare the actual size of /etc, to 
whats left and if there is enough room, make a backup of /etc on md2, 
otherwise I'll just copy the important stuff like my hosts file so I 
don't have to reinvent that wheel.


So all my cnc machines are still on buster, and will stay there until 
wayland CAN replace X11.  wayland is just barely able to run a simple 
gui, and until it can transparently do everything X11 has done for 
decades, its not open for discussion. Wayland is a cripple, and will 
remain so until I can ssh -Y into one of my buster machines and 
everything in its gui works just as if I was at that machines keyboard, 
mouse and monitor.  Until then wayland is still knocking on the door 
begging to be let in. I don't actually carve metal from this machine, as 
I cannot SEE the machine, but I do all the admin or gcode writing stuff 
from this office chair.


But you give me credit for around 17 months I haven't yet lived. 
Somebody on tv once made the remark about his age, George Burns IIRC, 
claiming he didn't buy green banana's, which is about how I shop since 
I'm alone now.

Take care & stay well Felix.

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: package managers problem

[Antonio Russo]

On 2023-06-16 13:14, gene heskett wrote:
> Has aptitude been tamed?
> 
> I've stayed away from it now for years because its torn the system down with 
> its idea of dependencies, to doing a reinstall 4 times in the decade passed. 
> I do not trust it at all, been burned to the ground too many times.  With 
> apt, I was able to remove cups-browsed all by itself with apt so the brother 
> factory drivers could actually run my pair of brother printers just now. I 
> have serious doubts aptitude would have allowed that without nuking 300 other 
> files too. Like the kernel thats running once.  That is not an ooops but 
> nobody seemed to notice at the time. The arm version seems to be ok, but x86 
> stuff?
> 
> Cheers, Gene Heskett.


If anything gets even a tiny bit hairy, I work in aptitude. That said, I 
disabled
"automatically fix broken packages before installing or removing" under 
"dependency
handling" in options->preferences .  I always review what exactly is being done 
(in
those situations) by looking over what is expressed after hitting "g" and making
sure I'm happy with it.

I (personally) use this.  It's extremely powerful if used correctly, but can be
tricky.  Force a package installation by highlighting something and pressing 
"+".
You can mark things manually installed with "m" (and auto-installed/removable 
with
"M"). If things go south after one action, press "Control-u" to undo that. 
Things
can get tangled here, but you always see what happens before you do it!  You may
have to review suggested resolutions of things ("!" will apply the 
recommendation,
sometimes this does NOTHING, which is a little counter-intuitive at first).  Set
a package to be kept in the original state with ":", and force-hold to it's 
current
version (and pin it there) with "=".  Notice that ":" may still uninstall a 
package
if it is automatically installed and nothing depends on it (anymore)!

I just tried to get apper working, and could not get it to ask for authorization
through polkit.  That might be a trixie bug, a "I locked polkit down too tight"
bug, or a wayland bug.  If you *really* want a gui, I'd at least try apper. I
wasn't willing to try synaptic (GTK dependencies and all).

You might be able to get your Xwayland token to root, but I don't recommend
running root GUI applications.

Best,
Antonio

OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: package managers problem

[David Wright]

On Fri 16 Jun 2023 at 15:14:43 (-0400), gene heskett wrote:

> Has aptitude been tamed?

I don't think aptitude ever needed taming, unlike your TERM setting.

> I've stayed away from it now for years because its torn the system
> down with its idea of dependencies, to doing a reinstall 4 times in
> the decade passed. I do not trust it at all, been burned to the ground
> too many times.  With apt, I was able to remove cups-browsed all by
> itself with apt so the brother factory drivers could actually run my
> pair of brother printers just now. I have serious doubts aptitude
> would have allowed that without nuking 300 other files too. Like the
> kernel thats running once.  That is not an ooops but nobody seemed to
> notice at the time. The arm version seems to be ok, but x86 stuff?

You reported running aptitude with the ncurses interface, and with
a TERM setting that meant the screen became more and more encumbered
with cruft. There's no knowing what characters were being sent to
the program that were intended for driving the terminal.

You wrote "with aptitude, like mc, whatever terminal its running IN,
MUST DO ncurses emulations.  And that is compulsory!" In fact, all you
have to do to avoid ncurses is to supply an action on the command line.

Sorry I can't help with choosing a GUI. I've never seen the point for
running such a package manager.

Cheers,
David.

Re: package managers problem

[Felix Miata]

gene heskett composed on 2023-06-16 14:32 (UTC-0400):

> greetings, just had to reinstall bullseye. from an 11.2 netinstall.

> Sudo -E cannot run synaptic, and cannot run it from menu pulldown after 
> entering my pw. So what package manager with a gui for selection is 
> compatible with wayland?

Switching to Wayland at 90 years old to run CRCs and other machinery, really? I
have yet to open a Wayland session. Hopefully I won't live long enough to be
forced to switch, and I'm younger than you by at least a decade.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: mail --> mutt

[Jordi]

Gracies per les respostes i perdoneu que trigui a contestar, però a la
feina no puc mirar el correu (per falta de temps)

El dj. 15 de 06 de 2023 a les 20:57 +0200, en/na Narcis Garcia va
escriure:
> El 15/6/23 a les 18:05, Ernest Adrogué ha escrit:
> > 2023-06-15, 10:29 (+0200); Jordi escriu:
> > > Ja fa un temps vaig voler configurar postfix i alguna altra cosa
> > > i no
> > > me'n vaig sortir, el que tinc ara son aplicacions que envien
> > > notificacions o redirigeixo la sortida a mail o a mutt segons si
> > > vull
> > > local o remotament.
> > 
> > Vols dir que amb el mail envies correu a adreces locals i amb el
> > mutt a
> > adreces d'internet?
> 
> Suposo que no es referia en ordre respectiu.

Exacte, algunes notificacions amb mail i altres més importants amb mutt
perquè arribin a l'ordinador de casa via el servidor de correu que
utilitzo (runbox). És així per evitar que al final, i com ha passat
alguna vegada, per algun error s'han enviat massa notificacions i al
final van a la carpeta spam o bé em passo de quota.

La meva primera opció era enviar totes les notificacions directament a
l'ordinador de casa, però ho vaig descartar perquè no tenia forma de
veure si era prou segur, i tampoc vull deixar un sucós servidor smtp
mal configurat. 

A part de l'ordinador de casa tinc dues Raspberry PI situades a
diferents punts geogràfics i volia estalviar-me el mosh que faig a
diari, enviant totes les notificacions via internet.

De moment ho deixaré com ho tinc

Gracies

Jordi
> 
> > > Amb això, segons les configuracions de les aplicacions si fico
> > > que
> > > enviïn el correu per exemple a jomat...@correumeu.cat simplement
> > > no
> > > envien res.
> > > 
> > > Mai he aconseguit configurar correctament postfix perquè enviï el
> > > correu al mateix ordinador, la mateixa xarxa o internet segons
> > > les
> > > meves necessitats. Tampoc vull deixar un servidor de smtp
> > > accessible
> > > des d'internet.
> > 
> > No és recomanable utilitzar postfix per enviar correu a internet. 
> > El
> > més pràctic és utilitzar el postfix (o un altre MTA) per enviar
> > correu
> > localment al mateix ordinador, i si els usuaris volen enviar correu
> > a
> > internet que utilitzin un client de correu (com el mutt) que
> > permeti
> > enviar correu a través d'un servidor de correu remot (com Gmail).
> 
> Postfix, igual com EXIM i Sendmail, és un «agent de transport de
> correu» 
> (MTA) i, com a tal, està ben orientat a l'admissió i transmissió de 
> cartes via SMTP, és a dir amb Internet.
> Com que està pensat per als serveis massius i ben exposats als
> elements, 
> convé configurar-lo adequadament, i val la pena si es tracten
> múltiples 
> comptes i que són utilitzables des d'Internet.
> 
> Però m'ha sembla que en Jordi tracta aquests enviaments de correu-e 
> només per a notificacions molt personalitzades.
> 
> > Llavors, per llegir el correu jo el que tinc és un servidor IMAP
> > local
> > (dovecot) i d'aquesta manera puc utilitzar qualsevol client de
> > correu
> > que em vingui de gust.  Les bústies locals estan sincronitzades amb
> > les
> > bústies remotes allotjades al meu proveïdor de correu mitjançant un
> > programa que es diu offlineimap.
> 
> Dovecot, igual com el Courier-IMAP, és principalment un «agent
> d'entrega 
> de correu» (MDA) i, com a tal, està ben orientat a dipositar i
> processar 
> cartes a bústies, i fer les bústies mitjançant comptes POP i/o IMAP.
> També pot fer d'intermediari d'altres MDA, tal com el Postfix pot fer
> d'intermediari d'altres MTA.
> 
> > D'aquesta manera està tot integrat.  Tant el correu local com el
> > d'internet va a parar a les mateixes bústies, i puc treballar
> > indistintament amb les bústies locals com amb les remotes (per
> > exemple,
> > amb webmail) ja que totes tenen el mateix correu.
> 
> M.Thunderbird, K-9 Mail, Roundcube i Mutt són «agents d'usuari de 
> correu» (MUA) que, com a tals, estan orientats a utilitzar els
> serveis 
> de MTA i MDA per a enviar, llegir i organitzar cartes de correu 
> electrònic. Són la interfície aparent del concepte de correu
> electrònic.
> 
> Val la pena esmentar la comanda «mail» del sistema operatiu GNU, que 
> està pensada per a enviar instantàniament un correu a través del MTA
> que 
> ja tinguis funcionant al mateix host, o el «swaks» que fa el mateix
> amb 
> el servei SMTP que li indiquis.
> i també val la pena esmentar plataformes web com NextCloud o Citadel,
> que inclouen MUA entre moltes coses.
> 
> Per a fer solament notificacions, jo faig servir sovint el «mail» o
> el 
> «swaks», un o altre en funció de si l'ordinador té o no té funcionant
> un 
> MTA propi.

Re: package managers problem

[gene heskett]

On 6/16/23 14:38, Jeffrey Walton wrote:

On Fri, Jun 16, 2023 at 2:32 PM gene heskett  wrote:


greetings, just had to reinstall bullseye. from an 11.2 netinstall.

Sudo -E cannot run synaptic, and cannot run it from menu pulldown after
entering my pw. So what package manager with a gui for selection is
compatible with wayland? Something I can get apt to install from a sudo
-i shell?


For Debian, the official package manager is Apt and Aptitude. See
https://wiki.debian.org/Aptitude .

Jeff
.

Has aptitude been tamed?

I've stayed away from it now for years because its torn the system down 
with its idea of dependencies, to doing a reinstall 4 times in the 
decade passed. I do not trust it at all, been burned to the ground too 
many times.  With apt, I was able to remove cups-browsed all by itself 
with apt so the brother factory drivers could actually run my pair of 
brother printers just now. I have serious doubts aptitude would have 
allowed that without nuking 300 other files too. Like the kernel thats 
running once.  That is not an ooops but nobody seemed to notice at the 
time. The arm version seems to be ok, but x86 stuff?


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: Apache logs and systemd

[Andy Smith]

Hello,

On Fri, Jun 16, 2023 at 12:38:40PM -0500, Tom Browder wrote:
> I should have mentioned in OP the logs are in a dir under my own apache
> installation dir, and they are text files. I’ll try to get “logrotate” to
> take them over.

It should happen by default.

Normally logrotate is called by a systemd timer:

$ systemctl status logrotate.timer

(on a sysvinit system this will be by an init script instead, but
again, I'm assuming you haven't gone too far out of your way to be
non-default)

The apache2 package ships the logrotate config snippet at
/etc/logrotate.d/apache2. That file should show the paths to your
apache2 log files.

Cheers,
Andy

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

Re: package managers problem

[Jeffrey Walton]

On Fri, Jun 16, 2023 at 2:32 PM gene heskett  wrote:
>
> greetings, just had to reinstall bullseye. from an 11.2 netinstall.
>
> Sudo -E cannot run synaptic, and cannot run it from menu pulldown after
> entering my pw. So what package manager with a gui for selection is
> compatible with wayland? Something I can get apt to install from a sudo
> -i shell?

For Debian, the official package manager is Apt and Aptitude. See
https://wiki.debian.org/Aptitude .

Jeff

package managers problem

[gene heskett]

greetings, just had to reinstall bullseye. from an 11.2 netinstall.

Sudo -E cannot run synaptic, and cannot run it from menu pulldown after 
entering my pw. So what package manager with a gui for selection is 
compatible with wayland? Something I can get apt to install from a sudo 
-i shell?


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: puis-je faire confiance a ce disque ?

[Th.A.C]

Le 16/06/2023 à 08:34, BERTRAND Joël a écrit :


Bonjour,

J'en pense que c'est un Seagate. J'ai eu des tas de disques comme ça
qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
problème est un firmware buggué et que Seagate n'en a rien à faire. Tant
que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.


je confirme, tous les seagate (sans exception) que j'ai eu dans les 
mains ont ce comportement, et ça ne date pas d'aujourd'hui.


Thierry

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[Eric DEGENETAIS]

Le ven. 16 juin 2023 à 16:36, Frédéric BOITEUX 
a écrit :

> Bonjour,
>
bonsoir

>
> > Quand /var/log/ se remplit de messages d'erreur (messages syslog et
> user.messages), ça sonne puisque plus rien qui utilise /var ne peut
> fonctionner !
> > Si root supprime les fichiers remplis de la même alerte, /var reste
> rempli à 100%.
>
> Oui, c’est un classique ! Tant que le [gros] fichier est ouvert par un
> processus, il existe encore et sa place n’est pas libérée. Ici, le truc
> c’est de relancer le service qui écrit dans les logs, probablement rsyslog
> : le processus en cours est terminé, et les fichiers supprimés sont alors
> réellement libérés…
>
> Tronquer les logs (c'est à dire réécire un fichier vide au lieu de le
supprimer) fonctionne probablement aussi. Il me semble d'ailleurs que
logrotate offre cette option (je n'ai pas les détails sous la main à
l'instant)

> Cdlt,
> Fred (pas trop barbu :-)
>

Éric Dégenètais

Re: Apache logs and systemd

[Tom Browder]

On Thu, Jun 15, 2023 at 16:57 Andy Smith  wrote:

> Hi Tom,
>
> On Thu, Jun 15, 2023 at 01:52:10PM -0500, Tom Browder wrote:
> > Maybe it's related to the rsyslog changes ?
>
> apache by default does not use a syslog for logging though, it

…

Thanks, Andy.

I should have mentioned in OP the logs are in a dir under my own apache
installation dir, and they are text files. I’ll try to get “logrotate” to
take them over.

Best regards,

-Tom

Re: Bluetooth driver error on boot after upgrade to bookworm

[The Wanderer]

On 2023-06-16 at 11:00, Unni wrote:

> Hello,
> 
> I am getting Bluetooth firmware error after upgrade. I've tried 
> reinstalling firmware-iwlwifi. But no luck. I've added non-free-firmware 
> in apt source, so thats not the issue. Help me to fix the error on booth.

From that last, I'm presuming that you've rebooted since the upgrade,
and that it's at boot time that the error appears.

> ~# dmesg | egrep -i 'bluetooth'
> [6.051557] Bluetooth: Core ver 2.22
> [6.051579] NET: Registered PF_BLUETOOTH protocol family
> [6.051580] Bluetooth: HCI device and connection manager initialized
> [6.051587] Bluetooth: HCI socket layer initialized
> [6.051589] Bluetooth: L2CAP socket layer initialized
> [6.051593] Bluetooth: SCO socket layer initialized
> [6.093212] bluetooth hci0: firmware: failed to load 
> intel/ibt-20-0-0.sfi (-2)
> [6.093358] bluetooth hci0: firmware: failed to load 
> intel/ibt-20-0-0.sfi (-2)

I see some things online that seem to suggest that this may be a
misleading message, and that the stack may already be using the
available firmware, but is also attempting to load this lower version
and is reporting that that attempt failed. However, those mentions are
somewhat older (2021-ish?), and the messages aren't quite the same, and
it looks like they should have been fixed by now, so I'm not assuming
that they're talking about this same thing.

Can you confirm whether you're seeing any actual functionality issues
along with this change, or whether it's just the fact that the message
is appearing that has you concerned?

FWIW, I get all of the above messages except the two about firmware (I
get two about a command timeout and a "Reading Intel version command
failed" instead)...

> [7.622442] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [7.622446] Bluetooth: BNEP filters: protocol multicast
> [7.622450] Bluetooth: BNEP socket layer initialized

...and also get these three...

> [7.623488] Bluetooth: MGMT ver 1.22
> [9.011767] Bluetooth: RFCOMM TTY layer initialized
> [9.011779] Bluetooth: RFCOMM socket layer initialized
> [9.011784] Bluetooth: RFCOMM ver 1.11
> [   32.748460] Bluetooth: hci0: Opcode 0x 401 failed: -16

...but not these. I don't actually know whether Bluetooth functionality
is available on my system, because I don't think I have any hardware
suitable to pair to it. Presumably, however, the lines we have in common
should not be relevant to what you're seeing.


$ apt-file search ibt-20-0-
firmware-iwlwifi: /lib/firmware/intel/ibt-20-0-3.ddc
firmware-iwlwifi: /lib/firmware/intel/ibt-20-0-3.sfi

(This is with the same package version you referenced; it's in both
stable and testing, at the moment.)

So ibt-20-0-3.sfi exists, but not the 20-0-0 version. The question would
then seem to be why the Bluetooth stack is attempting to load that
lower-numbered version.

Given that we're talking about firmware, it may be necessary to
reinitialize the relevant modules (et possibly cetera) after the
upgrade; that can almost certainly be done by rebooting, but should also
be possible to do manually in many cases by removing and reinserting
modules. If (as suggested above) you've rebooted, then presumably this
approach has already been tried.

(In my case, I'm fairly sure I haven't rebooted since the release, but I
was also tracking testing right up to the release so I'm already running
the same kernel etc. that you mentioned.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: tp-link tl-sf1005d version 7.1

[tomas]

On Fri, Jun 16, 2023 at 03:14:02PM +0200, Aleix Piulachs wrote:
> hallo debian gentlemen

If you only talk to gentlemen, you might receive less help :-)

> i can’t connect to the LAN from bullseye with
> tp-link tl-sf1005d version 7.1
> I’ve a hp6830s i386 with bullseye and intel pentium dual cpu t3400
> could you help me with this please?

I think the switch is the least of your problems for now.

Please tell us:

 - what else is connected to that switch
 - if the switch has lights for its Ethernet ports:
   which ones are on
 - what happens if you open a console on your hp6830 and
   enter each of those three commands
   - ip link show
   - ip addr show
   - ip route show
 - what IP addresses have the other machines connected
   to the switch

I think someone (whether gent or not) can take it up from there.

Cheers
-- 
t 


signature.asc
Description: PGP signature

Bluetooth driver error on boot after upgrade to bookworm

[Unni]

Hello,

I am getting Bluetooth firmware error after upgrade. I've tried 
reinstalling firmware-iwlwifi. But no luck. I've added non-free-firmware 
in apt source, so thats not the issue. Help me to fix the error on booth.



~# dmesg | egrep -i 'bluetooth'
[    6.051557] Bluetooth: Core ver 2.22
[    6.051579] NET: Registered PF_BLUETOOTH protocol family
[    6.051580] Bluetooth: HCI device and connection manager initialized
[    6.051587] Bluetooth: HCI socket layer initialized
[    6.051589] Bluetooth: L2CAP socket layer initialized
[    6.051593] Bluetooth: SCO socket layer initialized
[    6.093212] bluetooth hci0: firmware: failed to load 
intel/ibt-20-0-0.sfi (-2)
[    6.093358] bluetooth hci0: firmware: failed to load 
intel/ibt-20-0-0.sfi (-2)

[    7.622442] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.622446] Bluetooth: BNEP filters: protocol multicast
[    7.622450] Bluetooth: BNEP socket layer initialized
[    7.623488] Bluetooth: MGMT ver 1.22
[    9.011767] Bluetooth: RFCOMM TTY layer initialized
[    9.011779] Bluetooth: RFCOMM socket layer initialized
[    9.011784] Bluetooth: RFCOMM ver 1.11
[   32.748460] Bluetooth: hci0: Opcode 0x 401 failed: -16

~# hciconfig -a hci0
hci0:    Type: Primary  Bus: USB
    BD Address: 14:F6:D8:D7:FD:C9  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN
    RX bytes:1324 acl:0 sco:0 events:122 errors:0
    TX bytes:7670 acl:0 sco:0 commands:116 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: PERIPHERAL ACCEPT
    Name: 'unni-debian'
    Class: 0x7c0104
    Service Classes: Rendering, Capturing, Object Transfer, Audio, 
Telephony

    Device Class: Computer, Desktop workstation
    HCI Version: 5.2 (0xb)  Revision: 0x2279
    LMP Version: 5.2 (0xb)  Subversion: 0x2279
    Manufacturer: Intel Corp. (2)

~# lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:    12
Codename:    bookworm

~# cat /etc/apt/sources.list
# See https://wiki.debian.org/SourcesList for more information.
deb http://deb.debian.org/debian bookworm main contrib non-free 
non-free-firmware
deb-src http://deb.debian.org/debian bookworm main contrib non-free 
non-free-firmware


deb http://deb.debian.org/debian bookworm-updates main contrib non-free 
non-free-firmware
deb-src http://deb.debian.org/debian bookworm-updates main contrib 
non-free non-free-firmware


deb http://security.debian.org/debian-security/ bookworm-security main 
contrib non-free non-free-firmware
deb-src http://security.debian.org/debian-security/ bookworm-security 
main contrib non-free non-free-firmware

#Testing repo
# deb http://deb.debian.org/debian testing non-free non-free-firmware 
contrib main


~# dpkg-query -W | grep -E '(linux-image|firmware-iwlwifi)'
firmware-iwlwifi    20230210-5
linux-image-5.10.0-10-amd64    5.10.84-1
linux-image-5.10.0-11-amd64    5.10.92-2
linux-image-5.10.0-13-amd64    5.10.106-1
linux-image-5.10.0-14-amd64    5.10.113-1
linux-image-5.10.0-15-amd64    5.10.120-1
linux-image-5.10.0-16-amd64    5.10.127-2
linux-image-5.10.0-17-amd64    5.10.136-1
linux-image-5.10.0-19-amd64    5.10.149-2
linux-image-5.10.0-20-amd64    5.10.158-2
linux-image-5.10.0-21-amd64    5.10.162-1
linux-image-5.10.0-23-amd64    5.10.179-1
linux-image-5.10.0-9-amd64    5.10.70-1
linux-image-6.1.0-9-amd64    6.1.27-1
linux-image-amd64    6.1.27-1

~# uname -mrs
Linux 6.1.0-9-amd64 x86_64

Re: Is there no other tool but Zim, the graphical text editor based on wiki technologies, in Debian, to create intertwined wiki pages locally?

[Susmita/Rajib]

From: Me 
Date: Thu, 15 Jun 2023 19:23:26 +0200
Message-id: <[] 568e7aa9-e061-194a-13f8-8e2379f69...@nodatagrabbing.com>
In-reply-to: <[]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
References: <[]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>

and

From: l0f...@tuta.io
Date: Thu, 15 Jun 2023 23:28:40 +0200 (CEST)
Message-id: <[] ny-xtlx--...@tuta.io>
In-reply-to: <[] 568e7aa9-e061-194a-13f8-8e2379f69...@nodatagrabbing.com>
References: <[]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
<[] 568e7aa9-e061-194a-13f8-8e2379f69...@nodatagrabbing.com>

Mr. Me has recommended Basket Notes from github and Mr. l0f4r0,
cherrytree, also from github.

The either is available in the Debian Repositories as Basket and cherrytree.

Unfortunately, Basket requires very many KDE packages to be
co-installed, while I still use LXDE.

AT the first glance, Basket perhaps won't serve the purpose.
cherrytree, the hierarchical note-taking application, is installed and
will be checked.

So thank you, Mr. Me and Mr. l0f4r0 for your inputs. Much appreciated.

Best wishes.

RE: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[Frédéric BOITEUX]

Bonjour,

> Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
> user.messages), ça sonne puisque plus rien qui utilise /var ne peut 
> fonctionner !
> Si root supprime les fichiers remplis de la même alerte, /var reste rempli à 
> 100%.

Oui, c’est un classique ! Tant que le [gros] fichier est ouvert par un 
processus, il existe encore et sa place n’est pas libérée. Ici, le truc c’est 
de relancer le service qui écrit dans les logs, probablement rsyslog : le 
processus en cours est terminé, et les fichiers supprimés sont alors réellement 
libérés…

Cdlt,
Fred (pas trop barbu :-)

Re: RAID5 (Mdadm) non fonctionnel sous Debian 11

[NoSpam]

Bonjour. Pour gérer le RAID il faut savoir quel est est le controleur de 
la machine: sudo lpci|grep RAID puis chercher quel est le module chargé 
de sa gestion et le charger.


Le 16/06/2023 à 15:10, Romain P. a écrit :

Bonjour

Je suis passé de Debian 10 à Debian 11 et volume RAID5, géré par la 
carte mère, n'est pas reconnu.


Créé sous Windows 10, il fonctionnait sous Debian 10 juste en 
installant Mdadm.


Sous certaines distributions, Mdadm est inclus et mon RAID5 fonctionne 
sans paramétrage.


J'ai lu plusieurs pages Web à propos de Mdadm, mais il y est indiqué 
des commandes différentes. Je suis perdu.


Comment faire fonctionner mon RAID5 sans risquer de le détruite ?

Merci

Romain

mdadm.txt :
"
Les NOUVEAUX paquets suivants vont être installés :
  mdadm
0 paquets mis à jour, 1 nouvellement installés, 0 à enlever et 0 non 
mis à jour.
Il est nécessaire de télécharger 449 ko d'archives. Après dépaquetage, 
1 240 ko seront utilisés.
Prendre :  1 https://deb.debian.org/debian buster/main amd64 mdadm 
amd64 4.1-1 [449 kB]

 449 ko téléchargés en 0s (1 391 ko/s)
Préconfiguration des paquets...
Sélection du paquet mdadm précédemment désélectionné.
(Lecture de la base de données... 289552 fichiers et répertoires déjà 
installés.)

Préparation du dépaquetage de .../archives/mdadm_4.1-1_amd64.deb ...
Dépaquetage de mdadm (4.1-1) ...
Paramétrage de mdadm (4.1-1) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
Création du fichier de configuration GRUB…
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Image Linux trouvée : /boot/vmlinuz-4.19.0-14-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-14-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-13-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-13-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-12-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-12-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-11-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-11-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-6-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-6-amd64
Windows Boot Manager trouvé sur 
/dev/nvme0n1p3@/efi/Microsoft/Boot/bootmgfw.efi

Adding boot menu entry for EFI firmware configuration
fait
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) ...
Traitement des actions différées (« triggers ») pour systemd 
(241-7~deb10u6) ...
Traitement des actions différées (« triggers ») pour initramfs-tools 
(0.133+deb10u1) ...

update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
"

RAID5 (Mdadm) non fonctionnel sous Debian 11

[Romain P.]

Bonjour

Je suis passé de Debian 10 à Debian 11 et volume RAID5, géré par la 
carte mère, n'est pas reconnu.


Créé sous Windows 10, il fonctionnait sous Debian 10 juste en installant 
Mdadm.


Sous certaines distributions, Mdadm est inclus et mon RAID5 fonctionne 
sans paramétrage.


J'ai lu plusieurs pages Web à propos de Mdadm, mais il y est indiqué des 
commandes différentes. Je suis perdu.


Comment faire fonctionner mon RAID5 sans risquer de le détruite ?

Merci

Romain

mdadm.txt :
"
Les NOUVEAUX paquets suivants vont être installés :
  mdadm
0 paquets mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis 
à jour.
Il est nécessaire de télécharger 449 ko d'archives. Après dépaquetage, 
1 240 ko seront utilisés.
Prendre :  1 https://deb.debian.org/debian buster/main amd64 mdadm amd64 
4.1-1 [449 kB]

 449 ko téléchargés en 0s (1 391 ko/s)
Préconfiguration des paquets...
Sélection du paquet mdadm précédemment désélectionné.
(Lecture de la base de données... 289552 fichiers et répertoires déjà 
installés.)

Préparation du dépaquetage de .../archives/mdadm_4.1-1_amd64.deb ...
Dépaquetage de mdadm (4.1-1) ...
Paramétrage de mdadm (4.1-1) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
Création du fichier de configuration GRUB…
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Image Linux trouvée : /boot/vmlinuz-4.19.0-14-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-14-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-13-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-13-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-12-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-12-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-11-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-11-amd64
Image Linux trouvée : /boot/vmlinuz-4.19.0-6-amd64
Image mémoire initiale trouvée : /boot/initrd.img-4.19.0-6-amd64
Windows Boot Manager trouvé sur 
/dev/nvme0n1p3@/efi/Microsoft/Boot/bootmgfw.efi

Adding boot menu entry for EFI firmware configuration
fait
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) ...
Traitement des actions différées (« triggers ») pour systemd 
(241-7~deb10u6) ...
Traitement des actions différées (« triggers ») pour initramfs-tools 
(0.133+deb10u1) ...

update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
"

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[Thomas Trupel]

Bonjour,

Une piste avec 
https://manpages.debian.org/bookworm/systemd/tmpfiles.d.5.en.html ?

Cordialement,
Thomas

16 juin 2023 11:47:14 roger.tar...@free.fr:

> Bonjour,
> 
> Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
> user.messages), ça sonne puisque plus rien qui utilise /var ne peut 
> fonctionner !
> Si root supprime les fichiers remplis de la même alerte, /var reste rempli à 
> 100%.
> Il y aurait bien un lsof puis un kill de tout ce qui est "deleted".
> 
> Comment faire pour libérer l'espace sans devoir redémarrer la machine ?
> Fiablement, sans effet boomerang.
> 
> Egalement, comment éviter que /var ( partition dédiée) bloque la machine 
> quand il est plein ?
> 
> Je pensais à un script qui surveille les logs et tronçonne les messages 
> répétés pour maintenir.
> Un service du système ou un paquet gère-t-il ça ?
> ça doit arriver tellement souvent...
> 
> Merci.

Re: Unexpected change in behavior for adduser

[David Wright]

On Fri 16 Jun 2023 at 14:19:52 (+0200), Diego Fioravanti wrote:

> I am not sure if this is a bug in Debian, expected behaviour or something
> else, so I decided to write here before opening a bug. Maybe someone can
> help me out and tell me if it is something I should report.
> 
> I am using the official python docker image which builds out of Bullseye
> (btw, this happens in bookworm too). Until yesterday when I ran `adduser
> --system nonroot` it would populate `$HOME` with `/home/notroot/`. Today I
> rebuilt the image and it is set to `/nonexistent`. Was this intentional or
> is it a bug? I cannot find any reference to this change anywhere but maybe
> I have missed something. If it was intentional I have to say that it
> absolutely breaks python's ability to find the root for the current user.
> In case it helps someone else, I switched to useradd -m and that fixed it.

Everything is laid out in /usr/share/doc/adduser/NEWS.Debian.gz
and you were advised to read that in §5.2.7 of the Release Notes.

Cheers,
David.

tp-link tl-sf1005d version 7.1

[Aleix Piulachs]

hallo debian gentlemen
i can’t connect to the LAN from bullseye with
tp-link tl-sf1005d version 7.1
I’ve a hp6830s i386 with bullseye and intel pentium dual cpu t3400
could you help me with this please?

Re: Unexpected change in behavior for adduser

[tomas]

On Fri, Jun 16, 2023 at 02:19:52PM +0200, Diego Fioravanti wrote:
> Hi everyone,
> 
> I am not sure if this is a bug in Debian, expected behaviour or something
> else, so I decided to write here before opening a bug. Maybe someone can
> help me out and tell me if it is something I should report.
> 
> I am using the official python docker image which builds out of Bullseye
> (btw, this happens in bookworm too). Until yesterday when I ran `adduser
> --system nonroot` it would populate `$HOME` with `/home/notroot/`. Today I
> rebuilt the image and it is set to `/nonexistent`. Was this intentional or
> is it a bug? I cannot find any reference to this change anywhere but maybe
> I have missed something. If it was intentional I have to say that it
> absolutely breaks python's ability to find the root for the current user.
> In case it helps someone else, I switched to useradd -m and that fixed it.

I'd first check /etc/adduser.conf and possibly /usr/local/sbin/adduser.local
(both mentioned in the man page). It might be some configuration specific
to that docker image.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: 60-serial.rules, broken

[gene heskett]

On 6/14/23 12:01, Sascha Silbe wrote:

Hello,

gene heskett  writes:


That's Debian#1035094 [1]. A fix was uploaded three weeks ago and is
available in bullseye-proposed-updates [2] but not the regular Bullseye
repository. If I understand the status page [3] correctly it's only
scheduled for the next point release. Given that there already was a
point release recently (11.7 on 2023-05-01) it will probably another
couple of months until this bug gets fixed in bullseye. :-/

[...]

That is most unfortunate for 3d printer users, our support group on
discord is blowing up with the problems this is cause for klipper users,
can its priority be raised?  We use it because that gives us a
bulletproof method using the devices ChipID, which is totally unique,
like MAC addresses.


Tell me about it. As an embedded developer this bug is a huge PITA. I'm
surprised the fix for this regression hasn't already landed in
stable. But then I don't know what else changed and what the risks are
for other bugs to show up and potentially affect even more users. After
all systemd is a rather central component of most Debian systems.

You may want to try asking on the bug report (#1035094 [1]) about
it. I'm not a Debian Developer myself and don't have much experience
trying to get a fix landed in stable but I expect there is a way for the
maintainers of the package to request an exception and get the fix in
the repository before the next point release.

As a first step however we should try out the version from
bullseye-proposed-updates to make sure it's safe to use. I've already
installed it on one of my hosts (where it fixed the bug) and will
monitor it for regressions; would be great if others did the same.

Sascha

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035094


A fixit script was posted on discord/linux/klipper/configuration, and 
pinned. It worked ok on several of my bananapi-m5's and my i5 version of 
bullseye had a /dev/serial/by-path, but no by-id, so I ran that same 
script here, but it pulled in 39 other updates at the same time and blew 
away my passwd. no root pw had ever been set as I use sudo for that, so 
I was locked out. 5 installs later I'm finally back in business. But my 
setup is a bit unusual, /home is a raid10 of 1.7 TB on 4 1Tb samsung 
ssd's, with 60Gb of swap on the rest of that raid10. And I still haven't 
recreated my local /sshnet network of all my cnc'd machines and 3d 
printers but that's just details I haven't addressed yet.


That script does an apt update && apt upgrade -y before it pulls in this 
new 60-persistent-serial into /etc/udev/rules.d. Then recommended 
strongly that I reboot.


It has not actually bothered this machine. so given the nearly 3 days of 
hell it gave me to recover from it, I'll wait for it to make  64 bit 
intel bullseye.


As for the networking, I've found sshfs to be many times more dependable 
than nfs any version, it Just Works. That forces me to go to that 
machines keyboard for root stuffs, its only disadvantage. But I'll go 
check that bug since to see if its the same fix.


Take care & stay well.

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 

Unexpected change in behavior for adduser

[Diego Fioravanti]

Hi everyone,

I am not sure if this is a bug in Debian, expected behaviour or something
else, so I decided to write here before opening a bug. Maybe someone can
help me out and tell me if it is something I should report.

I am using the official python docker image which builds out of Bullseye
(btw, this happens in bookworm too). Until yesterday when I ran `adduser
--system nonroot` it would populate `$HOME` with `/home/notroot/`. Today I
rebuilt the image and it is set to `/nonexistent`. Was this intentional or
is it a bug? I cannot find any reference to this change anywhere but maybe
I have missed something. If it was intentional I have to say that it
absolutely breaks python's ability to find the root for the current user.
In case it helps someone else, I switched to useradd -m and that fixed it.

Best,
Diego

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[Alain Vaugham]

Le Fri, 16 Jun 2023 11:46:49 +0200 (CEST),
roger.tar...@free.fr a écrit :

> Egalement, comment éviter que /var ( partition dédiée ) bloque la
> machine quand il est plein ? 

Pour éviter de remplir /var à cause de la pollution des logs, je créé
une partition dédiée /var/log.


-- 
Alain Vaugham
Clef GPG : 0xDB77E054673ECFD2

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[plapla]

Le 16/06/2023 à 11:46, roger.tar...@free.fr a écrit :

Bonjour,

Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
user.messages), ça sonne puisque plus rien qui utilise /var ne peut 
fonctionner !
Si root supprime les fichiers remplis de la même alerte, /var reste 
rempli à 100%.

Il y aurait bien un lsof puis un kill de tout ce qui est "deleted".

Comment faire pour libérer l'espace sans devoir redémarrer la machine ?
Fiablement, sans effet boomerang.



Salut,

j'ai eu ce problème une fois, et un barbu m'a filé ce truc. En fait tant 
que le fichier est en écriture par le système, il ne s'efface pas 
vraiment. Il faut l'effacer sur place avec un :


echo 0>/var/log/le_log.log

Ça efface tout le texte, qu'on perd donc ! Il faut être sûr qu'on ne 
veut pas étudier le fichier ensuite.


mes 0.02 c.

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[elguero eric]

il faut aussi surveiller /var/tmp

j'y ai trouvé un jour des fichiers de plusieurs gigas.

e.e.







Le vendredi 16 juin 2023 à 11:47:12 UTC+2, roger.tar...@free.fr 
 a écrit : 





Bonjour,

Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
user.messages), ça sonne puisque plus rien qui utilise /var ne peut fonctionner 
!
Si root supprime les fichiers remplis de la même alerte, /var reste rempli à 
100%.
Il y aurait bien un lsof puis un kill de tout ce qui est "deleted".

Comment faire pour libérer l'espace sans devoir redémarrer la machine ?
Fiablement, sans effet boomerang.

Egalement, comment éviter que /var ( partition dédiée) bloque la machine quand 
il est plein ?

Je pensais à un script qui surveille les logs et tronçonne les messages répétés 
pour maintenir.
Un service du système ou un paquet gère-t-il ça ?
ça doit arriver tellement souvent...

Merci.

Re: Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[NoSpam]

Bonjour

Le 16/06/2023 à 11:46, roger.tar...@free.fr a écrit :

Bonjour,

Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
user.messages), ça sonne puisque plus rien qui utilise /var ne peut 
fonctionner !
Si root supprime les fichiers remplis de la même alerte, /var reste 
rempli à 100%.

??? Jamais vu cela en ext2/3/4 ou xfs  Quel fs ?

Il y aurait bien un lsof puis un kill de tout ce qui est "deleted".

Comment faire pour libérer l'espace sans devoir redémarrer la machine ?
Fiablement, sans effet boomerang.

Egalement, comment éviter que /var ( partition dédiée) bloque la 
machine quand il est plein ?
var est nécessaire. Il existe des outils comme 
librenms/munin/cacti/zabbix/... qui alertent


Je pensais à un script qui surveille les logs et tronçonne les 
messages répétés pour maintenir.

Un service du système ou un paquet gère-t-il ça ?
ça doit arriver tellement souvent...
Cela a du m'arriver à mes débuts avec Linux. Depuis, je surveille les 
serveurs comme le lait sur le feu ...

[...]

Libérer l'espace après suppression de fichiers de log énormes dans /var + éviter d'atteindre le blocage

[roger . tarani]

Bonjour, 

Quand /var/log/ se remplit de messages d'erreur (messages syslog et 
user.messages), ça sonne puisque plus rien qui utilise /var ne peut fonctionner 
! 
Si root supprime les fichiers remplis de la même alerte, /var reste rempli à 
100%. 
Il y aurait bien un lsof puis un kill de tout ce qui est "deleted". 

Comment faire pour libérer l'espace sans devoir redémarrer la machine ? 
Fiablement, sans effet boomerang. 

Egalement, comment éviter que /var ( partition dédiée ) bloque la machine quand 
il est plein ? 

Je pensais à un script qui surveille les logs et tronçonne les messages répétés 
pour maintenir. 
Un service du système ou un paquet gère-t-il ça ? 
ça doit arriver tellement souvent... 

Merci. 

Re: puis-je faire confiance a ce disque ?

[BERTRAND Joël]

hamster a écrit :
> Le 16/06/2023 à 11:21, BERTRAND Joël a écrit :
>> hamster a écrit :
>>> Le 16/06/2023 à 08:34, BERTRAND Joël a écrit :
  Bonjour,

  J'en pense que c'est un Seagate. J'ai eu des tas de disques
 comme ça
 qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
 problème est un firmware buggué et que Seagate n'en a rien à faire.
 Tant
 que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
 je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.
>>>
>>> Voila une inoformation interessante. Comment tu fais pour savoir si le
>>> noyau rale ?
>> 
>> Regarder par exemple ce qu'il dit dans /var/log/syslog ou dans dmesg.
>> Normalement, ces erreurs sont aussi logguées dans le disque dur (mais là
>> encore, attention aux firmwares buggués de Seagate).
> 
> Heu… Ca je m'en etais douté. Mais il y a beaucoup de choses dans syslog
> et dmesg, pour trouver l'aiguille dans la botte de foin, il faut un
> minimum avoir idée d'a quoi ressemble l'aiguille.
> 
> Quels sont les indices que tu cherche dans syslog et dmesg ?

Des erreurs de type ataXXX. Désolé, je n'ai pas la syntaxe en tête.
Vous ne pouvez pas les rater, ça fait des gros pâtés.

Re: puis-je faire confiance a ce disque ?

[hamster]

Le 16/06/2023 à 11:21, BERTRAND Joël a écrit :

hamster a écrit :

Le 16/06/2023 à 08:34, BERTRAND Joël a écrit :

 Bonjour,

 J'en pense que c'est un Seagate. J'ai eu des tas de disques comme ça
qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
problème est un firmware buggué et que Seagate n'en a rien à faire. Tant
que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.


Voila une inoformation interessante. Comment tu fais pour savoir si le
noyau rale ?


Regarder par exemple ce qu'il dit dans /var/log/syslog ou dans dmesg.
Normalement, ces erreurs sont aussi logguées dans le disque dur (mais là
encore, attention aux firmwares buggués de Seagate).


Heu… Ca je m'en etais douté. Mais il y a beaucoup de choses dans syslog 
et dmesg, pour trouver l'aiguille dans la botte de foin, il faut un 
minimum avoir idée d'a quoi ressemble l'aiguille.


Quels sont les indices que tu cherche dans syslog et dmesg ?

Re: puis-je faire confiance a ce disque ?

[BERTRAND Joël]

hamster a écrit :
> Le 16/06/2023 à 08:34, BERTRAND Joël a écrit :
>> Bonjour,
>>
>> J'en pense que c'est un Seagate. J'ai eu des tas de disques comme ça
>> qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
>> problème est un firmware buggué et que Seagate n'en a rien à faire. Tant
>> que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
>> je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.
> 
> Voila une inoformation interessante. Comment tu fais pour savoir si le
> noyau rale ?

Regarder par exemple ce qu'il dit dans /var/log/syslog ou dans dmesg.
Normalement, ces erreurs sont aussi logguées dans le disque dur (mais là
encore, attention aux firmwares buggués de Seagate).

Attention toutefois, il y a eu un noyau Linux buggué jusqu'à la moelle
qui provoquait des erreurs disques dans certaines configurations (raid
logiciel). Je ne me souviens plus de sa version, j'ai eu ça sur un
serveur de test.

Re: puis-je faire confiance a ce disque ?

[hamster]

Le 16/06/2023 à 06:05, Virgile Jarrige a écrit :

Bonjour,

 >qu'en pensez-vous ? est-ce que je peux continuer a faire confiance a ce
 >disque ou bien est-ce que je prévois d'avoir a le changer bientot ?
N'étant pas un expert, pour savoir quel message d'un rapport smart est 
critique je me réfère à : 
https://fr.m.wikipedia.org/wiki/Self-Monitoring,_Analysis_and_Reporting_Technology  dans la section "attributs".
Si la valeur d'un attribut sur fond orange est mauvaise, alors il ne 
faut plus faire confiance au disque dur. À noter que sur la page 
anglaise ce ne sont pas tout à fait les mêmes qui sont en orange, donc 
je consulte systématiquement les deux.


Merci beaucoup pour cette astuce, elle va m'etre fort utile.

Re: puis-je faire confiance a ce disque ?

[hamster]

Le 16/06/2023 à 08:34, BERTRAND Joël a écrit :

hamster a écrit :

j'ai un disque dur pour lequel badblocks s'est terminé sans erreurs,
l'auto-test de smart s'est aussi terminé sans erreurs, pourtant dans le
rapport de smart je vois 3 chiffres qui m'inquietent :
Raw_Read_Error_Rate 70428466
Seek_Error_Rate 371778543
149  ---  Number of Reported Uncorrectable Errors
mais j'ai un peu de mal a bien causer le jargon smart

rapport smart complet ici :
https://suna.fdn.fr/liens/rapport-smart.txt

qu'en pensez-vous ? est-ce que je peux continuer a faire confiance a ce
disque ou bien est-ce que je prévois d'avoir a le changer bientot ?


Bonjour,

J'en pense que c'est un Seagate. J'ai eu des tas de disques comme ça
qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
problème est un firmware buggué et que Seagate n'en a rien à faire. Tant
que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.


Voila une inoformation interessante. Comment tu fais pour savoir si le 
noyau rale ?

Re: apt-cdrom: How do I use the flash drive as a CD-ROM to install software in Debian 12?

[David Wright]

On Thu 15 Jun 2023 at 21:32:41 (+), Totoro wrote:

> After entering
> 
> sudo apt update
> 
> The following messages appeared on the console:
> 
> Ign:1 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD 
> Binary-1 with firmware 20230610-10:23"] bookworm InRelease
> Err:2 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD 
> Binary-1 with firmware 20230610-10:23"] bookworm Release
> Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update 
> cannot be used to add new CD-ROMs.
> Reading package lists.Done
> 
> E: The repository 'cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official 
> amd64 DVD Binary-1 with firmware 20230610-10:23"] bookworm Release' does not 
> have 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.
> 
> I have read the manpages of both 'apt-cdrom' and 'apt-secure' and they only 
> contain lists and descriptions of options and parameters. They do not contain 
> examples on how to use the options.
> 
> My objective is to mount the flash drive as a CD-ROM and use it to install 
> additional software. 

It looks as though you haven't added an entry in /etc/apt/sources.list
(or a file in its directory) for reading from the mounted stick.
Something like:

  deb file:/mnt/mount-iso bookworm main non-free contrib non-free-firmware

See   man sources.list

Cheers,
David.

Re: puis-je faire confiance a ce disque ?

[BERTRAND Joël]

hamster a écrit :
> j'ai un disque dur pour lequel badblocks s'est terminé sans erreurs,
> l'auto-test de smart s'est aussi terminé sans erreurs, pourtant dans le
> rapport de smart je vois 3 chiffres qui m'inquietent :
> Raw_Read_Error_Rate 70428466
> Seek_Error_Rate 371778543
> 149  ---  Number of Reported Uncorrectable Errors
> mais j'ai un peu de mal a bien causer le jargon smart
> 
> rapport smart complet ici :
> https://suna.fdn.fr/liens/rapport-smart.txt
> 
> qu'en pensez-vous ? est-ce que je peux continuer a faire confiance a ce
> disque ou bien est-ce que je prévois d'avoir a le changer bientot ?

Bonjour,

J'en pense que c'est un Seagate. J'ai eu des tas de disques comme ça
qui montraient des valeurs aberrantes et j'ai creusé. Il s'avère que le
problème est un firmware buggué et que Seagate n'en a rien à faire. Tant
que Current_Pending_Sector reste à 0 de même que Reallocated_Sector_Ct,
je ne m'affolerais pas. Sauf si, naturellement, le noyau râle.

Bien cordialement,

JKB

PS: je n'utilise plus de Seagate que contraint et forcé. Trop de
dysfonctionnements même dans les gammes SAS/SCA/SCSI.