Re: CVE-2022-27385 - Vendor Dependency Check In

[tomas]

On Tue, Aug 01, 2023 at 09:45:59PM +, Julius Ross (juliross) wrote:
> Hi team,

We are not a "team" -- we are Debian users, as the mailing
list name suggests. That said...

> We're looking for a contact or direction on gaining updates on open 
> vulnerabilities relating to known CVEs. Can you point us to the correct forum 
> or support email address? We want to be able to track these vulnerabilities 
> and when fixes become available.

... Debian does (almost) everything in the open, so the first
(non-advert) two hits in my favourite search engine (no, not
that one with the G) for the terms "debian cve vulnerabilities"
lead to:

  https://security-tracker.debian.org/tracker/
  https://www.debian.org/security/cve-compatibility

which is probably more or less what you are looking for.

Apart from that, there are (at least) two security related
mailing lists, whose subscribe pages you'll find here:

  https://lists.debian.org/debian-security/
  https://lists.debian.org/debian-security-announce/

of which the second one might be of interest to you.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Debian 30 anos! 14 a 18 de agosto de 2023

[Lucas Castro]

Em 01/08/2023 22:34, Paulo Henrique de Lima Santana escreveu:



Em 01/08/2023 21:23, Lucas Castro escreveu:

Porque não tentamos transmitir pelo peertube?
Ou configurar um servidor com rtmp?

Converso que estou bem desmotivado com diversos eventos de "software 
livre" que estão ocorrendo apenas em plataformas não livres(opinião).


Acredito que até o dia do evento daria pra testar o ambiente em 
alguma outra plataforma.


Infelizmente nenhuma platatorma livre oferece ainda a mesma 
possibildiade de intereação ao vivo como o Youtube.


Compreendido.




Mas sempre após os eventos, nós disponibilizamos as gravações no 
peertube do Debian.

https://peertube.debian.social/a/debianbrazilteam/videos?s=1


Sim, verdade.

Abraços,



OpenPGP_signature
Description: OpenPGP digital signature

Re: Recommendations for a UPS?

[Karl Vogel]

>> On Tue, 01 Aug 2023 03:47:28 -0400,
>> David  may have said:

> What everybody seems to be doing is catering to surge, when a low
> spike can do just as much damage.  Both need to be protected against,
> so any protective appliance selection has to consider that.

  Liebert protects against power surges, brownouts, blackouts or drops
  in voltage.  That's why they're a little more expensive.

--
Karl Vogel / vogelke AT pobox DOT com / I don't speak for anyone at the moment

Skills-wise they suck harder than a black hole with daddy issues.
--Review of Accenture Senior Management

Re: Debian versions

[Paul Wise]

On Tue, 2023-08-01 at 13:50 -0600, Alan Serrano Peña wrote:

> Is there a commercial version of Debian?
> Any version with technical support? 

The Debian project provides the Debian operating system for free and
provides technical support for free by volunteers. In addition, there
are a number of people and companies providing paid support for Debian.

https://www.debian.org/support
https://www.debian.org/consultants/
https://lists.debian.org/debian-consultants/

Outside Debian there are companies producing operating systems based on
Debian and providing commercial support for those operating systems,
probably the biggest example is Ubuntu provided by Canonical:

https://ubuntu.com/
https://canonical.com/

> I was reading on the website that there is a version called Debian
> LTS, specifically Debian 10 "Buster," but I'm not sure if this
> version meets what I'm asking for. I hope you can help me or even
> explain a little more about LTS and the "Buster" version.

Debian releases have normal security support for one year after the
following release and releases occur approximately every two years, so
Debian releases have approximately three years of security support. The
Debian LTS effort aims to extend the security support available to each
Debian release to at least 5 years. The LTS project is done using
funding contributed by the Freexian company, but their efforts are
distributed for free. Outside of Debian, Freexian extends security
support for Debian releases to up to 10 years. The ELTS results are
distributed for free, but only customers can choose what is supported.

https://wiki.debian.org/LTS
https://wiki.debian.org/LTS/Funding
https://wiki.debian.org/LTS/Extended

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Debian 30 anos! 14 a 18 de agosto de 2023

[Paulo Henrique de Lima Santana]

Em 01/08/2023 21:23, Lucas Castro escreveu:

Porque não tentamos transmitir pelo peertube?
Ou configurar um servidor com rtmp?

Converso que estou bem desmotivado com diversos eventos de "software 
livre" que estão ocorrendo apenas em plataformas não livres(opinião).


Acredito que até o dia do evento daria pra testar o ambiente em alguma 
outra plataforma.


Infelizmente nenhuma platatorma livre oferece ainda a mesma 
possibildiade de intereação ao vivo como o Youtube.


Mas sempre após os eventos, nós disponibilizamos as gravações no 
peertube do Debian.

https://peertube.debian.social/a/debianbrazilteam/videos?s=1

Abraços,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


OpenPGP_signature
Description: OpenPGP digital signature

Re: AMD GPU hard lockups

[Celejar]

On Tue, 1 Aug 2023 19:13:42 +0100
piorunz  wrote:

> On 01/08/2023 19:09, Celejar wrote:
> > Okay, thanks for the clarification. It seems, however, that I'm dealing
> > with a hardware issue (as Dan Ritter suggested): I did some more
> > testing, and after the latest crash, the system won't boot at all, and
> > the power LED blinks red six times, which according to the
> > manufacturer "indicates a pre-video graphic card error."
> >
> > "To resolve the issue, complete the following steps:
> >
> > 1) Reseat the graphics card.
> >
> > 2) Replace the graphic card.
> >
> > 3) Replace the system board."
> >
> > https://support.hp.com/gb-en/document/c03599666
> >
> > I suppose I'll begin by trying the first and see if it helps ...
> 
> Oh, that's more serious then. Could be power supply as well. Good luck
> troubleshooting it.

So, while troubleshooting today I thought I smelled an ominously acrid
odor of burning plastic. I wasn't sure whether it was real or a figment
of my stressed imagination, but when I opened the case, sure enough, the
cable feeding the GPU had burned and broken.

Fortunately, I don't see damage to the system's power cable or to the
GPU itself, just to the 6 pin to 8 pin PCIE adapter cable (the HP PSU
has only 6 pin cables, and the GPU needs an 8 pin connection). I
remember debating at the time (3 years ago) whether to buy the cheapest
one I could find, or to invest a few dollars more to buy a brand name
unit from a reputable company. I rolled the dice on the former, and it
did last three years - and hopefully didn't take out anything else with
it.

I'm going to order another one, from a reputable company this time, and
hope that it was just the cheapo implementation that was flawed, and
not the whole concept of 6 pin to 8 pin adapter cables ...

-- 
Celejar

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le mardi 01 août 2023 à 23:36 +0200, Gaëtan Perrier a écrit :
> Le lundi 31 juillet 2023 à 12:49 +0200, Gaëtan Perrier a écrit :
> > Le lundi 31 juillet 2023 à 12:42 +0200, Gaëtan Perrier a écrit :
> > > Pour l'instant ça semble tourner. Reste à voir si j'ai toujours des
> > > freeze
> > > ou
> > > pas ...
> > > 
> > 
> > Pas eu besoin d'attendre longtemps :(
> > Freeze juste après l'envoi du message précédent.
> > 
> > Rien dans /var/log/syslog à part une série de ^@
> > 
> > Gaëtan
> > 
> 
> Concernant les freeze j'ai avancé.
> Ce soir pendant le freeze je me suis connecté en ssh depuis une autre machine
> et c'est gnome-shell qui freeze en consommant 100% d'un cœur. Mais les fois
> d'avant je n'avais pas été assez patient parce que là en attendant je me suis
> aperçu que ça defreeze !
> Et dans journalctl j'ai cette trace qui est apparue à ce moment là:
> 
> geoclue[46380]: Service not used for 60 seconds. Shutting down..
> systemd[1]: geoclue.service: Deactivated successfully.
> 
> Et 60 s ce n'est pas impossible que ce soit la durée du freeze ...
> 
> Gaëtan

Bon en fait ce n'était pas un vrai freeze.
Je viens d'en avoir un et là y a des logs correspondant mais que je ne sais pas
interpréter:



août 02 01:07:39 reveillon kernel: INFO: task kworker/0:1H:26028 blocked for
more than 120 seconds.
août 02 01:07:39 reveillon kernel:   Tainted: G   OE  6.4.0-1-
amd64 #1 Debian 6.4.4-1
août 02 01:07:39 reveillon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
août 02 01:07:39 reveillon kernel: task:kworker/0:1H    state:D stack:0    
pid:26028 ppid:2  flags:0x4000
août 02 01:07:39 reveillon kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm]
août 02 01:07:39 reveillon kernel: Call Trace:
août 02 01:07:39 reveillon kernel:  
août 02 01:07:39 reveillon kernel:  __schedule+0x3df/0xb80
août 02 01:07:39 reveillon kernel:  schedule+0x61/0xe0
août 02 01:07:39 reveillon kernel:  schedule_timeout+0x151/0x160
août 02 01:07:39 reveillon kernel:  dma_fence_default_wait+0x22a/0x280
août 02 01:07:39 reveillon kernel:  ? __pfx_dma_fence_default_wait_cb+0x10/0x10
août 02 01:07:39 reveillon kernel:  dma_fence_wait_timeout+0x10c/0x130
août 02 01:07:39 reveillon kernel:  dma_resv_wait_timeout+0x7f/0xe0
août 02 01:07:39 reveillon kernel:  ttm_bo_delayed_delete+0x2a/0x80 [ttm]
août 02 01:07:39 reveillon kernel:  process_one_work+0x1c7/0x3d0
août 02 01:07:39 reveillon kernel:  worker_thread+0x51/0x390
août 02 01:07:39 reveillon kernel:  ? __pfx_worker_thread+0x10/0x10
août 02 01:07:39 reveillon kernel:  kthread+0xf7/0x130
août 02 01:07:39 reveillon kernel:  ? __pfx_kthread+0x10/0x10
août 02 01:07:39 reveillon kernel:  ret_from_fork+0x2c/0x50
août 02 01:07:39 reveillon kernel:  
août 02 01:07:39 reveillon kernel: INFO: task kworker/0:2H:26029 blocked for
more than 120 seconds.
août 02 01:07:39 reveillon kernel:   Tainted: G   OE  6.4.0-1-
amd64 #1 Debian 6.4.4-1
août 02 01:07:39 reveillon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
août 02 01:07:39 reveillon kernel: task:kworker/0:2H    state:D stack:0    
pid:26029 ppid:2  flags:0x4000
août 02 01:07:39 reveillon kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm]
août 02 01:07:39 reveillon kernel: Call Trace:
août 02 01:07:39 reveillon kernel:  
août 02 01:07:39 reveillon kernel:  __schedule+0x3df/0xb80
août 02 01:07:39 reveillon kernel:  schedule+0x61/0xe0
août 02 01:07:39 reveillon kernel:  schedule_timeout+0x151/0x160
août 02 01:07:39 reveillon kernel:  dma_fence_default_wait+0x22a/0x280
août 02 01:07:39 reveillon kernel:  ? __pfx_dma_fence_default_wait_cb+0x10/0x10
août 02 01:07:39 reveillon kernel:  dma_fence_wait_timeout+0x10c/0x130
août 02 01:07:39 reveillon kernel:  dma_resv_wait_timeout+0x7f/0xe0
août 02 01:07:39 reveillon kernel:  ttm_bo_delayed_delete+0x2a/0x80 [ttm]
août 02 01:07:39 reveillon kernel:  process_one_work+0x1c7/0x3d0
août 02 01:07:39 reveillon kernel:  worker_thread+0x51/0x390
août 02 01:07:39 reveillon kernel:  ? __pfx_worker_thread+0x10/0x10
août 02 01:07:39 reveillon kernel:  kthread+0xf7/0x130
août 02 01:07:39 reveillon kernel:  ? __pfx_kthread+0x10/0x10
août 02 01:07:39 reveillon kernel:  ret_from_fork+0x2c/0x50
août 02 01:07:39 reveillon kernel:  
août 02 01:07:39 reveillon kernel: INFO: task kworker/u8:0:26079 blocked for
more than 120 seconds.
août 02 01:07:39 reveillon kernel:   Tainted: G   OE  6.4.0-1-
amd64 #1 Debian 6.4.4-1
août 02 01:07:39 reveillon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
août 02 01:07:39 reveillon kernel: task:kworker/u8:0    state:D stack:0    
pid:26079 ppid:2  flags:0x4000
août 02 01:07:39 reveillon kernel: Workqueue: events_unbound
nv50_disp_atomic_commit_work [nouveau]
août 02 01:07:39 reveillon kernel: Call Trace:
août 02 01:07:39 reveillon kernel:  
août 02 01:07:39 reveillon kernel:  __schedule+0x3df/0xb80
août 02 01:07:39 reveillon 

Re: Debian 30 anos! 14 a 18 de agosto de 2023

[Lucas Castro]

Porque não tentamos transmitir pelo peertube?
Ou configurar um servidor com rtmp?

Converso que estou bem desmotivado com diversos eventos de "software livre" que 
estão ocorrendo apenas em plataformas não livres(opinião). 

Acredito que até o dia do evento daria pra testar o ambiente em alguma outra 
plataforma. 

Em 1 de agosto de 2023 21:11:09 BRT, Paulo Henrique de Lima Santana 
 escreveu:
>Olá pessoal,
>
>Todos os anos no dia 16 de agosto (ou no sábado mais próximo) comunidades ao 
>redor do mundo organizam nas suas cidades o Debian Day com o objetivo de 
>celebar o aniversário do Debian, sendo um dia totalmente dedicado a divulgação 
>e contribuições ao Projeto.
>
>Mas em 2023 o Projeto Debian completerá 30 anos!
>
>Para celebrar esta data especial, a comunidade Debian Brasil realizará não 
>apenas um dia de atividades, e sim uma semana inteira de palestras online com 
>pessoas que contribuem para o Debian :-)
>
>O evento chamado de "Debian 30 anos" acontecerá de 14 a 18 de agosto (segunda 
>a sexta) das 19h às 22h, com transmissão pelo nosso canal do YouTube:
>https://www.youtube.com/DebianBrasilOficial
>
>Para ver a programação completa do evento, acesse:
>https://deb.li/30anos
>
>Ah, e várias comunidades realizarão atividades nos dias próximos a 16 de 
>agosto. Para ver o que as outras cidades estão programando, acesse:
>https://wiki.debian.org/DebianDay/2023
>
>Abraços,
>
>-- 
>Paulo Henrique de Lima Santana (phls)
>Belo Horizonte - Brasil
>Debian Developer
>Site: http://phls.com.br
>GPG ID: 0443C450

Debian 30 anos! 14 a 18 de agosto de 2023

[Paulo Henrique de Lima Santana]

Olá pessoal,

Todos os anos no dia 16 de agosto (ou no sábado mais próximo) 
comunidades ao redor do mundo organizam nas suas cidades o Debian Day 
com o objetivo de celebar o aniversário do Debian, sendo um dia 
totalmente dedicado a divulgação e contribuições ao Projeto.


Mas em 2023 o Projeto Debian completerá 30 anos!

Para celebrar esta data especial, a comunidade Debian Brasil realizará 
não apenas um dia de atividades, e sim uma semana inteira de palestras 
online com pessoas que contribuem para o Debian :-)


O evento chamado de "Debian 30 anos" acontecerá de 14 a 18 de agosto 
(segunda a sexta) das 19h às 22h, com transmissão pelo nosso canal do 
YouTube:

https://www.youtube.com/DebianBrasilOficial

Para ver a programação completa do evento, acesse:
https://deb.li/30anos

Ah, e várias comunidades realizarão atividades nos dias próximos a 16 de 
agosto. Para ver o que as outras cidades estão programando, acesse:

https://wiki.debian.org/DebianDay/2023

Abraços,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


OpenPGP_signature
Description: OpenPGP digital signature

Re: OT: Protecting electrical equipment; was: Recommendations for a UPS?

[Nicholas Geovanis]

On Tue, Aug 1, 2023, 1:09 PM gene heskett  wrote:

> On 8/1/23 11:03, Nicholas Geovanis wrote:
> > On Tue, Aug 1, 2023, 2:40 AM Michael Kjörling <2695bd53d...@ewoof.net
> > > wrote:
> >
> > On 31 Jul 2023 15:21 -0400, from songb...@anthive.com
> >  (songbird):
> >  >   i do not run things for long when the power goes out
> >  > but the capacity for my needs is plenty and then i shut
> >  > down in an orderly fashion.  most of the time i shut down
> >  > the computer system and unplug the power cord and the
> >  > network cables and antenna cables if there is a storm
> >  > coming through - just out of the idea that i don't really
> >  > want things to get fried.
> >
> I replaced the original 60 amp service in 2008 with a 200, and brought
> this grandfathered 2970 house service up to code, doing all the internal
> work myself. I have a big ups running everything but the lights and
> printers in this room, got rid of the copper telephone because the cable
> was 70 years old, 50 pair paper insulated cable they would not keep
> working for a week at a time, so after 5 months of that I voted with my
> wallet and hooked all that up to the cable system. I must have done
> something right, I have not even blown a ccfl light bulb since and it
> all runs 24/7/365.25.


In your case then, you may need to pay attention to transients in your
cabling plant. Everytime a large motor starts, revs or stops, those
transients are hitting your cabling. My recollection is that you have
machine tools in addition to electronics and climate control. Even more so
then. Also grounding for your electrical system has to be proven
over-adequate. And any possible ground-loops need to be found and
remediated.


> It's worth mentioning that with a good UPS you get power-conditioning,
> > not just filtering and over/under-voltage protection. That can extend
> > the lifetime of any electric motor or other device using the conditioned
> > power. The UPS emits a controlled waveform beyond what your utility can
> > provide.
> >
> > And numerous datacenters have begun using DC-powered racks. Less power
> > loss in the individual transformers and motors in each racked server,
> > less heat to be expelled.
>
>

CVE-2022-27385 - Vendor Dependency Check In

[Julius Ross (juliross)]

Hi team,

We're looking for a contact or direction on gaining updates on open 
vulnerabilities relating to known CVEs. Can you point us to the correct forum 
or support email address? We want to be able to track these vulnerabilities and 
when fixes become available.
Thank you in advance for your assistance with this request.

Best,

Julius Ross
Security Engineer - Vulnerability Management | NY
julir...@cisco.com | M: 917.780.9334

[signature_3011522949]

Re: Debian versions

[Danial Behzadi]

Good afternoon, I have a question about Debian versions. Is there a 
commercial version of Debian? Any version with technical support?
No, Debian is a free software, but you can get commercial support from 
third-parties.


I was reading on the website that there is a version called Debian 
LTS, specifically Debian 10 "Buster," but I'm not sure if this 
version meets what I'm asking for. I hope you can help me or even 
explain a little more about LTS and the "Buster" version.

LTS is just the old-stable release with security repos.

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le lundi 31 juillet 2023 à 12:49 +0200, Gaëtan Perrier a écrit :
> Le lundi 31 juillet 2023 à 12:42 +0200, Gaëtan Perrier a écrit :
> > Pour l'instant ça semble tourner. Reste à voir si j'ai toujours des freeze
> > ou
> > pas ...
> > 
> 
> Pas eu besoin d'attendre longtemps :(
> Freeze juste après l'envoi du message précédent.
> 
> Rien dans /var/log/syslog à part une série de ^@
> 
> Gaëtan
> 

Concernant les freeze j'ai avancé.
Ce soir pendant le freeze je me suis connecté en ssh depuis une autre machine
et c'est gnome-shell qui freeze en consommant 100% d'un cœur. Mais les fois
d'avant je n'avais pas été assez patient parce que là en attendant je me suis
aperçu que ça defreeze !
Et dans journalctl j'ai cette trace qui est apparue à ce moment là:

geoclue[46380]: Service not used for 60 seconds. Shutting down..
systemd[1]: geoclue.service: Deactivated successfully.

Et 60 s ce n'est pas impossible que ce soit la durée du freeze ...

Gaëtan




signature.asc
Description: This is a digitally signed message part

Re: Recommendations for a UPS?

[Tom Browder]

On Tue, Aug 1, 2023 at 15:19 Roy J. Tellason, Sr.  wrote:

> On Monday 31 July 2023 07:47:14 pm Charles Curley wrote:
> > Replacement batteries from APC are expensive compared to buying
> > elsewhere, but they come with return shipping for the exhausted battery
> > so they can recycle it.


Roy, and many others, thank you for a voluminious set of helpful and timely
responses. I need to assemble a spreadsheet to evaluate it all.

I'm sure I have enough to make an informed decision.

Blessiing to all my Debian friends!

-Tom

Re: Debian versions

[Timothy M Butterworth]

On Tue, Aug 1, 2023 at 4:15 PM Alan Serrano Peña  wrote:

> Good afternoon, I have a question about Debian versions. Is there a
> commercial version of Debian? Any version with technical support? I was
> reading on the website that there is a version called Debian LTS,
> specifically Debian 10 "Buster," but I'm not sure if this version meets
> what I'm asking for. I hope you can help me or even explain a little more
> about LTS and the "Buster" version.
>
> I hope you can assist me as I don't have much knowledge about this
> operating system
>

LTS: All Debian releases are LTS. If you are doing a new install it is
better to install the latest version of Debian which is Bookworm.

You can purchase support for Debian from a Debian Partner
https://www.debian.org/partners/ or a Debian Consultant:
https://www.debian.org/consultants/


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Plantage suite à ajout de desktop icon dans /usr/share/applications/

[RogerT]

> Le 1 août 2023 à 20:53, didier gaumet  a écrit :
> 
> Le 01/08/2023 à 17:39, RogerT a écrit :
>> En résumé de mon précédent long exposé :
>> 1/ avec debian 11 (gnome) :
>> Quel est la manière usuelle (en CLI et via le GUI) de créer une desktop icon 
>> et de la déployer à partir du fichier exécutable ?
>> (En CLI, j’ai trouvé desktop-file-utils mais trouvé aucun moyen via le GUI)
>> Est-ce différent avec d’autres DE ?
> 
> GUI: pure supposition, comme c'est un boulot de fin de développement d'appli, 
> un IDE permettrait peut-être de le faire?

Un IDE ?
Alors, soit c’est un simple éditeur de texte. 
Soit il appelle des commandes comme celles du paquet desktop-file-utils que je 
viens de découvrir pour faciliter leur mise en oeuvre ?

Sur ton/vos DE gnome ou KDE ou Trinity, y a-t-il un menu contextuel pour 
transformer un exécutable en fichier .desktop via une panneau de configuration 
et la déployer sur le système ?

Re: gnome-shell erreur JSON (était Re: [testing] passage du pilote proprio à nouveau)

[Gaëtan Perrier]

Le mardi 01 août 2023 à 22:02 +0200, didier gaumet a écrit :
> Le 01/08/2023 à 21:27, Gaëtan Perrier a écrit :
> 
> > Probablement lié à un problème avec openvpn:
> [...]
> > ovpn-update-systemd-resolved[14381]: Options error: You must define TUN/TAP
> > device (--dev)
> [...]
> > unexpected end of data at line 1 column 1 of the JSON data
> > gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
> > unexpected end of data at line 1 column 1 of the JSON data
> 
> Ce n'est qu'une impression mais l'erreur openvpn ne me semble pas liée à 
> l'erreur gnome-shell (je peux me tromper)
> 
> de toute façon, tu peux essayer de solutionner le pb openvpn eb 
> paramétrant le périphérique TUN/TAP, si tu as de la chance ça résoudra 
> aussi le pb gnome-shell
> 

J'aimerai bien mais je n'ai pas trouvé de conf où il manque de tun/tap ...

Gaêtan


signature.asc
Description: This is a digitally signed message part

Re: singularity-container in bookworm?

[Nilesh Patra]

Hi Boyan,

On Tue, Aug 01, 2023 at 01:08:40PM -0400, Boyan Penkov wrote:
> Hello Nilesh,
> 
> Thanks kindly -- I do see it, and it's playing along wonderfully with
> the rest of bookworm on my systems...

Happy to know. I just uploaded a new version (3.11.4) of singularity to
fasttrack, this one has some new features too.
Would you consider to try it?

Best,
Nilesh


signature.asc
Description: PGP signature

Re: chrome web browser worthless

[Roy J. Tellason, Sr.]

On Tuesday 01 August 2023 05:33:55 am gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a browser 
> to run klipper as a google search intercepts port 80, so localhost:80 
> cannot be used for troubleshooting or for running a 3d printer with 
> klipper..
> 
> FF has no such problems.
> 
> Cheers, Gene Heskett.

I would never consider using chrome,  what with all of the "phone home" 
nonsense that's in it.  Chromium is supposed to be an open-source (?) variant 
of that without all of that stuff included.  You might consider giving that a 
try.

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: Recommendations for a UPS?

[Roy J. Tellason, Sr.]

On Monday 31 July 2023 07:47:14 pm Charles Curley wrote:
> Replacement batteries from APC are expensive compared to buying
> elsewhere, but they come with return shipping for the exhausted battery
> so they can recycle it.
 
OTOH local recycling places give me cash for exhausted lead-acid batteries...


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Debian versions

[Alan Serrano Peña]

Good afternoon, I have a question about Debian versions. Is there a commercial 
version of Debian? Any version with technical support? I was reading on the 
website that there is a version called Debian LTS, specifically Debian 10 
"Buster," but I'm not sure if this version meets what I'm asking for. I hope 
you can help me or even explain a little more about LTS and the "Buster" 
version.
 
I hope you can assist me as I don't have much knowledge about this operating 
system
 

Re: gnome-shell erreur JSON (était Re: [testing] passage du pilote proprio à nouveau)

[didier gaumet]

Le 01/08/2023 à 21:27, Gaëtan Perrier a écrit :


Probablement lié à un problème avec openvpn:

[...]

ovpn-update-systemd-resolved[14381]: Options error: You must define TUN/TAP
device (--dev)

[...]

unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data


Ce n'est qu'une impression mais l'erreur openvpn ne me semble pas liée à 
l'erreur gnome-shell (je peux me tromper)


de toute façon, tu peux essayer de solutionner le pb openvpn eb 
paramétrant le périphérique TUN/TAP, si tu as de la chance ça résoudra 
aussi le pb gnome-shell

Re: Prevent laptop from suspending when a user is logged in through SSH

[Michael Kjörling]

On 1 Aug 2023 21:30 +0200, from pipat...@gmail.com (Anders Andersson):
> Does anyone know the "correct" solution to this?

Might https://wiki.debian.org/Suspend#Systemd_timeouts be useful?

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: les adresses d'expéditeur dans thunderbird

[hamster]

Le 01/08/2023 à 21:11, didier gaumet a écrit :

Le 01/08/2023 à 17:53, hamster a écrit :

Le 01/08/2023 à 17:09, Erwann Le Bras a écrit :

[...]
J'aimerais pouvoir renseigner dans le carnet d'adresse, pour chaque 
destinataire, avec quelle adresse d'expéditeur je veux lui écrire.



quand je crée un mél, je tape le nom de l'expéditeur


C'est précisément ce point la que j'aimerais automatiser. Ne pas avoir 
a taper l'éxpéditeur, qu'il soit rempli automatiquement en fonction du 
destinataire que je met.
(j'ai pas testé) il y a une extension Thunderbird "Identités multiples" 
qui a l'air de faire ce que tu souhaites:

https://addons.thunderbird.net/fr/thunderbird/addon/flexible-identity/?src=search


En effet, ca a l'air d'etre exactement ce que je veux. J'avais déjà fait 
une recherche dans les extensions, mais visiblement j'avais mal cherché 
et j'etais passé a coté de celle ca.


Merci beaucoup.

Prevent laptop from suspending when a user is logged in through SSH

[Anders Andersson]

I just installed a plain debian 12.1 on my good old Thinkpad X200, my
first debian 12 install since I'm waiting for things to settle down
before I upgrade my other computers.

Going smooth so far and my first snag (after bug #1037304) is that it
just kicked me out of all my ssh sessions. Example from an active git
command that was aborted:

remote: Enumerating objects: 6944, done.
remote: Counting objects: 100% (6944/6944), done.
remote: Compressing objects:  73% (2131/2919)
Broadcast message from pipe@airwaves (Tue 2023-08-01 21:04:47 CEST):

The system will suspend now!

Timeout, server airwaves.computerwelt not responding.

At the time the laptop was on AC power and I was logged in as the
primary user in the default gnome session, but the laptop was sitting
idle except for my SSH sessions - all mostly active with aptitude, git
commands, text editing etc.

Does anyone know the "correct" solution to this? There's no difference
in activity for me hacking away in a terminal over SSH compared to a
terminal in a window on the laptop itself, so why isn't it registered
as "activity" for the automatic suspension?

gnome-shell erreur JSON (était Re: [testing] passage du pilote proprio à nouveau)

[Gaëtan Perrier]

Le mardi 01 août 2023 à 13:55 +0200, didier gaumet a écrit :
> Le 01/08/2023 à 13:52, didier gaumet a écrit :
> 
> > apparemment (vu que JSON et moi ça fait deux) ce pourrait être un 
> > argument vide passé en paramètre qui déclencherait cette erreur. Regarde 
> > éventuellement dans les lignes précédentes si tu vois où / dans quoi ça 
> > a lieu (plus précisément que gnome-shell)
> 
> j'ai oublié de précisé que je n'avais pas ce genre d'erreur renvoyé par 
> journalctl
> 
> 

Probablement lié à un problème avec openvpn:

systemd[1]: openvpn@update-systemd-resolved.service: Scheduled restart job,
restart counter is at 226.
systemd[1]: Stopped openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved.
systemd[1]: Starting openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved...
ovpn-update-systemd-resolved[14381]: Options error: You must define TUN/TAP
device (--dev)
systemd[1]: openvpn@update-systemd-resolved.service: Main process exited,
code=exited, status=1/FAILURE
ovpn-update-systemd-resolved[14381]: Use --help for more information.
systemd[1]: openvpn@update-systemd-resolved.service: Failed with result 'exit-
code'.
systemd[1]: Failed to start openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved.
systemd[1]: openvpn@update-systemd-resolved.service: Scheduled restart job,
restart counter is at 227.
systemd[1]: Stopped openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved.
systemd[1]: Starting openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved...
ovpn-update-systemd-resolved[14404]: Options error: You must define TUN/TAP
device (--dev)
ovpn-update-systemd-resolved[14404]: Use --help for more information.
systemd[1]: openvpn@update-systemd-resolved.service: Main process exited,
code=exited, status=1/FAILURE
systemd[1]: openvpn@update-systemd-resolved.service: Failed with result 'exit-
code'.
systemd[1]: Failed to start openvpn@update-systemd-resolved.service - OpenVPN
connection to update-systemd-resolved.
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data
gnome-shell[11345]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data


Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: les adresses d'expéditeur dans thunderbird

[didier gaumet]

Le 01/08/2023 à 17:53, hamster a écrit :

Le 01/08/2023 à 17:09, Erwann Le Bras a écrit :

[...]
J'aimerais pouvoir renseigner dans le carnet d'adresse, pour chaque 
destinataire, avec quelle adresse d'expéditeur je veux lui écrire.



quand je crée un mél, je tape le nom de l'expéditeur


C'est précisément ce point la que j'aimerais automatiser. Ne pas avoir a 
taper l'éxpéditeur, qu'il soit rempli automatiquement en fonction du 
destinataire que je met.
(j'ai pas testé) il y a une extension Thunderbird "Identités multiples" 
qui a l'air de faire ce que tu souhaites:

https://addons.thunderbird.net/fr/thunderbird/addon/flexible-identity/?src=search

Re: Plantage suite à ajout de desktop icon dans /usr/share/applications/

[didier gaumet]

Le 01/08/2023 à 17:39, RogerT a écrit :

En résumé de mon précédent long exposé :

1/ avec debian 11 (gnome) :
Quel est la manière usuelle (en CLI et via le GUI) de créer une desktop 
icon et de la déployer à partir du fichier exécutable ?

(En CLI, j’ai trouvé desktop-file-utils mais trouvé aucun moyen via le GUI)
Est-ce différent avec d’autres DE ?


GUI: pure supposition, comme c'est un boulot de fin de développement 
d'appli, un IDE permettrait peut-être de le faire?

Re: AMD GPU hard lockups

[piorunz]

On 01/08/2023 19:09, Celejar wrote:

Okay, thanks for the clarification. It seems, however, that I'm dealing
with a hardware issue (as Dan Ritter suggested): I did some more
testing, and after the latest crash, the system won't boot at all, and
the power LED blinks red six times, which according to the
manufacturer "indicates a pre-video graphic card error."

"To resolve the issue, complete the following steps:

1) Reseat the graphics card.

2) Replace the graphic card.

3) Replace the system board."

https://support.hp.com/gb-en/document/c03599666

I suppose I'll begin by trying the first and see if it helps ...


Oh, that's more serious then. Could be power supply as well. Good luck
troubleshooting it.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: AMD GPU hard lockups

[Celejar]

On Tue, 1 Aug 2023 18:25:39 +0100
piorunz  wrote:

> On 01/08/2023 18:16, Celejar wrote:
> > On Tue, 1 Aug 2023 16:56:37 +0100
> > piorunz  wrote:
> >
> >> On 01/08/2023 16:44, Celejar wrote:
> >>
> >>> Any ideas?
> >>>
> >> Revert to Debian Stable and check there. I have AMD Radeon card and it's
> >> 100% stable on Stable, and it had issues last year back when bookworm
> >> was in Testing.
> >
> > I'm confused - current stable *is* bookworm, so if you had issues with
> > bookworm, why would reverting to (current) stable help? Do you mean
> > oldstable / bullseye? I actually did test using kernel 6.1.0-10-amd64
> > from stable / bookworm, but the problem remained.
> >
> 
> I had problems with Testing when it was maturing to become Stable /
> Bookworm. Meaning, pre-release Bookworm, it has problems. So there is that.
> You are using Sid, so problems are to be expected.
> 
> Revert to Stable / Bookworm, which is very stable for me, all problems
> which it has last year (while Bookworm was Testing) have been fixed. I
> did not have single crash or freeze for months.

Okay, thanks for the clarification. It seems, however, that I'm dealing
with a hardware issue (as Dan Ritter suggested): I did some more
testing, and after the latest crash, the system won't boot at all, and
the power LED blinks red six times, which according to the
manufacturer "indicates a pre-video graphic card error."

"To resolve the issue, complete the following steps:

1) Reseat the graphics card.

2) Replace the graphic card.

3) Replace the system board."

https://support.hp.com/gb-en/document/c03599666

I suppose I'll begin by trying the first and see if it helps ...

-- 
Celejar

Re: OT: Protecting electrical equipment; was: Recommendations for a UPS?

[gene heskett]

On 8/1/23 11:03, Nicholas Geovanis wrote:
On Tue, Aug 1, 2023, 2:40 AM Michael Kjörling <2695bd53d...@ewoof.net 
> wrote:


On 31 Jul 2023 15:21 -0400, from songb...@anthive.com
 (songbird):
 >   i do not run things for long when the power goes out
 > but the capacity for my needs is plenty and then i shut
 > down in an orderly fashion.  most of the time i shut down
 > the computer system and unplug the power cord and the
 > network cables and antenna cables if there is a storm
 > coming through - just out of the idea that i don't really
 > want things to get fried.

I replaced the original 60 amp service in 2008 with a 200, and brought 
this grandfathered 2970 house service up to code, doing all the internal 
work myself. I have a big ups running everything but the lights and 
printers in this room, got rid of the copper telephone because the cable 
was 70 years old, 50 pair paper insulated cable they would not keep 
working for a week at a time, so after 5 months of that I voted with my 
wallet and hooked all that up to the cable system. I must have done 
something right, I have not even blown a ccfl light bulb since and it 
all runs 24/7/365.25.



You can have incoming-mains overvoltage protection installed to
provide a base level of protection for everything electrical against a
mains overvoltage (but generally not other types of power
fluctuations). It's not even all that expensive, or at least wasn't
some years ago. Consider asking your electrician what options would be
available in your particular situation and for a cost estimate or
quote.

Especially if you are in an area that frequently gets lightning, it
_might_ help the UPS last longer, too, since its protective circuitry
then doesn't need to take the brunt of the voltage spike after that is
already well inside your home with all the associated risks.


It's worth mentioning that with a good UPS you get power-conditioning, 
not just filtering and over/under-voltage protection. That can extend 
the lifetime of any electric motor or other device using the conditioned 
power. The UPS emits a controlled waveform beyond what your utility can 
provide.


And numerous datacenters have begun using DC-powered racks. Less power 
loss in the individual transformers and motors in each racked server, 
less heat to be expelled.



Michael Kjörling                      https://michael.kjorling.se

“Remember when, on the Internet, nobody cared that you were a dog?”



Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: AMD GPU hard lockups

[piorunz]

On 01/08/2023 18:16, Celejar wrote:

On Tue, 1 Aug 2023 16:56:37 +0100
piorunz  wrote:


On 01/08/2023 16:44, Celejar wrote:


Any ideas?


Revert to Debian Stable and check there. I have AMD Radeon card and it's
100% stable on Stable, and it had issues last year back when bookworm
was in Testing.


I'm confused - current stable *is* bookworm, so if you had issues with
bookworm, why would reverting to (current) stable help? Do you mean
oldstable / bullseye? I actually did test using kernel 6.1.0-10-amd64
from stable / bookworm, but the problem remained.



I had problems with Testing when it was maturing to become Stable /
Bookworm. Meaning, pre-release Bookworm, it has problems. So there is that.
You are using Sid, so problems are to be expected.

Revert to Stable / Bookworm, which is very stable for me, all problems
which it has last year (while Bookworm was Testing) have been fixed. I
did not have single crash or freeze for months.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: AMD GPU hard lockups

[Celejar]

On Tue, 1 Aug 2023 12:12:01 -0400
Dan Ritter  wrote:

> piorunz wrote: 
> > On 01/08/2023 16:44, Celejar wrote:
> > 
> > > Any ideas?
> > > 
> > Revert to Debian Stable and check there. I have AMD Radeon card and it's
> > 100% stable on Stable, and it had issues last year back when bookworm was in
> > Testing.
> 
> If that doesn't work, try a new power supply. Video cards and
> CPUs are typically the #1 and #2 draw on power, so power
> problems show up there first.

Thanks, but I can't easily / conveniently do that. I don't have one
handy, and the machine is an HP Z440, which I think may have trouble
using standard power supplies anyway.

-- 
Celejar

Re: AMD GPU hard lockups

[Celejar]

On Tue, 1 Aug 2023 16:56:37 +0100
piorunz  wrote:

> On 01/08/2023 16:44, Celejar wrote:
> 
> > Any ideas?
> > 
> Revert to Debian Stable and check there. I have AMD Radeon card and it's 
> 100% stable on Stable, and it had issues last year back when bookworm 
> was in Testing.

I'm confused - current stable *is* bookworm, so if you had issues with
bookworm, why would reverting to (current) stable help? Do you mean
oldstable / bullseye? I actually did test using kernel 6.1.0-10-amd64
from stable / bookworm, but the problem remained.

-- 
Celejar

Re: singularity-container in bookworm?

[Boyan Penkov]

Hello Nilesh,

Thanks kindly -- I do see it, and it's playing along wonderfully with
the rest of bookworm on my systems...

Cheers!

On Tue, Aug 1, 2023 at 5:55 AM Nilesh Patra  wrote:
>
> Hi Boyan,
>
> Sorry for late response, I don't read -user mailing list.
>
> > It seems the issue is one of the more structural issues that come up
> > when upsteam's maintenance policy does not match Debian's more stable
> > development cycle. Is this a viable candidate for inclusion in
> > https://fasttrack.debian.net/ for Bookworm?
>
> Absolutely. I pushed singularity to bookworm fasttrack a few days back.
> Please feel free to use it.
>
> [1]: https://groups.google.com/g/linux.debian.user/c/Smma75Z5qIw
> [2]: https://micronews.debian.org/2023/1686751737.html
>
> Best,
> Nilesh



-- 
Boyan Penkov

Re: chrome web browser worthless

[Bret Busby]

On 1/8/23 20:54, gene heskett wrote:

On 8/1/23 06:26, Bret Busby wrote:

On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a 
browser to run klipper as a google search intercepts port 80, so 
localhost:80 cannot be used for troubleshooting or for running a 3d 
printer with klipper..


FF has no such problems.

Cheers, Gene Heskett.



Willingly joining the google borg, by using chrome ("We have ways to 
obtain and sell all of your private information"), leads to the user 
having to take responsibility for the choice.


If you want an alternative to the fiery fox, you might want to try 
Vivaldi and Pale Moon, although, I think that, with their protections, 
they are a bit more resource demanding.



Not my choice, armbian's.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

.


Cheers, Gene Heskett.



I have not been aware of the existence of anything named armbian, before 
this thread, so, I know nothing of it.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: AMD GPU hard lockups

[Dan Ritter]

piorunz wrote: 
> On 01/08/2023 16:44, Celejar wrote:
> 
> > Any ideas?
> > 
> Revert to Debian Stable and check there. I have AMD Radeon card and it's
> 100% stable on Stable, and it had issues last year back when bookworm was in
> Testing.

If that doesn't work, try a new power supply. Video cards and
CPUs are typically the #1 and #2 draw on power, so power
problems show up there first.

-dsr-

Re: AMD GPU hard lockups

[piorunz]

On 01/08/2023 16:44, Celejar wrote:


Any ideas?

Revert to Debian Stable and check there. I have AMD Radeon card and it's 
100% stable on Stable, and it had issues last year back when bookworm 
was in Testing.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: les adresses d'expéditeur dans thunderbird

[hamster]

Le 01/08/2023 à 17:09, Erwann Le Bras a écrit :


Le 01/08/2023 à 15:20, Matthieu Roquejoffre a écrit :

Le 01/08/2023 à 15:38, Erwann Le Bras a écrit :

Le 30/07/2023 à 12:47, steve a écrit :

Je rève d'un système ou on pourrait renseigner (par exemple dans le
carnet d'adresses) pour chaque destinataire avec quelle adresse
d'expédition on veut lui écrire, et qu'il se charge automatiquement
de mettre la bonne adresse d'expéditeur. Je veux dire qu'on puisse
envoyer un message en mettant plusieurs destinataires différents en
meme temps, et que ca parte pour chaque destinataire avec la bonne
adresse d'expéditeur.

Thunderbird fait ça très bien.

Dans ce cas peux-tu nous expliquer comment faire ?
J'ai beau chercher je ne trouve rien ni dans la documentation ni dans
l'application.


  * un compte par adresse mél. Chaque compte a sa propre arborescence,
mais ce peut être unifié.


Ca en fait vraiment beaucoup. Je préfère un compte par boite mail et 
déclarer dans chaque compte plusieurs identités pour tous les alias qui 
arrivent dans la meme boite mail.



  * les expéditeurs sont dans le carnet d'adresse (nom, email). Il peut
y avoir plusieurs emails par nom
  * dans le carnet d'adresse on peut créer des listes de destinataires


J'aimerais pouvoir renseigner dans le carnet d'adresse, pour chaque 
destinataire, avec quelle adresse d'expéditeur je veux lui écrire.



quand je crée un mél, je tape le nom de l'expéditeur


C'est précisément ce point la que j'aimerais automatiser. Ne pas avoir a 
taper l'éxpéditeur, qu'il soit rempli automatiquement en fonction du 
destinataire que je met.

AMD GPU hard lockups

[Celejar]

Hello,

I have a system running Debian unstable with an AMD RX-570. It has been
working fine for a while, but recently, anything that uses the more
advanced features of the GPU causes the system to hard lockup: black
screen, no response to keyboard, no network connectivity.

I'm not sure exactly which functionality of the GPU causes this:
ordinary web browsing, development work, etc. never cause problems, but
games, the Unigine Heaven benchmark, and even glmark2 invariably do,
sometimes immediately, sometimes after a few seconds or minutes.

I'm not sure exactly when this began: I hadn't been using the system
for any of the problematic tasks for a while.

I've tried looking in the logs. Running 'journalctl -b -1' after a
lockup generally shows nothing. I've tried to catch the error with
'tail -F /var/log/syslog', and most of the time I see nothing (just the
hang, with no warning in the log), but once I caught this:

2023-08-01T10:41:23.531381-04:00 lucy kernel: [38532.241396] 
gmc_v8_0_process_interrupt: 15 callbacks suppressed
2023-08-01T10:41:23.531394-04:00 lucy kernel: [38532.241401] amdgpu 
:02:00.0: amdgpu: GPU fault detected: 147 0x06508401 for process heaven_x64 
pid 14771 thread heaven_x64:cs0 pid 14792
2023-08-01T10:41:23.531395-04:00 lucy kernel: [38532.241407] amdgpu 
:02:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x060004CA
2023-08-01T10:41:23.531396-04:00 lucy kernel: [38532.241408] amdgpu 
:02:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02084001
2023-08-01T10:41:23.531396-04:00 lucy kernel: [38532.241409] amdgpu 
:02:00.0: amdgpu: VM fault (0x01, vmid 1, pasid 32778) at page 100664522, 
read from 'TC7' (0x54433700) (132)
2023-08-01T10:41:23.531397-04:00 lucy kernel: [38532.241429] DMAR: DRHD: 
handling fault status reg 2
2023-08-01T10:41:23.531398-04:00 lucy kernel: [38532.241433] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfbff5000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531399-04:00 lucy kernel: [38532.241438] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfbfd1000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531400-04:00 lucy kernel: [38532.241442] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfbffd000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531409-04:00 lucy kernel: [38532.241445] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfffe [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531409-04:00 lucy kernel: [38532.241449] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfbffd000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531410-04:00 lucy kernel: [38532.241453] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0x8000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531411-04:00 lucy kernel: [38532.241456] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfffd8000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531412-04:00 lucy kernel: [38532.241460] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xfbbc1000 [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531412-04:00 lucy kernel: [38532.241460] pcieport 
:00:02.0: AER: Uncorrected (Fatal) error received: :00:02.0
2023-08-01T10:41:23.531413-04:00 lucy kernel: [38532.241464] DMAR: [DMA Write 
NO_PASID] Request device [02:00.0] fault addr 0xeffc [fault reason 0x05] 
PTE Write access is not set
2023-08-01T10:41:23.531414-04:00 lucy kernel: [38532.241477] pcieport 
:00:02.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction 
Layer, (Receiver ID)
2023-08-01T10:41:23.531415-04:00 lucy kernel: [38532.241482] pcieport 
:00:02.0:   device [8086:6f04] error status/mask=0004/
2023-08-01T10:41:23.531415-04:00 lucy kernel: [38532.241487] pcieport 
:00:02.0:[18] MalfTLP(First)
2023-08-01T10:41:23.531416-04:00 lucy kernel: [38532.241492] pcieport 
:00:02.0: AER:   TLP Header: 1000 020024ff aaa800c0 
2023-08-01T10:41:23.531417-04:00 lucy kernel: [38532.241500] [drm] PCI error: 
detected callback, state(2)!!

I've found similar reports online, e.g.:

https://unix.stackexchange.com/questions/327730/what-causes-this-pcieport-0003-0-pcie-bus-error-aer-bad-tlp
https://forums.linuxmint.com/viewtopic.php?t=380748
https://gitlab.freedesktop.org/drm/amd/-/issues/2358

But I'm really not clear whether these represent the same problem, or
are just different variations of a more general driver / firmware
problem. (I'm assuming it's software / firmware, since everything
worked fine previously, although I suppose it's possible that something
physical has broken in the hardware.)

Any ideas?

-- 
Celejar

Re: Plantage suite à ajout de desktop icon dans /usr/share/applications/

[RogerT]

En résumé de mon précédent long exposé :

1/ avec debian 11 (gnome) :
Quel est la manière usuelle (en CLI et via le GUI) de créer une desktop icon et 
de la déployer à partir du fichier exécutable ?
(En CLI, j’ai trouvé desktop-file-utils mais trouvé aucun moyen via le GUI)
Est-ce différent avec d’autres DE ?

2/ pensez-vous que ma manip pourtant ordinaire (sudo cp truc.desktop 
/usr/share/applications/ ) ait seule pu causer le plantage décrit (les petits 
diamants blancs en haut à gauche d’un écran subitement devenu noir) ?

Merci. 

> Le 31 juil. 2023 à 22:59, roger.tar...@free.fr a écrit :
> 
> 
> PS
> 
> En fouillant, je découvre un paquet 
> https://www.freedesktop.org/wiki/Software/desktop-file-utils/ qui est 
> installé apparemment d'office sur (ma) debian 11.
> 
> Il propose 3 fonctions :
>   desktop-file-validate  
>   desktop-file-install
>   update-desktop-database
> 
> Confirmez-vous que c'est "l'outil de référence" debian ?
> 
> Par ailleurs, je lis ici qu'il existe gnome-desktop-item-edit (inexistant sur 
> ma debian 11 gnome)
> https://www.xmodulo.com/create-desktop-shortcut-launcher-linux.html
> 
> Cet autre article explique un procédé entièrement manuel (comme je faisais) :
> https://cleberjamaral.hashnode.dev/how-to-create-a-desktop-launcher-on-debian
> 
> Enfin, je n'ai pas "Create Launcher" via un clic droit sur un fichier 
> d'exécutable, comme je le vois sur divers forums.
> Est-ce normal sur une debian 11 installée avec DE gnome ?
> 
> 
> 
> Détail de mon exploration de 4 commandes de desktop-file-utils
> =
> 
> En CLI, avec desktop-file TAB, je peux faire apparaître  :
>   desktop-file-edit -> bizarre, pas dans la doc
>   desktop-file-install
>   desktop-file-validate  
> 
> 
> 1/ Avec desktop-file-edit
> $ desktop-file-edit ~/Desktop/test.desktop
> Error on file "/home/test/Desktop/test.desktop": No such file or directory
> 
> $ touch ~/Desktop/test.desktop
> 
> $ desktop-file-edit ~/Desktop/test.desktop 
> /home/test/Desktop/test.desktop: error: required key "Type" in group "Desktop 
> Entry" is not present
> /home/test/Desktop/test.desktop: error: required key "Name" in group "Desktop 
> Entry" is not present
> Error on file "/home/test/Desktop/test.desktop": Failed to validate the 
> created desktop file
> 
> ...Après recherche, il faut spécifier comme suit :
> desktop-file-edit \
> --set-name="GIMP on LXD" \
> --set-comment="GIMP 2.8 with custom plugins" \
> --set-icon="/home/vivek/backups/desktop-entries/gimp.png" \
> --add-category="Graphics;2DGraphics;RasterGraphics;GTK;" \
> --set-key="Exec" --set-value="/snap/bin/lxc exec gui-1804-gimp -- sudo 
> --login --user vivek /usr/bin/gimp-2.8 %U" \
> --set-key="Type" --set-value="Application" \
> gimp-2.8.desktop
> 
> https://www.cyberciti.biz/howto/how-to-install-and-edit-desktop-files-on-linux-desktop-entries/
> 
> Mais cette commande, valide, n'est plus mise en avant par la doc. 
> D'ailleurs :
> $ dlocate -lsbin desktop-file-utils
> /usr/bin/desktop-file-install
> /usr/bin/desktop-file-validate
> /usr/bin/update-desktop-database
> et :
> ~$ dpkg -L desktop-file-utils | grep /usr/bin/
> /usr/bin/desktop-file-install
> /usr/bin/desktop-file-validate
> /usr/bin/update-desktop-database
> /usr/bin/desktop-file-edit
> 
> 
> 2/ Avec desktop-file-install
> $ sudo desktop-file-install ~/Desktop/test.desktop
> (OK ; code 0)
> 
> 
> 3/ Avec desktop-file-validate :
> La commande indique ce qui cloche, par exemple :
>warning: key "Encoding" in group "Desktop Entry" is deprecated
>warning: value "Application;Network;" for key "Categories" in group 
> "Desktop Entry" contains a deprecated value "Application"
> Pratique !
> 
> 
> 4/ Avec update-desktop-database
> man update-desktop-database dit : "Build cache database of MIME types handled 
> by desktop files"
> ~$ sudo update-desktop-database -v
> ...
> File "/usr/share/applications/remmina-gnome.desktop" lacks MimeType key
> 
> Notez que ce sont les icônes créées par debian 11...
> 
> Y a-t-il lieu de corriger ça ? Si oui, comment ?
> 
> =
> 

Re: NetworkManager, Iphone, and Bookworm

[Charles Curley]

On Tue, 1 Aug 2023 07:18:36 +0200
didier gaumet  wrote:

> Le 01/08/2023 à 06:30, Charles Curley a écrit :
> 
>  [...]  
> 
> I have no Apple hardware and have experimented this but you could 
> *probably* use a MDM solution to do it:
> https://support.apple.com/guide/deployment/intro-to-mdm-profiles-depc0aadd3fe/web
> https://support.apple.com/guide/deployment/choose-an-mdm-solution-dep1d7afa557/web

Thanks. I think I will defer this for now. It might not work. It strikes
me as an overly complicated solution to a problem that shouldn't exist.



> I suppose your Iphone 8 was set up with WPA2 while your Iphone 14 is
> set up with WPA3 (either pure, or rather, mixed)

That sounds likely. Also, my Bullseye machine (no WPA3) has no problem
connecting. This leads me to conjecture that the problem is in
negotiating WP3 vs. WP2. Just a guess, there.

> 
> If your Bookworm is an upgrade of a previous Debian installation, it 
> would be of interest to verify you have the good version of
> wpa_supplicant: didier@hp-notebook14:~$ LANG=en-US.UTF-8; apt policy
> wpasupplicant wpasupplicant:
>Installed: 2:2.10-12
>Candidate: 2:2.10-12
>Version table:
>   *** 2:2.10-12 500
>  500 http://deb.debian.org/debian bookworm/main amd64 Packages
>  100 /var/lib/dpkg/status

It is not an upgrade, it is a fresh installation. None the less:

root@tsalmoth:~# LANG=en-US.UTF-8; apt policy wpasupplicant
wpasupplicant:
  Installed: 2:2.10-12
  Candidate: 2:2.10-12
  Version table:
 *** 2:2.10-12 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status
root@tsalmoth:~# 

Compared to bullseye:

root@jhegaala:~# LANG=en-US.UTF-8; apt policy wpasupplicant
wpasupplicant:
  Installed: 2:2.9.0-21
  Candidate: 2:2.9.0-21
  Version table:
 2:2.10-8~bpo11+2 100
100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 2:2.9.0-21 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
root@jhegaala:~#


> 
> If wpasupplicant is up to date and you still are not able to connect, 
> consult le Archlinux wiki, there are instructions to manage WPA3
> mixed (with WPA2) manually (wpa_cli):
> https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE_access_points
> https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_mixed_WPA2-PSK/WPA3-SAE_access_points

I will look at these. Thank you.

Dammit, all of this wireless configuration stuff is supposed to
be automatic and painless for the end user. All the complexities should
be hidden from the end user (me). Well, they aren't.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: les adresses d'expéditeur dans thunderbird

[Erwann Le Bras]

Le 01/08/2023 à 15:20, Matthieu Roquejoffre a écrit :

Le 01/08/2023 à 15:38, Erwann Le Bras a écrit :

Le 30/07/2023 à 12:47, steve a écrit :

Je rève d'un système ou on pourrait renseigner (par exemple dans le
carnet d'adresses) pour chaque destinataire avec quelle adresse
d'expédition on veut lui écrire, et qu'il se charge automatiquement
de mettre la bonne adresse d'expéditeur. Je veux dire qu'on puisse
envoyer un message en mettant plusieurs destinataires différents en
meme temps, et que ca parte pour chaque destinataire avec la bonne
adresse d'expéditeur.

Thunderbird fait ça très bien.

Dans ce cas peux-tu nous expliquer comment faire ?
J'ai beau chercher je ne trouve rien ni dans la documentation ni dans
l'application.


 * un compte par adresse mél. Chaque compte a sa propre arborescence,
   mais ce peut être unifié.
 * les expéditeurs sont dans le carnet d'adresse (nom, email). Il peut
   y avoir plusieurs emails par nom
 * dans le carnet d'adresse on peut créer des listes de destinataires

quand je crée un mél, je tape le nom de l'expéditeur et me rempli l'email.
Le nom d'expéditeur par défaut est celui du compte, mais je peux en 
choisir un autre parmi tous les comptes configuré


Dans une réponse, je peux faire "répondre à l'expéditeur" ou "répondre à 
la liste".


c'est le fonctionnement par défaut. J'utilise une extension (cardbook) 
qui me permet d'avoir mes contacts sur un serveur CalDav (chez moi 
Owncloud) et donc partagés avec plusieurs périphériques et clients de 
messagerie différents.


Erwann

Re: OT: Protecting electrical equipment; was: Recommendations for a UPS?

[Nicholas Geovanis]

On Tue, Aug 1, 2023, 2:40 AM Michael Kjörling <2695bd53d...@ewoof.net>
wrote:

> On 31 Jul 2023 15:21 -0400, from songb...@anthive.com (songbird):
> >   i do not run things for long when the power goes out
> > but the capacity for my needs is plenty and then i shut
> > down in an orderly fashion.  most of the time i shut down
> > the computer system and unplug the power cord and the
> > network cables and antenna cables if there is a storm
> > coming through - just out of the idea that i don't really
> > want things to get fried.
>
> You can have incoming-mains overvoltage protection installed to
> provide a base level of protection for everything electrical against a
> mains overvoltage (but generally not other types of power
> fluctuations). It's not even all that expensive, or at least wasn't
> some years ago. Consider asking your electrician what options would be
> available in your particular situation and for a cost estimate or
> quote.
>
> Especially if you are in an area that frequently gets lightning, it
> _might_ help the UPS last longer, too, since its protective circuitry
> then doesn't need to take the brunt of the voltage spike after that is
> already well inside your home with all the associated risks.
>

It's worth mentioning that with a good UPS you get power-conditioning, not
just filtering and over/under-voltage protection. That can extend the
lifetime of any electric motor or other device using the conditioned power.
The UPS emits a controlled waveform beyond what your utility can provide.

And numerous datacenters have begun using DC-powered racks. Less power loss
in the individual transformers and motors in each racked server, less heat
to be expelled.


Michael Kjörling  https://michael.kjorling.se
> “Remember when, on the Internet, nobody cared that you were a dog?”
>
>

Re: les adresses d'expéditeur dans thunderbird

[Matthieu Roquejoffre]

Le 01/08/2023 à 15:38, Erwann Le Bras a écrit :
> Le 30/07/2023 à 12:47, steve a écrit :
>>> Je rève d'un système ou on pourrait renseigner (par exemple dans le 
>>> carnet d'adresses) pour chaque destinataire avec quelle adresse 
>>> d'expédition on veut lui écrire, et qu'il se charge automatiquement 
>>> de mettre la bonne adresse d'expéditeur. Je veux dire qu'on puisse 
>>> envoyer un message en mettant plusieurs destinataires différents en 
>>> meme temps, et que ca parte pour chaque destinataire avec la bonne 
>>> adresse d'expéditeur.
> Thunderbird fait ça très bien.
Dans ce cas peux-tu nous expliquer comment faire ?
J'ai beau chercher je ne trouve rien ni dans la documentation ni dans 
l'application.

-- 
Matthieu Roquejoffre 
Fingerprint: 0591 eccd 7f11 454b eb7f e81c b3dc 5a41 7fe4 5f42

Re: les adresses d'expéditeur dans thunderbird

[hamster]

Le 01/08/2023 à 15:38, Erwann Le Bras a écrit :


Le 30/07/2023 à 12:47, steve a écrit :

Le 30-07-2023, à 13:45:44 +0200, hamster a écrit :

Je rève d'un système ou on pourrait renseigner (par exemple dans le 
carnet d'adresses) pour chaque destinataire avec quelle adresse 
d'expédition on veut lui écrire, et qu'il se charge automatiquement 
de mettre la bonne adresse d'expéditeur. Je veux dire qu'on puisse 
envoyer un message en mettant plusieurs destinataires différents en 
meme temps, et que ca parte pour chaque destinataire avec la bonne 
adresse d'expéditeur.


mutt


Thunderbird fait ça très bien.


Alors il faut que tu m'explique parce que moi avec thunderbird j'y 
arrive pas.

Re: les adresses d'expéditeur dans thunderbird

[Erwann Le Bras]

Le 30/07/2023 à 12:47, steve a écrit :

Le 30-07-2023, à 13:45:44 +0200, hamster a écrit :

Je rève d'un système ou on pourrait renseigner (par exemple dans le 
carnet d'adresses) pour chaque destinataire avec quelle adresse 
d'expédition on veut lui écrire, et qu'il se charge automatiquement 
de mettre la bonne adresse d'expéditeur. Je veux dire qu'on puisse 
envoyer un message en mettant plusieurs destinataires différents en 
meme temps, et que ca parte pour chaque destinataire avec la bonne 
adresse d'expéditeur.


mutt


Thunderbird fait ça très bien.

Re: chrome web browser worthless

[gene heskett]

On 8/1/23 06:26, Bret Busby wrote:

On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a browser 
to run klipper as a google search intercepts port 80, so localhost:80 
cannot be used for troubleshooting or for running a 3d printer with 
klipper..


FF has no such problems.

Cheers, Gene Heskett.



Willingly joining the google borg, by using chrome ("We have ways to 
obtain and sell all of your private information"), leads to the user 
having to take responsibility for the choice.


If you want an alternative to the fiery fox, you might want to try 
Vivaldi and Pale Moon, although, I think that, with their protections, 
they are a bit more resource demanding.



Not my choice, armbian's.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: chrome web browser worthless

[Andrew M.A. Cater]

On Tue, Aug 01, 2023 at 08:13:50AM -0400, gene heskett wrote:
> On 8/1/23 06:16, Phil Wyett wrote:
> > On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:
> > 
> > Hi,
> > 
> > Maybe direct this to the appropriate arena. Debians default browser is
> > Firefox, if there is no issue with FF means you are in the wrong place
> > for this kind of statement/query.
> > 
> > Regards
> > 
> > Phil
> > 
> While armbians default seems to be chrome. But I believe armbian is using
> the debian repos. FF is installed as a snap, updated nightly from mozzilla,
> which is a PITA but it does work.  Google/Alphabet is turning into a bigger
> PITA than M$. So I'll hit the armbian forum with this bitch.  Thank you
> Phil, take care & stay well.
> 
> Cheers, Gene Heskett.

Gene,

With the best will in the world - this *isn't* a Debian problem.

It's an armbian problem, maybe - it's a Gene problem, but it's not a
problem with Debian-provided software.

Similarly with snaps/AppImages/flatpaks - install from third party sites
and you take yourself outside straightforward Debian - at whcih point it's
time to go and raise complaints with your software provider.

If you mix in packages from various sites, you create a sort of
FrankenDebian - that's fine, but don't ask Debian to sort out the
resultant problems when most of us here can only speak to Debian
experience.

All the very best, as ever,

Andy


> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page 
> 

Re: chrome web browser worthless

[gene heskett]

On 8/1/23 06:16, Phil Wyett wrote:

On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:

Google seems to have high jacked port 80, I cannot use it as a
browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer with
klipper..

FF has no such problems.

Cheers, Gene Heskett.


Hi,

Maybe direct this to the appropriate arena. Debians default browser is
Firefox, if there is no issue with FF means you are in the wrong place
for this kind of statement/query.

Regards

Phil

While armbians default seems to be chrome. But I believe armbian is 
using the debian repos. FF is installed as a snap, updated nightly from 
mozzilla, which is a PITA but it does work.  Google/Alphabet is turning 
into a bigger PITA than M$. So I'll hit the armbian forum with this 
bitch.  Thank you Phil, take care & stay well.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 13:52, didier gaumet a écrit :

apparemment (vu que JSON et moi ça fait deux) ce pourrait être un 
argument vide passé en paramètre qui déclencherait cette erreur. Regarde 
éventuellement dans les lignes précédentes si tu vois où / dans quoi ça 
a lieu (plus précisément que gnome-shell)


j'ai oublié de précisé que je n'avais pas ce genre d'erreur renvoyé par 
journalctl

Re: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 12:14, Gaëtan Perrier a écrit :


Ah je ne savais pas mais je viens de regarder dedans et rien au niveau du
freeze d'hier à part des quantités de log

gnome-shell[3330]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data

Mais y en a plein en permanence de ces logs.

Gaëtan


apparemment (vu que JSON et moi ça fait deux) ce pourrait être un 
argument vide passé en paramètre qui déclencherait cette erreur. Regarde 
éventuellement dans les lignes précédentes si tu vois où / dans quoi ça 
a lieu (plus précisément que gnome-shell)

Re: chrome web browser worthless

[Greg Wooledge]

On Tue, Aug 01, 2023 at 05:33:55AM -0400, gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a browser to
> run klipper as a google search intercepts port 80, so localhost:80 cannot be
> used for troubleshooting or for running a 3d printer with klipper..
> 
> FF has no such problems.

On my system, with this package:

ii  google-chrome-stable 115.0.5790.110-1 amd64The web browser from 
Google

and with Help -> About Google Chrome showing this version string:

Version 115.0.5790.110 (Official Build) (64-bit)

I cannot reproduce your result.  Typing this URL:

http://localhost:80/

gives me these messages:


This site can’t be reached
localhost refused to connect.

Try:

* Checking the connection
* Checking the proxy and the firewall

ERR_CONNECTION_REFUSED


I consider this a correct result, as I have no local web server running.

unicorn:~$ telnet localhost 80
Trying ::1...
Connection failed: Connection refused
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused


So, at least with my current configuration, I see no evidence that Google
Chrome "intercepts port 80".  Perhaps something in your configuration
is different.

The standard next steps in such a situation would be to try with a brand
new browser profile, or with a brand new user account that has never run
Google Chrome before (which can be simulated by moving your dot-directories
to new names temporarily, or not-simulated by actually creating a new
user account and logging in as that account).

I'm not sure what all of the dot-directories are, but I see
~/.config/google-chrome/ and ~/.cache/google-chrome as starting points.

Or, if you prefer, you could try digging through your configuration to
see what might be set incorrectly.  I wouldn't relish that task.  Maybe
you could start with proxy settings, though.  If I recall correctly,
however, those have to be set with command-line arguments or environment
variables.  Or at least that was true once upon a time.

... oh!  And one other thing you definitely should check is the definition
of localhost in your /etc/hosts file.  On a standard Debian system, you
should have something like this:


unicorn:~$ grep localhost /etc/hosts
127.0.0.1   localhost
::1 localhost ip6-localhost ip6-loopback


Given your penchant for altering network configurations, it would not
surprise me if you've customized this in a way that breaks something.

Re: which dput/method to chose for automatic uploads via cron?

[Michael Kjörling]

On 1 Aug 2023 10:59 +0200, from harald.dun...@aixigo.com (Harald Dunkel):
> - dput-ng/sftpworks fine on the command line, but dies with
>   "Failed to auth" in cron scripts.

I can't help you choose a dput method, but different results between
running on an interactive command line and through cron almost always
comes down to some relevant environment variable having a different
value, or sometimes /bin/sh doing things differently from your default
shell. Since dput-ng/sftp seems to be closest to doing what you want,
have you ruled out such differences being the cause of your
difficulties when running it through cron?

More than once I've ended up putting something in a shell script only
to make it easier to run sometimes even just a single command with a
preferred shell through cron.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Nettoyage du spam : juin 2023

[Jean-Pierre Giraud]

Bonjour,
Comme nous sommes en août, il est désormais possible de traiter les
archives du mois de juillet 2023 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Jean-Pierre Giraud


signature.asc
Description: This is a digitally signed message part

Re: chrome web browser worthless

[Bret Busby]

On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a browser 
to run klipper as a google search intercepts port 80, so localhost:80 
cannot be used for troubleshooting or for running a 3d printer with 
klipper..


FF has no such problems.

Cheers, Gene Heskett.



Willingly joining the google borg, by using chrome ("We have ways to 
obtain and sell all of your private information"), leads to the user 
having to take responsibility for the choice.


If you want an alternative to the fiery fox, you might want to try 
Vivaldi and Pale Moon, although, I think that, with their protections, 
they are a bit more resource demanding.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: chrome web browser worthless

[Phil Wyett]

On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a
> browser 
> to run klipper as a google search intercepts port 80, so localhost:80
> cannot be used for troubleshooting or for running a 3d printer with 
> klipper..
> 
> FF has no such problems.
> 
> Cheers, Gene Heskett.

Hi,

Maybe direct this to the appropriate arena. Debians default browser is
Firefox, if there is no issue with FF means you are in the wrong place
for this kind of statement/query.

Regards

Phil

-- 
Playing the game for the games sake.

* Debian Maintainer

Social:

* Twitter: kathenasorg
* Instagram: kathenasorg



signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le mardi 01 août 2023 à 12:14 +0200, didier gaumet a écrit :
> Le 01/08/2023 à 12:04, Gaëtan Perrier a écrit :
> 
> > Chez moi ça tourne bien en user sans avoir la ligne needs_root_rights=no
> > 
> > ~$ ps aux | grep Xorg
> > gpe 3127  2.5  0.6 460772 109108 tty2    Sl+  11:44   0:27
> > /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -
> > nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
> 
> tu utilises gdm avec Systemd donc je crois que tu trouveras ses messages 
> (ceux de gdm) via journalctl:
> https://wiki.archlinux.org/title/Xorg#General
> 

oui c'est celà: gdm et systemd mais rien dans journalctl (voir une de mes
autres réponses d'aujourd'hui)

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 12:14, didier gaumet a écrit :

tu utilises gdm avec Systemd donc je crois que tu trouveras ses messages 
(ceux de gdm) via journalctl:

https://wiki.archlinux.org/title/Xorg#General


et en l'occurrence, ceux de Xorg, normalement

Re: [testing] passage du pilote proprio à nouveau

[Michel Verdier]

Le 1 août 2023 Michel a écrit :

> Effectivement, c'est LightDM que j'utilise ( avec XFCE ).

Ah ba oui le postulat de base dont on parlait c'est lancer Xorg sans
DE...

Re: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 12:04, Gaëtan Perrier a écrit :


Chez moi ça tourne bien en user sans avoir la ligne needs_root_rights=no

~$ ps aux | grep Xorg
gpe 3127  2.5  0.6 460772 109108 tty2Sl+  11:44   0:27
/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -
nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3


tu utilises gdm avec Systemd donc je crois que tu trouveras ses messages 
(ceux de gdm) via journalctl:

https://wiki.archlinux.org/title/Xorg#General

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le lundi 31 juillet 2023 à 15:15 +0200, Erwan David a écrit :
> Le 31/07/2023 à 14:00, didier gaumet a écrit :
> > Le 31/07/2023 à 12:49, Gaëtan Perrier a écrit :
> > 
> > > Pas eu besoin d'attendre longtemps :(
> > > Freeze juste après l'envoi du message précédent.
> > > 
> > > Rien dans /var/log/syslog à part une série de ^@
> > 
> > Tu es sous Wayland ou Xorg (et tu es bien sous Systemd pax SysV)?
> > Pour Wayland il faudra fouiller dans les résultats de journalctl, pour 
> > Xorg lancé par un utilisateur avec un DE il faudra regarder le contenu 
> > de ~/.xsession-errors, pour Xorg lancé par un utilisateur sans DE, je 
> > ne me souviens plus, c'est peut-être plutôt ~/.xinitquelquechose (pas 
> > sûr). Pour un Xorg lancé par root ce devrait être /var/log/Xorg.0.log 
> > ou /var/log/Xorg.0.log.
> > 
> > Pour tous les fichiers d'erreur Xorg, de mémoire il faut chercher les 
> > chaînes EE pour les erreurs et WW pour les avertissements, le reste je 
> > crois que c'est principalement II pour info (me rappelle pas bien)
> > 
> > Et si tu veux vraiment faire de la plongée (je ne sais plus qui nous 
> > parlait de plongée récemment sur cette liste), tu peux essayer de 
> > debugger tout ça:
> > https://x.org/wiki/Development/Documentation/ServerDebugging/
> > 
> > 
> En testing ça fait plusieurs mois que les logs users après sddm sont 
> dans journal, plus dans .xsession-errors
> 

Ah je ne savais pas mais je viens de regarder dedans et rien au niveau du
freeze d'hier à part des quantités de log 

gnome-shell[3330]: failed to decode base64 json SyntaxError: JSON.parse:
unexpected end of data at line 1 column 1 of the JSON data

Mais y en a plein en permanence de ces logs.

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 11:51, Gaëtan Perrier a écrit :

Le lundi 31 juillet 2023 à 14:00 +0200, didier gaumet a écrit :



Je suis sous xorg et systemd


Pour Wayland il faudra fouiller dans les résultats de journalctl, pour
Xorg lancé par un utilisateur avec un DE il faudra regarder le contenu
de ~/.xsession-errors, pour Xorg lancé par un utilisateur sans DE, je ne
me souviens plus, c'est peut-être plutôt ~/.xinitquelquechose (pas sûr).


Rien de tel dans mon rép user


L'emplacement local que j'ai cité pour du X11 rootless ne semble plus 
d'actualité.
Dans un autre message, Michel Verdier a évoqué un endroit différent 
(~/.local/share/xorg/Xorg.0.log) et le wiki Archlinux va dans le même sens:

https://wiki.archlinux.org/title/Xorg#General

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le mardi 01 août 2023 à 08:50 +0200, Michel Verdier a écrit :
> Le 1 août 2023 Michel a écrit :
> 
> > > > Sur ma debian de base, les logs sont bien dans /var/log/Xorg.0.log par
> > > > défaut, sans modification de startx ou de  ~/.xsession ...
> > > 
> > > Ce ne serait pas parce que Xorg est lancé en root ? Par défaut les users
> > > n'ont pas accès à /var/log. Vérifie /etc/X11/Xwrapper.config qui doit
> > > avoir needs_root_rights=no (du moins si ta carte graphique le permet).
> > 
> > Non, j'ai seulement une ligne non commentée:
> > 
> > allowed_users=console
> 
> Ok donc tu dois tourner en root. Vérifie avec un ps aux | grep Xorg
> et si Xorg est en root ajoute needs_root_rights=no dans
> /etc/X11/Xwrapper.config. C'est mieux pour la sécurité.
> Mais ça peut coincer si tu as une carte graphique qui requiert les droits
> root (c'est rare mais il y en a).
> 

Chez moi ça tourne bien en user sans avoir la ligne needs_root_rights=no

~$ ps aux | grep Xorg
gpe 3127  2.5  0.6 460772 109108 tty2Sl+  11:44   0:27
/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -
nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3


Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le mardi 01 août 2023 à 07:03 +0200, Michel Verdier a écrit :
> Le 31 juillet 2023 Michel a écrit :
> 
> > > Si on modifie startx, ~/.xsession, etc, on peut avoir les logs ailleurs
> > > mais sinon on les a dans ~/.local/share/xorg/Xorg.0.log
> > 
> > Sur ma debian de base, les logs sont bien dans /var/log/Xorg.0.log par
> > défaut, sans modification de startx ou de  ~/.xsession ...
> 
> Ce ne serait pas parce que Xorg est lancé en root ? Par défaut les users
> n'ont pas accès à /var/log. Vérifie /etc/X11/Xwrapper.config qui doit
> avoir needs_root_rights=no (du moins si ta carte graphique le permet).
> 

Chez ce fichier date du 1/4/2014 et contient ceci:

# Xwrapper.config (Debian X Window System server wrapper configuration file)
#
# This file was generated by the post-installation script of the x11-common
# package using values from the debconf database.
#
# See the Xwrapper.config(5) manual page for more information.
#
# This file is automatically updated on upgrades of the x11-common package
# *only* if it has not been modified since the last upgrade of that package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command as root:
#   dpkg-reconfigure x11-common
allowed_users=console


Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le lundi 31 juillet 2023 à 15:13 +0200, Michel Verdier a écrit :
> Le 31 juillet 2023 didier gaumet a écrit :
> 
> > Tu es sous Wayland ou Xorg (et tu es bien sous Systemd pax SysV)?
> > Pour Wayland il faudra fouiller dans les résultats de journalctl, pour Xorg
> > lancé par un utilisateur avec un DE il faudra regarder le contenu de
> > ~/.xsession-errors, pour Xorg lancé par un utilisateur sans DE, je ne me
> > souviens plus, c'est peut-être plutôt ~/.xinitquelquechose (pas sûr). Pour
> > un
> > Xorg lancé par root ce devrait être /var/log/Xorg.0.log ou
> > /var/log/Xorg.0.log.
> 
> Si on modifie startx, ~/.xsession, etc, on peut avoir les logs ailleurs
> mais sinon on les a dans ~/.local/share/xorg/Xorg.0.log


Effectivement j'ai bien des fichiers log dans .local/share mais soit
d'aujourd'hui soit du mois d'octobre ...
Donc rien sur les dates des plantages et aucune erreur dans ceux d'aujourd'hui.

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: singularity-container in bookworm?

[Nilesh Patra]

Hi Boyan,

Sorry for late response, I don't read -user mailing list.

> It seems the issue is one of the more structural issues that come up
> when upsteam's maintenance policy does not match Debian's more stable
> development cycle. Is this a viable candidate for inclusion in
> https://fasttrack.debian.net/ for Bookworm?

Absolutely. I pushed singularity to bookworm fasttrack a few days back.
Please feel free to use it.

[1]: https://groups.google.com/g/linux.debian.user/c/Smma75Z5qIw
[2]: https://micronews.debian.org/2023/1686751737.html

Best,
Nilesh


signature.asc
Description: PGP signature

Re: [testing] passage du pilote proprio à nouveau

[ajh-valmer]

On Tuesday 01 August 2023 07:03:08 Michel Verdier wrote:
> Ce ne serait pas parce que Xorg est lancé en root ? 
> Par défaut les users n'ont pas accès à /var/log.
> Vérifie /etc/X11/Xwrapper.config qui doit 
> avoir needs_root_rights=no (du moins si ta carte graphique le permet).

Pour accéder aux configs de Xorg, il faut être root,
ils sont dans /etc/X11/
Je ne me suis jamais préoccupé d'un mode Xorg en root
ou user...

Re: [testing] passage du pilote proprio à nouveau

[Gaëtan Perrier]

Le lundi 31 juillet 2023 à 14:00 +0200, didier gaumet a écrit :
> Le 31/07/2023 à 12:49, Gaëtan Perrier a écrit :
> 
> > Pas eu besoin d'attendre longtemps :(
> > Freeze juste après l'envoi du message précédent.
> > 
> > Rien dans /var/log/syslog à part une série de ^@
> 
> Tu es sous Wayland ou Xorg (et tu es bien sous Systemd pax SysV)?

Je suis sous xorg et systemd

> Pour Wayland il faudra fouiller dans les résultats de journalctl, pour 
> Xorg lancé par un utilisateur avec un DE il faudra regarder le contenu 
> de ~/.xsession-errors, pour Xorg lancé par un utilisateur sans DE, je ne 
> me souviens plus, c'est peut-être plutôt ~/.xinitquelquechose (pas sûr). 

Rien de tel dans mon rép user

> Pour un Xorg lancé par root ce devrait être /var/log/Xorg.0.log ou 
> /var/log/Xorg.0.log.

Depuis le passage à nouveau les Xorg.*.log ne sont plus créés.

> 
> Pour tous les fichiers d'erreur Xorg, de mémoire il faut chercher les 
> chaînes EE pour les erreurs et WW pour les avertissements, le reste je 
> crois que c'est principalement II pour info (me rappelle pas bien)
> 
> Et si tu veux vraiment faire de la plongée (je ne sais plus qui nous 
> parlait de plongée récemment sur cette liste), tu peux essayer de 
> debugger tout ça:
> https://x.org/wiki/Development/Documentation/ServerDebugging/
> 

Pour la plongée je manque de souffle actuellement ;)

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: [testing] passage du pilote proprio à nouveau

[Michel]

Le 01/08/2023 à 10:30, didier gaumet a écrit :
> Le 01/08/2023 à 09:22, Michel a écrit :
> 
>> Je viens de faire le test, en ajoutant needs_root_rights=no à la fin du
>> fichier /etc/X11/Xwrapper.config.
>> Après un arrêt puis un démarrage de la machine, Xorg est toujours lancé
>> en root. Ma configuration était d'origine et non modifiée ( Xorg n'est
>> pas lancé depuis une console, mais depuis l'écran graphique de connexion ).
> 
> certains display managers ("l'écran graphique de connexion") ne 
> supportent pas le mode rootless. Parmi les display managers actuellement 
> maintenus, GDM et SDDM acceptent le mode rootless, LightDM et XDM ne 
> l'accpetent pas, TDM (le DM de Trinity), je ne sais pas mais je suppose 
> que non car il doit être dérivé de KDM, abandonné:
> https://wiki.archlinux.org/title/Xorg#Rootless_Xorg

Effectivement, c'est LightDM que j'utilise ( avec XFCE ).

chrome web browser worthless

[gene heskett]

Google seems to have high jacked port 80, I cannot use it as a browser 
to run klipper as a google search intercepts port 80, so localhost:80 
cannot be used for troubleshooting or for running a 3d printer with 
klipper..


FF has no such problems.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

which dput/method to chose for automatic uploads via cron?

[Harald Dunkel]

Hi folks,

which dput/method would you suggest for uploading packages to
a private repo via ssh? By now I tried

- dput/rsyncfails to upload files in a reproducible sequence,
breaking inoticoming on the receiver side
- dput/scp  "permission denied", ssh_config_options appear
to be ignored
- dput/sftp doesn't exist
- dput-ng/scp   ignores ssh_config_options
- dput-ng/sftp  works fine on the command line, but dies with
"Failed to auth" in cron scripts.
- dput-ng/rsync doesn't exist

I have to use a dedicated key pair for dput via ssh, ie.

IdentityFile=~/.ssh/id/id_ecdsa.debian
IdentitiesOnly=yes

are mandatory.

Every helpful comment is highly appreciated.


Harri

Monthly FAQ for Debian-user mailing list

[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; do not
   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: [testing] passage du pilote proprio à nouveau

[didier gaumet]

Le 01/08/2023 à 09:22, Michel a écrit :


Je viens de faire le test, en ajoutant needs_root_rights=no à la fin du
fichier /etc/X11/Xwrapper.config.
Après un arrêt puis un démarrage de la machine, Xorg est toujours lancé
en root. Ma configuration était d'origine et non modifiée ( Xorg n'est
pas lancé depuis une console, mais depuis l'écran graphique de connexion ).


certains display managers ("l'écran graphique de connexion") ne 
supportent pas le mode rootless. Parmi les display managers actuellement 
maintenus, GDM et SDDM acceptent le mode rootless, LightDM et XDM ne 
l'accpetent pas, TDM (le DM de Trinity), je ne sais pas mais je suppose 
que non car il doit être dérivé de KDM, abandonné:

https://wiki.archlinux.org/title/Xorg#Rootless_Xorg

Re: Recommendations for a UPS?

[Roger Price]

On Tue, 1 Aug 2023, Karl Vogel wrote:

  I give a solid vote to Liebert.  I had a near-miss lightning strike
  a few nights ago, and all it did was make my display go out for about
  a second.  It came right back, session intact, didn't lose a thing.


My place took a direct hit from a lightning strike.  Frightening.  Despite two 
differential circuit breakers in front of the UPS, it melted the circuit board 
in an Eaton Ellipse 1600.  The server crashed but no data was lost.  Eaton 
replaced the UPS.


Roger

Re: [testing] passage du pilote proprio à nouveau

[Michel]

Le 01/08/2023 à 09:00, Michel Verdier a écrit :
> Le 1 août 2023 Michel a écrit :
> 
 Sur ma debian de base, les logs sont bien dans /var/log/Xorg.0.log par
 défaut, sans modification de startx ou de  ~/.xsession ...
>>>
>>> Ce ne serait pas parce que Xorg est lancé en root ? Par défaut les users
>>> n'ont pas accès à /var/log. Vérifie /etc/X11/Xwrapper.config qui doit
>>> avoir needs_root_rights=no (du moins si ta carte graphique le permet).
>>
>> Non, j'ai seulement une ligne non commentée:
>>
>> allowed_users=console
> 
> Ok donc tu dois tourner en root. Vérifie avec un ps aux | grep Xorg
> et si Xorg est en root ajoute needs_root_rights=no dans
> /etc/X11/Xwrapper.config. C'est mieux pour la sécurité.
> Mais ça peut coincer si tu as une carte graphique qui requiert les droits
> root (c'est rare mais il y en a).

Je viens de faire le test, en ajoutant needs_root_rights=no à la fin du
fichier /etc/X11/Xwrapper.config.
Après un arrêt puis un démarrage de la machine, Xorg est toujours lancé
en root. Ma configuration était d'origine et non modifiée ( Xorg n'est
pas lancé depuis une console, mais depuis l'écran graphique de connexion ).

Re: Recommendations for a UPS?

[David]

On Tue, 2023-08-01 at 03:14 -0400, Karl Vogel wrote:
> Liebert

What everybody seems to be doing is catering to surge, when a low spike
can do just as much damage. Both need to be protected against, so any
protective appliance selection has to consider that.
Cheers!

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

Re: OT: Protecting electrical equipment; was: Recommendations for a UPS?

[Michael Kjörling]

On 31 Jul 2023 15:21 -0400, from songb...@anthive.com (songbird):
>   i do not run things for long when the power goes out
> but the capacity for my needs is plenty and then i shut
> down in an orderly fashion.  most of the time i shut down 
> the computer system and unplug the power cord and the 
> network cables and antenna cables if there is a storm 
> coming through - just out of the idea that i don't really 
> want things to get fried.

You can have incoming-mains overvoltage protection installed to
provide a base level of protection for everything electrical against a
mains overvoltage (but generally not other types of power
fluctuations). It's not even all that expensive, or at least wasn't
some years ago. Consider asking your electrician what options would be
available in your particular situation and for a cost estimate or
quote.

Especially if you are in an area that frequently gets lightning, it
_might_ help the UPS last longer, too, since its protective circuitry
then doesn't need to take the brunt of the voltage spike after that is
already well inside your home with all the associated risks.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Recommendations for a UPS?

[Karl Vogel]

>> On Mon, 31 Jul 2023 13:24:36 -0400,
>> Tom Browder  may have said:

> All the reviews I've seen on Amazon for smaller capacity UPSs
> for APC and Tripp Lite are not that great (I usually concentrate
> on the one- and two-star reviews).

> Any recommenndations from fellow Debian folks?
> Thanks.

  I give a solid vote to Liebert.  I had a near-miss lightning strike
  a few nights ago, and all it did was make my display go out for about
  a second.  It came right back, session intact, didn't lose a thing.

--
Karl Vogel / vogelke AT pobox DOT com / I don't speak for anyone at the moment

Why Trick or Treating is Better than Sex #9:
  If you get tired, you can wait 10 minutes and go at it again.

Re: NetworkManager, Iphone, and Bookworm

[didier gaumet]

Le 01/08/2023 à 07:18, didier gaumet a écrit :
[...]
If wpasupplicant is up to date and you still are not able to connect, 
consult le Archlinux wiki, there are instructions to manage WPA3 mixed 
(with WPA2) manually (wpa_cli):

https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE_access_points
https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_mixed_WPA2-PSK/WPA3-SAE_access_points


These parameters are in 
/etc/NetworkManager/system-connections/.nmconnection

(at least on my PC)

Re: [testing] passage du pilote proprio à nouveau

[Michel Verdier]

Le 1 août 2023 Michel a écrit :

>>> Sur ma debian de base, les logs sont bien dans /var/log/Xorg.0.log par
>>> défaut, sans modification de startx ou de  ~/.xsession ...
>> 
>> Ce ne serait pas parce que Xorg est lancé en root ? Par défaut les users
>> n'ont pas accès à /var/log. Vérifie /etc/X11/Xwrapper.config qui doit
>> avoir needs_root_rights=no (du moins si ta carte graphique le permet).
>
> Non, j'ai seulement une ligne non commentée:
>
> allowed_users=console

Ok donc tu dois tourner en root. Vérifie avec un ps aux | grep Xorg
et si Xorg est en root ajoute needs_root_rights=no dans
/etc/X11/Xwrapper.config. C'est mieux pour la sécurité.
Mais ça peut coincer si tu as une carte graphique qui requiert les droits
root (c'est rare mais il y en a).

Re: [testing] passage du pilote proprio à nouveau

[Michel]

Le 01/08/2023 à 07:10, Michel Verdier a écrit :
> Le 31 juillet 2023 Michel a écrit :
> 
>>> Si on modifie startx, ~/.xsession, etc, on peut avoir les logs ailleurs
>>> mais sinon on les a dans ~/.local/share/xorg/Xorg.0.log
>>
>> Sur ma debian de base, les logs sont bien dans /var/log/Xorg.0.log par
>> défaut, sans modification de startx ou de  ~/.xsession ...
> 
> Ce ne serait pas parce que Xorg est lancé en root ? Par défaut les users
> n'ont pas accès à /var/log. Vérifie /etc/X11/Xwrapper.config qui doit
> avoir needs_root_rights=no (du moins si ta carte graphique le permet).

Non, j'ai seulement une ligne non commentée:

allowed_users=console