Re: strange time problem with bullseye

[tomas]

On Wed, Mar 06, 2024 at 09:36:56PM -0500, Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> > no place in the ntpsec docs, nor the chrony docs
> > does it show the ability to slam the current time into the SW clock on these
> > arm systems at bootup's first access time.
> 
> Traditionally, this was done by the ntpdate command, which was in the
> ntpdate package.

[...]

>-g, --panicgate

[...]

Heh. Great minds read alike :-)

But thanks for the historical background, which I didn't know.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: strange time problem with bullseye

[tomas]

On Wed, Mar 06, 2024 at 08:06:15PM -0600, John Hasler wrote:
> Look at the chronyd settime command and the chrony.conf makestep
> directive.  These are intended for your situation.

This from man(8) ntpd:

 -g, --panicgate
   Allow the first adjustment to be Big.  This option may appear an
   unlimited number of times.

   Normally, ntpd exits with a message to the system log if the off‐
   set exceeds the panic threshold, which is 1000 s by default. This
   option allows the time to be set to any value without restric‐
   tion; however, this can happen only once. If the threshold is ex‐
   ceeded after that, ntpd will exit with a message to the system
   log. This option can be used with the -q and -x options.  See the
   tinker configuration file directive for other options.

 -G, --force-step-once
   Step any initial offset correction..
   [...]

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: strange time problem with bullseye

[Greg Wooledge]

On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> no place in the ntpsec docs, nor the chrony docs
> does it show the ability to slam the current time into the SW clock on these
> arm systems at bootup's first access time.

Traditionally, this was done by the ntpdate command, which was in the
ntpdate package.

On older Debian releases, you would install both of these (ntp and
ntpdate); ntpdate would run first, slamming the clock, and then ntp
would run second, to keep the clock in sync.

A few releases ago, ntpdate was deprecated, and its slamming functionality
was absorbed into the ntp package, as long as ntp is started with the -g
option.

   -g, --panicgate
   Allow the first adjustment to be big. This option may appear an
   unlimited number of times.

   Normally, ntpd exits with a message to the system log if the offset
   exceeds the panic threshold, which is 1000 s by default. This
   option allows the time to be set to any value without restriction;
   however, this can happen only once. If the threshold is exceeded
   after that, ntpd will exit with a message to the system log. This
   option can be used with the -q and -x options. See the tinker
   configuration file directive for other options.

With ntpsec replacing ntp in Debian 12, the same options apply.  By default,
Debian runs ntpsec with the -g option, to allow the clock to be slammed
at boot time.

hobbit:~$ ps -ef | grep ntpd
ntpsec   854   1  0 Feb17 ?00:01:17 /usr/sbin/ntpd -p 
/run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
greg  3947371138  0 21:34 pts/000:00:00 grep ntpd

Your claims that "no place in the ntpsec docs ... show the ability to
slam the current time" are simply false.

Re: strange time problem with bullseye

[John Hasler]

Look at the chronyd settime command and the chrony.conf makestep
directive.  These are intended for your situation.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: strange time problem with bullseye

[gene heskett]

On 3/6/24 18:02, Greg Wooledge wrote:

On Wed, Mar 06, 2024 at 05:56:29PM -0500, gene heskett wrote:

On 3/6/24 12:42, Greg Wooledge wrote:

On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:

  sudo timedatectl set-ntp true


But *don't* do that if you're using some other NTP program instead of
systemd-timesyncd.



Are you saying that both chrony and ntpsec, which are fully ntp
client/server ack the docs are worthless to timedatectl?


I'm saying "don't turn on systemd's NTP thing if you're using a different
NTP thing".

Roy's instructions failed to take into account that many of us are
already using a different NTP implementation, besides systemd's.


I can turn either off, but no place in the ntpsec docs, nor the chrony 
docs does it show the ability to slam the current time into the SW clock 
on these arm systems at bootup's first access time.  And the normal 
correction is maybe a second an hour so it its been turned off for a 
week, its another week out of time when turned back on. The whole thing 
never considered the no hwclock situation that exists in 99% of the arm 
world. I was hoping timedatectl had that ability but I see it says you 
must be synched first. The rpis's can do it, whats the secret recipe?


Thank Greg, take care & stay well.
Cheers, Gene Heskett, CET.
--
"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

Re: Firefox et PDF

[Th.A.C]

Le 06/03/2024 à 17:55, ajh-valmer a écrit :

On Wednesday 06 March 2024 12:50:06 Sébastien NOBILI wrote:

je constate que la version 115.8.0-esr Firefox,
marche mal, elle ne sait pas envoyer des formulaires,
ni faire apparaître des images, se bloque à un moment (ça mouline),
il faut le stopper et le ré-ouvrir...
Alors que Chrome n'a pas du tout ces défauts horripilants.
J'estime que Firefox est buggé.



Tout ça fonctionne très bien chez moi. Ça doit plutôt venir d'un
problème de configuration de ton profil.


Oui, mais quel problème de configuration dans les profils ?
J'ai pourtant bien regardé, tenté des choses et rien ne change.



Comme d'habitude, quand on a un problème de profil (ou supposé comme 
tel), il faut:


- consulter l'aide en ligne:
  https://support.mozilla.org/fr/products/firefox/fix-problems

- vider TOUS les caches

- tester en désactivant les extensions/themes/...
  par exemple:
  le mode dépannage qui désactive temporairement les extensions:
  Menu 'Aide' / Mode de dépannage
  ou
  Menu 'Aide' / Plus d'informations de dépannage

- Tester avec un nouveau profil

Tout ca existe et est répété pourtant depuis longtemps...
mais personne n'écoute...

Une simple recherche avec des mots clés comme: firefox probleme profil
te donnera immédiatement tout ce que je viens de te dire et plus encore.

Re: strange time problem with bullseye

[Greg Wooledge]

On Wed, Mar 06, 2024 at 05:56:29PM -0500, gene heskett wrote:
> On 3/6/24 12:42, Greg Wooledge wrote:
> > On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> > >  sudo timedatectl set-ntp true
> > 
> > But *don't* do that if you're using some other NTP program instead of
> > systemd-timesyncd.

> Are you saying that both chrony and ntpsec, which are fully ntp
> client/server ack the docs are worthless to timedatectl?

I'm saying "don't turn on systemd's NTP thing if you're using a different
NTP thing".

Roy's instructions failed to take into account that many of us are
already using a different NTP implementation, besides systemd's.

Re: strange time problem with bullseye

[gene heskett]

On 3/6/24 12:42, Greg Wooledge wrote:

On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:

Mine shows:

   Local time: Wed 2024-03-06 12:09:44 EST
   Universal time: Wed 2024-03-06 17:09:44 UTC
 RTC time: Wed 2024-03-06 17:20:53
Time zone: America/New_York (EST, -0500)
  Network time on: yes
NTP synchronized: no
  RTC in local TZ: no

How do I get the RTC to agree with the right time?


"hwclock -w" to copy the system clock to the hardware clock (RTC).  This
should also be done during shutdown, but it doesn't hurt to do it now.


On Wed, Mar 06, 2024 at 07:36:11PM +0200, Teemu Likonen wrote:

To get operating system's clock have accurate time it needs to be
synchronized with network time servers via network time protocol (NTP).
Systemd has that feature. Turn in on with

 sudo timedatectl set-ntp true


But *don't* do that if you're using some other NTP program instead of
systemd-timesyncd.  Unfortunately, timedatectl does not know about other
NTP programs, and won't report which one you're using.  You'll have
to find that out yourself


Are you saying that both chrony and ntpsec, which are fully ntp 
client/server ack the docs are worthless to timedatectl?


I have a quite good 3d printer, but its running armbian buster, its out 
of synch by days despite ntpsec running and I can see it access my own 
level 2 server but the timedate never synchronizes. I need to know how 
to setup timedatectl to slam the ntp time into the system clock on first 
access at bootup. That would fix a lot of bogus times reported by 
fluidd, the printers web based gui front end.


Thanks Greg. Take care & stay well.

Cheers, Gene Heskett, CET.
--
"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

Re: strange time problem with bullseye

[hlyg]

On 3/6/24 13:37, Teemu Likonen wrote:

It seems that you have solved the problem but here is another hint.
"timedatectl" is a good high-level tool for querying and adjusting time
settings. Without command-line arguments it prints a lot of useful info:

 $ timedatectl
Local time: ke 2024-03-06 07:33:00 EET
Universal time: ke 2024-03-06 05:33:00 UTC
  RTC time: ke 2024-03-06 05:33:00
 Time zone: Europe/Helsinki (EET, +0200)
 System clock synchronized: yes
   NTP service: active
   RTC in local TZ: no

See "timedatectl -h" or manual page for more info.



Thank Likonen, timedatectl is useful, ntp isn't installed

System clock synchronized: no NTP service: n/a RTC in local TZ: no

perhaps it's because i didn't install a set of standard tools during 
deb11 installation

Re: Problema chroot sid

[Alex Muntada]

Hola,

> 2024-03-04 08:20:28 
> URL:http://deb.debian.org/debian/pool/main/z/zlib/zlib1g_1.3.dfsg-3.1_amd64.deb
>  [87580/87580] -> 
> "/srv/chroot/sid//var/cache/apt/archives/partial/zlib1g_1%3a1.3.dfsg-3.1_amd64.deb"
>  [1]
> tar: ./usr/lib/x86_64-linux-gnu/libuuid.so.1.3.0: Cannot open: File exists
> tar: ./usr/lib/x86_64-linux-gnu/libuuid.so.1: Cannot create symlink to 
> 'libuuid.so.1.3.0': File exists
> tar: Exiting with failure status due to previous errors

Ho he tornat a provar ara i l'error era diferent: es queixava
d'una incompatibilitat entre libssl3t64 i libssl3. Això m'ha
fet pensar que, essent sid la versió inestable, potser hi ha
alguna transició en marxa i he trobat això:

https://release.debian.org/transitions/html/auto-openssl.html

> Els primers cops no me'n vaig adonar d'aquest error. Total que he enviat un 
> bug:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065343

He vist que han resolt una part, però segueix fallant el
debootstrap per altres transicions que hi ha en marxa.
Segurament debootstrap no està pensat per utilitzar-se amb
sid, encara que s'utilitzi el de backports, perquè instal·la els
paquets amb dpkg directament enlloc de fer-ho amb apt.

He provat el mmdebstrap que suggereixen al bug i a mi també
m'ha funcionat bé (com deia abans, mmdebstrap utilitza apt per
instal·lar els paquets i aleshores resol millor les dependències
que debootstrap).

> Vols dir que no utilitzes el debootstrap de bookworm-backports?
> No ho entenc, perquè si utilitzo el debootstrap de bookworm en
> lloc del de bookworm-backports a mi me surt el mateix error de
> "Cannot open: File exists".

Perquè el problema està a la resolució de dependències que
comento més amunt en una versió del sistema que és inestable per
les transicions que hi ha constantment:

https://release.debian.org/transitions/

Salut,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

rTorrent: unable to connect to UDP tracker

[Franco Martelli]

Hi everybody,

I'm trying to download some live DVD images using rTorrent,

$ apt show rtorrent

all works fine with Debian's images, I've successfully downloaded:

- debian-12.5.0-amd64-DVD-1.iso
- debian-live-12.5.0-amd64-kde.iso

using their torrent files respectively. I've trouble with KDE NEON 
website ¹  the .torrent downloaded at this URL ²  fails with this error 
message:


"Tracker: [unable to connect to UDP tracker]"

Does it depend on me?

Thanks in advance, kind regards.

¹ https://neon.kde.org/download
² 
https://files.kde.org/neon/images/user/20240304-2101/neon-user-20240304-2101.iso.torrent

--
Franco Martelli

Re: messages on my phone

[Charles Curley]

On Wed, 06 Mar 2024 18:39:17 +
ghe2001  wrote:

> Worst of all, I haven't been able to find out how to delete them :-)

To delete them, press and hold the message. A menu will pop up. Hit
More…. Hit the trash can in the lower left.

If you have a mac, you may be able to delete from it.

-- 
Does anybody read signatures any more?

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

Re: messages on my phone

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



Vast apologies for mis-posting to the list.  Please try to forget you ever saw 
that :-)

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAnBYJl6MW4CZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC
rIwyAABP2wgAwcEs4sgWyLi/w5OHuPzST8yBXJMBeK9FCMWEw2ga9R5BTFJP
zj8/HJTFLedF5fIPr0ADU8IgdiBt6s9xmJZ3sKKAbuUr7z8SulxdSxadsDZ2
U3dLc7+lXIw9CL8USQ823wtQM3LYbBFDldjlR8yfu2aOk79j9nlvzu4fyYKs
f5IGZ2EZ+dYqN7OF+im4f38y5xNGkUxoQ5bxrKARqNGXjFw37yXFZiVzYSbv
vLEIF7XVBTan133neEfiKDzcJuuB9jZmExXaQOQe9uOElNNA12Ajkfdj12t2
lK09d5MjnFgJ2353ArxXfhadb4VcGxBrAJ6qf3eJ7IdPM2Rw6Y742w==
=fnIk
-END PGP SIGNATURE-

Re: strange time problem with bullseye

[David Wright]

On Wed 06 Mar 2024 at 07:07:36 (-0500), Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
> > settings. Without command-line arguments it prints a lot of useful info:
> > 
> > $ timedatectl
> >Local time: ke 2024-03-06 07:33:00 EET
> >Universal time: ke 2024-03-06 05:33:00 UTC
> >  RTC time: ke 2024-03-06 05:33:00
> > Time zone: Europe/Helsinki (EET, +0200)
> > System clock synchronized: yes
> >   NTP service: active
> >   RTC in local TZ: no
> > 
> > See "timedatectl -h" or manual page for more info.
> 
> This is a great hint, but be warned that it doesn't quite know about
> NTP services other than systemd-timesyncd.  If you're running ntpsec,
> for example, it'll simply say:
> 
> System clock synchronized: yes
>   NTP service: n/a

Note also that it only shows the system's time zone, and not
necessarily that of the user running it:

$ timedatectl ; echo ; date
   Local time: Wed 2024-03-06 19:18:58 UTC
   Universal time: Wed 2024-03-06 19:18:58 UTC
 RTC time: Wed 2024-03-06 19:18:58
Time zone: Etc/UTC (UTC, +)
System clock synchronized: yes
  NTP service: active
  RTC in local TZ: no

Wed Mar  6 13:18:58 CST 2024
$ 

Cheers,
David.

Re: distribution archives became unusable

[Darac Marjal]

On 06/03/2024 08:09, Harald Dunkel wrote:

Hi folks,

the repositories listed on https://www.debian.org/distrib/archive have
been signed using expired keys. Unfortunately this page doesn't deal
with this problem.

Do you think this could be improved?


No, I wouldn't have said so. The packages were signed with keys that 
were valid before they were archived. The archive then provides a 
bit-for-bit copy of what was in the repository at that point in time.


If the keys that signed the packages didn't have an expiry, then there'd 
be an opportunity for someone to update (and validly) sign packages 
retroactively.


The fact that the keys /have/ expired should reassure you that the 
archive hasn't been tampered with.





Regards
Harri



OpenPGP_signature.asc
Description: OpenPGP digital signature

messages on my phone

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I'm getting a lot of txt lately on my iPhone.  I suspect the spam from Niki 
Haley will drop off now, but there's a lot of stuff that I think might be from 
some of you guys.  This morning there was talk from area code 713 talking about 
something called Cajun House (or Cajun Street) in Tomball and mentioning how 
Karen likes the grits, and a couple from area code 281 containg Joel's 
copyright "10-4" with a thumbs-up emoji.  Lots of others from 281 too.

If it's one or more of you folks, could you please make it stop?  When they 
come in, my AppleWatch buzzes on my wrist like it does when it wants to give me 
a flood or snow warning or something.

Worst of all, I haven't been able to find out how to delete them :-)

--
Glenn English
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAnBYJl6LgyCZDmyitW0WqrdxYhBMRG7aHlwXhPX67r9+bKK1bR
aqt3AABrwgf/ebRLGHeIjowXSidpdWL3hsw7dLY/pA0OhrESeehY0N2OG/ED
F/cR6X/OJVeLMETsezG2ccv3nyJl1QD3AsxfrWogGchtvJ0osb9zvdpzu7yO
U8gmZEyB964A7r9sC2nlLf3B9FbpBVEFCeCXlll6yjZpjaQxIMaTk7E5S6VM
whq6DHgIS5gEyZCap6vrs6Cx/sfpQ2+K2qYdV6KjvZuJym4cbisLLpFXSCzY
wX30eDecHhK1vUJ70toi9g319w4kLtKe0XIsdXuhSTEEZc9xtVYzSpJ/dNhp
y2sfi8FN/aD+yqd10sA8W83V74y9Uz8aIUZerG2QwyRaEnBZG8NJIg==
=WKv1
-END PGP SIGNATURE-

Re: strange time problem with bullseye

[Jeffrey Walton]

On Wed, Mar 6, 2024 at 7:08 AM Greg Wooledge  wrote:
>
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
> > settings. Without command-line arguments it prints a lot of useful info:
> >
> > $ timedatectl
> >Local time: ke 2024-03-06 07:33:00 EET
> >Universal time: ke 2024-03-06 05:33:00 UTC
> >  RTC time: ke 2024-03-06 05:33:00
> > Time zone: Europe/Helsinki (EET, +0200)
> > System clock synchronized: yes
> >   NTP service: active
> >   RTC in local TZ: no
> >
> > See "timedatectl -h" or manual page for more info.
>
> This is a great hint, but be warned that it doesn't quite know about
> NTP services other than systemd-timesyncd.  If you're running ntpsec,
> for example, it'll simply say:
>
> System clock synchronized: yes
>   NTP service: n/a

This may help in the future:
.

Jeff

Re: Question about what package to report bug

[Erwan David]

Le 06/03/2024 à 18:19, ke6jti a écrit :

Hi,

I have a possible kernel regression for a usb-dvb tuner card.  I know 
the error in dmesg points to kernel : au0828 but I am not sure what 
package this belongs to.  I think it belongs to v4l(video for linux) 
but I am still not sure what specific v4l package.



Thanks for you help.


apt-file shows au0828.ko comes in the linux-image-* packages. So report 
the bug for the one you use.

Question about what package to report bug

[ke6jti]

Hi,

I have a possible kernel regression for a usb-dvb tuner card.  I know 
the error in dmesg points to kernel : au0828 but I am not sure what 
package this belongs to.  I think it belongs to v4l(video for linux) but 
I am still not sure what specific v4l package.



Thanks for you help.

Re: strange time problem with bullseye

[Jeffrey Walton]

On Wed, Mar 6, 2024 at 12:13 PM Roy J. Tellason, Sr.  wrote:
>
> On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote:
> > * 2024-03-06 02:47:06+0800, hlyg wrote:
> >
> > > my newly-installed deb11 for amd64 shows wrong time,  it lags behind
> > > correct time by 8 hours though difference between universal and local
> > > is ok.
> >
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
> > settings. Without command-line arguments it prints a lot of useful info:
> >
> > $ timedatectl
> >Local time: ke 2024-03-06 07:33:00 EET
> >Universal time: ke 2024-03-06 05:33:00 UTC
> >  RTC time: ke 2024-03-06 05:33:00
> > Time zone: Europe/Helsinki (EET, +0200)
> > System clock synchronized: yes
> >   NTP service: active
> >   RTC in local TZ: no
> >
> > See "timedatectl -h" or manual page for more info.
> >
>
> Mine shows:
>
>   Local time: Wed 2024-03-06 12:09:44 EST
>   Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
>  Network time on: yes
> NTP synchronized: no
>  RTC in local TZ: no
>
> How do I get the RTC to agree with the right time?  I don't reboot this 
> often,  but when I do the time displayed on the onscreen clock is typically 
> off by several minutes.

Install ntp, ntpsec or systemd-timesyncd. Once installed and time is
sync'd, run 'sudo hwclock -w'.

Also see  and
.

Jeff

Re: strange time problem with bullseye

[Greg Wooledge]

On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> Mine shows:
> 
>   Local time: Wed 2024-03-06 12:09:44 EST
>   Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
>  Network time on: yes
> NTP synchronized: no
>  RTC in local TZ: no
> 
> How do I get the RTC to agree with the right time?

"hwclock -w" to copy the system clock to the hardware clock (RTC).  This
should also be done during shutdown, but it doesn't hurt to do it now.


On Wed, Mar 06, 2024 at 07:36:11PM +0200, Teemu Likonen wrote:
> To get operating system's clock have accurate time it needs to be
> synchronized with network time servers via network time protocol (NTP).
> Systemd has that feature. Turn in on with
> 
> sudo timedatectl set-ntp true

But *don't* do that if you're using some other NTP program instead of
systemd-timesyncd.  Unfortunately, timedatectl does not know about other
NTP programs, and won't report which one you're using.  You'll have
to find that out yourself.

Re: strange time problem with bullseye

[Teemu Likonen]

* 2024-03-06 12:31:46-0500, Roy J. Tellason, Sr. wrote:

>   Local time: Wed 2024-03-06 12:09:44 EST
>   Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
>  Network time on: yes
> NTP synchronized: no
>  RTC in local TZ: no
>
> How do I get the RTC to agree with the right time? I don't reboot this
> often, but when I do the time displayed on the onscreen clock is
> typically off by several minutes.

RTC is the clock on computer's motherboard. It has battery and it can
keep time when the computer is off. That's its purpose. When computer is
shut down the operating system saves its time to RTC. When computer is
booted operating system reads RTC time and sets operating system's
clock. The time is not accurate but at very least it's something instead
of random time. When operating system is running RTC does not matter
anymore.

To get operating system's clock have accurate time it needs to be
synchronized with network time servers via network time protocol (NTP).
Systemd has that feature. Turn in on with

sudo timedatectl set-ntp true

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462


signature.asc
Description: PGP signature

Re: Spam from the list?

[debian-user]

Hans  wrote:
> HI Brad,
> 
> I do not believe, it is a training problem. Why? Well, your formerly
> mail was marked as spam. So I marked it as ham. Now, your second mail
> again is marked as spam. 
> 
> We know, there is nothing unusual with your mail, but it is again
> marked as spam. Even, when I explicity marked your mails as ham! 
> 
> Thus the problem is not on my computer. 
> 
> I believe, what Thomas said: Megamail or my mailprovider is setting
> the X- Spam-Flag to YES, and my spamassassin is recognizing this and
> marks this as spam.
> 
> The solution would be, either to make megamails or my provider make
> things correctly (but I have no atom bombs to force them) , or delete
> my rule, to check the X-Spam-Flag (which I actually do not want). 

You don't need an atom bomb. Simply contact their support and tell them
they appear to be misclassifying mail. If they don't fix the problem
then consider changing your provider. Or at least tell them you will :)

Also they are still sending the mail to you, so it is your choice
whether to actually classify it as spam! Look at your mail program and
see what options it has regarding classifying spam. Change it to not
respect the particular header you think is causing problems.

> Important is: The cause is not at debian server (which is fine!) and
> not on my system (which is also fine), but on the provider server. 
> 
> To know this, I think we can safely close this issue.
> 
> We have learnt some things (which is always important) and could find
> the reason.
> 
> Thank you all for your help and input!!

Re: strange time problem with bullseye

[Roy J. Tellason, Sr.]

On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote:
> * 2024-03-06 02:47:06+0800, hlyg wrote:
> 
> > my newly-installed deb11 for amd64 shows wrong time,  it lags behind
> > correct time by 8 hours though difference between universal and local
> > is ok.
> 
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a lot of useful info:
> 
> $ timedatectl
>Local time: ke 2024-03-06 07:33:00 EET
>Universal time: ke 2024-03-06 05:33:00 UTC
>  RTC time: ke 2024-03-06 05:33:00
> Time zone: Europe/Helsinki (EET, +0200)
> System clock synchronized: yes
>   NTP service: active
>   RTC in local TZ: no
> 
> See "timedatectl -h" or manual page for more info.
> 

Mine shows:

  Local time: Wed 2024-03-06 12:09:44 EST
  Universal time: Wed 2024-03-06 17:09:44 UTC
RTC time: Wed 2024-03-06 17:20:53
   Time zone: America/New_York (EST, -0500)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: no

How do I get the RTC to agree with the right time?  I don't reboot this often,  
but when I do the time displayed on the onscreen clock is typically off by 
several minutes.

-- 
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: Firefox et PDF

[ajh-valmer]

On Wednesday 06 March 2024 12:50:06 Sébastien NOBILI wrote:
> > je constate que la version 115.8.0-esr Firefox,
> > marche mal, elle ne sait pas envoyer des formulaires,
> > ni faire apparaître des images, se bloque à un moment (ça mouline),
> > il faut le stopper et le ré-ouvrir...
> > Alors que Chrome n'a pas du tout ces défauts horripilants.
> > J'estime que Firefox est buggé.

> Tout ça fonctionne très bien chez moi. Ça doit plutôt venir d'un
> problème de configuration de ton profil.

Oui, mais quel problème de configuration dans les profils ?
J'ai pourtant bien regardé, tenté des choses et rien ne change.

Re: ldap_result() failed: Can't contact LDAP server

[Dan Ritter]

Shaheena Kazi wrote: 
> Package: nslcd
> 
> I have upgraded from Debian 11 to Debian 12.
> 
> The problem is that I keep getting the below errors in the syslog...
> 893:2024-02-29T16:30:13.055665+00:00 hostname-shaheena nslcd[7712]:
> [d062c2]  ldap_start_tls_s() failed (uri=ldap://
> 127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not
> connected

nslcd is expecting to reach an LDAP server that sits on the same
machine (127.0.0.1 means "me") and it can't.

This probably means that there is no LDAP server running on the
same machine.

> binddn cn=ldap_login,ou=people,dc=subdomain,dc=domain,dc=com
> bindpw xxx
> ldap_version 3
> base ou=people,dc=subdomain,dc=domain,dc=com

Are those literal values, or did you obfucate them?

Do you think that you are running an LDAP server?

-dsr-

ldap_result() failed: Can't contact LDAP server

[Shaheena Kazi]

Package: nslcd

I have upgraded from Debian 11 to Debian 12.

The problem is that I keep getting the below errors in the syslog...
893:2024-02-29T16:30:13.055665+00:00 hostname-shaheena nslcd[7712]:
[d062c2]  ldap_start_tls_s() failed (uri=ldap://
127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not
connected
894:2024-02-29T16:30:13.055747+00:00 hostname-shaheena nslcd[7712]:
[d062c2]  failed to bind to LDAP server ldap://
127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not
connected
1423:2024-03-01T09:08:08.473189+00:00 hostname-shaheena nslcd[24301]:
[8b4567]  ldap_start_tls_s() failed (uri=ldap://
127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not
connected
1424:2024-03-01T09:08:08.473204+00:00 hostname-shaheena nslcd[24301]:
[8b4567]  failed to bind to LDAP server ldap://
127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not
connected
1648:2024-03-01T09:09:08.556456+00:00 hostname-shaheena nslcd[36935]:
[8b4567]  ldap_start_tls_s() failed (uri=ldap://
127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not
connected
1649:2024-03-01T09:09:08.556475+00:00 hostname-shaheena nslcd[36935]:
[8b4567]  failed to bind to LDAP server ldap://
127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not
connected
1651:2024-03-01T09:09:08.668341+00:00 hostname-shaheena nslcd[36935]:
[7b23c6]  ldap_start_tls_s() failed (uri=ldap://
127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not
connected
1652:2024-03-01T09:09:08.668363+00:00 hostname-shaheena nslcd[36935]:
[7b23c6]  failed to bind to LDAP server ldap://
127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not
connected

My nslcd.conf looks like below:
# /etc/nslcd.conf
# nslcd configuration file. See nslcd.conf(5)
# for details.

# The user and group nslcd should run as.
uid nslcd
gid nslcd

uri ldap://127.0.0.1:389/
binddn cn=ldap_login,ou=people,dc=subdomain,dc=domain,dc=com
bindpw xxx
ldap_version 3
base ou=people,dc=subdomain,dc=domain,dc=com
ssl start_tls
tls_reqcert never


cat /etc/nsswitch.conf
# /etc/nsswitch.conf


gshadow:files

hosts:  files dns
networks:   files

protocols:  db files
services:   db files
ethers: db files
rpc:db files


passwd:compat ldap
group: compat ldap
shadow:compat ldap
netgroup:  nis ldap

All the services are up and running fine. Only thing is I am not able to
figure out what is causing these messages in the syslog.
Can u guys help me understand this ?

Re: 404 Not Found Error Problem

[Stephen P. Molnar]

On 03/06/2024 09:09 AM, Greg Wooledge wrote:

On Wed, Mar 06, 2024 at 08:21:11AM -0500, Stephen P. Molnar wrote:

Not Found

The requested URL was not found on this server.
Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80

I've installed WebMO a number of times and have not encountered this
particular problem before.

Are you "abnormal.att.net"?  Or at least pretending to be that host
in your error messages?

Or is your web browser going to that host, when you expected it to go
to localhost or something?

When I went to abnormal.att.net there was an index.html in /var/www/html 
that opened with the message that the installation was correct and that 
the index.hml should be removed.


After I deleted the file WebMO opened!

Problem solved.

Many thanks for your reply.

--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: Spam from the list?

[Brad Rogers]

On Wed, 06 Mar 2024 15:36:25 +0100
Hans  wrote:

Hello Hans,

>I do not believe, it is a training problem. Why? Well, your formerly
>mail was marked as spam. So I marked it as ham. Now, your second mail
>again is marked as spam. 

Spam/ham training is not, IME, a single shot affair.  However, as you go
on to say, this particular issue is in all likelihood due to forces
outside of our control.

At which point, I'll hand over to people far more experienced than I.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
You criticize us, you say we're sh*t, but we're up here doin' it
We're The League - Anti-Nowhere League


pgpPJCjXv8hya.pgp
Description: OpenPGP digital signature

Re: Spam from the list?

[Hans]

HI Brad,

I do not believe, it is a training problem. Why? Well, your formerly mail was 
marked as spam. So I marked it as ham. Now, your second mail again is marked 
as spam. 

We know, there is nothing unusual with your mail, but it is again marked as 
spam. Even, when I explicity marked your mails as ham! 

Thus the problem is not on my computer. 

I believe, what Thomas said: Megamail or my mailprovider is setting the X-
Spam-Flag to YES, and my spamassassin is recognizing this and marks this as 
spam.

The solution would be, either to make megamails or my provider make things 
correctly (but I have no atom bombs to force them) , or delete my rule, to 
check the X-Spam-Flag (which I actually do not want). 

Important is: The cause is not at debian server (which is fine!) and not on my 
system (which is also fine), but on the provider server. 

To know this, I think we can safely close this issue.

We have learnt some things (which is always important) and could find the 
reason.

Thank you all for your help and input!!

Best regards

Hans


Am Mittwoch, 6. März 2024, 14:24:19 CET schrieb Brad Rogers:
> On Wed, 06 Mar 2024 13:53:49 +0100
> Hans  wrote:
> 
> Hello Hans,
> 
> >It should be well trained
> 
> Spam training is an ongoing process
> 
> >But until then suddenly the false positives increased from one day to
> >another, although I had changed nothing.
> 
> because the spam changes.  What's coming now is new, and SA has not
> seen it before.  You have to train it.  Equally, what you consider ham
> can change - for example, when you subscribe to a new mailing list that
> caters to a subject not encountered by you before because of, say, taking
> up a new hobby.
> 
> I've been using my spam filtering set up for years too, and I still get
> the occasional false positive.  I mark them as ham to (hopefully)
> improve spam filtering here.

Re: 404 Not Found Error Problem

[Greg Wooledge]

On Wed, Mar 06, 2024 at 08:21:11AM -0500, Stephen P. Molnar wrote:
> Not Found
> 
> The requested URL was not found on this server.
> Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80
> 
> I've installed WebMO a number of times and have not encountered this
> particular problem before.

Are you "abnormal.att.net"?  Or at least pretending to be that host
in your error messages?

Or is your web browser going to that host, when you expected it to go
to localhost or something?

Re: Spam from the list?

[Brad Rogers]

On Wed, 06 Mar 2024 13:53:49 +0100
Hans  wrote:

Hello Hans,

>It should be well trained

Spam training is an ongoing process

>But until then suddenly the false positives increased from one day to
>another, although I had changed nothing.

because the spam changes.  What's coming now is new, and SA has not
seen it before.  You have to train it.  Equally, what you consider ham
can change - for example, when you subscribe to a new mailing list that
caters to a subject not encountered by you before because of, say, taking
up a new hobby.

I've been using my spam filtering set up for years too, and I still get
the occasional false positive.  I mark them as ham to (hopefully)
improve spam filtering here.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
If you ain't sticking your knives in me, you will be eventually
Monsoon - Robbie Williams


pgpW7BRD_vUWU.pgp
Description: OpenPGP digital signature

[Resolu] Re: Firefox et PDF

[Thierry]

Merci à tous pour vos réponses.
Cela m'a amené à faire d'autres tests et le problème ne se produit que 
sur un document particulier. Sans doute un pb de formatage de ce 
document qui fait planter le plugin?

Désolé pour le bruit pour un pb somme toute mineur.

Le 06/03/2024 à 13:02, Bureau LxVx a écrit :

No problème de mon côté non plus :-D

Le 06/03/2024 à 12:50, Sébastien NOBILI a écrit :

Bonjour,

Le 2024-03-06 12:38, ajh-valmer a écrit :

Désolé, je ne réponds pas au problème,
mais je constate que la version 115.8.0-esr Firefox,
marche mal, elle ne sait pas envoyer des formulaires,
ni faire apparaître des images, se bloque à un moment (ça mouline),
il faut le stopper et le ré-ouvrir...
Alors que Chrome n'a pas du tout ces défauts horripilants.
J'estime que Firefox est buggé.


Tout ça fonctionne très bien chez moi. Ça doit plutôt venir d'un
problème de configuration de ton profil.

Sébastien

Re: *****SPAM***** Re: Spam from the list?

[Nicolas George]

Hans (12024-03-06):
> I am using this spamfilter now for several years. It should be well trained 
> and 
> almost until about 4 months I never had any problems with it.

Hi.

It is probably not the reason for you problem now, but it is important
to note that in the “several years” since your spam filter was trained,
spammers have not stayed idle, they have learned, they have refined
their mail to bypass the most common protections. And in turn,
protections have evolved to fight the new stealthiness of spammers.

Spammers also have changed topics, they used to sell pills, now they
sell cryptocurrencies. If your Bayesian filter is trained to recognize
mails that sell pills, they might accept mails that seem to talk about
technical points of computing.

So if your own mail filter has not evolved, it is not surprising that it
becomes progressively less efficient.

> Am Mittwoch, 6. März 2024, 12:22:53 CET schrieb Brad Rogers:

Please remember not to top-post.

Regards,

-- 
  Nicolas George

Re: 404 Not Found Error Problem

[Marco Moock]

Am 06.03.2024 schrieb "Stephen P. Molnar" :

> The requested URL was not found on this server.
> Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80

Check the apache config.
What is the Webroot?

Is the file you are looking for available in the webroot?

Re: Spam from the list?

[Thomas Schmitt]

Hi,

Hans wrote:
> Re: *SPAM* Re: Spam from the list?
> In-Reply-To: <20240306112253.55e25...@earth.stargate.org.uk>

referring the mail

> > Date: Wed, 6 Mar 2024 11:22:53 +
> > From: Brad Rogers 
> > Message-ID: <20240306112253.55e25...@earth.stargate.org.uk>

I assume that this mail appeared with the "*SPAM*" marker in
your mailbox.
(The currently most plausible theory is that megamailservers.eu adds
"X-Spam-Flag: YES" and your local mail processing takes this header as
reason to change the subject.)

So what does the mail which you received from Brad via debian-user
say about "Authentication-Results:" ?
Your initial post quoted three such headers. Expect more than one.


Have a nice day :)

Thomas

404 Not Found Error Problem

[Stephen P. Molnar]

I am running a new installation of Bookworm and have encountered a 404 
Not Found error problem with WebMO (https://www.webmo.net):


Not Found

The requested URL was not found on this server.
Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80

I've installed WebMO a number of times and have not encountered this 
particular problem before. There are complete installation instruction 
on the web page The installation process did not generate any warning or 
error messages. In fact a diagnose.html file is generated (attached) and 
shows no problems.


--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

<<< text/html; charset=UTF-8; name="diagnose.html": Unrecognized >>>

Re: *****SPAM***** Re: Spam from the list?

[tomas]

On Wed, Mar 06, 2024 at 01:53:49PM +0100, Hans wrote:
> Hi Brad,
> 
> I am using this spamfilter now for several years. It should be well trained 
> and 
> almost until about 4 months I never had any problems with it.
> 
> But until then suddenly the false positives increased from one day to 
> another, 
> although I had changed nothing. 

You keep saying that. Your mail provider seems to have changed something.
Your spamassassin is seeing those new headers (which, by all comments in
this thread are being added on the way from the mailing list to you)
and acts accordingly.

So nothing weird. Except, perhaps, your mail provider. There are few of
them which are not weird these days.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: *****SPAM***** Re: Spam from the list?

[Hans]

Hi Brad,

I am using this spamfilter now for several years. It should be well trained and 
almost until about 4 months I never had any problems with it.

But until then suddenly the false positives increased from one day to another, 
although I had changed nothing. 

And weired: It happened only with mails from the debian forum! This looks 
weired for me. Other spammails are still well recognized and I get no false 
positives from any other site. 

Maybe this is by chance. But mails, which are recognized as spam are looking 
not fishy in any kind. Even a mail sent by myself to the forum was seen as 
spam.

Of course there is the option, that my own spamfilter has changed, although I 
did nothing manually, it could not be excluded.

I do not believe, it is is a training model, but of course, i will mark white 
mails as ham manually and see, if the false positives decrease.

Will inform you again in a few days.

Best 

Hans



Am Mittwoch, 6. März 2024, 12:22:53 CET schrieb Brad Rogers:
> On Wed, 06 Mar 2024 11:19:27 +0100
> Hans  wrote:
> 
> Hello Hans,
> 
> >Does one see any reason, why this is considered as spam???
> 
> Further to what Thomas says;  You haven't told your spam filtering that
> it's ham.  If you don't train your spam filters, it's never going to get
> any better at detecting what you consider to be ham/spam.

Re: Spam from the list?

[debian-user]

Hans  wrote:
> Hi Thomas,
> 
> > you perhaps subscribed to one of the "Resent-*" lists ?
> >  
> Not as far as I know.
>  
> > > Subject: *SPAM* Bug#1065537: ITP: bleak-retry-connector --
> > > Connector for Bleak Clients that handles transient connection
> > > failures  
> > 
> > The mark "*SPAM*" does not appear in the archive
> >   
> 
> This line is set by spamassassin on my own computer, when a spam mail
> is marked as spam. Then it will be filtered out. But I can not see,
> WHJY it is recognised as apam!
> 
> >   https://lists.debian.org/debian-devel/2024/03/msg00076.html
> > 
> > All in all it looks like a legit message, not like spam.
> > So the suspect would sit after Debian's mail servers.
> > 
> > The only Received header i see between Debian and you is:  
> > > Received: from bendel.debian.org (bendel.debian.org
> > > [82.195.75.100])
> > > 
> > > by mail104c50.megamailservers.eu (8.14.9/8.13.1) with
> > > ESMTP id 4269vZOl098298
> > > for ; Wed, 6 Mar 2024 09:57:37
> > > +  
> > 
> > It looks like either megamailservers.eu or your own processing added
> > the spam mark to the subject.
> >   
> Hmm, suspicious. I changed nothing and suddenly many mails from
> debian-user (but not all, only some) are recognized as spam. And I
> can not see, why they are. Thre are no URLs in it, no suspicous gifs
> or any other content. Just quite normal mails. And some are flagged
> as spam, some not. Weired.

So if it's not you, then it sounds like you need to ask
megamailservers.eu why.

Re: Spam from the list?

[Brad Rogers]

On Wed, 06 Mar 2024 11:19:27 +0100
Hans  wrote:

Hello Hans,

>Does one see any reason, why this is considered as spam???

Further to what Thomas says;  You haven't told your spam filtering that
it's ham.  If you don't train your spam filters, it's never going to get
any better at detecting what you consider to be ham/spam.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
People stare like they've seen a ghost
Titanic (My Over) Reaction - 999


pgp8hb40F8jjN.pgp
Description: OpenPGP digital signature

Re: strange time problem with bullseye

[Greg Wooledge]

On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a lot of useful info:
> 
> $ timedatectl
>Local time: ke 2024-03-06 07:33:00 EET
>Universal time: ke 2024-03-06 05:33:00 UTC
>  RTC time: ke 2024-03-06 05:33:00
> Time zone: Europe/Helsinki (EET, +0200)
> System clock synchronized: yes
>   NTP service: active
>   RTC in local TZ: no
> 
> See "timedatectl -h" or manual page for more info.

This is a great hint, but be warned that it doesn't quite know about
NTP services other than systemd-timesyncd.  If you're running ntpsec,
for example, it'll simply say:

System clock synchronized: yes
  NTP service: n/a

Re: Firefox et PDF

[Bureau LxVx]

No problème de mon côté non plus :-D

Le 06/03/2024 à 12:50, Sébastien NOBILI a écrit :

Bonjour,

Le 2024-03-06 12:38, ajh-valmer a écrit :

Désolé, je ne réponds pas au problème,
mais je constate que la version 115.8.0-esr Firefox,
marche mal, elle ne sait pas envoyer des formulaires,
ni faire apparaître des images, se bloque à un moment (ça mouline),
il faut le stopper et le ré-ouvrir...
Alors que Chrome n'a pas du tout ces défauts horripilants.
J'estime que Firefox est buggé.


Tout ça fonctionne très bien chez moi. Ça doit plutôt venir d'un
problème de configuration de ton profil.

Sébastien

Re: Spam from the list?

[Thomas Schmitt]

Hi,

Hans wrote:
> I changed nothing and suddenly many mails from debian-user
> (but not all, only some) are recognized as spam.

But the one you posted here did not come from debian-user.

So maybe what changed is an inadverted subscription to one of
  debian-bugs-d...@lists.debian.org
  debian-de...@lists.debian.org
  debian-pyt...@lists.debian.org,
  w...@debian.org
This might have broadened the set of mail senders and thus gives your
mail provider opportunities to complain like spotted by Dan Ritter:

> Authentication-Results: mail104c50.megamailservers.eu;
>   dkim=fail reason="signature verification failed" (4096-bit key)
> header.d=4angle.com header.i=@4angle.com header.b="bS+3bWmq"

"4angle.com" matches the mail address of the bug submitter
"Edward Betts ".


The shown message headers offer unsubscription from debian-devel:

> List-Unsubscribe: 
> 

I.e. to send a mail to debian-devel-requ...@lists.debian.org with the
subject line
  unsubscribe


Have a nice day :)

Thomas

Re: Firefox et PDF

[Sébastien NOBILI]

Bonjour,

Le 2024-03-06 12:38, ajh-valmer a écrit :

Désolé, je ne réponds pas au problème,
mais je constate que la version 115.8.0-esr Firefox,
marche mal, elle ne sait pas envoyer des formulaires,
ni faire apparaître des images, se bloque à un moment (ça mouline),
il faut le stopper et le ré-ouvrir...
Alors que Chrome n'a pas du tout ces défauts horripilants.
J'estime que Firefox est buggé.


Tout ça fonctionne très bien chez moi. Ça doit plutôt venir d'un
problème de configuration de ton profil.

Sébastien

Re: Spam from the list?

[Hans]

Am Mittwoch, 6. März 2024, 12:10:57 CET schrieb Dan Ritter:

> > 
> >  X-Spam-Flag: YES
> > 
> > X-SPAM-FACTOR: DKIM
> 
> What sets these two headers?
> 

I do not know. So I asked on this list.

What I believe is, that the X-Spam-Flag: YES is set somehow on the way and as 
spamassin is looking at that is marking the mail as spam. 

The question is: Where and why is this flag set? Maybe because of the DKIM 
failure? 

Sorry, I do not know, and maybe you are right: It might be a problem with 
megamailservers, who knows.

Best

Hans

Re: Firefox et PDF

[ajh-valmer]

On Tuesday 05 March 2024 16:50:44 Thierry wrote:
> depuis la mise à jour dans la version 115.8.0esr (testing), je reçois le 
> message suivant à l'ouverture d'un PDF:
> "Votre navigateur ne comprend pas de plugin de lecture de PDF"
> Quelqu'un a t'il rencontré ce problème? (pas très gênant par ailleurs 
> puisqu'il suffit de télécharger le PDF pour le lire)

Désolé, je ne réponds pas au problème,
mais je constate que la version 115.8.0-esr Firefox,
marche mal, elle ne sait pas envoyer des formulaires,
ni faire apparaître des images, se bloque à un moment (ça mouline),
il faut le stopper et le ré-ouvrir...
Alors que Chrome n'a pas du tout ces défauts horripilants.
J'estime que Firefox est buggé.

Re: Spam from the list?

[Hans]

Hi Thomas,

> you perhaps subscribed to one of the "Resent-*" lists ?
>
Not as far as I know.
 
> > Subject: *SPAM* Bug#1065537: ITP: bleak-retry-connector --
> > Connector for Bleak Clients that handles transient connection failures
> 
> The mark "*SPAM*" does not appear in the archive
> 

This line is set by spamassassin on my own computer, when a spam mail is 
marked as spam. Then it will be filtered out. But I can not see, WHJY it is 
recognised as apam!

>   https://lists.debian.org/debian-devel/2024/03/msg00076.html
> 
> All in all it looks like a legit message, not like spam.
> So the suspect would sit after Debian's mail servers.
> 
> The only Received header i see between Debian and you is:
> > Received: from bendel.debian.org (bendel.debian.org [82.195.75.100])
> > 
> > by mail104c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP
> > id 4269vZOl098298
> > for ; Wed, 6 Mar 2024 09:57:37 +
> 
> It looks like either megamailservers.eu or your own processing added
> the spam mark to the subject.
> 
Hmm, suspicious. I changed nothing and suddenly many mails from debian-user 
(but not all, only some) are recognized as spam. And I can not see, why they 
are. Thre are no URLs in it, no suspicous gifs or any other content. Just 
quite normal mails. And some are flagged as spam, some not. Weired.

> 
> Have a nice day :)
> 
> Thomas


Best

Hans

Re: Spam from the list?

[Dan Ritter]

Hans wrote: 
> Hi folks,
> 
> during the last moonths I get more mails from the debian-user list marked as 
> spam than before. Something must have changed.
> 
> I examined the header of the mails, but did not see any unusual.
> 
> Below I send the header of an example of such a mail, maybe you can see the 
> reason?
> 
> On my computer I am also using spamassassin, and my own score is set to 3.4, 
> so even so it should not considered as spam. 
> 
>  X-Spam-Flag: YES
> X-SPAM-FACTOR: DKIM

What sets these two headers?


> Authentication-Results: mail104c50.megamailservers.eu;
>   dkim=fail reason="signature verification failed" (4096-bit key) 
> header.d=4angle.com header.i=@4angle.com header.b="bS+3bWmq"

That's the source of the DKIM fail.

> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bendel.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-6.7 required=4.0 tests=BODY_INCLUDES_PACKAGE,
>   
> DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,LDO_WHITELIST,
>   T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no
>   version=3.4.2

This is debian.org's mailserver checking for spam and deciding that it isn't,
even though DKIM is invalid.

> X-Virus-Scanned: at lists.debian.org with policy bank en-ht
> X-Amavis-Spam-Status: No, score=-8.561 tagged_above=-1 required=5.3
>   tests=[BAYES_00=-2, BODY_INCLUDES_PACKAGE=-2, DKIM_INVALID=0.1,
>   DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249,
>   LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01]
>   autolearn=ham autolearn_force=no

This is debian.org again.

> X-Bogosity: Ham, tests=bogofilter, spamicity=0.053994, version=1.2.5
> 
> --- snap ---
> 
> Does one see any reason, why this is considered as spam???

Whatever set X-SPAM-FLAG: YES is probably at fault.

-dsr-

Re: Spam from the list?

[Thomas Schmitt]

Hi,

Hans wrote:
> during the last moonths I get more mails from the debian-user list marked as
> spam than before.
> [...]
> Below I send the header of an example of such a mail, maybe you can see the
> reason?

The message does not look like it came to you via debian-user:

> X-Original-To: lists-debian-de...@bendel.debian.org
> Delivered-To: lists-debian-de...@bendel.debian.org
> Received: from localhost (localhost [127.0.0.1])
> by bendel.debian.org (Postfix) with ESMTP id B720220598
> for ; Wed,  6 Mar 2024
> [...]
> Resent-To: debian-bugs-d...@lists.debian.org
> Resent-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org,
> w...@debian.org

Are you perhaps subscribed to one of the "Resent-*" lists ?


> Subject: *SPAM* Bug#1065537: ITP: bleak-retry-connector -- Connector
> for Bleak Clients that handles transient connection failures

The mark "*SPAM*" does not appear in the archive

  https://lists.debian.org/debian-devel/2024/03/msg00076.html

All in all it looks like a legit message, not like spam.
So the suspect would sit after Debian's mail servers.


The only Received header i see between Debian and you is:

> Received: from bendel.debian.org (bendel.debian.org [82.195.75.100])
> by mail104c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP
> id 4269vZOl098298
> for ; Wed, 6 Mar 2024 09:57:37 +

It looks like either megamailservers.eu or your own processing added
the spam mark to the subject.


Have a nice day :)

Thomas

Re: Firefox et PDF

[Bureau LxVx]

Bonjour


puisqu'il suffit de télécharger le PDF pour le lire

En effet en paramétrant Ffx pour l'ouverture des fichiers :
Rubrique "Général" >>> "Applications" (bas de page).
 :-D

@pluX ;-)


Le 05/03/2024 à 16:50, Thierry a écrit :

Bonjour,

depuis la mise à jour dans la version 115.8.0esr (testing), je reçois 
le message suivant à l'ouverture d'un PDF:

"Votre navigateur ne comprend pas de plugin de lecture de PDF"

Quelqu'un a t'il rencontré ce problème? (pas très gênant par ailleurs 
puisqu'il suffit de télécharger le PDF pour le lire)


Merci.

Spam from the list?

[Hans]

Hi folks,

during the last moonths I get more mails from the debian-user list marked as 
spam than before. Something must have changed.

I examined the header of the mails, but did not see any unusual.

Below I send the header of an example of such a mail, maybe you can see the 
reason?

On my computer I am also using spamassassin, and my own score is set to 3.4, 
so even so it should not considered as spam. 

Thisis the header:

--- snip ---

 X-Spam-Flag: YES
X-SPAM-FACTOR: DKIM
X-Envelope-From: bounce-debian-devel=hans.ullrich=loop...@lists.debian.org
DMARC-Filter: OpenDMARC Filter v1.4.1 mail104c50.megamailservers.eu 
4269vZOl098298
Authentication-Results: mail104c50.megamailservers.eu; dmarc=fail (p=reject 
dis=none) header.from=4angle.com
Authentication-Results: mail104c50.megamailservers.eu; spf=none 
smtp.mailfrom=lists.debian.org
Authentication-Results: mail104c50.megamailservers.eu;
dkim=fail reason="signature verification failed" (4096-bit key) 
header.d=4angle.com header.i=@4angle.com header.b="bS+3bWmq"
Return-Path: 
Received: from bendel.debian.org (bendel.debian.org [82.195.75.100])
by mail104c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 
4269vZOl098298
for ; Wed, 6 Mar 2024 09:57:37 +
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with QMQP
id C9230205B1; Wed,  6 Mar 2024 09:57:27 + (UTC)
X-Mailbox-Line: From debian-devel-requ...@lists.debian.org  Wed Mar  6 
09:57:27 2024
Old-Return-Path: 
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bendel.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-6.7 required=4.0 tests=BODY_INCLUDES_PACKAGE,

DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,LDO_WHITELIST,
T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no
version=3.4.2
X-Original-To: lists-debian-de...@bendel.debian.org
Delivered-To: lists-debian-de...@bendel.debian.org
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with ESMTP id B720220598
for ; Wed,  6 Mar 2024 
09:57:16 + (UTC)
X-Virus-Scanned: at lists.debian.org with policy bank en-ht
X-Amavis-Spam-Status: No, score=-8.561 tagged_above=-1 required=5.3
tests=[BAYES_00=-2, BODY_INCLUDES_PACKAGE=-2, DKIM_INVALID=0.1,
DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249,
LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01]
autolearn=ham autolearn_force=no
Received: from bendel.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 
2525)
with ESMTP id CnwFbHimGCbL for ;
Wed,  6 Mar 2024 09:57:08 + (UTC)
Received: from buxtehude.debian.org (buxtehude.debian.org 
[IPv6:2607:f8f0:614:1::1274:39])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) 
server-digest SHA256
 client-signature RSA-PSS (2048 bits) client-digest SHA256)
(Client CN "buxtehude.debian.org", Issuer "Debian SMTP CA" (not 
verified))
by bendel.debian.org (Postfix) with ESMTPS id F06C820576;
Wed,  6 Mar 2024 09:57:07 + (UTC)
Received: from debbugs by buxtehude.debian.org with local (Exim 4.94.2)
(envelope-from )
id 1rho1I-0040qp-GA; Wed, 06 Mar 2024 09:57:04 +
X-Loop: ow...@bugs.debian.org
Subject: *SPAM* Bug#1065537: ITP: bleak-retry-connector -- Connector 
for Bleak Clients that handles transient connection failures
Reply-To: Edward Betts , 1065...@bugs.debian.org
Resent-From: Edward Betts 
Resent-To: debian-bugs-d...@lists.debian.org
Resent-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org,
w...@debian.org
X-Loop: ow...@bugs.debian.org
Resent-Date: Wed, 06 Mar 2024 09:57:02 +
Resent-Message-ID: 
X-Debian-PR-Message: report 1065537
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords: 
Received: via spool by sub...@bugs.debian.org id=B.1709718770954021
  (code B); Wed, 06 Mar 2024 09:57:02 +
Received: (at submit) by bugs.debian.org; 6 Mar 2024 09:52:50 +
Received: from 4angle.com ([78.129.222.14]:43828)
by buxtehude.debian.org with esmtps 
(TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from )
id 1rhnxC-0040B7-74
for sub...@bugs.debian.org; Wed, 06 Mar 2024 09:52:50 +
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=4angle.com;
s=bridge; h=Content-Type:MIME-Version:Message-
ID:Subject:To:From:Date:Sender:
Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-
Description:
Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-
Message-ID:
In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-
Subscribe:
List-Post:List-Owner:List-Archive;
bh=RkmeLzNl75rHSQ2ewaAj7V5oqKSJrzv7gFEX+bkonac=; 
b=bS+3bWmquMXLNzmyviYErz0ZgQ

Re: Temporary failure in name resolution

[Dan Ritter]

Shaheena Kazi wrote: 
> Package: ntpsec
> 
> Hello, we were using Bullseye and have upgraded to Bookworm.
> With Bookworm, we have ntpsec.
> The package is installed successfully and the service looks good.
> But the syslog is filled with below messages:
> 
> 2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_check: DNS error: -3, Temporary failure in name resolution
> 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_take_status: None=>temp, 3
> 2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_probe: None, cast_flags:1, flags:20801
> 2024-03-06T14:58:19.588607+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_check: processing None, 1, 20801
> 
> In ntp.conf the server is always set to None. We keep it to None always.

Did you name a machine "None" in /etc/hosts or your local DNS?

NTP does not work without either an authoritative clock or a
remote NTP server - preferably a pool of NTP servers. Do you
have an authoritative clock source, such as a GPS receiver or an
atomic clock?

Please show us your complete ntp.conf


-dsr-

Temporary failure in name resolution

[Shaheena Kazi]

Package: ntpsec

Hello, we were using Bullseye and have upgraded to Bookworm.
With Bookworm, we have ntpsec.
The package is installed successfully and the service looks good.
But the syslog is filled with below messages:

2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_check: DNS error: -3, Temporary failure in name resolution
2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_take_status: None=>temp, 3
2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_probe: None, cast_flags:1, flags:20801
2024-03-06T14:58:19.588607+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_check: processing None, 1, 20801

In ntp.conf the server is always set to None. We keep it to None always.

In bullseye it never gave any such messages in the syslog.. even though the
server was None.
But with Bookworm, it gives the above messages in syslog.

When I change the server to the ntp server name in the ntp.conf file... I
don't see these messages in the syslog.

Am I missing any configurations or anything else..
How can get rid of these messages in syslog
Any help will be appreciated. Thanks

Regards,
SK

Re: Firefox et PDF

[François LE GAD]

Le 05/03/2024 à 16:50, Thierry a écrit :

Bonjour,

depuis la mise à jour dans la version 115.8.0esr (testing), je reçois le 
message suivant à l'ouverture d'un PDF:

"Votre navigateur ne comprend pas de plugin de lecture de PDF"


Bonjour,
Aucun problème de mon côté (même version)

--
François

distribution archives became unusable

[Harald Dunkel]

Hi folks,

the repositories listed on https://www.debian.org/distrib/archive have
been signed using expired keys. Unfortunately this page doesn't deal
with this problem.

Do you think this could be improved?


Regards
Harri