Re: spamassassin Debian package unsafe to use in stable?

On 2025-06-09 16:24:41 +0200, Thomas Hochstein wrote: > Rules are updated by the sa-update service, started e.g. by > | systemctl enable --now spamassassin-maintenance.timer > | systemctl start spamassassin-maintenance.service > > Doing that, the scores are up to date: > | thh@angmar:~$ grep RCVD_

Re: spamassassin Debian package unsafe to use in stable?

On 2025-06-09 13:50:52 +0200, Nicolas George wrote: > Vincent Lefevre (HE12025-06-09): > > Jun 09 13:07:48 joooj spamd[164780]: check: dns_block_rule > > RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating > > /root/.spamassassin/dnsblock_bl.score.senderscore.com > > A system

Re: spamassassin Debian package unsafe to use in stable?

On 2025-06-09 08:03:58 +, Andy Smith wrote: > sa-update already picked it up: > > $ grep RCVD_IN_VALIDITY > /var/lib/spamassassin/4.01/updates_spamassassin_org/50_scores.cf > score RCVD_IN_VALIDITY_CERTIFIED 0 > score RCVD_IN_VALIDITY_SAFE 0 > score RCVD_IN_VALIDITY_RPBL 0 > #score RCVD_

Re: spamassassin Debian package unsafe to use in stable?

On 2025-06-09 02:58:07 +0200, Santiago Vila wrote: > El 9/6/25 a las 1:18, Vincent Lefevre escribió: > > Is the spamassassin Debian package unsafe to use in stable? > > > > The issue is that things related to spam evolves rapidly, but > > Debian stable is... stabl

spamassassin Debian package unsafe to use in stable?

Is the spamassassin Debian package unsafe to use in stable? The issue is that things related to spam evolves rapidly, but Debian stable is... stable. So its rules become obsolete, such as those that generate RCVD_IN_VALIDITY_CERTIFIED_BLOCKED RCVD_IN_VALIDITY_RPBL_BLOCKED RCVD_IN_VALIDITY_S

Re: systemd may silently break your system!

On 2024-08-01 23:17:42 -0400, Jeffrey Walton wrote: > The reference also says: > > Only pure stable release with security updates provides the best > stability. But stable does not mean bugless. Unfortunately stable sometimes has major bugs, and the only thing to do is to wait for the nex

Re: nvidia vs nouveau driver and initrd.* size

On 2024-08-02 14:55:31 +0200, Franco Martelli wrote: > Sorry but have you read that bug report (#1076561)? Some users has posted > solutions to make smaller the initrd file: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076561#10 > and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1

Re: nvidia vs nouveau driver and initrd.* size

On 2024-08-01 12:12:31 -0700, Van Snyder wrote: > On Thu, 2024-08-01 at 15:26 +0200, Vincent Lefevre wrote: > > Should I switch to the proprietary nvidia driver on these machines? > > Without NVidia's graphics accelerator, using software rendering with > nouveau is painful

Re: nvidia vs nouveau driver and initrd.* size

On 2024-08-01 11:32:10 -0400, Felix Miata wrote: > Vincent Lefevre composed on 2024-08-01 17:18 (UTC+0200): > > > On 2024-08-01 10:23:53 -0400, Felix Miata wrote: > > >> the bug fix should trim initrd size considerably before > >> too long. > > > What

Re: nvidia vs nouveau driver and initrd.* size

On 2024-08-01 10:23:53 -0400, Felix Miata wrote: > Vincent Lefevre composed on 2024-08-01 15:26 (UTC+0200): > > > I have several Debian/unstable machines, all with a Nvidia card. > > > On one of them, due to a bug in nouveau in the past, I use the > > proprietary nvid

Re: systemd may silently break your system!

On 2024-08-01 09:37:54 -0400, Greg Wooledge wrote: > On Thu, Aug 01, 2024 at 14:47:16 +0200, Vincent Lefevre wrote: > > No, even for unstable, maintainers should ensure that packages are > > upgraded in the right order. > > Once again, here is my understanding of the current

nvidia vs nouveau driver and initrd.* size

I have several Debian/unstable machines, all with a Nvidia card. On one of them, due to a bug in nouveau in the past, I use the proprietary nvidia driver: libnvidia-legacy-390xx-* packages. And the initrd size is reasonable: -rw-r--r-- 1 root root 66937544 2024-07-30 11:27:32 initrd.img-6.9.12-am

Re: systemd may silently break your system!

On 2024-07-29 23:36:02 -0500, David Wright wrote: > On Mon 29 Jul 2024 at 11:24:25 (+0200), Vincent Lefevre wrote: > > On 2024-07-28 22:26:10 -0500, David Wright wrote: > > > On Sun 28 Jul 2024 at 16:43:01 (+0200), Vincent Lefevre wrote: > > > > On 2024-07-28 00:0

Re: info is not dead

On 2024-07-28 22:49:43 -0500, David Wright wrote: > On Sun 28 Jul 2024 at 16:23:48 (+0200), Vincent Lefevre wrote: > > On 2024-07-28 00:08:51 -0500, David Wright wrote: > > > On Sun 28 Jul 2024 at 02:06:38 (+0200), Vincent Lefevre wrote: > > > > But for searching

Re: systemd may silently break your system!

On 2024-07-28 22:26:10 -0500, David Wright wrote: > On Sun 28 Jul 2024 at 16:43:01 (+0200), Vincent Lefevre wrote: > > On 2024-07-28 00:07:56 -0500, David Wright wrote: > > > It looks accidental to me that systemd did that tidying up before > > > procps had attempted

Re: Upgrading systemd may silently break your Unstable/Sid system!

On 2024-07-28 20:01:35 -0400, Greg Wooledge wrote: > In the interests of posting something *useful*, here's a timeline. > As I understand it, here's what's happened so far: > > 2024-06-23: bug #1074156 filed against package procps > procps: Depend or Recommend linux-sysctl-defaults > Bug f

Re: systemd may silently break your system!

On 2024-07-28 11:21:01 -0400, Greg Wooledge wrote: > On Sun, Jul 28, 2024 at 16:43:01 +0200, Vincent Lefevre wrote: > > More or less. In the systemd case, for each file, either one chooses > > it, i.e. one has all the current defaults, or one chooses to provide > > a replac

Re: Upgrading systemd may silently break your Unstable/Sid system!

On 2024-07-28 14:13:09 +, Michael Kjörling wrote: > And posting on debian-user with a bombastic Subject line which implies > that this is a widespread issue when it really only seems to exist in > Unstable is, quite frankly, in my opinion at best dishonest. No, the breakage was done *on purpos

Re: systemd may silently break your system!

On 2024-07-28 00:07:56 -0500, David Wright wrote: > On Sun 28 Jul 2024 at 04:25:32 (+0200), Vincent Lefevre wrote: > > On 2024-07-27 20:25:54 -0400, Greg Wooledge wrote: > > > > On Sun, Jul 28, 2024 at 01:17:19 +0200, Vincent Lefevre wrote: > > > > The confi

Re: info is not dead

On 2024-07-28 00:08:51 -0500, David Wright wrote: > On Sun 28 Jul 2024 at 02:06:38 (+0200), Vincent Lefevre wrote: > > On 2024-07-23 11:13:47 -0500, Nate Bargmann wrote: > > > The GNU info documentation is really intended to be read in Emacs where > > > some nice fo

Re: systemd may silently break your system!

On 2024-07-27 20:25:54 -0400, Greg Wooledge wrote: > On Sun, Jul 28, 2024 at 01:04:14 +0200, Vincent Lefevre wrote: > > On 2024-07-27 10:23:01 +0200, Michel Verdier wrote: > > > /etc/sysctl.d/README.sysctl recommends to use a separate file such as > > > /etc/sysctl.d

Re: bash history

On 2024-07-27 22:50:17 +0100, mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? > Is this something that can be changed so history is shared between virtual > terminals? This

Re: info is not dead

On 2024-07-23 11:13:47 -0500, Nate Bargmann wrote: > The GNU info documentation is really intended to be read in Emacs where > some nice formatting is done in the GUI Emacs version. The stand alone > GNU info browser is rather obtuse. I found a much better option to be > the independent pinfo (De

Re: systemd may silently break your system!

On 2024-07-27 09:26:49 -0400, Greg Wooledge wrote: > > On 2024-07-26, Vincent Lefevre wrote: > > > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > > (currently in unstable) *without any announcement*, so that > > > the /etc/sysctl.co

Re: systemd may silently break your system!

On 2024-07-27 10:23:01 +0200, Michel Verdier wrote: > On 2024-07-26, Vincent Lefevre wrote: > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > (currently in unstable) *without any announcement*, so that > > the /etc/sysctl.conf file (which is still do

Re: stty permanently undef "start"

On 2024-07-10 16:00:48 +0200, Nicolas George wrote: > Greg Wooledge (12024-07-10): > > You could -- but if you do so, you should definitely surround it with > > a check for stdin being a terminal (test -t 0 or equivalent). > > Does bash execute .bashrc when it is not interactive? Yes, it may exec

Re: systemd-cryptsetup

On 2024-07-14 13:17:45 +0200, Lists wrote: > On 2024-07-14 11:00, Nicolas George wrote: > > Hi. > > > > In case you are running unstable or testing and it recently started > > blocking at boot waiting for encrypted swap or something to do with > > encrypted disks: > > > > Check if systemd-cryptse

systemd may silently break your system!

The /etc/sysctl.d/99-sysctl.conf symlink has been removed (currently in unstable) *without any announcement*, so that the /etc/sysctl.conf file (which is still documented, BTW) is no longer read. So, be careful if you have important settings there (security...). -- Vincent Lefèvre - Web:

Re: Need help with narroely focused use case of Emacs

On 2024-06-28 20:53:50 +, Michael Kjörling wrote: > Yes, it almost certainly can be done with a single sed (or other > similar tool) invocation where the regular expression matches > precisely what you want it to match. But unless this is something you > will do very often, I tend to prefer rea

Re: can't connect to eduroam due to SSL3 unsupported protocol

On 2024-06-17 15:08:54 -0400, Dan Ritter wrote: > Vincent Lefevre wrote: > > On 2024-06-17 08:26:39 -0400, Dan Ritter wrote: > > > On stable: > > > $ openssl list -disabled > > > Disabled algorithms: > > > IDEA > > > MD2 > > > MDC2 &

Re: can't connect to eduroam due to SSL3 unsupported protocol

On 2024-06-17 10:18:09 -0400, Stefan Monnier wrote: > > Under Debian/unstable, I can't connect to eduroam due to the following > > reason: > > AFAIK, while "the eduroam" looks like one thing it's just a bunch of > local wifi networks, each one administered&managed mostly independently > and with d

Re: can't connect to eduroam due to SSL3 unsupported protocol

On 2024-06-17 08:26:39 -0400, Dan Ritter wrote: > On stable: > $ openssl list -disabled > Disabled algorithms: > IDEA > MD2 > MDC2 > RC5 > SCTP > SSL3 > ZLIB > > So, SSL3 support was removed at least that long ago. I think it > was actually dropped around 2016. That's strange because when I insta

can't connect to eduroam due to SSL3 unsupported protocol

Hi, Under Debian/unstable, I can't connect to eduroam due to the following reason: Jun 17 13:58:31 qaa wpa_supplicant[1184]: wlp0s20f3: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 Jun 17 13:58:31 qaa wpa_supplicant[1184]: wlp0s20f3: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) sele

Re: Copy from xterm to text editor........

On 2024-06-12 21:16:51 -0600, Charles Curley wrote: > Note that this is very temporary storage. It will not put the text in > the clipboard, nor will a clipboard stack program like clipman see it. This can be changed with selectToClipboard: selectToClipboard (class SelectToClipboard) Tell

Re: Why isn't the "whois" package (Priority: standard) installed by default?

On 2024-06-13 22:15:05 +0200, Javier Barroso wrote: > Hello, > > El jue., 13 jun. 2024 20:48, Vincent Lefevre escribió: > > > On 2024-06-13 14:43:25 -0400, Greg Wooledge wrote: > > > On Thu, Jun 13, 2024 at 07:57:59PM +0200, Vincent Lefevre wrote: > > >

Why isn't the "whois" package (Priority: standard) installed by default?

The "whois" package has "Priority: standard". According to the Debian policy[*]: standard These packages provide a reasonably small but not too limited character-mode system. This is what will be installed by default if the user doesn’t select anything else. It doesn’t include many

Re: Why isn't the "whois" package (Priority: standard) installed by default?

On 2024-06-13 14:43:25 -0400, Greg Wooledge wrote: > On Thu, Jun 13, 2024 at 07:57:59PM +0200, Vincent Lefevre wrote: > > The "whois" package has "Priority: standard". > > hobbit:~$ apt-cache show whois | grep Priority > Priority: optional qaa:~> apt-

Re: timeout in shutdown, mutt killed by SIGKILL

On 2024-05-31 19:05:45 +0700, Max Nikulin wrote: > Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL? Unfortunately, there was no information from systemd. Some daemons log a received SIGTERM, but mutt isn't a daemon. > What other processes survived first step? Are there so

Re: timeout in shutdown, mutt killed by SIGKILL

On 2024-05-31 10:10:32 +0200, Vincent Lefevre wrote: > On 2024-05-31 10:02:57 +0700, Max Nikulin wrote: > > Do you mean that mutt properly exits unless it receives SIGTERM in the > > course of shutdown process? > > I think that this was not the first time I did a shutdown w

Re: timeout in shutdown, mutt killed by SIGKILL

On 2024-05-31 10:02:57 +0700, Max Nikulin wrote: > Do you mean that mutt properly exits unless it receives SIGTERM in the > course of shutdown process? I think that this was not the first time I did a shutdown while Mutt was still running. But this was the first time it did not exit. > I would tr

Re: timeout in shutdown, mutt killed by SIGKILL

On 2024-05-30 00:19:30 +0700, Max Nikulin wrote: > On 29/05/2024 07:44, Vincent Lefevre wrote: > > But I don't understand why there was a timeout. Does this mean that > > mutt didn't react to SIGTERM? Any reason? > > Have you tried to send SIGTERM to mutt? I

Re: timeout in shutdown, mutt killed by SIGKILL

On 2024-05-29 16:13:05 -, Curt wrote: > On 2024-05-29, Vincent Lefevre wrote: > > During the latest shutdown: > > > > May 29 01:55:05 qaa systemd[1]: Stopping session-2.scope - Session 2 of > > User vinc17... > > [...] > > May 29 01:55:26 qaa systemd[

Re: Uninstalling a package and its entourage

On 2024-05-27 18:42:48 +0300, mindaugascelies...@gmail.com wrote: > On Monday, May 27, 2024 5:59:55 PM EEST Nicolas George wrote: > > Eben King (12024-05-27): > > > Is there an easier way to uninstall a package and everything it brought in > > > at one swell foop? Thanks. > > > > The packages you

timeout in shutdown, mutt killed by SIGKILL

During the latest shutdown: May 29 01:55:05 qaa systemd[1]: Stopping session-2.scope - Session 2 of User vinc17... [...] May 29 01:55:26 qaa systemd[1]: session-2.scope: Stopping timed out. Killing. May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990 (mutt) with signal SIGKILL.

Re: LibreOffice removed from Debian

On 2024-04-17 16:13:30 +0200, Vincent Lefevre wrote: > I've sent a message to bug 1069123 (which requested the removal). > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069123#20 and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069123#25 say > that the request

Re: LibreOffice removed from Debian

On 2024-04-17 14:59:18 +0100, Brad Rogers wrote: > On Wed, 17 Apr 2024 15:35:57 +0200 > Vincent Lefevre wrote: > > Hello Vincent, > > >If this is not permanent, why have all the bugs been closed? > > That I have no answer for. I've sent a message to bug 1069

Re: LibreOffice removed from Debian

On 2024-04-17 14:26:12 +0100, Brad Rogers wrote: > On Wed, 17 Apr 2024 15:12:39 +0200 > Vincent Lefevre wrote: > > Hello Vincent, > > >Is there any reason why LibreOffice has been removed from Debian??? > > https://tracker.debian.org/pkg/libreoffice > > Ha

Re: LibreOffice removed from Debian

On 2024-04-17 15:24:47 +0200, Vincent Lefevre wrote: > On 2024-04-17 15:19:26 +0200, Marco Moock wrote: > > Am 17.04.2024 um 15:12:39 Uhr schrieb Vincent Lefevre: > > > > > Is there any reason why LibreOffice has been removed from Debian??? > > > > https:

Re: LibreOffice removed from Debian

On 2024-04-17 15:19:26 +0200, Marco Moock wrote: > Am 17.04.2024 um 15:12:39 Uhr schrieb Vincent Lefevre: > > > Is there any reason why LibreOffice has been removed from Debian??? > > https://tracker.debian.org/pkg/libreoffice > According to the tracker, it specific rel

LibreOffice removed from Debian

Is there any reason why LibreOffice has been removed from Debian??? -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: inconsistency in the symlinks under /etc/systemd

On 2024-04-10 23:47:36 -0500, David Wright wrote: > On Thu 11 Apr 2024 at 03:36:59 (+0200), Vincent Lefevre wrote: > > On 2024-04-10 09:52:51 -0400, Dan Purgert wrote: > > > I'd hazard it's a consequence of usrmerge being the "default state" in &g

Re: inconsistency in the symlinks under /etc/systemd

On 2024-04-10 09:52:51 -0400, Dan Purgert wrote: > I'd hazard it's a consequence of usrmerge being the "default state" in > one installation and not the other. Both machines have always been usr-merged (i.e. from the Debian installation). -- Vincent Lefèvre - Web: 100%

inconsistency in the symlinks under /etc/systemd

Hi, On one machine, I have lrwxrwxrwx 1 root root 35 2023-10-07 13:43:24 /etc/systemd/system/sockets.target.wants/dm-event.socket -> /lib/systemd/system/dm-event.socket and on another one, I have lrwxrwxrwx 1 root root 39 2024-01-05 16:54:09 /etc/systemd/system/sockets.target.wants/dm-event.

test of a gnuplot bug visible with Pango 1.52 (Debian/unstable)

Hi, Since the upgrade of the Pango library to 1.52 in Debian/unstable, I'm seeing an annoying bug in gnuplot with the wxt terminal. The issue can be reproduced with the following command: echo 'set terminal wxt; plot x' | gnuplot -persist A window appears, but it is not drawn and it cannot be

ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100)

In one of my new machines, I have a DVD+/-RW drive. There were no issues on January 8 and 9. But today, I'm getting ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100) errors at boot time. Excerpts of the journal concerning ata6: journalctl-9:Jan 08 11:23:19 disset kernel: ata6: SATA max

Re: Perl module installation via CPAN and signature error

With strace, I could see the command that was executed: gpg --verify --batch --no-tty -q --logger-fd=1 --keyserver=hkp://pool.sks-keyservers.net:11371 on a temporary file, but almost equivalent to the CHECKSUMS file. Now, I can try that directly: qaa:~> gpg --verify --batch --no-tty -q --log

Perl module installation via CPAN and signature error

Hi, I have 2 Debian/unstable machines on the same network, with the same .cpan/CPAN/MyConfig.pm file. On one of them, I get no errors: qaa:~> cpan -i XML::RPC CPAN: HTTP::Tiny loaded ok (v0.086) CPAN: Net::SSLeay loaded ok (v1.92) CPAN: IO::Socket::SSL loaded ok (v2.084) Fetching with HTTP::Tiny

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 14:04:08 -0500, Greg Wooledge wrote: > On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > > I have the latest version!!! I recall that this is a Debian/unstable > > machine, which I upgrade regularly. So, everytime I get such an error, > > I h

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 17:03:10 +0100, Klaus Singvogel wrote: > Vincent Lefevre wrote: > > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > > errors like > > > > kex_exchange_identification: read: Connection reset by peer > > Connection reset by

openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Since 2 years (from early 2022 to 2023-11-26), I've got recurrent errors like kex_exchange_identification: read: Connection reset by peer Connection reset by x.x.x.x port 22 or kex_exchange_identification: Connection closed by remote host Connection closed by x.x.x.x port 22 But yesterday, the

Re: Image handling in mutt

On 2023-12-11 09:34:09 -0500, Pocket wrote: > On 12/11/23 09:04, Vincent Lefevre wrote: > > On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote: > > > 2) When *receiving* email, mutt will use the sender's MIME type label > > > to decide how to deal with the a

Re: Image handling in mutt

On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote: > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote: > > I do not care about the "microsoft world", and I doubt that this is > > required there at the low level (what would be the equivalen

Re: Image handling in mutt

On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote: > 2) When *receiving* email, mutt will use the sender's MIME type label >to decide how to deal with the attachment. But the notion of filename extension is even used in this context too. Quoting the Mutt manual: --

Re: Image handling in mutt

On 2023-12-11 07:32:30 -0500, Pocket wrote: > > On 12/11/23 07:12, Vincent Lefevre wrote: > > On 2023-12-10 15:51:02 -0500, Pocket wrote: > > > On Dec 10, 2023, at 3:05 PM, David Wright > > > wrote: > > > > ¹ Re the argument raging in this thread about

Re: Image handling in mutt

On 2023-12-10 15:51:02 -0500, Pocket wrote: > On Dec 10, 2023, at 3:05 PM, David Wright wrote: > > ¹ Re the argument raging in this thread about "extension", the > > term is clearly appropriate, as a glance at /etc/mime.types > > demonstrates. The literature is full of the term. > > > > I woul

Re: Image handling in mutt

On 2023-12-08 17:06:15 -0500, Pocket wrote: > On 12/8/23 16:53, David wrote: > > Hi, the filename extension is usually irrelevant on Linux, because > > Linux tools typically > > use the standard 'file' command to inspect the content of the > > fileinstead of relying on > > the filename to indicate

Re: systemd-journald log location

On 2023-12-04 13:33:33 +0100, Vincent Lefevre wrote: > On 2023-12-04 11:46:23 +, Adam Weremczuk wrote: > > Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log? > > > > I can't find a suitable option in /etc/systemd/journald.conf See the

Re: systemd-journald log location

On 2023-12-04 11:46:23 +, Adam Weremczuk wrote: > Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log? > > I can't find a suitable option in /etc/systemd/journald.conf > > I recently increased SystemMaxUse and RuntimeMaxUse which quickly filled up > all space. On my D

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-18 23:43:34 -0600, David Wright wrote: > On Sat 18 Nov 2023 at 23:33:59 (+0100), Vincent Lefevre wrote: > > On 2023-11-18 09:18:56 -0500, Greg Wooledge wrote: > > > The "6.1.0-" part comes from the upstream release series. All the > > > kernel image

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-18 09:18:56 -0500, Greg Wooledge wrote: > The "6.1.0-" part comes from the upstream release series. All the > kernel images containing "6.1.0-" in this section should come from the > same upstream series (6.1.x), and should have basically the same feature > set, with no major changes.

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-18 00:20:25 -0600, David Wright wrote: > On Fri 17 Nov 2023 at 13:30:32 (+0100), Vincent Lefevre wrote: > > On 2023-11-16 14:04:29 -0600, David Wright wrote: > > > On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote: > > > > In any case,

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-16 23:53:51 +0700, Max Nikulin wrote: > On 16/11/2023 20:59, Vincent Lefevre wrote: > > The question is what suppresses software buttons. If this is libinput > > that suppresses them (just like it suppressed pointer moves when > > typing, while pointer moves are

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-16 14:04:29 -0600, David Wright wrote: > On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote: > > In any case, if a package is renamed (which particularly applies to > > unstable, I don't know about backports), I would expect reportbug > > to also c

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-08 12:06:10 +0700, Max Nikulin wrote: > On 04/11/2023 15:59, Vincent Lefevre wrote: > > On 2023-11-03 09:48:16 +0700, Max Nikulin wrote: > > > From the "See ... for details" page > > > > > > > Note > > > > > > > &

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 13:54:51 -0600, David Wright wrote: > On Wed 15 Nov 2023 at 20:01:20 (+0100), Vincent Lefevre wrote: > > On 2023-11-15 18:06:45 +, Tixy wrote: > > > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote: [...] > > > > But the bookworm-backports ke

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 13:54:51 -0600, David Wright wrote: > On Wed 15 Nov 2023 at 20:01:20 (+0100), Vincent Lefevre wrote: > > On 2023-11-15 18:06:45 +, Tixy wrote: > > > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote: > > > > On 2023-11-15 16:39:15 -, Curt

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 18:06:45 +, Tixy wrote: > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote: > > On 2023-11-15 16:39:15 -, Curt wrote: > > > On 2023-11-14, Vincent Lefevre wrote: > > > > > > > > The base number is the same, but I would h

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 16:39:15 -, Curt wrote: > On 2023-11-14, Vincent Lefevre wrote: > > > > The base number is the same, but I would have thought that this other > > kernel might have additional patches. > > > >> That's why I suggested ignoring the message

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 08:50:50 +0100, didier gaumet wrote: > I don't know why particularly a Bullseye-backports kernel is promoted here > in a mixed stable/unstable context but perhaps (I have not tested it) you > could set check-available to 0 in /etc/reportbug.conf (1) to avoid to be > proposed a newer k

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-15 10:15:35 +0700, Max Nikulin wrote: > On 15/11/2023 05:01, Vincent Lefevre wrote: > > > On Tue, Nov 14, 2023 at 10:21:13PM +0100, Vincent Lefevre wrote: > > > > # $ wget -qO- > > > > 'https://qa.debian.org/madison.php?package=emacs&am

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-14 16:34:18 -0500, Greg Wooledge wrote: > On Tue, Nov 14, 2023 at 10:21:13PM +0100, Vincent Lefevre wrote: > > On 2023-11-14 23:54:31 +0700, Max Nikulin wrote: > > > On 14/11/2023 19:00, Vincent Lefevre wrote: > > > > To my surprise, reportbug ask

Re: Why is bullseye-backports recommended on bookworm?

On 2023-11-14 23:54:31 +0700, Max Nikulin wrote: > On 14/11/2023 19:00, Vincent Lefevre wrote: > > To my surprise, reportbug asks me to use bullseye-backports > > (= oldstable-backports) on my bookworm (= stable) machine: > > Might it happen that you have bullseye-backport

Why is bullseye-backports recommended on bookworm?

To my surprise, reportbug asks me to use bullseye-backports (= oldstable-backports) on my bookworm (= stable) machine: Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of date. The following newer release(s) are available in the Debian archive: bullseye-backports (backport

Re: Request advice on Optimal Combo-usage of Gmail and Mailman, as mentioned in Msg-Id. "2023/11/msg00443"

On 2023-11-13 10:57:34 -0300, Eduardo M KALINOWSKI wrote: > And those are getting rare, I can't find a nice MUA for Android with > proper threading. Not sure if that counts, but Mutt in Termux? -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 15:32:53 +, fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenom

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 10:57:21 +0100, Michael wrote: > On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > > No, this is not a normal phenomenon for bookworm upgrades. I've never > > heard of it happening to anyone before. > > i disagree. i had the same problem b/c i also had dropbear insta

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-03 09:48:16 +0700, Max Nikulin wrote: > On 03/11/2023 01:55, Vincent Lefevre wrote: > > > > (EE) event14 - VEN_04F3:00 04F3:311C Touchpad: kernel bug: Touch jump > > > > detected and discarded. > > > > See > > > > https://wayland.f

Re: touchpad buttons sometimes stop working for several seconds

Some additional details: the time during which the issue occurs varies very much: from 25" to 6'20". The time between two consecutive issues also varies and can be very short, such as 30". -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-02 22:46:13 +0700, Max Nikulin wrote: > On 02/11/2023 04:51, Vincent Lefevre wrote: > > On 2023-11-01 20:15:49 +0100, Vincent Lefevre wrote: > > > On 2023-11-01 09:09:45 +0700, Max Nikulin wrote: > > > > Can you move cursor during these periods? > &

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-01 20:15:49 +0100, Vincent Lefevre wrote: > On 2023-11-01 09:09:45 +0700, Max Nikulin wrote: > > On 01/11/2023 00:53, Vincent Lefevre wrote: > > > I have a new laptop. An issue I have is that the touchpad buttons often > > > stop working for several seconds (u

Re: touchpad buttons sometimes stop working for several seconds

On 2023-11-01 09:09:45 +0700, Max Nikulin wrote: > On 01/11/2023 00:53, Vincent Lefevre wrote: > > I have a new laptop. An issue I have is that the touchpad buttons often > > stop working for several seconds (under X11). > > Can you move cursor during these periods? Ye

touchpad buttons sometimes stop working for several seconds

Hi, I have a new laptop. An issue I have is that the touchpad buttons often stop working for several seconds (under X11). This is visible even with evtest: when I click on any of the soft buttons, I normally get an event like Event: time 1698773368.142943, type 1 (EV_KEY), code 272 (BTN_LEFT), v

Re: using ddrescue on the root partition - boot with / as read-only

On 2023-09-14 22:24:59 -0700, David Christensen wrote: > On 9/14/23 03:17, Vincent Lefevre wrote: > > I get UNC errors like > > > > 2023-09-10T11:50:59.858670+0200 zira kernel: ata1.00: exception Emask 0x0 > > SAct 0xc00 SErr 0x4 action 0x0 > > 2023-09-10

Re: using ddrescue on the root partition - boot with / as read-only

On 2023-09-14 21:44:18 +0700, Max Nikulin wrote: > If data are really precious then seek for a specialized service. I normally have 2+ backups for important data. But I'd like to double-check with what is no longer readable on the laptop disk. -- Vincent Lefèvre - Web:

Re: su

On 2023-09-14 21:25:56 +0700, Max Nikulin wrote: > On 14/09/2023 17:30, Vincent Lefevre wrote: > > Yes, XDG_RUNTIME_DIR is problematic, but as "su -" doesn't work in > > GNU Screen (it yields major display issues), I presume that some > > environment variables

Re: su

On 2023-09-06 14:36:48 +0700, Max Nikulin wrote: > On 06/09/2023 10:41, Greg Wooledge wrote: > > > > Just put "ALWAYS_SET_PATH yes" into /etc/default/su and the problem > > is FIXED. "su" will work properly again! > > Greg, you provided a valid example when "su -" is undesirable, however in > ge

Re: using ddrescue on the root partition - boot with / as read-only

On 2023-09-13 20:52:43 -0700, David Christensen wrote: > On 9/13/23 04:54, Vincent Lefevre wrote: > > Hi, > > > > I need to use ddrescue on the root partition of my laptop. > > > > So I need to have the root partition mounted in read-only mode. > > How can

Re: using ddrescue on the root partition - boot with / as read-only

On 2023-09-13 23:00:27 -0400, Stefan Monnier wrote: > > Or perhaps I could use /bin/sh as init, so that systemd (and its > > remount as rw) would be avoided? > > Indeed booting with `init=/bin/bash` can be a handy option I've used in > the past: you get into the normal root (so you don't have to f

Re: using ddrescue on the root partition - boot with / as read-only

On 2023-09-13 14:15:30 +0200, to...@tuxteam.de wrote: > On Wed, Sep 13, 2023 at 01:54:04PM +0200, Vincent Lefevre wrote: > > I need to use ddrescue on the root partition of my laptop. > > > > So I need to have the root partition mounted in read-only mode. BTW, in recover

using ddrescue on the root partition - boot with / as read-only

Hi, I need to use ddrescue on the root partition of my laptop. So I need to have the root partition mounted in read-only mode. How can I do that? Note that "mount -o remount,ro /" gives an error "mount point is busy" apparently because various log files are open in write mode. Using the recover

  1   2   3   4   5   6   7   8   9   10   >