Re: where are the crontab files in Trixie?

[David Wright]

On Wed 28 Feb 2024 at 22:32:57 (+0700), Max Nikulin wrote:
> On 28/02/2024 10:35, David Wright wrote:
> > In which case, I'd write the remaining cron line as:
> > 
> >@reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
> 
> I am in doubts if it is a task for cron. Wouldn't udev rules be better?
> 
> https://stackoverflow.com/questions/442833/how-to-force-driver-to-device-match-in-linux/52943745#52943745
> https://unix.stackexchange.com/questions/67936/attaching-usb-serial-device-with-custom-pid-to-ttyusb0-on-embedded/165845#165845
> 
> Moreover, to load and configure modules there are /etc/modprobe.d/ and
> /etc/modules.
> 
> If it is a weird device that may appear either as 13b1:0039 (supported
> by brcmfmac accordingly to modinfo) and 13b1:0bdc, may it happen that
> it is possible to use e.g. usb-modeswitch to adjust which way the
> device tries to present itself?

Those are fair questions. If the appearance of the brcmfmac/ directory
is the sole precondition, then I would probably try udev. But I claim
no knowledge about the module or any device connected with it.

Where cron/sleep is useful is where some device has to settle, or
wait in some way, before the string is sent. One example I use is:

  @reboot sleep 15 && printf '\n' > /dev/tty1 && /usr/sbin/rfkill > /dev/tty1 
&& /usr/bin/ip a > /dev/tty1

which tells me whether the hardware toggle switch on my ancient laptop
is actually unblocked (the switch's indicator lamp is unreliable) and
whether it's connected to the router, and how.

Cheers,
David.

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[ajh-valmer]

On Wednesday 28 February 2024 21:29:38 Pierre ESTREm wrote:
> Faut écrire :
> $ xrandr -s 1920x1080 # Notez le 'x' et pas le '*' :

Pour moi, c'est le pilote vidéo qui n'est plus correctement installé.
Résolvons le problèmes dans le bon ordre.

Fix for missing gsettings desktop schemas on unstable

[Ash Joubert]

There is a huge transition underway on unstable to migrate to 64-bit 
time_t. After upgrading to the new libglib2.0-0t64, nothing could find 
gsettings desktop schemas, breaking applications like rednotebook and 
reportbug (lol), and after a reboot, stopping services like at-spi from 
starting, causing huge timeouts at system and application start.


A workaround that worked for me was to reinstall gsettings-desktop-schemas:

# apt-get reinstall gsettings-desktop-schemas
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not 
upgraded.

Need to get 660 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian sid/main amd64 
gsettings-desktop-schemas all 46~beta-3 [660 kB]

Fetched 660 kB in 2s (431 kB/s)
(Reading database ... 35 files and directories currently installed.)
Preparing to unpack .../gsettings-desktop-schemas_46~beta-3_all.deb ...
Unpacking gsettings-desktop-schemas (46~beta-3) over (46~beta-3) ...
Setting up gsettings-desktop-schemas (46~beta-3) ...
Processing triggers for libglib2.0-0t64:amd64 (2.78.4-2) ...

Cheers,

--
Ash Joubert (they/them) 
Director / Game Developer
Transient Software Limited 
New Zealand

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[Pierre ESTREm]

Faut écrire :
$ xrandr -s 1920x1080 # Notez le 'x' et pas le '*'

pierre estrem



Le 28/02/2024 à 18:34, Olivier a écrit :

# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minim 800x600, current 800x600, maximum 800x600
default connected primary 800x600+0+0 0mm x 0mm
   800x600 75.00'

# xrandr -s 1920*1080
Size 1920*1080 not found in available modes


Est-il possible de "lancer manuellement" la fonction KMS une fois que
l'on a démarré avec i915.modesetting=0 ?

Le mer. 28 févr. 2024 à 18:16, Olivier  a écrit :

dmesg -l err

[0.210659] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[0.210667] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[0.210697] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[0.210702] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[1.074140] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[1.074182] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[1.074236] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[1.074266] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)


dmesg -l warn
[0.069946] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[0.311681] pnp 00:02: disabling [mem 0xc000-0xcfff]
because it overlaps :00:02.0 BAR 9 [mem 0x-0xdfff
64bit pref]
[0.708514] hpet_acpi_add: no address or irqs in _CRS
[0.715962] i8042: PNP: PS/2 appears to have AUX port disabled, if
this is incorrect please boot with i8042.nopnp
[0.972498] i2c i2c-0: Systems with more than 4 memory slots not
supported yet, not instantiating SPD
[1.081026] usb: port power management may be unreliable
[1.174989] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is
disabled. Duplicate IMA measurements will not be recorded in the IMA
log.
[3.655595] thermal thermal_zone6: failed to read out thermal zone (-61)
[4.144718] ext2 filesystem being mounted at /boot supports
timestamps until 2038-01-19 (0x7fff)
[5.372381] kauditd_printk_skb: 15 callbacks suppressed
[   16.139210] systemd[864]: memfd_create() called without MFD_EXEC or
MFD_NOEXEC_SEAL set

Le mer. 28 févr. 2024 à 18:05, Olivier  a écrit :

Par SSH, j'ai:
root@foo:~# ps aux|grep -i xorg
root 886  0.1  0.4 317152 78152 tty1 Sl+  17:48   0:00
/usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/116/gdm/Xauthority
-nolisten tcp -background none -noreset -keeptty -novtswitch -verbose
3
...
root@foo:~# DISPLAY=:0.0 xrandr
Authorization required, but no authorization protocol specified

Can't open display :0.0


Comment résoudre ?

Le mer. 28 févr. 2024 à 14:23, Sébastien NOBILI
  a écrit :

Bonjour,

Le 2024-02-27 18:08, Olivier a écrit :

Comment utiliser xrandr par SSH ? Faut-il se connecter en tant que
root ou simple utilisateur ?

Il faut être connecté avec le compte qui fait tourner la session Xorg
(sinon on peut passer par `xhost` mais c'est à éviter).

Il faudra aussi déclarer la variable `DISPLAY` :

```
export DISPLAY=:0.0
```

Sébastien

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[didier gaumet]

Bonjour,

je ne suis pas forcément très au courant concernant ce genre de 
problème, mais à la louche (je peux me tromper) ça ressemble plus à une 
problème dé récupération des caractéristiques EDID (dont la résolution) 
de l'écran qu'à un problème de pilote ou de serveur X/Wayland.


Ton écran a l'air reconnu comme un truc basique SVGA (800x600 au format 
4/3 alors que les moniteurs récents au format 4/3 me paraissent très 
rares voire inexistants).


ça peut arriver quand on utilise un câble VGA au lieu d'un truc moderne 
du genre câble HDMI ou DVI (à cause de la reconversion en analogique, je 
pense): dans ce cas passer à un câble HDMI ou DVI
ça peut arriver aussi quand l'écran en question n'annonce pas 
correctement ses caractéristiques EDID. Il y a un article sur wiki 
archlinux qui te permettra peut-être de spécifier la résolution native 
correcte de ton écran (au besoin regarder les spécifications techniques 
du modèle concerné):

https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID

Une fois le problème résolu, repasser en mode KMS (supprimer les options 
nomodeset ou modeset=0), les pilotes modernes en ont besoin

Re: TESTE DE INTEGRIDADE SSD

[João Pedro Nader Gervasoni]

Me retire desta lista

Obter o Outlook para Android

From: Jose Tavares 
Sent: Wednesday, February 28, 2024 2:02:14 AM
To: Yuri Musachio 
Cc: Rafael de Almeida ; debian-user-portuguese 

Subject: Re: TESTE DE INTEGRIDADE SSD

Me lembrei de algo extra..

Se a máquina onde o SSD está ficar fazendo muito swap, e for colocado no SSD 
uma particao de swap muito pequena, alguns blocos do SSD serão super stressados 
com escrita e leitura, podendo danificar aquele espaco precocemente. A 
recomendacao é que o swap seja sempre 2x a quantidade de ram. Hoje em dia isto 
pode ser bastante de espaco desperdicado.

Lembrei disto pois já estourei SSD e nvme de laptops algumas vezes. lol ..
Deixa eu contar como aconteceu comigo o problema repetitivamente:
Se o cara ir atrás do MTBF dos modelos de SSD e ler quantos bytes eles aceitam 
de escrita antes de pifar, e então dividir os bytes pelo espaco de disco, se 
consegue saber quantas vezes um determinado bloco consegue aceitar escritas 
antes de estourar.

Depois o cara cria o swap 2x o tamanho da ram e passa a hibernar a máquina no 
trajeto pro office e no trajeto pra casa, o que seria uma boa prática. Dois 
hibernates por dia, duas escritas da ram no SSD, no mesmo espaco do swap, vezes 
uns 2 anos fazendo isto e plim, o SSD comeca a ficar lerdo quando se vai 
hibernar (realocando) e uma hora dá zebra. É só fazer os calculos, mas pelos 2 
anos o problema acontece.

Jose Tavares


On Wed, Feb 28, 2024 at 1:44 AM Jose Tavares 
mailto:jaatavar...@gmail.com>> wrote:
Alguns fabricantes de SSD tem produtos muito ruins.

Instala o pacote smartmontools, e usa o smartctl fazendo teste short e long .. 
Quando disparares o teste, verifica quanto tempo irá levar e depois de concluir 
o tempo, com o parâmetro -a consegues ver o resultado.

O smart roda em background, então não afeta a perf da máquina. Lê com atenção 
os resultados.

Uma tool simples que recomendo é o f3.
https://fight-flash-fraud.readthedocs.io/en/latest/introduction.html
Foi escrita por um brasileiro.

Basicamente o que ela faz é escrever padrões em toda a memória flash e depois 
lê e compara os resultados. Com isto, dá para ver se há diferenças na escrita e 
depois leitura, o que indicaria erro no armazenamento. Serve para qualquer tipo 
de armazenamento.

Durante as operações, acompanhe os logs da máquina para ver se acontece resets 
nas controladoras de disco.

Sobre raid1, é uma opção, mas utilize preferivelmente 2 marcas de SSD 
diferentes, para contornar problemas de fabricantes e de modelos específicos. 
Outra opção é usar um SSD e um HDD, e então configurar write-mostly para que 
todas as leituras se dêem somente do SSD e as escritas em ambos para não ter 
perda de performance significativa.

Uma coisa que costumo sempre fazer antes de usar qualquer disco é rodar um dd 
if= of=/dev/null
Desta forma fazendo uma leitura completa do disco antes de começar o seu uso. 
Nisto já se percebe se houver erros. É possível também fazer testes de escrita 
e leitura usando o fsck.ext4 com -cc caso o disco tenha sido configurado com 
ext4.. O comando shred também pode te ajudar fazendo passes no disco e vendo 
resultados.

Mas de todas opções, o f3 me parece o mais fácil e direto para os teus testes, 
e irá acusar problemas se houverem.

Ah, e execute todos os testes antes de colocar o disco em produção.

Espero ter ajudado.
Jose Tavares


On Wed, Feb 28, 2024 at 12:00 AM Yuri Musachio 
mailto:yuri.musac...@gmail.com>> wrote:
MUITO FÁCIL fazer o RAID1 (no Debian)… chega a ser ridículo! PORÉM, existem 
certos “pulo do gato” que eu penei pra encontrar soluções na internet, e que na 
real não encontrei solução pro meu problema. Eu mesmo “desenvolvi”/descobri uma 
solução. Rs
Outra solução também, bem simples, é deixar o sistema num HD e o /home colocar 
num segundo HD… Simples, fácil e invisível pro cliente, caso dê problema no HD 
do sistema.
Mas se for o caso de não haver um segundo slot de HD, acho que um programa 
(pode ser GUID mesmo) que faça backup num HD externo, pode ser também uma 
alternativa.





Best,

Em 27 de fev. de 2024, à(s) 21:47, Rafael de Almeida 
mailto:rafael.i...@gmail.com>> escreveu:


Cara é surreal o que estou passando aqui em Fortaleza CE , com tanto SSD dando 
problema .
Parece que os bichos são descartáveis e o pior a gente tenta falar para o 
cliente fazer backup e é mesmo que nada .
Peguei a sugestão do Eriberto o qual tenho grande admiração. De aconselhar a 
fazer RAID 1 .( espelhamento )


Rafael de Almeida Matias
Especialista em Segurança da Informação
Tecnólogo em Redes de Computadores
Técnico em Informática
Currículo Lattes: https://goo.gl/RqclG4



Em ter., 27 de fev. de 2024 às 16:47, Leandro Cunha 
mailto:leandrocunha...@gmail.com>> escreveu:
Este é um bom tópico pra se levantar, tendo em vista o aumento em uso de SSD.

Links sobre isso
https://wiki.debian.org/SSDOptimization
https://wiki.debian.org/SSD%20Installation

duvida idioma opera

[Vitor Hugo]

Boa tarde,

Teria como fazer o Opera ficar no idioma português?

Obrigado;

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[Olivier]

# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minim 800x600, current 800x600, maximum 800x600
default connected primary 800x600+0+0 0mm x 0mm
  800x600 75.00'

# xrandr -s 1920*1080
Size 1920*1080 not found in available modes


Est-il possible de "lancer manuellement" la fonction KMS une fois que
l'on a démarré avec i915.modesetting=0 ?

Le mer. 28 févr. 2024 à 18:16, Olivier  a écrit :
>
> dmesg -l err
>
> [0.210659] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
> [0.210667] ACPI Error: Aborting method
> \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
> (20230331/psparse-529)
> [0.210697] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
> [0.210702] ACPI Error: Aborting method
> \_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND)
> (20230331/psparse-529)
> [1.074140] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
> [1.074182] ACPI Error: Aborting method
> \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
> (20230331/psparse-529)
> [1.074236] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
> [1.074266] ACPI Error: Aborting method
> \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
> (20230331/psparse-529)
>
>
> dmesg -l warn
> [0.069946] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
> [0.311681] pnp 00:02: disabling [mem 0xc000-0xcfff]
> because it overlaps :00:02.0 BAR 9 [mem 0x-0xdfff
> 64bit pref]
> [0.708514] hpet_acpi_add: no address or irqs in _CRS
> [0.715962] i8042: PNP: PS/2 appears to have AUX port disabled, if
> this is incorrect please boot with i8042.nopnp
> [0.972498] i2c i2c-0: Systems with more than 4 memory slots not
> supported yet, not instantiating SPD
> [1.081026] usb: port power management may be unreliable
> [1.174989] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is
> disabled. Duplicate IMA measurements will not be recorded in the IMA
> log.
> [3.655595] thermal thermal_zone6: failed to read out thermal zone (-61)
> [4.144718] ext2 filesystem being mounted at /boot supports
> timestamps until 2038-01-19 (0x7fff)
> [5.372381] kauditd_printk_skb: 15 callbacks suppressed
> [   16.139210] systemd[864]: memfd_create() called without MFD_EXEC or
> MFD_NOEXEC_SEAL set
>
> Le mer. 28 févr. 2024 à 18:05, Olivier  a écrit :
> >
> > Par SSH, j'ai:
> > root@foo:~# ps aux|grep -i xorg
> > root 886  0.1  0.4 317152 78152 tty1 Sl+  17:48   0:00
> > /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/116/gdm/Xauthority
> > -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose
> > 3
> > ...
> > root@foo:~# DISPLAY=:0.0 xrandr
> > Authorization required, but no authorization protocol specified
> >
> > Can't open display :0.0
> >
> >
> > Comment résoudre ?
> >
> > Le mer. 28 févr. 2024 à 14:23, Sébastien NOBILI
> >  a écrit :
> > >
> > > Bonjour,
> > >
> > > Le 2024-02-27 18:08, Olivier a écrit :
> > > > Comment utiliser xrandr par SSH ? Faut-il se connecter en tant que
> > > > root ou simple utilisateur ?
> > >
> > > Il faut être connecté avec le compte qui fait tourner la session Xorg
> > > (sinon on peut passer par `xhost` mais c'est à éviter).
> > >
> > > Il faudra aussi déclarer la variable `DISPLAY` :
> > >
> > > ```
> > > export DISPLAY=:0.0
> > > ```
> > >
> > > Sébastien
> > >

Re: where are the crontab files in Trixie?

[Max Nikulin]

On 29/02/2024 00:00, Kamil Jońca wrote:

How precisely linger works? (what it starts? What not etc)
I read about lingering  some time ago, and I have had impression
(wrong?) that it  may conflict with my normal session.


Multiple sessions may be started for a user: DM, ssh, VT logins. I am 
unsure what one you consider as your normal session. These sessions run 
withing single systemd user service.

Re: where are the crontab files in Trixie?

[Kamil Jońca]

Andy Smith  writes:

> Hi,
>
> On Wed, Feb 28, 2024 at 04:47:59PM +0100, Kamil Jońca wrote:
>> Andy Smith  writes:
>> > Once you enable lingering for a user, that user's timers will
>> > trigger all the time.
>> 
>> IIRC lingered user cannot be "normal" with session and so on. Am I
>> wrong? 
>
> How do you mean? On several machines I have linger enabled for my
> main user, and timers run when I am not logged in.

How precisely linger works? (what it starts? What not etc)
I read about lingering  some time ago, and I have had impression
(wrong?) that it  may conflict with my normal session.
KJ

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[Olivier]

dmesg -l err

[0.210659] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[0.210667] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[0.210697] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[0.210702] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[1.074140] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[1.074182] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)
[1.074236] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.UBTC.RUCC], AE_NOT_FOUND (20230331/psargs-330)
[1.074266] ACPI Error: Aborting method
\_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND)
(20230331/psparse-529)


dmesg -l warn
[0.069946] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[0.311681] pnp 00:02: disabling [mem 0xc000-0xcfff]
because it overlaps :00:02.0 BAR 9 [mem 0x-0xdfff
64bit pref]
[0.708514] hpet_acpi_add: no address or irqs in _CRS
[0.715962] i8042: PNP: PS/2 appears to have AUX port disabled, if
this is incorrect please boot with i8042.nopnp
[0.972498] i2c i2c-0: Systems with more than 4 memory slots not
supported yet, not instantiating SPD
[1.081026] usb: port power management may be unreliable
[1.174989] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is
disabled. Duplicate IMA measurements will not be recorded in the IMA
log.
[3.655595] thermal thermal_zone6: failed to read out thermal zone (-61)
[4.144718] ext2 filesystem being mounted at /boot supports
timestamps until 2038-01-19 (0x7fff)
[5.372381] kauditd_printk_skb: 15 callbacks suppressed
[   16.139210] systemd[864]: memfd_create() called without MFD_EXEC or
MFD_NOEXEC_SEAL set

Le mer. 28 févr. 2024 à 18:05, Olivier  a écrit :
>
> Par SSH, j'ai:
> root@foo:~# ps aux|grep -i xorg
> root 886  0.1  0.4 317152 78152 tty1 Sl+  17:48   0:00
> /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/116/gdm/Xauthority
> -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose
> 3
> ...
> root@foo:~# DISPLAY=:0.0 xrandr
> Authorization required, but no authorization protocol specified
>
> Can't open display :0.0
>
>
> Comment résoudre ?
>
> Le mer. 28 févr. 2024 à 14:23, Sébastien NOBILI
>  a écrit :
> >
> > Bonjour,
> >
> > Le 2024-02-27 18:08, Olivier a écrit :
> > > Comment utiliser xrandr par SSH ? Faut-il se connecter en tant que
> > > root ou simple utilisateur ?
> >
> > Il faut être connecté avec le compte qui fait tourner la session Xorg
> > (sinon on peut passer par `xhost` mais c'est à éviter).
> >
> > Il faudra aussi déclarer la variable `DISPLAY` :
> >
> > ```
> > export DISPLAY=:0.0
> > ```
> >
> > Sébastien
> >

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[Olivier]

Par SSH, j'ai:
root@foo:~# ps aux|grep -i xorg
root 886  0.1  0.4 317152 78152 tty1 Sl+  17:48   0:00
/usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/116/gdm/Xauthority
-nolisten tcp -background none -noreset -keeptty -novtswitch -verbose
3
...
root@foo:~# DISPLAY=:0.0 xrandr
Authorization required, but no authorization protocol specified

Can't open display :0.0


Comment résoudre ?

Le mer. 28 févr. 2024 à 14:23, Sébastien NOBILI
 a écrit :
>
> Bonjour,
>
> Le 2024-02-27 18:08, Olivier a écrit :
> > Comment utiliser xrandr par SSH ? Faut-il se connecter en tant que
> > root ou simple utilisateur ?
>
> Il faut être connecté avec le compte qui fait tourner la session Xorg
> (sinon on peut passer par `xhost` mais c'est à éviter).
>
> Il faudra aussi déclarer la variable `DISPLAY` :
>
> ```
> export DISPLAY=:0.0
> ```
>
> Sébastien
>

Re: where are the crontab files in Trixie?

[Andy Smith]

Hi,

On Wed, Feb 28, 2024 at 04:47:59PM +0100, Kamil Jońca wrote:
> Andy Smith  writes:
> > Once you enable lingering for a user, that user's timers will
> > trigger all the time.
> 
> IIRC lingered user cannot be "normal" with session and so on. Am I
> wrong? 

How do you mean? On several machines I have linger enabled for my
main user, and timers run when I am not logged in.

Thanks,
Andy

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

Re: where are the crontab files in Trixie?

[Kamil Jońca]

Andy Smith  writes:

> Hi,
>
> On Wed, Feb 28, 2024 at 05:49:58AM +0100, Kamil Jońca wrote:
>> With cron, regular user can set up his/her jobs wihtout using admin
>> credentials, and these jobs will be triggered regardless of being logged
>> in. Is it possible with systemd timers?
>
> Once you enable lingering for a user, that user's timers will
> trigger all the time.

IIRC lingered user cannot be "normal" with session and so on. Am I
wrong? 

KJ

Re: where are the crontab files in Trixie?

[Nicolas George]

Max Nikulin (12024-02-28):
> I am in doubts if it is a task for cron. Wouldn't udev rules be better?

Or even the good old simple way that still works:

   install modulename command...
   This command instructs modprobe to run your command instead of
   inserting the module in the kernel as normal. The command can be
   any shell command: this allows you to do any kind of complex
   processing you might wish. For example, if the module "fred" works
   better with the module "barney" already installed (but it doesn't
   depend on it, so modprobe won't automatically load it), you could
   say "install fred /sbin/modprobe barney; /sbin/modprobe
   --ignore-install fred", which would do what you wanted. Note the
   --ignore-install, which stops the second modprobe from running the
   same install command again. See also remove below.

Regards,

-- 
  Nicolas George

Re: where are the crontab files in Trixie?

[Max Nikulin]

On 28/02/2024 10:35, David Wright wrote:

In which case, I'd write the remaining cron line as:

   @reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id


I am in doubts if it is a task for cron. Wouldn't udev rules be better?

https://stackoverflow.com/questions/442833/how-to-force-driver-to-device-match-in-linux/52943745#52943745
https://unix.stackexchange.com/questions/67936/attaching-usb-serial-device-with-custom-pid-to-ttyusb0-on-embedded/165845#165845

Moreover, to load and configure modules there are /etc/modprobe.d/ and 
/etc/modules.


If it is a weird device that may appear either as 13b1:0039 (supported 
by brcmfmac accordingly to modinfo) and 13b1:0bdc, may it happen that it 
is possible to use e.g. usb-modeswitch to adjust which way the device 
tries to present itself?

Re: where are the crontab files in Trixie?

[Andy Smith]

Hi,

On Wed, Feb 28, 2024 at 05:49:58AM +0100, Kamil Jońca wrote:
> With cron, regular user can set up his/her jobs wihtout using admin
> credentials, and these jobs will be triggered regardless of being logged
> in. Is it possible with systemd timers?

Once you enable lingering for a user, that user's timers will
trigger all the time.

https://wiki.archlinux.org/title/Systemd/User#Automatic_start-up_of_systemd_user_instances

I haven't yet found anything that I could do with cron that I can't
do with systemd timers, though sometimes the behaviour of cron where
it emails you the output (if any) is very convenient and is tricky
(but not impossible) to replicate with systemd timers.

Thanks,
Andy

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

Re: where are the crontab files in Trixie?

[Andy Smith]

Hello,

On Tue, Feb 27, 2024 at 02:58:13PM -0500, Greg Wooledge wrote:
> I don't foresee real cron going away any time soon.

If you today install bookworm base system and select no packages,
the only reason why you get cron is because logrotate depends upon
it. If you do not need logrotate then you can also remove cron, and
nothing complains.

It seems likely that at some point logrotate will become optional
(because of journald) or that logrotate will get a systemd timer, at
which point cron wouldn't be installed on a base install unless
there is some other package dependency.

On this list we already saw a post from someone who did not have
cron installed. Initially I thought that was a rather bold
modification by their hosting provider, but it turned out that they
really did have no package that depended upon cron.

So as far as Debian is concerned I do see it as fairly inevitable
that cron soon doesn't get installed on many systems and
increasingly becomes a curiosity, but since it will have to stick
around until the last package stops shipping (only) a cron job,
arguably it still remains in the archive for a very long time yet.

Thanks,
Andy

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

Re: which package to file a bug report ?

[Jonathan Dowland]

On Tue Feb 27, 2024 at 7:12 AM GMT, Frank Weißer wrote:
> So we are at my original question: Which package to file a bug report ?

Package "debian-installer", I think; and/or submit an installation report,
which can be done with reportbug against the "installation-report" pseudo
package. See 


-- 
Please do not CC me for listmail.

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

Re: Passer en 1920x1080 une machine démarrant avec i915.modeset=0 ?

[Sébastien NOBILI]

Bonjour,

Le 2024-02-27 18:08, Olivier a écrit :

Comment utiliser xrandr par SSH ? Faut-il se connecter en tant que
root ou simple utilisateur ?


Il faut être connecté avec le compte qui fait tourner la session Xorg
(sinon on peut passer par `xhost` mais c'est à éviter).

Il faudra aussi déclarer la variable `DISPLAY` :

```
export DISPLAY=:0.0
```

Sébastien

Re: How to upgrade the GLIBCXX and GLIBC to the specific version

[Thomas Pircher]

Gremlin wrote:

The new OS called Raspberry Pi OS is a new animal.  The foundation
used raspian and the the Raspberry Pi OS is the foundations, developed
by the foundation.


Yet it is still based on Debian, according to their changelog
https://downloads.raspberrypi.com/raspios_arm64/release_notes.txt

| 2023-10-10:
|  * Based on Debian bookworm release

Resolu: Boot USB Potable Asus K551L

[Informatique BILLARD]

Il y a une autre option dans le boot pour activer le boot usb.

Cordialement

Le 28/02/2024 à 11:43, Informatique BILLARD a écrit :

Bonjour

je souhaite au minimum tester linux en lice sur ce portable et je 
n'arrive pas à sélectionner l'usb comme source de boot.


J'ai pris une version live de Linux Mate basée sur debian LMDE copiée 
sur une clé avec dd ifof


Sur le portable j'ai désactivé SECURE BOOT et activé Launch CSM

Mais dans le  boot option priority je ne vois pas le support USB.

Au redémarrage du PC j'appui sur F2 ce qui me permet de sélectionner 
le point de démarrage et n'apparait que windows ou le DVD.


Merci par avance.

cordialement

François-Marie

Boot USB Potable Asus K551L

[Informatique BILLARD]

Bonjour

je souhaite au minimum tester linux en lice sur ce portable et je 
n'arrive pas à sélectionner l'usb comme source de boot.


J'ai pris une version live de Linux Mate basée sur debian LMDE copiée 
sur une clé avec dd ifof


Sur le portable j'ai désactivé SECURE BOOT et activé Launch CSM

Mais dans le  boot option priority je ne vois pas le support USB.

Au redémarrage du PC j'appui sur F2 ce qui me permet de sélectionner le 
point de démarrage et n'apparait que windows ou le DVD.


Merci par avance.

cordialement

François-Marie

Re: How to upgrade the GLIBCXX and GLIBC to the specific version

[debian-user]

Gremlin  wrote:
> On 2/27/24 16:08, debian-u...@howorth.org.uk wrote:
> > Gremlin  wrote:
> >   
> >> The provider is raspberry foundation and Raspian has been
> >> dis-continued.  

> Nope that is just wrong.
> 
> https://www.raspbian.org/
[snip]
> Note: Raspbian is not affiliated with the Raspberry Pi Foundation.

[OT] VMware vende su negocio enfocado a usaurios finales

[Camaleón]

Hola,

Pues eso, ojo avizor quienes uséis productos de VMware que Broadcom 
está empezando a hacer caja «soltando lastre»:

Broadcom Sells VMware's End-User Computing Division for $4bn
https://news.itsfoss.com/broadcom-vmware-euc/

KKR comprará la unidad de informática de usuario final de Broadcom por 4.000 
millones de dólares 
https://es.investing.com/news/stock-market-news/kkr-comprara-la-unidad-de-informatica-de-usuario-final-de-broadcom-por-4000-millones-de-dolares-93CH-2581920

Saludos,

-- 
Camaleón