Re: systemd may silently break your system!

wait for the next stable release (except when one is the admin, in which case, one can patch the software and recompile). -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic

Re: nvidia vs nouveau driver and initrd.* size

drivers for the Nvidia cards. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

future bugs), this might not be possible. Should I switch to the proprietary nvidia driver on these machines? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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!

l open. No, this thread was started *after* bug #1077184 (which I reported) was closed as wontfix and *after* I reported bug #1077187. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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!

done *on purpose* (together with the lack of announcement). -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

en virtual > terminals? This is possible with zsh (option SHARE_HISTORY). But I do not use this option: if I want to retrieve a command from another terminal, I simply re-execute the shell to get the whole history of commands typed so far (but there are other ways to manipulate the history). -

Re: info is not dead

atch with pinfo? (info has { and } to navigate through the matches, Lynx has n and N, but what about pinfo?) -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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"

ractive? Yes, it may execute it. From the bash(1) man page: If bash determines it is being run non-interactively in this fashion, it reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist and are readable. -- Vincent Lefèvre - Web: <https://www.vinc17.net/>

Re: systemd-cryptsetup

etup. > systemd has "Recommends: [...] systemd-cryptsetup [...]". So this is the following bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931283 -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

nd to prefer readability over being clever, > even if the readable version is somewhat less performant. To match a range inside a regexp, $(rgxg range 1 119) is readable. :) rgxg is provided by the package of the same name. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessi

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

d&managed mostly independently > and with different configurations. By and large, if you can connect to > eduroam at one place it's likely it'll also work elsewhere but it's not > always the case. Isn't the authentication done by the remote side, thus will always

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

nd 2016. That's strange because when I installed the machine in October, there were no issues. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

can't connect to eduroam due to SSL3 unsupported protocol

[1184]: wlp0s20f3: CTRL-EVENT-EAP-FAILURE EAP authentication failed Anyone knows what's wrong? (There were such kinds of issues several years ago, but I thought this was fixed.) -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://

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

lls it to use PRIMARY. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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?

. It doesn’t include many large applications. Two packages that both have a priority of standard or higher must not conflict with each other. [*] https://www.debian.org/doc/debian-policy/ch-archive.html So, why isn't this package installed by default? -- Vincent Lefèvre - Web

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

? Are there something suspicious > before SIGKILL stage? According to the journalctl output, only mutt survived (the only process to receive a SIGKILL). And nothing suspicious. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www

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

his one is a known issue: https://github.com/flatpak/xdg-desktop-portal/issues/999 I'm wondering whether there could be a same cause. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

kage could have been automatically installed due to a dependency, but it may be in another OR dependency, in which case apt will not propose its removal, even though the OR dependency would still be satisfied. So, you should either look at the logs or keep trace of the packages that are i

timeout in shutdown, mutt killed by SIGKILL

was just a local one. Mutt does no network connections (I do not use IMAP). I general, I quit it before logging out, but this time, it seems that I forgot. But I don't understand why there was a timeout. Does this mean that mutt didn't react to SIGTERM? Any reason? -- Vincent Le

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: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/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: <

inconsistency in the symlinks under /etc/systemd

equivalent), for instance to ease the comparison of configurations between machines? For instance, shouldn't usr-is-merged convert the symlinks to a canonical path? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.

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

ils in my bug reports: https://sourceforge.net/p/gnuplot/bugs/2693/ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064982 Can anyone else reproduce this issue, in particular with other window managers? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <

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

, and the others ones to a boot with the 6.6.9-amd64 kernel. So this does not seems to be related to the kernel version. Any idea? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer

Re: Perl module installation via CPAN and signature error

uid [ expired] PAUSE Batch Signing Key 2021 i.e. the subkeys are missing. Why? Note that on zira, doing gpg --recv-keys 2E66557AB97C19C791AF8E20328DA867450F89EC again doesn't change anything. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Perl module installation via CPAN and signature error

ublic key given by "gpg --list-public-keys" on qaa are on zira too. Where does the problem come from? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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?

e any explanation of such a change? Has anyone noticed a similar change (for those who get such errors)? -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

3) Many other programs besides mutt will also use file extensions to >determine how to deal with input files. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

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

term. A filename extension is a suffix, but a suffix (e.g. as in POSIX) is not necessarily a filename extension. For instance: $ basename foobar bar foo Here, "bar" is a suffix, but it does not have the form of a filename extension. So the notion of "filename extension" is mo

Re: Image handling in mutt

lying on > > the filename to indicate content. > > In Unix and Linux there isn't a file extension, that is a microsoft > invention. More and more applications under Linux, like atril and lynx, care about the file extension. -- Vincent Lefèvre - Web: <https://www.v

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

> all space. On my Debian machines, /run/log/journal is empty, and everything goes into /var/log/journal. I haven't changed the location. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR IN

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?

> set, with no major changes. BTW, since this is for 6.1.x, I've always wondered why Debian uses the "6.1.0-" prefix instead of "6.1-". The "6.1.0" is a bit confusing. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated

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?

proposed a newer kernel at all. > > (1) https://manpages.debian.org/bookworm/reportbug/reportbug.conf.5.en.html This would apply to *all* packages. I certainly don't want to do that. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: &

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?

(backports-policy): 6.1.55+1~bpo11+1 Please try to verify if the bug you are about to report is already addressed by these releases. Do you still want to file a report [y|N|q|?]? Why? Shouldn't a more recent kernel be available in bookworm-backports (= stable-backports)? -- Vincent Lefèvre

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: <https://www.vinc17.net/> 100% accessible validated (X)HT

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

em b/c i also had dropbear installed. It would be interesting to know why dropbear got installed (if openssh-server was already installed, this is rather surprising), e.g. with "aptitude why dropbear". -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X

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: <https://www.vinc17.net/> 100% accessible valida

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

rg X server -- input driver metapackage ii xserver-xorg-input-libinput 1.2.1-1+b1 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-wacom1.1.0-1 amd64X.Org X server -- Wacom input

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: <https://www

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

So "su -" > should have less unexpected effects. 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 (terminal related?) are still useful. FYI, I had written a su

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

n I found on the web was to set kernel.printk to 3 3 3 3. I did that with: sysctl kernel.printk="3 3 3 3" Then I resumed ddrescue. Still onging... -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17

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

ite mode. Using the recovery mode via GRUB (which mounts / in read-only mode) is useless because the system remounts it later as rw. Or is there a way to force a remount in read-only mode? (I could probably trigger a disk error to make the kernel remount / as read-only, but well...) -- Vincent Le

Re: bookworm upgrade report: boring

m a shell. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

which is rather limited: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=32877 (yes, 1999). Some packages offer a 3-way merge, which is very useful. I think that in this case, the configuration file handling is done via ucf (the possibility of a merge is mentioned in its man page). --

Re: bookworm upgrade report: boring

ried that > there may be new settings that should be set, and so on. I always look at the diffs (I track all the config files I modify), and sometimes at the logs too. In general, I do some kind of merge. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

ported. Otherwise, this is not surprising. -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: X11 should not run as root or?

default values. > It looks like i3 doesn't need x11 as root either. i3-wm is a window manager, not a display manager. So it depends on what display manager you're using (if any). -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  1   2   3   4   5   6   7   8   9   10   >