Pastebins [was Re: SSD Optimization - Crucial CT1000MX500SSD1]

2022-10-01 Thread David
On Sun, 2 Oct 2022 at 06:55, David Christensen
 wrote:

> Please run the following command and post the complete console session
> -- prompt, command entered, output displayed -- on a web site
> (pastebin.com, etc.):

Or paste.debian.net [1][2], which is a better match with the
philosophy [3] of the Debian project.

Maybe this is worth a mention in the mailing list Monthly FAQ?

[1] http://paste.debian.net
[2] http://paste.debian.net/paste.pl?show_template=about
[3] https://www.debian.org/intro/philosophy



Re: SSD Optimization - Crucial CT1000MX500SSD1

2022-10-01 Thread David Christensen

On 10/1/22 17:40, Marcelo Laia wrote:
Please run the following command and post the complete console session 
-- prompt, command entered, output displayed -- on a web site 
(pastebin.com, etc.):



# smartctl -x /dev/sda


Here is:

https://pastebin.com/znfuz82t

Thank you so much!



These attributes all indicate that the internal functions of the drive 
are correct:


  1 Raw_Read_Error_Rate POSR-K   100   100   000-0
  5 Reallocate_NAND_Blk_Cnt -O--CK   100   100   010-0

171 Program_Fail_Count  -O--CK   100   100   000-0
172 Erase_Fail_Count-O--CK   100   100   000-0

180 Unused_Reserve_NAND_Blk PO--CK   000   000   000-64

184 Error_Correction_Count  -O--CK   100   100   000-0
187 Reported_Uncorrect  -O--CK   100   100   000-0

196 Reallocated_Event_Count -O--CK   100   100   000-0
197 Current_Pending_ECC_Cnt -O--CK   100   100   000-0
198 Offline_Uncorrectable   CK   100   100   000-0

202 Percent_Lifetime_Remain CK   099   099   001-1

206 Write_Error_Rate-OSR--   100   100   000-0


This attribute indicates that the drive is having a problems when 
communicating with the motherboard:


199 UDMA_CRC_Error_Count-O--CK   100   100   000-38


So, I would still do the steps I suggested earlier:

https://lists.debian.org/debian-user/2022/09/msg00772.html


David



Re: Re: SSD Optimization - Crucial CT1000MX500SSD1

2022-10-01 Thread Marcelo Laia
Please run the following command and post the complete console session 
-- prompt, command entered, output displayed -- on a web site 
(pastebin.com, etc.):



# smartctl -x /dev/sda


Here is:

https://pastebin.com/znfuz82t

Thank you so much!

--
Marcelo



Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread The Wanderer
On 2022-10-01 at 18:25, Stefan Monnier wrote:

>> For example: as soon as you've had more than one change in the
>> entire history of the document, you need to start considering what
>> the previous version against which you're showing differences is.
>> If you try to do it against all of them, it very quickly becomes
>> unwieldy; if you try to do
> 
> For me the better option is to point to a version of the file with
> all its VCS history so people can see what's been changed when.

Yes, but for a tiny and rarely-updated document like this that's even
*more* clearly overkill.

-- 
   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: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread Stefan Monnier
> For example: as soon as you've had more than one change in the entire
> history of the document, you need to start considering what the previous
> version against which you're showing differences is. If you try to do it
> against all of them, it very quickly becomes unwieldy; if you try to do

For me the better option is to point to a version of the file with all
its VCS history so people can see what's been changed when.


Stefan



Re: 10/Buster --> 11/Bulleye

2022-10-01 Thread hamster

Le 01/10/2022 à 23:34, Alain Vaugham a écrit :

Il y a eu un démontage qui n'a pas pu se faire:
umount /mnt/racine/sys : Target is busy.
En regardant j'ai vu que la cible c'était sur la clef USB du System
Rescue.


Heu, c'est curieux.

Personnellement j'utilise l'option "docache" de systemrescue, comme ca 
il commence par copier le système dans la RAM, puis il boote sur l'image 
qui est dans la RAM. Comme ca la clef n'est plus utilisée et tu peux la 
débrancher. Les performances sont bien meilleures et en plus, c'est 
parfois pratique de liberer une prise USB.



Est-ce qu'il y a d'autres subtilités de ton install que tu nous a pas
encore dites ?


Non, je ne pense pas que ce soit des subtilités. J'aime bien avoir


Ah, désolé de mon vocabulaire. Je n'ai pas pensé a quoi que ce soit de 
dévalorisant en utilisant ce mot. Alors je reformule : est-ce qu'il y a 
d'autres trucs que tu nous a pas encore dits ?



- une partition que pour les logs,
- une pour un user (moi)
- une tmp en RAM
J'aime bien aussi avoir de la place disponible sur le disque au cas où
j'aurai besoin d'ajouter brutalement une partition.

Est-ce que les deux montages ci-dessous seraient des subtilités?
tmpfs /tmp tmpfs defaults,size=1g 0 0
192.168.33.128:/mnt/nfs_labas /mnt/nfs_ici nfs defaults 0 2


Pour que le chroot fonctionne, il faut que le système ait tout ses 
morceaux. Tu peux comparer ca a un organisme : pour qu'il soit vivant il 
faut qu'il ait tous ses organes.


Quand tu fais un chroot, c'est le noyau de systemrescue qui fonctionne, 
donc le noyau du système sur lequel tu chroote n'est pas utilisé. Par 
contre il faut que le système ait accès a tous ses dossiers et fichiers 
système.


Il n'y a pas besoin de /home pour reinstaller grub parce que c'est une 
commande qui ne manipule rien dans ce dossier, mais pour d'autres 
commandes ca pourrait etre necessaire.


Il y a besoin de tous les autres dossiers système, y compris la partoche 
dédiée aux logs et /tmp. Mais /tmp est juste un espace dans lequel des 
fichiers temporaires pourront etres écrits et il peut tout a fait etre 
vide au démarrage. Donc tu peux très bien ne rien monter sur le dossier 
/tmp : ainsi les éventuels fichiers temporaires générées par les 
commandes que tu exécute seront écrits directement dans le dossier /tmp, 
c'est a dire dans la partition racine. Dans ce cas je te conseille 
d'aller supprimer tout le contenu de /mnt/racine/tmp après etre sorti du 
chroot, pour éviter d'avoir des fichiers temporaires obsolètes qui 
trainent pour rien dans ce dossier.


Par contre un dossier distant NFS n'est pas un dossier du système, donc 
y'a pas besoin de le monter pour que le système fonctionne. De facon 
générale tout ce qui est monté dans /mnt et dans /média ne fait pas 
partie du système, vu que c'est précisément des dossiers dédiés au 
montage de trucs exterieurs au système.




Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread The Wanderer
On 2022-10-01 at 09:44, rhkra...@gmail.com wrote:

> On Saturday, October 01, 2022 06:10:48 AM The Wanderer wrote:
> 
>> On 2022-10-01 at 05:46, Andrew M.A. Cater wrote:
>> 
>>> Debian-user is a mailing list provided for support for Debian
>>> users, and to facilitate discussion on relevant topics.
> 
>> I therefore reiterate my suggestion, from what I think was one of
>> the first times (a previous version of?) this FAQ was (re)posted,
>> that some versioning information be attached to - and posted along
>> with each copy of - this FAQ.
> 
> +1
> 
> And I would expand the suggestion to add "revision marks" (ideally in
> the left margin) of the changed sections.
> 
> After all, many of us are used to using (word)diff or similar.

That's about showing what the changes are (when there are any), which is
an entirely separate and much larger / more-complicated matter.

For example: as soon as you've had more than one change in the entire
history of the document, you need to start considering what the previous
version against which you're showing differences is. If you try to do it
against all of them, it very quickly becomes unwieldy; if you try to do
it against just the previous most recent update, then people have to
track that down to understand what the context of the changes was, and
still need to read the updated document to understand those changes in
full context.

It can still be worth doing - typically against the last formally
published version, preferably with a "commit message" type of notice
along with each such version - for larger documents, EULAs and TOS
notices and privacy policies the like.

But for something like this FAQ, the document is small enough that I
don't mind reading it again when there have been changes, as long as I
don't need to reread it *every time* just *in case there have been
changes*, without any good way to tell whether or not there have (aside
from tracking down the previous posting and comparing for myself).

As such, this request is limited to the specific point of having some
type of versioning attached to the FAQ document. Having a list of "what
changed since the previous version" available somewhere (e.g. in the
header section of the document) might be a nice benefit, but for a
document this short I think it'd probably be overkill.

-- 
   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: 10/Buster --> 11/Bulleye

2022-10-01 Thread Alain Vaugham
Le Fri, 30 Sep 2022 11:48:42 +0200,
Alain Vaugham  a écrit :

> Bonjour,
> 
> Le Wed, 28 Sep 2022 15:11:24 +0200,
> hamster  a écrit :
> 
> > Non, tu y est presque. Je t'incite a perseverer, meme si c'est pas
> > sur cette machine, parce que c'est très pratique et efficace pour
> > réparer grub.  
> 
> J'ai installé Bulleye sur un autre disque. Cela m'a permis de
> préserver le disque de 4T sur lequel je vais pouvoir, grâce aux
> conseils que je trouve ici, continuer mon expérience de chroot.
> Je m'y remet ce soir.
> 

Bonjour,

Cette fois-ci, grâce à tes conseils, la mise à jour de grub a réussi.
Depuis ce matin j'ai un disque qui semble être constamment accepté par
le BIOS/UEFI.

Au préalable, cela a été laborieux. J'ai réinstallé deux fois.
Même le disque pour lequel j'avais vérifié la solidité de ses
redémarrages a fini par être refusé par ce BIOS/UEFI. Je suis incapable
de recréer le défaut.
Je n'ai donc eu d'autre choix que de réussir à mettre à jour le grub,
donc d'utiliser chroot.

Par précaution j'ai fait une installation "tout dans une seule
partition".
sda1EFI
sda2/
sda3swap
Les montages, le chroot et la mise à jour de grub n'ont pas généré
d'erreur.
Il y a eu un démontage qui n'a pas pu se faire:
umount /mnt/racine/sys : Target is busy.
En regardant j'ai vu que la cible c'était sur la clef USB du System
Rescue. Je n'ai pas cherché à comprendre, comme ce n'était que du
démontage avant un reboot, j'ai rebooté.

Je croise les doigts maintenant pour que cette config tienne. Je laisse
quelques jours avant de refaire une install cette fois-ci avec une /var
séparée. Pour ça, j'ai gardé tes conseils ainsi que ceux de Sébastien.



>Est-ce qu'il y a d'autres subtilités de ton install que tu nous a pas 
>encore dites ?

Non, je ne pense pas que ce soit des subtilités. J'aime bien avoir 
- une partition que pour les logs,
- une pour un user (moi)
- une tmp en RAM
J'aime bien aussi avoir de la place disponible sur le disque au cas où
j'aurai besoin d'ajouter brutalement une partition.

Est-ce que les deux montages ci-dessous seraient des subtilités?
tmpfs /tmp tmpfs defaults,size=1g 0 0
192.168.33.128:/mnt/nfs_labas /mnt/nfs_ici nfs defaults 0 2


Merci beaucoup encore pour le coup de pouce.

-- 
Alain Vaugham
Clef GPG : 0xDB77E054673ECFD2



Re: SSD Optimization - Crucial CT1000MX500SSD1

2022-10-01 Thread David Christensen

On 10/1/22 04:09, Marcelo Laia wrote:

Hi Andy, so sorry for that. Here is the long one.

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.0-2-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status  Remaining  
LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error   00%   
544 -
# 2  Short offline   Completed without error   00%   
507 -



Please run the following command and post the complete console session 
-- prompt, command entered, output displayed -- on a web site 
(pastebin.com, etc.):


# smartctl -x /dev/sda


David



Re: update-initramfs outside of /boot

2022-10-01 Thread Brian
On Sat 01 Oct 2022 at 20:07:13 +0200, Erwan David wrote:

> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> > 
> > > My /boot is 235 MB (from deb 10 installer), however in testing I now
> > > have 56MB initramfs files and update-initramfs cannot work for the 3rd
> > > kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade
> > > there are temporarily 3 kernels).
> > > I see that all the files of the initramfs are put in /boot before
> > > creating the compressed image, thus the need for place. Is there a way
> > > to cofigure update-initrams so that the creation of the im age is done
> > > in another filesystem before instalation in /boot ?
> > Alternative options:
> > 
> > 1-Move the oldest kernel files to another filesystem, or everything, from 
> > /boot.
> > You don't need them there until time to reboot.
> > 
> > 2-You're not forced to keep two kernels. Remove the non-running one 
> > manually.
> > 
> > 3-As Stefan already suggested, MODULES=dep. It's routine here. Big initrds 
> > take
> > more time to load, which can be quite noticeable on old hardware.
> > 
> > 4-Is your /boot adjacent to your swap? If yes, easily recreate both, with 
> > smaller
> > swap, larger /boot. Don't forget to adjust fstab for UUID change of swap, 
> > or apply
> > the one from fstab on the new.
> 
> 
> My /boot is next to an encrypted lvm containing te rest of the disk. I fear
> resizing /boot would require a reinstall, I'll set modules=dep

It seems that a larger /boot is not an option for you.
I also suspect modules=dep may not give you sufficient
extra space, but it is worth a try.

A lack of success with modules=dep just might propel you
towards purging one or more of the installed kernels
to improve the situation.

-- 
Brian.



Re: update-initramfs outside of /boot

2022-10-01 Thread debian-user
> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> >  
> >> My /boot is 235 MB (from deb 10 installer), however in testing I
> >> now have 56MB initramfs files and update-initramfs cannot work for
> >> the 3rd kernel to install (and apt autoremove keeps 2 kernels,
> >> thus at upgrade there are temporarily 3 kernels).
> >> I see that all the files of the initramfs are put in /boot before
> >> creating the compressed image, thus the need for place. Is there a
> >> way to cofigure update-initrams so that the creation of the im age
> >> is done in another filesystem before instalation in /boot ?  
> > Alternative options:
> >
> > 1-Move the oldest kernel files to another filesystem, or
> > everything, from /boot. You don't need them there until time to
> > reboot.
> >
> > 2-You're not forced to keep two kernels. Remove the non-running one
> > manually.
> >
> > 3-As Stefan already suggested, MODULES=dep. It's routine here. Big
> > initrds take more time to load, which can be quite noticeable on
> > old hardware.
> >
> > 4-Is your /boot adjacent to your swap? If yes, easily recreate
> > both, with smaller swap, larger /boot. Don't forget to adjust fstab
> > for UUID change of swap, or apply the one from fstab on the new.  
> 
> 
> My /boot is next to an encrypted lvm containing te rest of the disk.
> I fear resizing /boot would require a reinstall, I'll set modules=dep

If you happen to have extra disk space somewhere else, you could
migrate your LVM to the spare disk, then shrink the 'real' LVM and move
it to leave space adjacent to /boot, which you could then extend.
Finally, migrate the LVM contents back (or copy them piecemeal, I don't
know exactly what is possible). Whether that is simpler than a
reinstallation will depend on your circumstances.



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Alfonso García Rodríguez
> Pues... a ver, que yo hice un montón de cambios porque odio las 
> animaciones esas de la wonderbar que te ampliaban la barra de 
> direcciones, los iconos que saltan y los efectos de degradados y 
> demás... he tuneado tanto a Firefox que ya ni lo reconozco :-)
> 
> about:config → ui.prefersReducedMotion → true
> 
> También tengo habilitado en Privacidad el modo Estricto y siempre qe 
> cierro el navegador elimino las cookies y los datos y el historial de 
> navegación (vamos, que mi Firefox es anmésico).
> 
> Pero lo de la aceleración por hardware sí es sencillo, desde los 
> Ajustes, opción de Renidmiento, ahí tengo desactivadas las dos:
> 
> Rendimiento
> 
> [ ] Usar configuración de rendimiento recomendada
>   [ ] Usar aceleración de hardware cuando esté disponible
> 
> Si las habilito, Firefox se vuelve lentorro del copón y casca cada dos 
> por tres. Un horror.
> 
> También puedes probar desactivando WebGL (about:config → webgl.disabled → 
> true), eso sí, algunas páginas que usen esta tecnología dejarán de 
> funcionar, claro está.

Tomo nota. Gracias por la explicación.

> Manda la salida de «grep -i flags /proc/cpuinfo».
>  

Ahí va:

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts xtopology nonstop_tsc cpuid aperfmperf 
pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr 
pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb pti ibrs ibpb stibp tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 
erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple 
shadow_vmcs pml
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts xtopology nonstop_tsc cpuid aperfmperf 
pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr 
pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb pti ibrs ibpb stibp tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 
erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple 
shadow_vmcs pml
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts xtopology nonstop_tsc cpuid aperfmperf 
pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr 
pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb pti ibrs ibpb stibp tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 
erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple 
shadow_vmcs pml
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts xtopology nonstop_tsc cpuid aperfmperf 
pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr 
pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb pti ibrs ibpb stibp tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 
erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple 
shadow_vmcs pml

> Ninguno, tendrías que volver a instalar todo el sistema desde cero :-(, 
> por eso te digo, que si tienes que volver a instalar, y tu sistema lo 
> admite, mejor instala un kernel de 64 bits.
>

¡Qué pereza...!



Re: update-initramfs outside of /boot

2022-10-01 Thread Stefan Monnier
> I alreaady have compres=zstd (should be better than lzma).

I'd be surprised if `zstd` compresses better than `lzma` (which itself
should compress about the same as `xz`).  I just tested here and I get

zstd => 11049378
xz   =>  9989884
lzma =>  9965122

Maybe with more control over the compression parameters `zstd` can be
more competitive, I don't know.

In any case, my quick tests do suggest that indeed changing to `lzma`
probably won't help you very much (not nearly as much as changing to
MODULES=dep).


Stefan



Re: Thunderbird 102 & {Cal,Card}DAV

2022-10-01 Thread Paul van der Vlis

Op 01-10-2022 om 18:44 schreef Paul van der Vlis:

Hoi Geert en anderen,

Op 30-09-2022 om 12:57 schreef Geert Stappers:



Zou ik dat moeten lezen als:
   Zorg dat er discovery service is die vertelt waar de Ca{l,rd}DAV
   server staat en dan hoef je die in TB niet meer te configuren.
??


Nee. Je setup wordt er wat gemakkelijker van.


Eigenlijk bedoel ik dus "ja". Maar het gaat ook prima met de hand.

Tot de vorige versie werkte autoconfiguratie nog niet bij carddav en 
caldav. Misschien nu wel.


Ik heb wel scripts die werken met IMAP, POP, SMTP etc. voor Mozilla.

Er zijn 3 van dit soort autoconfiguratie dingen die van belang zijn, 
namelijk die van Mozilla, die van Apple, en die van Microsoft. Onderling 
niet compatibel. Ik kwam laatst iets tegen wat alle drie ondersteunde.


Groet,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/



Re: update-initramfs outside of /boot

2022-10-01 Thread Erwan David

Le 01/10/2022 à 18:25, Felix Miata a écrit :

Erwan David composed on 2022-10-01 16:21 (UTC+0200):


My /boot is 235 MB (from deb 10 installer), however in testing I now
have 56MB initramfs files and update-initramfs cannot work for the 3rd
kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade
there are temporarily 3 kernels).
I see that all the files of the initramfs are put in /boot before
creating the compressed image, thus the need for place. Is there a way
to cofigure update-initrams so that the creation of the im age is done
in another filesystem before instalation in /boot ?

Alternative options:

1-Move the oldest kernel files to another filesystem, or everything, from /boot.
You don't need them there until time to reboot.

2-You're not forced to keep two kernels. Remove the non-running one manually.

3-As Stefan already suggested, MODULES=dep. It's routine here. Big initrds take
more time to load, which can be quite noticeable on old hardware.

4-Is your /boot adjacent to your swap? If yes, easily recreate both, with 
smaller
swap, larger /boot. Don't forget to adjust fstab for UUID change of swap, or 
apply
the one from fstab on the new.



My /boot is next to an encrypted lvm containing te rest of the disk. I 
fear resizing /boot would require a reinstall, I'll set modules=dep




firmware-iwlwifi

2022-10-01 Thread Georgi Naplatanov

Dear Debian community,

what is the problem with firmware-iwlwifi in testing?

The package is outdated but it's important.

Kind regards
Georgi



Re: Thunderbird 102 & {Cal,Card}DAV

2022-10-01 Thread Paul van der Vlis

Hoi Geert en anderen,

Op 30-09-2022 om 12:57 schreef Geert Stappers:

On Thu, Sep 29, 2022 at 10:28:23PM +0200, Richard Lucassen wrote:

On Thu, 29 Sep 2022 21:09:16 +0200 Paul van der Vlis wrote:


Ik ben over op Thunderbird versie 102, die zit bij de security
updates. Tot nu toe bevalt hij me wel.

Ik had wel wat problemen met de nieuwsgroepen support. Eerst was de
nieuwsserver verdwenen. Na afsluiten en opstarten van Thunderbird was
hij er weer, maar hij vroeg wel opnieuw naar username en wachtwoord.

Het adresboek is herschreven en staat nu eindelijk in een tab.



Ook cardav en caldav is nu beter geregeld :)



(hierboven staat ook een :)


In mijn Thunderbird, versie 102.3, installatie vind ik wel agenda en
adresboek dingen.  Wat ik nog niet gevonden heb, is de plek voor het
configuren van de CalDAV en/of CardDAV server.

Onder welk menu zou ik beter moeten kijken?


De agenda is wel logisch:
"bestand | nieuw | agenda | op het netwerk".

Het adresboek staat op een rare plaats, namelijk in het adresboek zelf.
Daar zie je een knop "Nieuw adresboek" met daarnaast een pijl naar 
beneden, klap dat open. Je ziet daar "Carddav adresboek toevoegen".



Het zou ook kunnen dat ik een plugin mis, dat ik eerst een thunderbird
plugin moet installeren.  


Niet nodig.


Ik deed `apt search thunderbird` met de hoop
om het missende onderdeel te vinden.
Zo vond ik Debian package "webext-dav4tbsync".

$ apt show webext-dav4tbsync 2> /dev/null | sed --quiet '/^Descr/,$p'
Description: Provide CalDAV & CardDAV for TbSync
  The CalDAV & CardDAV Provider for TbSync to sync contacts, tasks and
  calendars to Thunderbird.
  .
  Most CalDAV & CardDAV servers provide a discovery service, which allows
  one to use just the plain server name (FQDN) like "cloud.server.com" as
  server URL. TbSync will find all available calendars and address books
  and there is no need to know any specific URLs for individual address
  books or calendars. If this does not work because your server does not
  provide the discovery service, you have to enter the full path to the
  dav server itself, like "cloud.server.com/SOGo/dav".
  .
  This provider also includes some pre-defined service profiles for easy
  setup of accounts of iCloud, Yahoo!, Fruux and others.


Zou ik dat moeten lezen als:
   Zorg dat er discovery service is die vertelt waar de Ca{l,rd}DAV
   server staat en dan hoef je die in TB niet meer te configuren.
??


Nee. Je setup wordt er wat gemakkelijker van.


Of 'Ook cardav en caldav is nu beter geregeld :)' lezen als
   De net niet vlekkeloos is nu minder net niet vlekkeloos
??


Het werkt goed. Alleen moet dat aanmaken van een adresboek nog verhuist 
worden naar "bestand | nieuw | adresboek", zodat het net zo is als het 
instellen van andere accounts.



Ook dan ben ik benieuwd naar de ervaringen.:-)


Voor persoonlijk gebruik werkt het wel goed.

Groet,
Paul



--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/



Re: Thunderbird 102

2022-10-01 Thread Paul van der Vlis




Op 29-09-2022 om 22:28 schreef Richard Lucassen:

On Thu, 29 Sep 2022 21:09:16 +0200
Paul van der Vlis  wrote:


Ik ben over op Thunderbird versie 102, die zit bij de security
updates. Tot nu toe bevalt hij me wel.

Ik had wel wat problemen met de nieuwsgroepen support. Eerst was de
nieuwsserver verdwenen. Na afsluiten en opstarten van Thunderbird was
hij er weer, maar hij vroeg wel opnieuw naar username en wachtwoord.

Het adresboek is herschreven en staat nu eindelijk in een tab.

Ik ben niet ontevreden tot nu toe!


Ook cardav en caldav is nu beter geregeld :)


Wat ervaar je als verbeterd?  Voor mij werkte het ook goed in de vorige 
versie.


Groet,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/



Re: update-initramfs outside of /boot

2022-10-01 Thread Felix Miata
Erwan David composed on 2022-10-01 16:21 (UTC+0200):

> My /boot is 235 MB (from deb 10 installer), however in testing I now 
> have 56MB initramfs files and update-initramfs cannot work for the 3rd 
> kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade 
> there are temporarily 3 kernels).

> I see that all the files of the initramfs are put in /boot before 
> creating the compressed image, thus the need for place. Is there a way 
> to cofigure update-initrams so that the creation of the im age is done 
> in another filesystem before instalation in /boot ?

Alternative options:

1-Move the oldest kernel files to another filesystem, or everything, from /boot.
You don't need them there until time to reboot.

2-You're not forced to keep two kernels. Remove the non-running one manually.

3-As Stefan already suggested, MODULES=dep. It's routine here. Big initrds take
more time to load, which can be quite noticeable on old hardware.

4-Is your /boot adjacent to your swap? If yes, easily recreate both, with 
smaller
swap, larger /boot. Don't forget to adjust fstab for UUID change of swap, or 
apply
the one from fstab on the new.
-- 
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: update-initramfs outside of /boot

2022-10-01 Thread Sven Joachim
On 2022-10-01 17:26 +0200, Erwan David wrote:

> Le 01/10/2022 à 17:16, Stefan Monnier a écrit :
>>> My /boot is 235 MB (from deb 10 installer), however in testing I now have
>>> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
>>> install (and apt autoremove keeps 2 kernels, thus at upgrade there are
>>> temporarily 3 kernels).

The most sustainable solution is to increase your /boot filesystem,
which unfortunately might not be convenient.

>>  MODULES=dep
>>
>> and
>>
>>  COMPRESS=lzma
>>
>> in `initramfs.conf` can make a big difference.
>>
>>
>>  Stefan
>>
>>
> I alreaady have compres=zstd (should be better than
> lzma). modules=most because I do not like the "guess".

MODULES=dep should be fine as long as you do not intend to move your
disk to another machine.

> An d It would
> be a temporary mesuer since initramfs siuze keeps growing. I just do
> not see the point of building it in /boot rather than eg /tmp or
> another directory specified in conf.

It would be possible to create the initramfs in another directory, but
to ensure atomic upgrades it would have to be copied to /boot anyway
_before_ unlinking the old one (if any).  Otherwise the system could
become unbootable if it crashes at the wrong moment.

Cheers,
   Sven



Re: update-initramfs outside of /boot

2022-10-01 Thread Erwan David

Le 01/10/2022 à 17:16, Stefan Monnier a écrit :

My /boot is 235 MB (from deb 10 installer), however in testing I now have
56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
install (and apt autoremove keeps 2 kernels, thus at upgrade there are
temporarily 3 kernels).

 MODULES=dep

and

 COMPRESS=lzma

in `initramfs.conf` can make a big difference.


 Stefan


I alreaady have compres=zstd (should be better than lzma). modules=most 
because I do not like the "guess". An d It would be a temporary mesuer 
since initramfs siuze keeps growing. I just do not see the point of 
building it in /boot rather than eg /tmp or another directory specified 
in conf.





Re: update-initramfs outside of /boot

2022-10-01 Thread Stefan Monnier
> My /boot is 235 MB (from deb 10 installer), however in testing I now have
> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
> install (and apt autoremove keeps 2 kernels, thus at upgrade there are
> temporarily 3 kernels).

MODULES=dep

and

COMPRESS=lzma

in `initramfs.conf` can make a big difference.


Stefan



Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread Greg Wooledge
On Sat, Oct 01, 2022 at 02:19:47PM +, Andrew M.A. Cater wrote:
> That's probably a reasonable assumption. It's manually posted by me: it's
> the same text, fairly well, each month (modulo any copying error), it's
> not currently in version control. Now, I might be prepared to change
> that if I were to make any significnt changes.

It's not in a file that you simply :r (or equivalent) into the email?
That surprises me.



update-initramfs outside of /boot

2022-10-01 Thread Erwan David
My /boot is 235 MB (from deb 10 installer), however in testing I now 
have 56MB initramfs files and update-initramfs cannot work for the 3rd 
kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade 
there are temporarily 3 kernels).


I see that all the files of the initramfs are put in /boot before 
creating the compressed image, thus the need for place. Is there a way 
to cofigure update-initrams so that the creation of the im age is done 
in another filesystem before instalation in /boot ?





Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread Andrew M.A. Cater
On Sat, Oct 01, 2022 at 06:10:48AM -0400, The Wanderer wrote:
> On 2022-10-01 at 05:46, Andrew M.A. Cater wrote:
> 
> > Debian-user is a mailing list provided for support for Debian users, 
> > and to facilitate discussion on relevant topics.
> > 
> > Some guidelines which may help explain how the list works:
> 
> Allow me, if you will, to share my experience on receiving each month's
> copy of the mailing-list FAQ:
> 
> "Oh, there's this month's repost of the FAQ."
> 

That's probably a reasonable assumption. It's manually posted by me: it's
the same text, fairly well, each month (modulo any copying error), it's
not currently in version control. Now, I might be prepared to change
that if I were to make any significnt changes.

> "Well, there's no version number or last-changed date or other
> information like that, so I can't tell whether or not it's been updated."
> 
> "I know I've read the FAQ before, so in the absence of any reason to
> think that it may have changed, I'll just assume that it hasn't, and
> skip reading it because I probably already know what it says."
> 

Also a fair assumption: see above. This is really intended for new readers
- if I do the right thing, it comes early in the month on the first page,
relatively near the top. Anybody reading the list - and I *really* advise
folks to read lists rather than posting in passing - should see it.
> 
> By contrast, if the FAQ *did* include an indication of when it was last
> updated, I would have one of two lines of reaction. Either:
> 
> "Oh, there's this month's repost of the FAQ."
> 
> "The version number is the same as last month's / the last-changed date
> is more than a month old, so I know I've already read it."
> 
> "I'll skip reading it, because I already know what it says."
> 
> Or:
> 
> "Oh, there's this month's repost of the FAQ."
> 
> "Hey, the version number has been increased / I don't know what version
> number last month's posting had / the last-changed date is recent, so
> there might be information in there that I'm not familiar with."
> 
> "I'll read the whole thing, just to be sure I'm up to date on it."
> 
(lots of good reasoning skipped for space)
> 
> I therefore reiterate my suggestion, from what I think was one of the
> first times (a previous version of?) this FAQ was (re)posted, that some
> versioning information be attached to - and posted along with each copy
> of - this FAQ.
> 

OK, understood.

All best, as ever,

Andy Cater

> -- 
>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
> 




Re: usrmerge

2022-10-01 Thread billium

On 01/10/2022 15:07, billium wrote:

Thanks for your time Greg

This occurred from updates only no installs for a while.

I did try moving some of the files and sym linking, then rebooting to 
check, all worked (inc libc) but got bored doing it after about 30 
times.  I also tried sym linking /usr/bin and /usr/lib etc but it locked 
up then :).


This system is old now repeatedly doing upgrade, dist-upgrade and 
full-upgrade through the years.  So maybe its time is done ! :(  One 
mistake, through laziness, I never update the config files, so maybe a 
re-install (Sounds Windows-ish) may help.


This is the original text:
aurora:~# apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 604 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up usrmerge (31) ...

FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and 
/usr/lib/x86_64-linux-gnu/libc.so.6 exist.


You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
  installed usrmerge package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
  usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)

also:
aurora:~# apt install usr-is-merged
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
   usr-is-merged
0 upgraded, 1 newly installed, 0 to remove and 604 not upgraded.
1 not fully installed or removed.
Need to get 4,920 B of archives.
After this operation, 12.3 kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org/debian testing/main amd64 usr-is-merged 
all 31 [4,920 B]

Fetched 4,920 B in 0s (35.6 kB/s)
Selecting previously unselected package usr-is-merged.
(Reading database ... 493237 files and directories currently installed.)
Preparing to unpack .../usr-is-merged_31_all.deb ...


**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to 
merged-/usr.

*
* For more information please read https://wiki.debian.org/UsrMerge.
*
**


dpkg: error processing archive 
/var/cache/apt/archives/usr-is-merged_31_all.deb (--unpack):
  new usr-is-merged package pre-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
  /var/cache/apt/archives/usr-is-merged_31_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Billy

On 01/10/2022 13:40, Greg Wooledge wrote:

On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:
Since the last update to my debian testing I am unable to install 
anything

or upgrade.

Setting up usrmerge (31) ...

FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and 
/usr/lib/x86_64-linux-gnu/libc.so.6

exist.


How did you arrive in this state?  Is /lib already a symlink to /usr/lib
on your system?


I can move the stated file and create a symlink


DO NOT TRY THAT!

That's libc.  If you try to move that in the most naive way imaginable,
your system will break immediately.

If you've already got a fully merged /usr, there is a package you can
install to indicate this (usr-is-merged).  Install that, and usrmerge
won't try to set itself up.  Or something like that.  So I'm told.  I'm
not running testing at this time.

If you've got a *partially* merged /usr, then I may not be able to help
you much.  You'll need an expert.  A good start would be understanding
whatever state you're in and how you got there.

Did a previous apt-get operation try to install usrmerge and fail?  Do
you have the original error message?  Can you trace through the steps
that usrmerge performs, and undo whichever ones have already been done?
Or, if you're close to completion, complete the remaining steps by hand,
and then install usr-is-merged?

In the worst possible case, you might need to reinstall from scratch.
So, no matter what you try to do at this point, making a full backup
of your important data (/home /etc /usr/local and so on) would be highly
advisable.




Sorry about top posting misplaced cursor




Re: usrmerge

2022-10-01 Thread billium

Thanks for your time Greg

This occurred from updates only no installs for a while.

I did try moving some of the files and sym linking, then rebooting to 
check, all worked (inc libc) but got bored doing it after about 30 
times.  I also tried sym linking /usr/bin and /usr/lib etc but it locked 
up then :).


This system is old now repeatedly doing upgrade, dist-upgrade and 
full-upgrade through the years.  So maybe its time is done ! :(  One 
mistake, through laziness, I never update the config files, so maybe a 
re-install (Sounds Windows-ish) may help.


This is the original text:
aurora:~# apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 604 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up usrmerge (31) ...

FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and 
/usr/lib/x86_64-linux-gnu/libc.so.6 exist.


You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
 installed usrmerge package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
 usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)

also:
aurora:~# apt install usr-is-merged
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  usr-is-merged
0 upgraded, 1 newly installed, 0 to remove and 604 not upgraded.
1 not fully installed or removed.
Need to get 4,920 B of archives.
After this operation, 12.3 kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org/debian testing/main amd64 usr-is-merged 
all 31 [4,920 B]

Fetched 4,920 B in 0s (35.6 kB/s)
Selecting previously unselected package usr-is-merged.
(Reading database ... 493237 files and directories currently installed.)
Preparing to unpack .../usr-is-merged_31_all.deb ...


**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
**


dpkg: error processing archive 
/var/cache/apt/archives/usr-is-merged_31_all.deb (--unpack):
 new usr-is-merged package pre-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
 /var/cache/apt/archives/usr-is-merged_31_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Billy

On 01/10/2022 13:40, Greg Wooledge wrote:

On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:

Since the last update to my debian testing I am unable to install anything
or upgrade.

Setting up usrmerge (31) ...

FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6
exist.


How did you arrive in this state?  Is /lib already a symlink to /usr/lib
on your system?


I can move the stated file and create a symlink


DO NOT TRY THAT!

That's libc.  If you try to move that in the most naive way imaginable,
your system will break immediately.

If you've already got a fully merged /usr, there is a package you can
install to indicate this (usr-is-merged).  Install that, and usrmerge
won't try to set itself up.  Or something like that.  So I'm told.  I'm
not running testing at this time.

If you've got a *partially* merged /usr, then I may not be able to help
you much.  You'll need an expert.  A good start would be understanding
whatever state you're in and how you got there.

Did a previous apt-get operation try to install usrmerge and fail?  Do
you have the original error message?  Can you trace through the steps
that usrmerge performs, and undo whichever ones have already been done?
Or, if you're close to completion, complete the remaining steps by hand,
and then install usr-is-merged?

In the worst possible case, you might need to reinstall from scratch.
So, no matter what you try to do at this point, making a full backup
of your important data (/home /etc /usr/local and so on) would be highly
advisable.





Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread rhkramer
On Saturday, October 01, 2022 06:10:48 AM The Wanderer wrote:
> On 2022-10-01 at 05:46, Andrew M.A. Cater wrote:
> > Debian-user is a mailing list provided for support for Debian users,
> > and to facilitate discussion on relevant topics.

> I therefore reiterate my suggestion, from what I think was one of the
> first times (a previous version of?) this FAQ was (re)posted, that some
> versioning information be attached to - and posted along with each copy
> of - this FAQ.

+1

And I would expand the suggestion to add "revision marks" (ideally in the left 
margin) of the changed sections.

After all, many of us are used to using (word)diff or similar.

(And, this should be done for all legal type documents (changes in terms, 
etcs.)

(And, to go one step further, those emails (not from Debian) which say some 
list of terms / items has been changed, but without describing the change are 
also annoying -- you don't know whether the change might be relevant to you or 
not and you have to decide whether to follow the link and then (probably) try 
to skim a large part of the document to see what has changed.)

-- 
rhk

If you reply: snip, snip, and snip again; leave attributions; avoid HTML; 
avoid top posting; and keep it "on list".  (Oxford comma included at no 
charge.)  If you change topics, change the Subject: line. 

Writing is often meant for others to read and understand (legal agreements 
excepted?) -- make it easier for your reader by various means, including 
liberal use of whitespace and minimal use of (obscure?) jargon, abbreviations, 
acronyms, and references.

If someone else has already responded to a question, decide whether any 
response you add will be helpful or not ...

A picture is worth a thousand words -- divide by 10 for each minute of video 
(or audio) or create a transcript and edit it to 10% of the original.



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Camaleón
El 2022-10-01 a las 13:44 +0200, Alfonso García Rodríguez escribió:

> > Hum... para que Firefox vaya suavecito en sistemas viejitos como los 
> > nuestros, tienes que desactivar la aceleración gráfica por hardware y 
> > las demás animaciones y efectos, seguro que notas la diferencia. 
> > 
> > Eso es válido tanto para la ESR como la Release.
> > 
> > Y bueno, si te animas a probar la 105 Release, es sencillo, sólo tienes 
> > que descargar el paquete de la página de Firefox, lo descomprimes en 
> > /opt y antes de ejecutar el binario, renombra el perfil de tu usuario 
> > de firefox actual para que no lo sobreescriba.
> > 
> > Pero si quieres mantener la ESR que instala Debian, intenta primero 
> > desactivando la aceleración por hardware de la GPU.
> > 
> 
> ¡Ostras! ¿Y cómo hago eso?

Pues... a ver, que yo hice un montón de cambios porque odio las 
animaciones esas de la wonderbar que te ampliaban la barra de 
direcciones, los iconos que saltan y los efectos de degradados y 
demás... he tuneado tanto a Firefox que ya ni lo reconozco :-)

about:config → ui.prefersReducedMotion → true

También tengo habilitado en Privacidad el modo Estricto y siempre qe 
cierro el navegador elimino las cookies y los datos y el historial de 
navegación (vamos, que mi Firefox es anmésico).

Pero lo de la aceleración por hardware sí es sencillo, desde los 
Ajustes, opción de Renidmiento, ahí tengo desactivadas las dos:

Rendimiento

[ ] Usar configuración de rendimiento recomendada
  [ ] Usar aceleración de hardware cuando esté disponible

Si las habilito, Firefox se vuelve lentorro del copón y casca cada dos 
por tres. Un horror.

También puedes probar desactivando WebGL (about:config → webgl.disabled → 
true), eso sí, algunas páginas que usen esta tecnología dejarán de 
funcionar, claro está.

> > > * Sistema operativo: <>
> > > 
> > > * Núcleo: < > > (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 
> > > 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 
> > > 5.10.140-1 (2022-09-02)>>
> > > 
> > ¿Existe algún motivo para usar un kernel PAE? :-?
> >
> 
> Perdona mi ignorancia. Pero ¿qué es un kernel PAE?

Es un kernel de 32 bits pero que permite al sistema acceder a más de 4 
GiB de memoria RAM que sería lo normal en un kernel de 32 bits.

Lo que no entiendo es cómo Debian ha instalado el kernel PAE, tu equipo 
es lo bastante moderno para que admita las extensiones de 64 bits 
nativas, es raro.

Manda la salida de «grep -i flags /proc/cpuinfo».
 
> > Con 8 GiB de RAM te recomiendo una versión de 64 bits, no para ahora 
> > sino cuando tengas que actualizar el sistema operativo.
> 
> ¿Qué paquete de Debian uso para esto?
 
Ninguno, tendrías que volver a instalar todo el sistema desde cero :-(, 
por eso te digo, que si tienes que volver a instalar, y tu sistema lo 
admite, mejor instala un kernel de 64 bits.

Saludos,

-- 
Camaleón 



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Saúl
vamos carajo esta comunidad va  :
https://www.youtube.com/watch?v=ir6nk2zrMG0
vamos que es sábado carajo jejeje xdxdxd no importa la capa de one hundred
madafakin eighty nine

El sáb, 1 oct 2022 a la(s) 08:48, Alfonso García Rodríguez (
alfon...@gmail.com) escribió:

> > >
> > > Hola Camaleón,
> > >
> > > Yo estoy usando <> en Debian y me va fatal.
> > > Estoy desesperado. Se cuelga cada 2 x 3 hasta el punto de que me estoy
> > > planteando usar otro navegador. Cada actualización que hago complica
> > > la situación, haciéndome sufrir cuelgues con más frecuencia.
> >
> >
> > ¿Qué error te da cuando lo lanzas desde el terminal al colgarse? ¿Se te
> > cierra?
> >
>
> La verdad es que no he probado a lanzarlo desde un terminal.
>
> > Yo localicé una versión que no se me congelaba , las posteriores siguen
> > fallando me
> >
>
> En mi caso particular no se congela, simplemente se cierra. Luego muestra
> una pantalla indicando que informe al equipo de desarrollo y tal... Yo
> marco
> la opción de que lo haga y adios.
>
>


Re: usrmerge

2022-10-01 Thread Greg Wooledge
On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote:
> Since the last update to my debian testing I am unable to install anything
> or upgrade.
> 
> Setting up usrmerge (31) ...
> 
> FATAL ERROR:
> Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6
> exist.

How did you arrive in this state?  Is /lib already a symlink to /usr/lib
on your system?

> I can move the stated file and create a symlink

DO NOT TRY THAT!

That's libc.  If you try to move that in the most naive way imaginable,
your system will break immediately.

If you've already got a fully merged /usr, there is a package you can
install to indicate this (usr-is-merged).  Install that, and usrmerge
won't try to set itself up.  Or something like that.  So I'm told.  I'm
not running testing at this time.

If you've got a *partially* merged /usr, then I may not be able to help
you much.  You'll need an expert.  A good start would be understanding
whatever state you're in and how you got there.

Did a previous apt-get operation try to install usrmerge and fail?  Do
you have the original error message?  Can you trace through the steps
that usrmerge performs, and undo whichever ones have already been done?
Or, if you're close to completion, complete the remaining steps by hand,
and then install usr-is-merged?

In the worst possible case, you might need to reinstall from scratch.
So, no matter what you try to do at this point, making a full backup
of your important data (/home /etc /usr/local and so on) would be highly
advisable.



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Alfonso García Rodríguez
> >
> > Hola Camaleón,
> >
> > Yo estoy usando <> en Debian y me va fatal.
> > Estoy desesperado. Se cuelga cada 2 x 3 hasta el punto de que me estoy
> > planteando usar otro navegador. Cada actualización que hago complica
> > la situación, haciéndome sufrir cuelgues con más frecuencia.
> 
> 
> ¿Qué error te da cuando lo lanzas desde el terminal al colgarse? ¿Se te
> cierra?
>

La verdad es que no he probado a lanzarlo desde un terminal.

> Yo localicé una versión que no se me congelaba , las posteriores siguen
> fallando me
>

En mi caso particular no se congela, simplemente se cierra. Luego muestra
una pantalla indicando que informe al equipo de desarrollo y tal... Yo marco
la opción de que lo haga y adios.



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Alfonso García Rodríguez
> Hum... para que Firefox vaya suavecito en sistemas viejitos como los 
> nuestros, tienes que desactivar la aceleración gráfica por hardware y 
> las demás animaciones y efectos, seguro que notas la diferencia. 
> 
> Eso es válido tanto para la ESR como la Release.
> 
> Y bueno, si te animas a probar la 105 Release, es sencillo, sólo tienes 
> que descargar el paquete de la página de Firefox, lo descomprimes en 
> /opt y antes de ejecutar el binario, renombra el perfil de tu usuario 
> de firefox actual para que no lo sobreescriba.
> 
> Pero si quieres mantener la ESR que instala Debian, intenta primero 
> desactivando la aceleración por hardware de la GPU.
> 

¡Ostras! ¿Y cómo hago eso?

> > * Sistema operativo: <>
> > 
> > * Núcleo: < > (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, 
> > GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.140-1 
> > (2022-09-02)>>
> > 
> ¿Existe algún motivo para usar un kernel PAE? :-?
>

Perdona mi ignorancia. Pero ¿qué es un kernel PAE?

> Con 8 GiB de RAM te recomiendo una versión de 64 bits, no para ahora 
> sino cuando tengas que actualizar el sistema operativo.

¿Qué paquete de Debian uso para esto?



Re: Re: Re: SSD Optimization - Crucial CT1000MX500SSD1

2022-10-01 Thread Marcelo Laia

Hi Andy, so sorry for that. Here is the long one.

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.0-2-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_DescriptionStatus  Remaining  LifeTime(hours)  
LBA_of_first_error
# 1  Extended offlineCompleted without error   00%   544 -
# 2  Short offline   Completed without error   00%   507 -


--
Marcelo



usrmerge

2022-10-01 Thread billium
Since the last update to my debian testing I am unable to install 
anything or upgrade.


Setting up usrmerge (31) ...

FATAL ERROR:
Both /lib/x86_64-linux-gnu/libc.so.6 and 
/usr/lib/x86_64-linux-gnu/libc.so.6 exist.


I can move the stated file and create a symlink but there are so many 
files, it seems endless.


Has anybody got a quick reliable solution?

Thanks
Billy



Re: Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread The Wanderer
On 2022-10-01 at 05:46, Andrew M.A. Cater wrote:

> Debian-user is a mailing list provided for support for Debian users, 
> and to facilitate discussion on relevant topics.
> 
> Some guidelines which may help explain how the list works:

Allow me, if you will, to share my experience on receiving each month's
copy of the mailing-list FAQ:

"Oh, there's this month's repost of the FAQ."

"Well, there's no version number or last-changed date or other
information like that, so I can't tell whether or not it's been updated."

"I know I've read the FAQ before, so in the absence of any reason to
think that it may have changed, I'll just assume that it hasn't, and
skip reading it because I probably already know what it says."


By contrast, if the FAQ *did* include an indication of when it was last
updated, I would have one of two lines of reaction. Either:

"Oh, there's this month's repost of the FAQ."

"The version number is the same as last month's / the last-changed date
is more than a month old, so I know I've already read it."

"I'll skip reading it, because I already know what it says."

Or:

"Oh, there's this month's repost of the FAQ."

"Hey, the version number has been increased / I don't know what version
number last month's posting had / the last-changed date is recent, so
there might be information in there that I'm not familiar with."

"I'll read the whole thing, just to be sure I'm up to date on it."



I apply similar reasoning to updated terms-of-service documents, updated
telephone menus ("please listen carefully, as our options have changed",
without any indication of when they changed and so whether there's
anything new since the last time I *did* listen to the whole menu), et
cetera - except that in some of those cases there are immediate or
legally-binding consequences to missing any changes by failing to review
such a document (so I have incentive to shoulder the burden of going
through the document again), whereas with a FAQ such as this there is
not (so I do not).

Including a version number means there's a chance of people with my
mindset - who have read the FAQ before, and don't want to waste time on
reading an unaltered document - reading it again.

Not including one means that such people are guaranteed to not read the
FAQ each time it is reposted - and, therefore, that for such people the
monthly "reminder" copy of the FAQ is a pure waste, and is not achieving
or producing any benefit at all.

I therefore reiterate my suggestion, from what I think was one of the
first times (a previous version of?) this FAQ was (re)posted, that some
versioning information be attached to - and posted along with each copy
of - this FAQ.

-- 
   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: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Camaleón
El 2022-10-01 a las 11:16 +0200, Alfonso García Rodríguez escribió:

> El día 29/09/2022, a las 19:55, Camaleón escribió:
> > Hola,
> > 
> > Me estoy planteando el cambio de Firefox (release) a Firefox (ESR), 
> > ambos instalados directamente desde Mozilla, manteniendo el perfil 
> > actual del usuario pero desconozco si la transición tendrá algún 
> > inconveniente.
> > 
> > El motivo es que mi equipo es viejito (Intel(R) Core(TM)2 Quad CPU Q9550
> >  @ 2.83GHz, NVIDIA Corporation NV43 [Quadro NVS 440]) y las aplicaciones 
> > cada vez son más demandantes (sobre todo en cuestión de gráfica y 
> > controladores de aceleración de la GPU). 
> > 
> > Ya he pasado de LibreOffice Fresh a LibreOffice Still porque la Fresh 
> > tiene algunos fallos que ronca el mango y yo tampoco estoy para sustos, 
> > por eso quiero hacer lo mismo con Firefox.
> > 
> > La versión actual de Firefox es la 105.0.1 (la que tengo instalada) y la 
> > ESR creo que va por la 102.3.0.
> > 
> > Si alguien ha hecho esa transición, se agradece cualquier comentario o 
> > sugerencia, problemas encontrados o cómo le ha ido.
> 
> Hola Camaleón,
> 
> Yo estoy usando <> en Debian y me va fatal.
> Estoy desesperado. Se cuelga cada 2 x 3 hasta el punto de que me estoy
> planteando usar otro navegador. Cada actualización que hago complica 
> la situación, haciéndome sufrir cuelgues con más frecuencia. 
> 
> O sea que mi experiencia es malísima. No te puedo decir otra cosa.

Hum... para que Firefox vaya suavecito en sistemas viejitos como los 
nuestros, tienes que desactivar la aceleración gráfica por hardware y 
las demás animaciones y efectos, seguro que notas la diferencia. 

Eso es válido tanto para la ESR como la Release.

Y bueno, si te animas a probar la 105 Release, es sencillo, sólo tienes 
que descargar el paquete de la página de Firefox, lo descomprimes en 
/opt y antes de ejecutar el binario, renombra el perfil de tu usuario 
de firefox actual para que no lo sobreescriba.

Pero si quieres mantener la ESR que instala Debian, intenta primero 
desactivando la aceleración por hardware de la GPU.

> A continuación listo las características de mi equipo y versiones del
> sistema operativo y núcleo:
> 
> * Sistema operativo: <>
> 
> * Núcleo: < (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
> 2.35.2) #1 SMP Debian 5.10.140-1 (2022-09-02)>>
> 
> * Microprocesador: 4 x <>
> 
> * Modelo portátil: Dell Latitude 7280 - 8GB RAM
> 
> * Gráfica: 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 
> [HD Graphics 520] (rev 07)

¿Existe algún motivo para usar un kernel PAE? :-?

Con 8 GiB de RAM te recomiendo una versión de 64 bits, no para ahora 
sino cuando tengas que actualizar el sistema operativo.

Saludos,

-- 
Camaleón 



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Javier Barroso
Buenas,

El sáb., 1 oct. 2022 11:17, Alfonso García Rodríguez 
escribió:

> El día 29/09/2022, a las 19:55, Camaleón escribió:
> > Hola,
> >
> > Me estoy planteando el cambio de Firefox (release) a Firefox (ESR),
> > ambos instalados directamente desde Mozilla, manteniendo el perfil
> > actual del usuario pero desconozco si la transición tendrá algún
> > inconveniente.
> >
> > El motivo es que mi equipo es viejito (Intel(R) Core(TM)2 Quad CPU Q9550
> >  @ 2.83GHz, NVIDIA Corporation NV43 [Quadro NVS 440]) y las aplicaciones
> > cada vez son más demandantes (sobre todo en cuestión de gráfica y
> > controladores de aceleración de la GPU).
> >
> > Ya he pasado de LibreOffice Fresh a LibreOffice Still porque la Fresh
> > tiene algunos fallos que ronca el mango y yo tampoco estoy para sustos,
> > por eso quiero hacer lo mismo con Firefox.
> >
> > La versión actual de Firefox es la 105.0.1 (la que tengo instalada) y la
> > ESR creo que va por la 102.3.0.
> >
> > Si alguien ha hecho esa transición, se agradece cualquier comentario o
> > sugerencia, problemas encontrados o cómo le ha ido.
>
> Hola Camaleón,
>
> Yo estoy usando <> en Debian y me va fatal.
> Estoy desesperado. Se cuelga cada 2 x 3 hasta el punto de que me estoy
> planteando usar otro navegador. Cada actualización que hago complica
> la situación, haciéndome sufrir cuelgues con más frecuencia.


¿Qué error te da cuando lo lanzas desde el terminal al colgarse? ¿Se te
cierra?

Yo localicé una versión que no se me congelaba , las posteriores siguen
fallando me

En el bugzilla no parecen saber dónde está el problema

Saludos


Monthly FAQ for the Debian-user mailing list

2022-10-01 Thread Andrew M.A. Cater
Debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics. 

Some guidelines which may help explain how the list works:

* The language on this mailing list is English. There may be other mailing 
  lists that are language-specific for example debian-user-french 

* It is common for users to be redirected here from other lists - for example,
  from debian-project. It is also common for people to be posting here when 
  English is not their primary language. Please be considerate.

* The list is a Debian communication forum. As such, it is subject to both 
  the Debian mailing list Code of Conduct and the main Debian Code of Conduct

 https://www.debian.org/MailingLists/#codeofconduct
 https://www.debian.org/code_of_conduct

* This is a fairly busy mailing list and you may have to wait for an
  answer - please be patient. Please post answers back to the list so
  others can benefit; private conversations don't benefit people who
  may be following along on the list or reading the archives later.

* Help and advice on this list is provided by volunteers in their own time.
  It is common for there to be different opinions or answers provided.

 * Please try to stay on topic. Arguments for the sake of it are not
   welcome here. Partisan political / religious / cultural arguments
   do not belong here either. Debian's community is world wide; don't
   assume others will agree with your views or need to read them on a
   Debian list.

* There is an FAQ on the Debian wiki derived from some questions asked on this
  list at https://wiki.debian.org/FAQsFromDebianUser

* One question that comes up on almost all Debian lists from time to time is of
  the form: 

  "I have done something wrong / included personal details in an email.
   Could you please delete my name / details / remove the mail"

Practically, this is impossible: the mailing lists are archived, potentially 
cached
by Google and so on. Unfortunately, there is nothing much we can do to ensure 
that
all copies anywhere on the Internet are deleted. Asking to do this may only 
serve to
draw further attention - the so-called "Streisand effect"
See:  https://en.wikipedia.org/wiki/Streisand_effect

Problems?
=

Complaints about inappropriate behaviour should be referred to the
Debian Community Team .

Inappropriate behaviour on the list may lead to warnings; repeated bad
behaviour may lead to temporary or permanent bans for offenders.
 



Re: Pasar de Firefox (release) a Firefox ESR

2022-10-01 Thread Alfonso García Rodríguez
El día 29/09/2022, a las 19:55, Camaleón escribió:
> Hola,
> 
> Me estoy planteando el cambio de Firefox (release) a Firefox (ESR), 
> ambos instalados directamente desde Mozilla, manteniendo el perfil 
> actual del usuario pero desconozco si la transición tendrá algún 
> inconveniente.
> 
> El motivo es que mi equipo es viejito (Intel(R) Core(TM)2 Quad CPU Q9550
>  @ 2.83GHz, NVIDIA Corporation NV43 [Quadro NVS 440]) y las aplicaciones 
> cada vez son más demandantes (sobre todo en cuestión de gráfica y 
> controladores de aceleración de la GPU). 
> 
> Ya he pasado de LibreOffice Fresh a LibreOffice Still porque la Fresh 
> tiene algunos fallos que ronca el mango y yo tampoco estoy para sustos, 
> por eso quiero hacer lo mismo con Firefox.
> 
> La versión actual de Firefox es la 105.0.1 (la que tengo instalada) y la 
> ESR creo que va por la 102.3.0.
> 
> Si alguien ha hecho esa transición, se agradece cualquier comentario o 
> sugerencia, problemas encontrados o cómo le ha ido.

Hola Camaleón,

Yo estoy usando <> en Debian y me va fatal.
Estoy desesperado. Se cuelga cada 2 x 3 hasta el punto de que me estoy
planteando usar otro navegador. Cada actualización que hago complica 
la situación, haciéndome sufrir cuelgues con más frecuencia. 

O sea que mi experiencia es malísima. No te puedo decir otra cosa.

A continuación listo las características de mi equipo y versiones del
sistema operativo y núcleo:

* Sistema operativo: <>

* Núcleo: <>

* Microprocesador: 4 x <>

* Modelo portátil: Dell Latitude 7280 - 8GB RAM

* Gráfica: 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD 
Graphics 520] (rev 07)

Un saludo.



Re: Plugin HP

2022-10-01 Thread Xavier BAR
Bonjour à tous.

Version 3.21 desinstallée.
Réinstallation de la version 3.22 téléchargée directement depuis le site dev de 
HP.
J'ai toujours une erreur bad check sum quand je fais un hp-plugin -i mais le 
plugin s'installe quand même.
Aucun changement pour la partie impression. Elle fonctionne toujours bien.

La partie numérisation fonctionne aussi maintenant.

Les voies du Seigneur sont impénétrables...
^^

Bonne journée à tous !
Cordialement.
Xavier.

30 sept. 2022 20:34:56 debian-user...@emailasso.net:

> Eurêka !
> 
> - télécharger le plugin avec wget(ici la hplip-3.22.6) : wget 
> https://developers.hp.com/sites/default/files/hplip-3.22.6-plugin.run
>  
> - lancer un script (pas de sudo ni root)  ./hplip-3.22.6-plugin.run
> L'installation s'ouvre en GUI.
> 
> Et ça marche !!!
> 
> @ Xavier : dis-nous si pour toi aussi, c'est ok.
> 
> Bonne soirée
> 
> Sylvie
> 
> On 30/09/2022 18:43, Bureau LxVx  wrote:
>> Bonsoir et merci de votre aide.
>> 
>> @P Merlin : ça dépend des imprimantes
>> @Hamster :
>>> Est-ce que le dépot non-free est activé dans son sources.list ?
>> oui
>> 
>> @David :
>>> ça dépend de l'imprimante, pour scanner avec la mienne (MFP m125nw) il
>>> faut installer un plugin qui est un bout de firmware binaire fourni
>>> par HP mais qui n'est pas dans les paquets debian à ce qu'il semble
>> oui, c'est le cas :-(
>> Quelle version de hplip as-tu ?
>> perso, j'ai dernier :
>> 
>> @Xavier : je n'ai même pas d'impression : il FAUT le plugin ...
>> 
>> Aussi, je viens de refaire une install complète avec toutes les "non-free"
>> Je viens de découvrir que le hplip.run doit être lancé non-root .. Une
>> alerte dans le terminal ...
>> Ok. fin d'install : Redémarrage demandé en cours ...
>> Demande de page test >> Driver plugin installation  :
>> "file does not match its checksum. File may have been corrupted or altered"
>> Failed to install Plug-in. Either you have chosen to skip the plug-in
>> installation or entered incorrect password ...  Ni l'un ni l'autre :-(
>> 
>> Dans le fichier "plugin" correspondant
>> https://developers.hp.com/sites/default/files/hplip-3.21.2-plugin.run
>> Comment vérifier le checksum ou MD5 visible dans le script ?
>>> CRCsum="515935464"
>>> MD5="3b6bcfaccc9b698544899b3fd8b0193c"
>> 
>> Une solution ? Merci
>> 
>> Sylvie
>> 
>> 
>> Le 30/09/2022 à 17:40, Xavier BAR a écrit :
>>> Bonjour à tous.
>>> 
>>> J'ai exactement le même pb.
>>> Un hp-plugin ou hp-plugin -i me donnent la même erreur.
>>> La partie impression fonctionne parfaitement. Mais pas la partie
>>> numérisation qui nécessite le plugin. Sans lui le scanner n'est pas
>>> détecté par le numériseur de documents.
>>> Si vous trouvez la solution je suis preneur.
>>> Cordialement.
>>> Xavier.
>>> 
>>> 30 sept. 2022 15:43:14 Bureau LxVx :
>>> 
>>>     Bonjour,
>>> 
>>>     Sur le pc d'un am et une debian toute fraîche et mise à jour, je
>>>     ne réussis
>>>     pas à installer / finaliser le HPLIP.
>>>     A la fin de l'installation, impossibilité d'imprimer la page test.
>>>     Il manque le plugin  : ok
>>> 
>>>     Toutefois, l'installation de ce plugin et du lancement du .run
>>>     https://developers.hp.com/sites/default/files/hplip-3.21.2-plugin.run
>>>     se termine par checksum corrompu.
>>> 
>>>     Et cela que ce soit la dernière version hplip téléchargée sur
>>>     https://developers.hp.com/hp-linux-imaging-and-printing : Version:
>>>     3.22.6
>>>     Clé du plugin correspondant corrompue
>>> 
>>>     ou celle de synaptic :
>>>     3.21.2+dfsg1-2 (unstable ?)
>>> 
>>>     https://developers.hp.com/sites/default/files/hplip-3.21.2-plugin.run
>>>     Dans le script : HPLIP 3.21.2 Plugin Self Extracting Archive"
>>> 
>>>     J'espère avoir été assez claire ...
>>> 
>>>     Merci de votre aide.
>>> 
>>>     Bien librement,
>>> 
>>>     Sylvie
>>> 
>> 
>>