Bug#1073998: linux: Purging linux-image- doesn't clean up modules.weakdep file

This bug has been fixed in unstable kernels. Shouldn't it be fixed in stable kernels too (as the fix is rather trivial)? For instance, I still have -rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep while the kernel has been purged. So I got Purging confi

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Control: reassign -1 src:linux Control: found -1 6.10.12-1 Control: severity -1 minor Control: notforwarded -1 Control: retitle -1 linux: for tmpfs, /proc/mounts and /proc/self/mountinfo do not always show the size when corresponding to the default, at least on /tmp Summary: On my Debian/unstable

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Control: forwarded -1 https://github.com/systemd/systemd/issues/34620 I've just reported the bug upstream. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-L

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Control: found -1 256.6-1 (but it seems that the bug has always been present, i.e. since /tmp uses tmpfs). On 2024-10-02 18:54:05 +0200, Chris Hofstaedtler wrote: > Control: reassign -1 systemd > > I don't see why mount is involved here. Well, the tmpfs(5) man page mentions the mount command an

Bug#1083183: bluez: headset no longer connects with 6.10.12-amd64 kernel

And if I run bluetoothctl, I can see messages [CHG] Device 38:18:4C:4B:AC:93 Connected: yes [CHG] Device 38:18:4C:4B:AC:93 Connected: no [CHG] Device 38:18:4C:4B:AC:93 Connected: yes [CHG] Device 38:18:4C:4B:AC:93 Connected: no [CHG] Device 38:18:4C:4B:AC:93 Connected: yes [CHG] Device 38:18:4C:4B

Bug#1083183: bluez: headset no longer connects with 6.10.12-amd64 kernel

Package: bluez Version: 5.77-1 Severity: important After upgrading to the 6.10.12-amd64 kernel, my headset no longer connects. I can see in the journalctl logs: Oct 02 22:14:36 qaa bluetoothd[1359]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 38:18:4C:4B:AC:93: Connect

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Package: mount Version: 2.40.2-9 Severity: normal The tmpfs size for /tmp is normally 50%: /usr/lib/systemd/system/tmp.mount has [Mount] What=tmpfs Where=/tmp Type=tmpfs Options=mode=1777,strictatime,nosuid,nodev,size=50%%,nr_inodes=1m But the size is randomly ignored: after some boots, cventin

Bug#1082745: aptitude: information mismatch for package removal

This issue occurred again for the new Linux kernel upgrade. Here's additional information. The reformatted diff on the /var/lib/aptitude/pkgstates file just after the upgrade: Package: linux-headers-6.10.12-amd64 Architecture: amd64 Unseen: yes State:

Bug#1057695: debian-goodies: checkrestart gives SyntaxWarning messages with python3.12

Version: 0.88.2 On 2024-08-31 12:55:06 +0200, Francesco Poli wrote: > I therefore prepared a patch for checkrestart. [...] I can no longer reproduce the issue. It seems that the bug had actually been fixed in the Git repository on 2024-08-27, thus before your patch: https://salsa.debian.org/debi

Bug#407531: Should detect screen size changes when listing bugs

Control: found -1 13.0.1 On 2007-01-19 09:11:41 +, Joachim Breitner wrote: > when I am confronted with a large list of bugs to check if mine is > already filed, I tend to enlargen the terminal window, hoping to see > more at once, and see longer subject lines. Unfortunately, reportbug > does n

Bug#1083094: checkrestart: misleading info about deleted files, actually replaced

Package: debian-goodies Version: 0.88.2 Severity: minor With "checkrestart -f", I get: [...] The following systemd units started programmes that are using deleted files: lightdm.service: Program /usr/lib/xorg/Xorg (PID: 1163, CMDLINE: '/usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lig

Bug#1082788: chkrootkit: README.FALSE-POSITIVES documentation for bindshell is incomplete

On 2024-09-29 19:52:24 +0100, Richard Lewis wrote: > On Thu, 26 Sept 2024 at 11:21, Vincent Lefevre wrote: > > For instance, one should be able to use > > > > { /usr/bin/ss -anp | /usr/bin/grep -v > > '^udp.*:60001[[:space:]].*"mosh-server"'

Bug#1082788: chkrootkit: README.FALSE-POSITIVES documentation for bindshell is incomplete

Package: chkrootkit Version: 0.58b-2 Severity: normal /usr/lib/python3/dist-packages/ansible_collections/cyberark/conjur/usr/share/doc/chkrootkit/README.FALSE-POSITIVES.gz says: ** use of well-known ports Some rootkits are known to listen on common ports that are also used by legitimate ser

Bug#1082745: aptitude: information mismatch for package removal

Control: retitle -1 aptitude: removes a kernel package not requested to be removed Control: severity -1 grave Wow! This is much worse than expected! When I typed 'g' to remove the 3 packages, aptitude also removed the linux-image-6.10.7-amd64 kernel package, which was *not* in the list of package

Bug#1082745: aptitude: information mismatch for package removal

Package: aptitude Version: 0.8.13-6.1 Severity: normal 4005 kB + 61.4 MB + 2264 kB does not give 172 MB. Actions Undo Package Resolver Search Options Views Help C-T: Menu ?: Help q: Quit u: Update g: Preview/Download/Install/Remove Pkgs Packages

Bug#1078402: gimp: FTBFS: dh_install: error: missing files, aborting

Any news? gimp has just been removed from testing because of this bug. Nothing has been done upstream for a backport for autoconf. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic /

Bug#948892: Please document that apt does not keep files in /var/cache/apt/archives

On 2024-09-23 17:52:33 +, Helge Kreutzmann wrote: > Hello David, > Am Thu, Sep 19, 2024 at 09:55:28PM +0200 schrieb David Kalnischkies: > > So, if you are interested in the config differences: > > | apt-config dump Binary::apt > > This is a very helpful hint, and I would strongly support havin

Bug#1080330: coreutils: who no longer works

Control: retitle -1 coreutils: "who" should support wtmpdb (y2038) Control: severity -1 wishlist Control: tags -1 upstream [Cc Luca Boccassi so that he gets aware of this issue. In short, "who" from coreutils still relies on utmp.] On 2024-09-20 11:39:55 -0300, Adilson dos Santos Dantas wrote: >

Bug#1076308: wtmpdb: wtmp.db created with wrong mode with system-wide umask 077

On 2024-07-14 13:22:08 +0200, Chris Hofstaedtler wrote: > On Sat, Jul 13, 2024 at 11:33:01PM -0400, ov2k wrote: > > wtmpdb respects the system-wide umask when creating > > /var/lib/wtmpdb/wtmp.db. This is inappropriate when the system-wide > > umask is 077 or something similarly restrictive, as wt

Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

Control: found -1 1.54.0+ds-2 And this still occurs with the latest libpango-1.0-0 version when testing with echo 'set terminal wxt; plot x' | gnuplot -persist -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: C

Bug#1064982: gnuplot-qt: gnuplot displays a window with nothing in it

nuplot-x11 On 2024-02-29 16:10:06 +0100, Vincent Lefevre wrote: > I've identified the "problematic" commit in Pango, and I would tend > to say that this is the reason: > > https://gitlab.gnome.org/GNOME/pango/-/commit/89442dae443eba2aa0f0a526b4d6d39c0c9b13c6 > > Ac

Bug#1014124: nomacs: CVE-2020-23884

Control: tags -1 - fixed-upstream Control: reassign -1 qt5-image-formats-plugins Control: retitle -1 buffer overflow in the mng plugin for Qt (CVE-2020-23884) The upstream fix in Nomacs was for MS Windows only: "I removed the qmng.dll plugin from Windows version. MNG files will not work by defaul

Bug#1081219: manpages: libc(7) bad display with "info glibc"

Package: manpages Version: 6.8-2 Severity: normal When I type "info glibc", this gives the libc(7), and I get [...] glibc By far the most widely used C library on Linux is the ^[]8;;http://www.g\ nu.org/software/libc/^[\GNU C Library^[]8;;^[\, of‐ [...] Other C libraries There

Bug#1078127: libc6: mcheck(NULL) fails even at the beginning of a program

Control: tags -1 upstream Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=32156 On 2024-09-09 11:42:43 +0200, Bernhard Übelacker wrote: [...] > In Bookworm and Trixie [3] the function mcheck always returns -1, > because "IS_IN (libc)" seems to be true at compile time. > > Re

Bug#1080978: libreoffice: steals the PRIMARY selection

Control: found -1 4:24.2.5-4 BTW, testing is affected (and maybe earlier versions too: I do not use LibreOffice often). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC projec

Bug#1080972: guile-3.0: triggers lots of warnings in gnucash

[Cc'ing the gnucash maintainer. As a summary, the downgrade of the guile-3.0 packages to upstream's 3.0.9 with 3.0.10+really3.0.9-1 prevents gnucash from using the compiled files, with consequences: lots of warnings and slowness.] On 2024-09-08 16:26:57 -0500, Rob Browning wrote:

Bug#1080972: guile-3.0: triggers lots of warnings in gnucash

On 2024-09-08 13:05:09 +0200, Vincent Lefevre wrote: > On 2024-09-07 17:43:07 -0500, Rob Browning wrote: > > Was just wondering if that was causing unexpected errors and > > auto-re-compilation, and if gnucash was built against that version > > (don't know how it handles

Bug#1080972: guile-3.0: triggers lots of warnings in gnucash

On 2024-09-07 17:43:07 -0500, Rob Browning wrote: > Vincent Lefevre writes: > > > And in particular, it makes the loading very slow. > > Did you ever install the (unstable only) 3.0.10 package? Unfortunately > we had to downgrade it because it isn't compatible w

Bug#1081071: gtk3-nocsd: Vcs information is obsolete: move to salsa

Source: gtk3-nocsd Version: 3-1 Severity: normal In the debian/control file: Vcs-Git: https://anonscm.debian.org/git/collab-maint/gtk3-nocsd.git -b debian/master Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/gtk3-nocsd.git With the move to salsa, I think that this should now be: Vc

Bug#825989: gtk3-nocsd: unclear comment in /etc/X11/Xsession.d/01gtk3-nocsd

On 2024-09-08 00:19:36 +0200, Vincent Lefevre wrote: > Hmm... This bug has been marked a pending since 2016! > > And the commit is no longer available, as the Git repository > no longer exists! At the PTS page > > https://tracker.debian.org/pkg/gtk3-nocsd >

Bug#825989: gtk3-nocsd: unclear comment in /etc/X11/Xsession.d/01gtk3-nocsd

On 2024-09-07 22:03:10 +0200, Enrique Garcia wrote: > I saw this but in the "Bug of the Day" page and since I am using it I just > wanted to check. As the last comment mentions, the comment in > /etc/X11/Xsession.d/01gtk3-nocsd seems fine now (confirmed in the last version > of gtk3-nocsd in Debian

Bug#1080978: libreoffice: steals the PRIMARY selection

Control: forwarded -1 https://bugs.documentfoundation.org/show_bug.cgi?id=162821 I've just reported the bug upstream. On 2024-09-06 11:17:43 +0200, Vincent Lefevre wrote: > To reproduce: > > 1. Open a .odt file with LibreOffice. Actually, other LibreOffice applications list Cal

Bug#1080978: libreoffice: steals the PRIMARY selection

Package: libreoffice Version: 4:24.2.6-1 Severity: important Tags: security LibreOffice steals the PRIMARY selection when a search is active, just when the mouse happens to move over the LibreOffice window. The PRIMARY selection should be changed only when the user selects something, not by just m

Bug#1080972: guile-3.0: triggers lots of warnings in gnucash

On 2024-09-06 08:08:43 +0200, Vincent Lefevre wrote: > Package: guile-3.0 > Version: 3.0.10+really3.0.9-1 > Severity: important > > This latest version triggers lots of warnings in gnucash: > > ;;; WARNING: loading compiled file > /usr/lib/x86_64-linux-gnu/guile

Bug#1080972: guile-3.0: triggers lots of warnings in gnucash

Package: guile-3.0 Version: 3.0.10+really3.0.9-1 Severity: important This latest version triggers lots of warnings in gnucash: ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/gnucash/utilities.go failed: ;;; In procedure load-thunk-from-memory: incompatible byt

Bug#1080492: firmware-nonfree: [i915] With 20240709-2, the external monitors randomly blank for 2-3 seconds (regression)

Source: firmware-nonfree Version: 20240709-2 Severity: important First, some context: I have a Dell laptop with 2 external monitors connected via a dock. With 6.8+ Linux kernels, one of the external monitors randomly blanks for 2-3 seconds (no such issue with earlier kernels); not always the same

Bug#1067679: libvte-2.91-0: backspace character (code 8) output at the end of a line goes 2 columns backward

Control: retitle -1 libvte-2.91-0: backspace character (code 8) output at the end of a line goes 2 columns backward (no reverse-wraparound) Control: close -1 On 2024-09-04 08:00:31 -0400, Jeremy Bícha wrote: > I don't think there is anything we are going to change directly in the > vte packaging

Bug#1080330: coreutils: who no longer works

On 2024-09-04 11:15:26 +0200, Chris Hofstaedtler wrote: > On Mon, Sep 02, 2024 at 11:15:19AM -0400, Michael Stone wrote: > > On Mon, Sep 02, 2024 at 01:07:59PM +0200, Vincent Lefevre wrote: > > > Severity: grave > > > Justification: renders package unusable > >

Bug#1080413: fail2ban: very old FSF address in debian/fail2ban.default

Package: fail2ban Version: 1.1.0-7 Severity: minor The debian/fail2ban.default file (installed as /etc/default/fail2ban) contains a very old FSF address (it has changed twice): # You should have received a copy of the GNU General Public License # along with Fail2Ban; if not, write to the Free Sof

Bug#1080336: reportbug: incorrect "Configuration Files" for procps

ot; EMAIL="vinc...@vinc17.net" INTERFACE="text" ** /home/vlefevre/.reportbugrc: reportbug_version "2.10" mode advanced ui text realname "Vincent Lefevre" email "vinc...@vinc17.net" mua mutt cc timeout 20 -- System Information: Debian Release: tr

Bug#1080335: w: missing tty information

Package: procps Version: 2:4.0.4-5 Severity: normal cventin:~> w 13:48:17 up 2 days, 23:50, 4 users, load average: 0.16, 0.15, 0.10 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT vlefevre -Fri13 22:45m 0.00s 0.25s /usr/lib/system vlefevre

Bug#1080333: procps: w(1) man page: obsolete contents about /var/run/utmp

Package: procps Version: 2:4.0.4-5 Severity: normal The w(1) man page contains: /var/run/utmp information about who is currently logged on and in SEE ALSO: "utmp(5)". As of systemd 256.5-2, utmp support is disabled (/var/run/utmp no longer exists), while w is still working.

Bug#1080330: coreutils: who no longer works

BTW, note that the "w" utility from procps still works, but according to strace, it doesn't seem to use wtmpdb. However, though the w(1) and who(1) man pages are similar ("show who is logged on"), w misses some information. -- Vincent Lefèvre - Web: 100% accessible vali

Bug#1080330: coreutils: who no longer works

Control: retitle -1 coreutils: "who" no longer works with systemd 256.5-2 (utmp is now disabled, use wtmpdb instead) (title with more details) -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer

Bug#1080332: chkrootkit: chkutmp failure - obsolete as utmp is now disabled

Package: chkrootkit Version: 0.58b-1+b4 Severity: normal With systemd 256.5-2, I now get: Checking `chkutmp'... WARNING WARNING: chkutmp output: failed opening utmp ! -

Bug#1080331: manpages: utmp(5): should warn that utmp is now obsolete

Package: manpages Version: 6.8-2 Severity: normal The utmp file is now obsolete. There should be a warning about that in the utmp(5) man page. FYI: systemd (256.5-2) unstable; urgency=medium [...] [ Luca Boccassi ] * Disable utmp support, replaced by wtmpdb. utmp is not y2038-safe, util-

Bug#1080330: coreutils: who no longer works

Package: coreutils Version: 9.4-3.1 Severity: grave Justification: renders package unusable Though the whole package is not unusable, an important utility is now unusable because coreutils still hasn't switched to wtmpdb. This must be fixed before the next Debian release. With systemd 256.5-2, "w

Bug#1079922: texlive-base: pathname missing in tl-paper output for context

Package: texlive-base Version: 2024.20240706-1 Severity: normal disset:~> tl-paper Current context paper size (from ): A4 Current dvipdfmx paper size (from /var/lib/texmf/dvipdfmx/dvipdfmx-paper.cfg): a4 Current dvips paper size (from /var/lib/texmf/dvips/config/config-paper.ps): a4 Current pdfte

Bug#1079786: texlive-latex-base: buggy testpage.tex: missing \usepackage{geometry}

On 2024-08-27 22:44:13 +0900, Norbert Preining wrote: > What youare asking is a fix to testpage.tex, to use geometry or some > other ways to set the *physical* page size. But that is as said not the > basic assumption. You can use testpage, and then print it on the correct > page size. The goal of

Bug#1079786: texlive-latex-base: buggy testpage.tex: missing \usepackage{geometry}

Package: texlive-latex-base Version: 2024.20240706-1 Severity: normal I've tried pdflatex /usr/share/texlive/texmf-dist/tex/latex/base/testpage.tex under Debian/unstable (TeX Live packages 2024.20240706-1) with \papertype=a5paper \doublesided=n (when asked to the question). The contents ass

Bug#1032609: zathura: immediate segmentation fault on some PDF file

Control: forwarded -1 https://github.com/pwmt/zathura/issues/395 Updating upstream bug number (duplicate of this bug). Other users have reported crashes under similar conditions. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#640462: libreoffice: default window appears partly off-screen

Control: retitle -1 libreoffice: default/document window can appear partly off-screen Control: found -1 4:24.2.5-3 I ran libreoffice with "libreoffice Downloads/n3148.doc", and most of the document appeared off-screen. I think that the center of the document window was positioned at the top-left

Bug#1079283: zathura: the first pages of a PDF document can appear as black

Control: severity -1 important Raising to important because on very large PDF files, such as the "Arm Architecture Reference Manual", the bug is always reproducible without any good workaround. Switching to dual view makes the problem disappear, but this is very slow and may require a lot of memor

Bug#1079283: zathura: the first pages of a PDF document can appear as black

Control: retitled -1 zathura: the first pages of a large PDF file can appear as black Control: tags -1 upstream Control: forwarded -1 https://github.com/pwmt/zathura/issues/365 There are 2 very similar issues open upstream: * https://github.com/pwmt/zathura/issues/65 (reported on 2018-06-13) "La

Bug#1079283: zathura: the first pages of a PDF document can appear as black

I restarted Firefox, so that the .local/share/zathura directory did not exist yet (as it is local to the sandbox), and I couldn't reproduce the problem at this point. I tried again several times after removing the .local/share/zathura directory. The real bug may be that bookmarks.sqlite became "co

Bug#1079283: zathura: the first pages of a PDF document can appear as black

Package: zathura Version: 0.5.8-1 Severity: normal I opened https://www.intel.fr/content/www/fr/fr/content-details/782158/intel-64-and-ia-32-architectures-software-developer-s-manual-combined-volumes-1-2a-2b-2c-2d-3a-3b-3c-3d-and-4.html with Firefox, which runs in firejail (firefox profile).

Bug#1079088: diffutils: diff -d can be very slow, affecting GNU Emacs

On 2024-08-20 02:10:08 +0200, Vincent Lefevre wrote: > I've just reported the following bug upstream: > > -- > When opening a .diff file, GNU Emacs runs "diff -ad" on 2 files > it has built (I suppose th

Bug#1079088: diffutils: diff -d can be very slow, affecting GNU Emacs

Package: diffutils Version: 1:3.10-1 Severity: important Affects: emacs-gtk Forwarded: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=72723 I've just reported the following bug upstream: -- When opening a .diff file, GNU Emacs runs "d

Bug#1079014: bugs.debian.org: unknown maintainers reported on bembo

On 2024-08-18 23:55:18 +0200, Chris Hofstaedtler wrote: > Control: retitle -1 bugs.debian.org: unknown maintainers reported on bembo > > The problem is not limited to specific packages, but to the specific > BTS installation on bembo. Indeed, I can see this issue for other package names, while th

Bug#1079014: bugs.debian.org: says that the maintainer is unknown for src:gcc-doc-defaults and src:gcc-13-doc

Package: bugs.debian.org Severity: normal On https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078158 Package: src:gcc-doc-defaults; Maintainer for src:gcc-doc-defaults is (unknown); and on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079010 Package: src:gcc-13-doc; Maintainer for s

Bug#1078939: zsh: incorrect expansion with expand-or-complete and single quote

Package: zsh Version: 5.9-8 Severity: normal Forwarded: https://zsh.org/workers/53040 Consider a directory with the following 3 files: a'1 a'2 ab I get as expected: disset% echo a\'* a'1 a'2 But if I type [Tab] (expand-or-complete) after a\'*, I get disset% echo a\'1 a\'2 ab instead of disse

Bug#1078158: gcc-doc-defaults: switch to GCC 14

On 2024-08-07 15:13:52 +0200, Andreas Beckmann wrote: > gcc-doc-defaults started to FTBFS when the default compiler has been > switched to GCC 14. Please update the doc package to GCC 14, too. But gcc-14-doc is not available in Debian yet. -- Vincent Lefèvre - Web: 100

Bug#1051496: mailgraph: does not support the new syslog format

(Replying only now because I haven't received some of these messages, though I'm normally subscribed to this bug.) On 2024-03-28 18:23:33 +0100, Jörg Frings-Fürst wrote: > We are using mailgraph one multiple server with Debian Bullseye, > Bookworm and Trixie without any failure. This is normal fo

Bug#708979: closed by Gioele Barabucci (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions)

At http://www.catb.org/esr/jargon/html/M/meta-bit.html it is written meta bit: n. The top bit of an 8-bit character, which is on in character values 128--255. Also called high bit, alt bit. Some terminals and consoles (see space-cadet keyboard) have a META shift key. [...] That's

Bug#708979: closed by Gioele Barabucci (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions)

On 2024-08-13 16:28:42 +0100, Reuben Thomas wrote: > I'm not quite sure I understand you here: are you saying that it's > documented somewhere that one should use the "\e" form? I'm saying that since the documentation says that the Meta key may generate an Escape character (which is actually the c

Bug#708979: closed by Gioele Barabucci (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions)

On 2024-08-10 15:50:55 +0100, Reuben Thomas wrote: > On Sat, 10 Aug 2024 at 10:03, Debian Bug Tracking System < > ow...@bugs.debian.org> wrote: > > -- Forwarded message -- > > From: Gioele Barabucci > > To: 708979-d...@bugs.debian.org > > Cc: > > Bcc: > > Date: Sat, 10 Aug 2024 11:

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

Control: tags -1 patch I've attached a patch fixing both issues. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) --- fail2ban-1.1.0-a/config/filter.d/

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

On 2024-08-11 02:53:27 +0200, Vincent Lefevre wrote: > On 2024-08-08 11:25:07 +0200, Vincent Lefevre wrote: > > As seen at https://github.com/fail2ban/fail2ban/pull/3782/files > > the change is quite simple: change > > > > _daemon = sshd > > > >

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

On 2024-08-08 11:25:07 +0200, Vincent Lefevre wrote: > As seen at https://github.com/fail2ban/fail2ban/pull/3782/files > the change is quite simple: change > > _daemon = sshd > > to > > _daemon = sshd(?:-session)? Unfortunately this change alone does not solve the issue

Bug#708979: \C-u still broken

On 2024-08-10 11:35:21 +0200, Vincent Lefevre wrote: > On 2024-08-10 09:03:04 +, Debian Bug Tracking System wrote: > > On Wed, 19 Apr 2006 15:11:20 +0100 Reuben Thomas wrote: > > > In my .inputrc I have the following lines: > > > > > > "\M-n"

Bug#1078428: libreadline8t64: \C-u kill-whole-line kills only the characters before the cursor instead of the whole line if ^U is the kill character

Package: libreadline8t64 Version: 8.2-4 Severity: normal With "\C-u": kill-whole-line in the .inputrc file, if ^U is the kill character (usual tty settings), \C-u kills only the characters before the cursor instead of the whole line. This bug was already present in some old libreadline versio

Bug#708979: \C-u still broken

Control: reopen -1 Control: found -1 5.2.21-2.1 On 2024-08-10 09:03:04 +, Debian Bug Tracking System wrote: > On Wed, 19 Apr 2006 15:11:20 +0100 Reuben Thomas wrote: > > In my .inputrc I have the following lines: > > > > "\M-n": history-search-forward > > "\M-p": history-search-backward > >

Bug#1078255: xterm: segmentation fault when clicking on the right button

On 2024-08-09 15:01:17 -0400, Thomas Dickey wrote: > On Fri, Aug 09, 2024 at 02:44:46PM -0400, Thomas Dickey wrote: > > Is this something that you might reproduce, to provide test-data? I tried to reproduce it, but I couldn't. > ld could be null if there's some inconsistency in the select begin/e

Bug#1078255: xterm: segmentation fault when clicking on the right button

Package: xterm Version: 393-1 Severity: important I got a segmentation fault when clicking on the right button. Core was generated by `/usr/bin/xterm -xrm *printFileOnXError: /home/vinc17/private/xterm-saved-172316'. Program terminated with signal SIGSEGV, Segmentation fault. #0 class_of (cell=

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

Package: fail2ban Version: 1.1.0-4 Severity: serious Tags: upstream fixed-upstream The fail2ban sshd.conf filter does not works with OpenSSH 9.8. This is due to openssh (1:9.8p1-1) unstable; urgency=medium * New upstream release (https://www.openssh.com/releasenotes.html#9.8p1): [...] - ss

Bug#1076449: Re-assigning to mercurial, should be fixed there

On 2024-08-07 15:55:14 +0200, Matthias Klose wrote: > Python 3.12.5 released with that patch, so I assume upstream will not fix > that. > > The Debian bug contains a proposal for a less invasive fix in mercurial, > therefore re-assigning and keeping the bug open Note that this has already been fi

Bug#1078166: apt-daily.service is sometimes executed during package installation

On 2024-08-07 16:42:56 +0200, Julian Andres Klode wrote: > As I mentioned in the other thread, we do not do anything with the > systemd services. We do restart the timers, which I guess could mess > up the randomization or something? > > But I don't know, I'd need more info from systemd people. A

Bug#1070027: apt: daily systemd service handles dpkg frontend locking incorrectly?

On 2024-08-07 14:16:59 +0200, Julian Andres Klode wrote: > On upgrades, we do not restart or reload or otherwise interact with > either apt-daily service, and the services are ordered so they do not > run at the same time either; so you won't see races between the services > or races from the servi

Bug#1078166: apt-daily.service is sometimes executed during package installation

Package: apt Version: 2.9.7 Severity: normal The installation/upgrade of some packages reloads the systemd daemons, which occasionally has the effect to execute the apt-daily service, which runs "/usr/lib/apt/apt.systemd.daily update". This is silly, because precisely at this time, either there a

Bug#1070027: apt: daily systemd service handles dpkg frontend locking incorrectly?

On 2024-08-07 11:56:56 +0200, Julian Andres Klode wrote: > Control: reassign -1 aptitude > Control: retitle -1 aptitude: frontend lock support > > On Wed, Aug 07, 2024 at 11:38:35AM GMT, Vincent Lefevre wrote: > > On 2024-08-07 11:04:15 +0200, Guillem Jover wrote: > > &g

Bug#1070027: apt: daily systemd service handles dpkg frontend locking incorrectly?

On 2024-08-07 11:04:15 +0200, Guillem Jover wrote: > On Thu, 2024-07-25 at 11:03:50 +0200, Vincent Lefevre wrote: [...] > > With VERBOSE=2, I could get more details about this failure: > > > > Jul 25 13:22:16 qaa systemd[1]: Starting apt-daily.service - Daily apt &g

Bug#1078128: libc6: mtrace() + malloc() do not generate data

Package: libc6 Version: 2.39-6 Severity: normal When testing the example given in the mtrace(3) man page, no data are generated: $ cat t_mtrace.c #include #include #include int main(void) { mtrace(); for (unsigned int j = 0; j < 2; j++) malloc(100);/* Never freed--a memor

Bug#1078127: libc6: mcheck(NULL) fails even at the beginning of a program

Package: libc6 Version: 2.39-6 Severity: normal The following program #include #include int main (void) { int r; r = mcheck (NULL); printf ("%d\n", r); return 0; } outputs -1, which is incorrect. It should have been 0. The glibc manual says It is too late to begin allocation chec

Bug#1076729: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

On 2024-08-05 12:42:42 +0200, Vincent Lefevre wrote: > This bug was closed, but has not been marked as fixed in > libwayland-client0, so that the current version is still > regarded as buggy, as reported by apt-listbugs: > > serious bugs of libwayland-client0 (1.22.0-2.1+b1 →

Bug#1076729: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

This bug was closed, but has not been marked as fixed in libwayland-client0, so that the current version is still regarded as buggy, as reported by apt-listbugs: serious bugs of libwayland-client0 (1.22.0-2.1+b1 → 1.23.0-1) b1 - #1076729 - libwayland: breaks plasma desktop start after last upgra

Bug#1032609: zathura: immediate segmentation fault on some PDF file

Control: retitle -1 zathura: crash when quitting before PDF rendering is complete Control: forwarded -1 https://github.com/pwmt/zathura/issues/656 I've submitted an issue upstream. On 2024-08-05 10:03:45 +0200, Vincent Lefevre wrote: > I can still reproduce the segmentation fault on

Bug#1032609: zathura: immediate segmentation fault on some PDF file

Control: found -1 0.5.6-1 Control: found -1 0.5.8-1 I can still reproduce the segmentation fault on the same machine before the upgrade to the latest version, and after the upgrade. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#1077886: xterm: spurious characters in reverse video in scrollback buffer

On 2024-08-05 04:17:16 +0200, Vincent Lefevre wrote: > Unfortunately, I can't reproduce the issue with a simple testcase. The issue might be due to the progress bar, which is kept at the bottom of the xterm window while there is scrolling output above it. This probably involves some

Bug#1074390: "SyntaxWarning: invalid escape sequence" with python 3.12

Control: tags -1 upstream fixed-upstream Control: forwarded -1 https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/188 On 2024-08-04 17:29:54 -0500, john faulk wrote: > this bug appears to still exist in Trixie as of 8/4/20204, in version 3.4.7-2 Yes, it was reported against this version.

Bug#1077886: xterm: spurious characters in reverse video in scrollback buffer

On 2024-08-04 18:56:11 -0400, Thomas Dickey wrote: > On Sun, Aug 04, 2024 at 03:34:12AM +0200, Vincent Lefevre wrote: > > Some characters in the scrollback buffer can appear in reverse video. > > But after scrolling again, they appear as normal, even when there was > > no outp

Bug#1077961: zathura: useless message about the database on a new machine

Package: zathura Version: 0.5.8-1 Severity: normal I've just installed zathura on a new machine (Debian/unstable), i.e. it does not come from an upgrade. Each time I run it, I get the following useless message: info: Opening plain database via sqlite backend. info: No plain database available. C

Bug#1077886: xterm: spurious characters in reverse video in scrollback buffer

Package: xterm Version: 393-1 Severity: normal Some characters in the scrollback buffer can appear in reverse video. But after scrolling again, they appear as normal, even when there was no output. This occurred while I was upgrading packages with apt on a remote machine (via ssh in xterm), perha

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression)

Control: found -1 6.9.12-1 Control: forwarded -1 https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11821 On 2024-07-31 20:21:12 +0200, Ben Hutchings wrote: > Could you please report this upstream following > ? Done: h

Bug#1077587: still occurs (reply to Sylvestre Ledru ) (Bug#1077587: fixed in llvm-toolchain-18 1:18.1.8-8)

On 2024-08-01 14:02:15 +0200, Vincent Lefevre wrote: > On 2024-07-30 09:39:08 +, Debian Bug Tracking System wrote: > > Changes: > > llvm-toolchain-18 (1:18.1.8-8) unstable; urgency=medium > > . > >* Fix breaks/replaces (Closes: #1077587) > > Package: llv

Bug#1077587: still occurs (reply to Sylvestre Ledru ) (Bug#1077587: fixed in llvm-toolchain-18 1:18.1.8-8)

Control: reopen -1 Control: found -1 1:18.1.8-8 On 2024-07-30 09:39:08 +, Debian Bug Tracking System wrote: > Changes: > llvm-toolchain-18 (1:18.1.8-8) unstable; urgency=medium > . >* Fix breaks/replaces (Closes: #1077587) Package: llvm-18-dev Source: llvm-toolchain-18 Version: 1:18.1.8

Bug#1021533: pinfo: cat: /usr/share/info/python3.10: Is a directory

Control: retitle -1 pinfo: "pinfo " fails if also exists as a directory On 2022-10-10 11:31:57 +0200, Jakub Wilk wrote: >$ pinfo python3.10 >Przemek's Info Viewer v0.6.13 >cat: /usr/share/info/python3.10: Is a directory >Failed to execute command 'cat /usr/share/info/python3.10>

Bug#1077605: pinfo: copies a file from the current directory to /tmp

Package: pinfo Version: 0.6.13-1.3+b1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team When running "pinfo mpfr", I can see in the strace output: execve("/bin/sh", ["sh", "-c", "--", "cat ./mpfr> /tmp/pinfo.tVVaeB"], 0x7ffc16308110 /* 135 vars

Bug#1077587: llvm-18-dev: tries to overwrite '/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is also in libllvm18 1:18.1.8-5

Package: llvm-18-dev Version: 1:18.1.8-7 Severity: serious When upgrading the llvm-toolchain-18 packages: Unpacking llvm-18-dev (1:18.1.8-7) over (1:18.1.8-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-LjdMdY/04-llvm-18-dev_1%3a18.1.8-7_amd64.deb (--unpack): trying to overwrite '/

Bug#1076582: Bug#1077274: Excessive initramfs size with firmware-nvidia-graphics and plymouth

On 2024-07-29 15:59:14 +0200, Rodrigo Campos wrote: > On 7/28/24 10:33 PM, Ben Hutchings wrote: > > This issue was fixed by initramfs-tools version 0.143 in experimental. > > I have just uploaded version 0.143.1 to unstable, so you should be able > > to get the fix through a regular upgrade in a fe

Bug#1076582: Processed (with 1 error): tagging 1076539, forcibly merging 1076582 1076539

Control: notfixed -1 0.143 Control: fixed -1 initramfs-tools/0.143 There's a bug in the BTS software, which forgot the source package name for bug 1076582. On 2024-07-28 20:27:17 +, Debian Bug Tracking System wrote: > After four attempts, the following changes were unable to be made: > fixed_

  1   2   3   4   5   6   7   8   9   10   >