Bug#1056313: network-manager: breaks networking

On 2023-11-20 12:42:14 +0100, Vincent Lefevre wrote: > I suspect that nm-dhcp-helper has been added because it is now needed. > But it doesn't work due to the "Permission denied". If I understand correctly, /usr/lib/NetworkManager/nm-dhcp-helper moved to /usr/libexec/nm-

Bug#1056313: network-manager: breaks networking

Control: found -1 1.44.2-3 Control: retitle -1 network-manager: breaks networking (Permission denied for the new /usr/libexec/nm-dhcp-helper) On 2023-11-20 12:24:36 +0100, Vincent Lefevre wrote: > Package: network-manager > Version: 1.44.2-4 > Severity: grave > Justification: ren

Bug#1056313: network-manager: breaks networking

Package: network-manager Version: 1.44.2-4 Severity: grave Justification: renders package unusable Just after the upgrade of network-manager from 1.44.2-1 to 1.44.2-4, my network is down. In the journalctl logs, I can see [...] Nov 20 12:08:58 cventin NetworkManager[286424]: [1700478538.0092]

Bug#1056051: reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved Permanently, which is ignored

On 2023-11-16 17:34:57 +0100, Nis Martensen wrote: > On 16.11.2023 12.48, Vincent Lefevre wrote: > > Control: retitle -1 reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved > > Permanently > > > > On 2023-11-16 12:34:17 +0100, Vincent Lefevre wrote: > &g

Bug#1055931: apt ignores bullseye-backports

Hi Nis, On 2023-11-16 17:31:13 +0100, Nis Martensen wrote: > On 14.11.2023 15.17, Vincent Lefevre wrote: > >> Checking for newer versions at madison and > >> https://ftp-master.debian.org/new.html > >> > >> Your version (6.1.55-1) of linux-image-6.1.0-1

Bug#1056051: reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved Permanently, which is ignored

Control: retitle -1 reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved Permanently On 2023-11-16 12:34:17 +0100, Vincent Lefevre wrote: > So this URL gives a 301 Moved Permanently with > https://ftp-master.debian.org/new.822 as the new URL, > and reportbug does not attempt to use thi

Bug#1056051: reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved Permanently, which is ignored

ing should be output in order to be aware of the issue, in case of a future move. -- Package-specific info: ** Environment settings: EDITOR="/home/vinc17/bin/eclient" PAGER="less -Lis" VISUAL="/home/vinc17/bin/eclient" EMAIL="vinc...@vinc17.net" INTERFACE=&quo

Bug#1055971: atril: should not use the filename extension to determine the file type

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

Bug#1055971: atril: should not use the filename extension to determine the file type

Package: atril Version: 1.26.0-2+b1 Severity: normal Consider a gzipped postscript file with 2 different names: file.ps.gz file.ps-1.gz While file.ps.gz can be read correctly by atril, for file.ps-1.gz, atril gives the following error: Unable to open document File type Gzip archive (app

Bug#1055945: linux-image-6.1.0-13-amd64: touchpad buttons sometimes stop working for several seconds/minutes

Package: src:linux Version: 6.1.55-1 Severity: important The touchpad buttons of my new laptop sometimes stop working for several seconds or minutes (typically from 25" to 6'20"). The time between two consecutive issues also varies and can be very short, such as 30 seconds. The device in question

Bug#1055931: apt ignores bullseye-backports

Cc'ing Reportbug Maintainers. On 2023-11-14 14:51:18 +0100, Vincent Lefevre wrote: > Going back to what reportbug says, it still outputs > > [...] > Getting status for linux-image-6.1.0-13-amd64... > Verifying package integrity... > Checking for newer versions at mad

Bug#1055931: apt ignores bullseye-backports

On 2023-11-14 13:45:21 +0100, Vincent Lefevre wrote: > But "apt show -a linux-image-6.1.0-13-amd64" just gives the 6.1.55-1 > version (no 6.1.55+1~bpo11+1 version), and > > apt install -t bullseye-backports linux-image-6.1.0-13-amd64 > > also thinks that 6.1.55-1 is

Bug#1055931: apt ignores bullseye-backports

Package: apt Version: 2.6.1 Severity: important When I want to report a bug against the Linux kernel, reportbug recommends to use bullseye-backports to get a more recent version (even though this is currently a bookworm based machine): Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears

Bug#1041838: Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a

1838@b.d.o, so that I was confused). On 2023-11-09 14:13:37 +0100, Vincent Lefevre wrote: > On 2023-07-24 06:54:27 +0200, Helmut Grohne wrote: > > Control: clone -1 -2 > > Control: reassign -2 libclang-rt-17-dev > > > > On Mon, Jul 24, 2023 at 06:45:00AM +0200, Helmut G

Bug#1055624: viking: Segmentation fault when quitting viking

Package: viking Version: 1.10-2 Severity: important I got a segmentation fault when I quit viking: [...] (viking:45727): GLib-GObject-WARNING **: 00:24:41.116: invalid unclassed pointer in cast to 'VikLayer' (viking:45727): GLib-GObject-WARNING **: 00:24:41.116: invalid unclassed pointer in ca

Bug#808425: firefox: hover status becomes false when the mouse pointer is invisible

on my new machine because Debian installs unclutter by default! The problem disappears after I kill unclutter. On 2015-12-20 00:40:38 +0100, Vincent Lefevre wrote: > Package: iceweasel > Version: 43.0-1 > Severity: important > > The hover status becomes false when the mouse pointe

Bug#1055309: gkrellm: the clock format should honor the LC_TIME locale by default

Package: gkrellm Version: 2.3.11-2 Severity: wishlist The default clock (time) format is %l:%M %S but %l is the hour between 1 and 12, which is not the format used by most countries (in addition to being confusing). The default clock format should be based on the current LC_TIME locale. -- S

Bug#1055243: libinput10: invalid URL in Xorg logs due to incorrect HTTP_DOC_LINK value

Package: libinput10 Version: 1.22.1-1 Severity: minor In my Xorg logs (e.g. Keyb/var/log/Xorg.0.log), I get messages like [ 10491.518] (EE) event14 - VEN_04F3:00 04F3:311C Touchpad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.22.1/touchpad-j

Bug#1055197: cron: "crontab -l" background color output is still incorrect

On 2023-11-01 23:08:53 +0100, Vincent Lefevre wrote: > "crontab -l" still incorrectly outputs a yellow background color where > it shouldn't: when scrolling is involved[*], the trailing whitespace > in a line that follows a comment (possibly the prompt line) has a

Bug#1055197: cron: "crontab -l" background color output is still incorrect

Package: cron Version: 3.0pl1-178 Severity: normal "crontab -l" still incorrectly outputs a yellow background color where it shouldn't: when scrolling is involved[*], the trailing whitespace in a line that follows a comment (possibly the prompt line) has a yellow background. BTW, among the progra

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

Hi Andreas, On 2023-11-01 18:39:24 +0100, Andreas Metzler wrote: > I am closing this since afaict this is a solved issue and I do not see > any TODOs on the gpgme side. > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gpgme-config-transition;users=pkg-gnupg-ma...@lists.alioth.debian.org > has s

Bug#1055055: lightdm-gtk-greeter: fonts should be large enough by default

Package: lightdm-gtk-greeter Version: 2.0.8-2+b1 Severity: wishlist I have a 15" laptop with a 4K screen, i.e. with a very high DPI. With the gdm3 display manager, the font size was OK by default. But when I switched to lightdm, the fonts became tiny and difficult to read. For obvious accessibili

Bug#1054985: gpg-agent: missing dependency on pinentry-curses or pinentry-gtk2

Package: gpg-agent Version: 2.2.40-1.1 Severity: important gpg-agent needs a working pinentry program. As pinentry-gnome3 (installed by default) doesn't work on non-GNOME environments, it should depend on pinentry-curses or pinentry-gtk2. With just pinentry-gnome3 installed, this makes emacs comp

Bug#1054656: perl: segfault in a threaded script after a Ctrl-C

Package: perl Version: 5.32.1-4+deb11u2 Severity: normal I've done a Ctrl-C to terminate a Perl script. But it was terminated with a segmentation fault: [...] Reading tmp/tst-arbre-1698058266-44878-8.results ... ^CInterrupt Perl exited with active threads: 1 running and unjoined 9

Bug#1054650: dbus: makes the machine extremely slow, freezes on shutdown

Package: dbus Version: 1.14.10-2 Severity: critical Justification: breaks the whole system dbus 1.14.10-2 makes the machine extremely slow (this affects the boot, login, the su command, and package installation at least), and it freezes on shutdown. This is reproducible (I've tested on 2 successiv

Bug#1054628: unzip: zipgrep doesn't handle regexp with some special characters correctly

Package: unzip Version: 6.0-28 Severity: normal Tags: upstream patch zipgrep doesn't handle regexp with some special characters correctly, as shown below. $ echo a.b > file1 $ echo a-b > file2 $ zip files.zip file1 file2 adding: file1 (stored 0%) adding: file2 (stored 0%) With egrep: $ egre

Bug#1020358: libmagickcore-6.q16-7: transition gsfonts/gsfonts-x11 --> fonts-urw-base35

On 2023-10-23 14:07:36 +0200, Bastien ROUCARIES wrote: > Le lun. 23 oct. 2023 à 11:45, Vincent Lefevre a écrit : > > > Control: found -1 8:6.9.12.98+dfsg1-2 > > > > On 2022-09-20 18:18:23 +0200, fab...@debian.org wrote: > > > you are receiving this bug report

Bug#1054506: imagemagick: typo in debian/patches/0030-Add-a-debian-policy.patch

Source: imagemagick Version: 8:6.9.12.98+dfsg1-2 Severity: normal In the debian/patches/0030-Add-a-debian-policy.patch file: --- a/config/Makefile.am +++ b/config/Makefile.am @@ -1,4 +1,4 @@ -# Copyright 1999 ImageMagick Studio LLC, a non-profit organization +# Copyrght 1999 ImageMagick Studio

Bug#1054487: manpages-dev: mtrace(3): LD_PRELOAD=libc_malloc_debug.so is needed

Control: retitle -1 manpages-dev: mcheck(3), mtrace(3): LD_PRELOAD=libc_malloc_debug.so is needed Control: forwarded -1 https://lore.kernel.org/linux-man/20231024143144.76490-1-vinc...@vinc17.net/T/#u There's the same issue in the mcheck(3) man page. I've submitted a patch upstream. Ideally, th

Bug#1054492: exim4: please fix documentation about QUEUEINTERVAL in /etc/default/exim4

Package: exim4 Version: 4.97~RC3-1 Severity: normal QUEUEINTERVAL in /etc/default/exim4 no longer works (according to tests and to debian/NEWS), while it is still documented in debian/debconf/conf.d/retry/30_exim4-config, which contains: # Please note that these rules only limit the frequency of

Bug#1054487: manpages-dev: mtrace(3): LD_PRELOAD=libc_malloc_debug.so is needed

Control: reassign -1 manpages-dev 6.03-2 Control: retitle -1 manpages-dev: mtrace(3): LD_PRELOAD=libc_malloc_debug.so is needed Control: tags -1 upstream I can also reproduce the issue on a Red Hat machine with glibc 2.34, but this is actually an error in the man page: one now needs to preload th

Bug#1054487: libc6: mtrace doesn't produce any result

Control: retitle -1 libc6: mtrace doesn't produce any result Control: found -1 2.36-9+deb12u3 On 2023-10-24 14:07:10 +0200, Vincent Lefevre wrote: > Even when MALLOC_TRACE is set, mtrace() doesn't produce any result. > > I've tested the example given in the mtrace(3) ma

Bug#1054487: libc6:amd64: mtrace doesn't produce any result

Package: libc6 Version: 2.37-12 Severity: normal Even when MALLOC_TRACE is set, mtrace() doesn't produce any result. I've tested the example given in the mtrace(3) man page, and the /tmp/t file is not created. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT p

Bug#1054390: noisy output

On 2023-10-23 10:41:27 +0100, Barak A. Pearlmutter wrote: > It's great that people are using Xournal++, and care enough about it > to be bothered by this! FYI, I've been using Xournal (xournal package) until now, which doesn't have this issue. But I suppose that xournal will be removed from Debian

Bug#1020358: libmagickcore-6.q16-7: transition gsfonts/gsfonts-x11 --> fonts-urw-base35

Control: found -1 8:6.9.12.98+dfsg1-2 On 2022-09-20 18:18:23 +0200, fab...@debian.org wrote: > you are receiving this bug report, because your package declares a > relationship with the gsfonts and/or gsfonts-x11 packages. Both > packages have been replaced by fonts-urw-base35 since version > 2020

Bug#1054327: cron: color patch is undocumented and buggy but cannot be disabled

Control: found -1 3.0pl1-177 Control: retitle -1 cron: crontab color patch is undocumented and buggy but cannot be disabled Control: severity -1 important (mentioning "crontab" in the bug title and raising the severity because "crontab -l" modifies the terminal output status, which can affect the

Bug#1054390: xournalpp: outputs spurious ALSA lib warning messages in the terminal

Package: xournalpp Version: 1.2.2-1 Severity: important xournalpp outputs spurious ALSA lib warning messages in the terminal: ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2675:(sn

Bug#650479: iputils-ping: ping on an IP address doesn't do reverse DNS lookups

Control: tags -1 upstream Control: forwarded -1 https://github.com/iputils/iputils/issues/421 On 2011-11-30 04:08:11 +0100, Vincent Lefevre wrote: > According to the ping(8) man page, this is the -n option that > controls whether reverse DNS lookup is done or not, not the > fact

Bug#1054022: libncursesw6: broken in GNU Screen

Via JuiceSSH+mosh under Android, if I hit a key, I can see spurious escape sequences in the output after the error message: ^[[1;1R^[[49;80R^[[49;80R^[[49;80R -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR IN

Bug#1054022: libncursesw6: broken in GNU Screen

On 2023-10-16 04:10:36 -0400, Thomas Dickey wrote: > But in a quick check to "upgrade", my sources.list to investigate this, > I get stopped by the "improvements". It might help if you posted the > corresponding sources.list (or are you using the separate gpg stuff?). I'm wondering why this matte

Bug#1054022: libncursesw6: broken in GNU Screen

Package: libncursesw6 Version: 6.4+20231007-1 Severity: grave Justification: renders package unusable With libncursesw6 6.4+20231007-1, I get the following issue: $ screen -dRR mutt /usr/bin/mutt [screen is terminating] after a few seconds (or immediately "[screen is terminating]" when I hit a k

Bug#1053851: glx-diversions generates a dangling symlink for libGLX_indirect.so.0

Package: glx-diversions Version: 1.2.2 Severity: normal /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLX_indirect.so.0 is a symbolic link that points to an inexistent target: cventin% ls -l /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLX_indirect.so.0 lrwxrwxrwx 1 root root 16 2023-09-29 07:38:02 /

Bug#1053745: dateutils: broken symlinks: dateutils.dround -> dateroud, dateutils.dround.1.gz -> dateroud.1.gz

Control: tags -1 patch On 2023-10-10 14:14:59 +0800, Paul Wise wrote: > dateutils 0.4.10-2 introduced two broken symlinks: > >  /usr/bin/dateutils.dround -> dateroud >/usr/share/man/man1/dateutils.dround.1.gz -> dateroud.1.gz > > This appears to be because of a typo in the symlink creat

Bug#939079: nouveau: screen dimensions and resolution are wrong

Control: found -1 6.1.55-1 On 2019-09-01 04:11:15 +0200, Vincent Lefevre wrote: > With the nouveau driver, I get: > > $ xdpyinfo > [...] > screen #0: > dimensions:3200x1800 pixels (846x476 millimeters) > resolution:96x96 dots per inch > [...] > > whi

Bug#1053521: ghostscript: ps2pdf modifies ASCII text of a PDF file, breaking conversion to text and searching for text (regression)

Package: ghostscript Version: 10.02.0~dfsg-2 Severity: important Tags: upstream Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=707237 (Note that this is some form of data corruption.) If I run ps2pdf on the PDF file from https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3163.pdf the

Bug#1041731: groff-base: "-" mapped as HYPHEN

On 2023-09-11 20:33:27 -0700, Russ Allbery wrote: > Yes, I understand why upstream really wants to find a way to make the > distinction between a language hyphen and an ASCII hyphen to work. They > are different characters in the *roff language, and in a proper > typesetting system such as troff i

Bug#1052713: firejail(1) man page has U+2010 HYPHEN characters instead of U+002D HYPHEN-MINUS

Package: firejail Version: 0.9.72-2 Severity: minor The firejail(1) man page has U+2010 HYPHEN characters, e.g. $ firejail ‐‐dbus‐system=filter ‐‐dbus‐system.broadcast=\ org.freedesktop.Notifications=\ org.freedesktop.Notifications.*@/org/freedesktop/Notifications but sometimes the "

Bug#970557: Closing this bug (BTS maintenance for src:linux bugs)

Hi, On 2023-09-22 17:10:37 +0200, car...@debian.org wrote: > This bug was filed for a very old kernel or the bug is old itself > without resolution. > > If you can reproduce it with > > - the current version in unstable/testing > - the latest kernel from backports [...] Just a note to say that

Bug#1052451: when receiving a SIGINT, unison should send it to the process group, not just to ssh

Control: reassign -1 unison-2.53 2.53.3-2 Control: retitle -1 when receiving a SIGINT, unison should send it to the process group, not just to ssh A summary of the issue: I'm using a wrapper to ssh in order to call ssh-add before the real ssh, when needed. When I run unison and type Ctrl-C when a

Bug#1052451: openssh-client: Ctrl-C kills ssh but not ssh-add, which steals input from the terminal

Control: retitle -1 openssh-client: Ctrl-C does not kill a ssh-add run from a script (No issues with ssh-add is run directly from the shell, see below.) On 2023-09-22 12:18:24 +0200, Vincent Lefevre wrote: > On 2023-09-22 12:10:19 +0200, Vincent Lefevre wrote: > > On 2023-09-22 11:28

Bug#1052451: openssh-client: Ctrl-C kills ssh but not ssh-add, which steals input from the terminal

On 2023-09-22 12:10:19 +0200, Vincent Lefevre wrote: > On 2023-09-22 11:28:12 +0200, Vincent Lefevre wrote: > > It seems that that ssh command runs ssh-add automatically. > > While I did a Ctrl-C to interrupt ssh started by unison (for > > synchronization with a remote machin

Bug#1052451: openssh-client: Ctrl-C kills ssh but not ssh-add, which steals input from the terminal

On 2023-09-22 11:28:12 +0200, Vincent Lefevre wrote: > It seems that that ssh command runs ssh-add automatically. > While I did a Ctrl-C to interrupt ssh started by unison (for > synchronization with a remote machine) from mutt, ssh-add is > still running and attached to the termin

Bug#1052451: openssh-client: Ctrl-C kills ssh but not ssh-add, which steals input from the terminal

Package: openssh-client Version: 1:9.4p1-1 Severity: important It seems that that ssh command runs ssh-add automatically. While I did a Ctrl-C to interrupt ssh started by unison (for synchronization with a remote machine) from mutt, ssh-add is still running and attached to the terminal: UID

Bug#1052164: xemacs21: should not try to byte-compile the files from /usr/share/emacs/site-lisp

On 2023-09-18 16:20:00 +0200, Vincent Lefevre wrote: > Files in /usr/share/emacs/site-lisp are not necessarily compatible > with XEmacs. So XEmacs should not try to byte-compile them, or > at least, package installation should no fail because of that. > > For instance, mmm-mode is

Bug#1052166: mmm-mode: should avoid the conflict with xemacs21 by disabling the xemacs flavors

Package: mmm-mode Version: 0.5.9-2 Severity: important Tags: patch The conflict with xemacs21 is not acceptable as it prevents the installation of mmm-mode on machines with both emacs-gtk and xemacs21 installed (typically multi-user machines). It appears that disabling the xemacs flavors avoids t

Bug#1052164: xemacs21: should not try to byte-compile the files from /usr/share/emacs/site-lisp

Package: xemacs21 Version: 21.4.24-12 Severity: important Files in /usr/share/emacs/site-lisp are not necessarily compatible with XEmacs. So XEmacs should not try to byte-compile them, or at least, package installation should no fail because of that. For instance, mmm-mode is not compatible with

Bug#1052136: libcdb1: tries to overwrite /usr/share/man/man5/cdb.5.gz in tinycdb 0.78+b1

Package: libcdb1 Version: 0.80-1 Severity: serious When upgrading, I got: Unpacking libcdb1:amd64 (0.80-1) over (0.78+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-DmVfNl/25-libcdb1_0.80-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man5/cdb.5.gz', which is also in

Bug#1051116: maildrop: depends on libgcc1, which is no longer in the archive

On 2023-09-17 13:05:16 +0200, Sebastian Ramacher wrote: > On 2023-09-03 02:26:55 +0200, Vincent Lefevre wrote: > > Package: maildrop > > Version: 2.9.3-2+b1 > > Severity: grave > > Justification: renders package unusable > > > > maildrop depends on lib

Bug#1052040: mmm-mode: post-install script fails

Control: tags -1 - upstream The issue actually comes from the 01-xemacs patch. On 2023-09-16 17:46:23 +0200, Vincent Lefevre wrote: > An easy solution would be to avoid the XEmacs form (marked as > obsolete in GNU Emacs since 23.1 and whose support was removed > in GNU Emacs 28[*]), i.

Bug#1052040: mmm-mode: post-install script fails

Control: forwarded -1 https://github.com/dgutov/mmm-mode/issues/137 Control: tags -1 upstream On 2023-09-16 17:02:54 +0200, Vincent Lefevre wrote: > This appears to be related to macro expansion, which seems to > occur even if the code is not executed. An easy solution would be to avo

Bug#1052040: mmm-mode: post-install script fails

On 2023-09-16 16:53:33 +0200, Vincent Lefevre wrote: > If I understand correctly, the second define-obsolete-function-alias > (with 2 arguments) is executed instead of the first one (with 4 > arguments). This would mean that > > (string-match "XEmacs" (emacs-version

Bug#1052040: mmm-mode: post-install script fails

Ditto here. On 2023-09-16 14:31:11 +0200, mister...@web.de wrote: > In toplevel form: > mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2 This seems to be due to this change: -(defalias 'mmm-add-find-file-hooks #'mmm-add-find-file-hook) +(if (not (string-match "XEmacs" (emacs-versi

Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

And ghostscript 10.02.0~dfsg-2 has just appeared. Its changelog says * declare that ghostscript replaces older ghostscript-x so that now Package: ghostscript Version: 10.02.0~dfsg-2 Installed-Size: 180 Maintainer: Debian QA Group Architecture: amd64 Replaces: ghostscript-x (<< 10.02.0~dfsg-1)

Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

Note that just in case this would matter, I have several packages that depend on ghostscript-x: gv pspresent xournal -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (L

Bug#1051923: aptitude: incorrect dependency resolution for ghostscript vs virtual package ghostscript-x

Package: aptitude Version: 0.8.13-5 Severity: normal I have the following ghostscript-related packages installed: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/

Bug#1051844: initramfs-tools-core: the man pages have U+2010 HYPHEN characters instead of U+002D HYPHEN-MINUS

Package: initramfs-tools-core Version: 0.142 Severity: minor In the initramfs-tools(7) man page: Both /usr/share/initramfs‐tools/scripts and /etc/initramfs‐ tools/scripts contains the following subdirectories. where the dashes are U+2010 HYPHEN. This is incorrect and breaks copy-pa

Bug#1051579: nomacs: segmentation fault in std::__atomic_base

Package: nomacs Version: 3.17.2282+dfsg-2 Severity: important I got a segmentation fault when doing "View -> Close Tab" then a double click on a directory. The latest messages: [...] [INFO] "/home/vinc17/photos-tmp/DCIM/chamonix/20230620_175745.jpg" does not exist - according to a fast check [I

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

Control: tags -1 patch upstream On 2023-09-08 19:30:29 +0200, Vincent Lefevre wrote: > mailgraph no longer works after the upgrade to bookworm, and > this is probably due to the fact that it does not support the > new syslog format: /usr/sbin/mailgraph contains [...] > and this

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

Package: mailgraph Version: 1.14-20 Severity: grave Justification: renders package unusable mailgraph no longer works after the upgrade to bookworm, and this is probably due to the fact that it does not support the new syslog format: /usr/sbin/mailgraph contains sub _next_syslog($) { [...] li

Bug#1051441: systemd: user unit is no longer started after upgrade to bookworm

On 2023-09-08 14:21:49 +0200, Michael Biebl wrote: > If you have a custom mount setup, you should be able to tweak those unit > files to your needs e.g. via RequiresMountsFor= I had tried that in the past for apache2, but without any effect. I suppose that the goal of the "RequiresMountsFor" seems

Bug#1051441: systemd: user unit is no longer started after upgrade to bookworm

On 2023-09-08 13:05:23 +0200, Michael Biebl wrote: > Am 08.09.23 um 11:08 schrieb Vincent Lefevre: > > On 2023-09-08 07:48:43 +0200, Michael Biebl wrote: > > > Please attach the output of > > > systemctl --user status rsysinfo.service > > > > rsysinfo-statu

Bug#557328: apt: autoremove / build-dep interaction broken by virtual packages

Control: found -1 2.6.1 On 2009-11-21 13:14:25 +0100, Andreas Metzler wrote: > With APT::Get::Build-Dep-Automatic "apt-get autoremove" does not > remove packages pulled in by provides. The extended_states file gets a > wrong entry for the virtual package, instead of the real one. For "apt-get aut

Bug#1051441: systemd: user unit is no longer started after upgrade to bookworm

On 2023-09-08 07:48:43 +0200, Michael Biebl wrote: > Please attach the output of > systemctl --user status rsysinfo.service rsysinfo-status attached. > systemctl --user cat rsysinfo.service rsysinfo-cat attached. -- Vincent Lefèvre - Web: 100% accessible validated (X

Bug#1051331: mmm-mode: warnings in comp when starting Emacs 29 for the first time

Control: tags -1 fixed-upstream This was actually fixed upstream almost one year ago! https://github.com/dgutov/mmm-mode/commit/869d5ef62896f95e52c33aea8267e986bdb7d2c3 https://github.com/dgutov/mmm-mode/commit/d5af05a4a95b4e29663b0d7815a79d3ae1793453 and these fixes should be included in 0.5.9.

Bug#1051369: mmm-mode: please update to new upstream version 0.5.9

Package: mmm-mode Version: 0.5.8-4 Severity: normal Version 0.5.9 has been available since October 2022. Please update to this version. This should at least fix bug 1051331. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500

Bug#1051331: mmm-mode: warnings in comp when starting Emacs 29 for the first time

Control: tags -1 upstream Control: forwarded -1 https://github.com/dgutov/mmm-mode/issues/136 On 2023-09-06 11:37:38 +0200, Vincent Lefevre wrote: > When I remove the .emacs.d/eln-cache directory and run Emacs 29, > say with "emacs -q", I get the following warnings: > >

Bug#1051331: mmm-mode: warnings in comp when starting Emacs 29 for the first time

Package: mmm-mode Version: 0.5.8-4 Severity: normal When I remove the .emacs.d/eln-cache directory and run Emacs 29, say with "emacs -q", I get the following warnings: ⛔ Warning (comp): mmm-vars.el:869:2: Warning: defvar `mmm-classes-alist' docstring has wrong usage of unescaped single quotes (u

Bug#1041492: xpra: FTBFS with ffmpeg 6.0

Control: tags -1 fixed-upstream On 2023-07-19 19:10:36 +0200, Sebastian Ramacher wrote: > xpra FTBFS with ffmpeg 6.0 (available in experimental) and in unstable since a few weeks. Any news? FYI, https://github.com/Xpra-org/xpra/blob/v3.1.x/src/NEWS says that this is fixed in v3.1.4 (2023-03-05)

Bug#1051116: maildrop: depends on libgcc1, which is no longer in the archive

Package: maildrop Version: 2.9.3-2+b1 Severity: grave Justification: renders package unusable maildrop depends on libgcc1, which is no longer in the archive. This can be checked on https://packages.debian.org/en/bullseye/maildrop which says: dep: libgcc1 (>= 1:3.0) [not armel, armhf, i386,

Bug#1019732: apt-listbugs: undefined method `default' for " # returns password\n":String

On 2023-08-30 23:12:48 +0200, Francesco Poli wrote: > On Wed, 30 Aug 2023 00:19:51 +0200 Vincent Lefevre wrote: > > I don't see how this would separate the debug messages from the > > error messages. I recall that I do *not* want the debug data on > > the scree

Bug#1050866: poppler: missing ToUnicode support for similarequal

43, "asymptoticallyequal" } so one just needs to add the missing { 0x2243, "similarequal" } Merge-Request: https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1444 Author: Vincent Lefevre Last-Update: 2023-08-30 diff --git a/poppler/NameToUnicodeTable.h b/pop

Bug#1019732: apt-listbugs: undefined method `default' for " # returns password\n":String

On 2023-08-29 22:45:40 +0200, Francesco Poli wrote: > On Sun, 2 Apr 2023 23:18:57 +0200 Vincent Lefevre wrote: > > > On 2023-04-02 17:32:29 +0200, Francesco Poli wrote: > > > On Thu, 30 Mar 2023 01:02:00 +0200 Vincent Lefevre wrote: > > > > > > > On 2

Bug#880541: RFP: unison2.48.3 -- file-synchronization tool for Unix and Windows

On 2023-08-23 21:05:43 +0200, Bastian Germann wrote: > Please package version 2.53.x, which depends on lablgtk3 instead of > lablgtk2. AFAIK, it should now be sufficient to upgrade unison to 2.53.x. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#1046055: mpfr4: Fails to build source after successful build

On 2023-08-28 11:51:17 +0200, Vincent Lefevre wrote: > On 2023-08-28 11:15:15 +0200, Matthias Klose wrote: > > the package is built in a separate build dir. shouldn't the upstream > > makefile also build the info file in the build tree? > > I'm not sure. The

Bug#1046055: mpfr4: Fails to build source after successful build

On 2023-08-28 11:15:15 +0200, Matthias Klose wrote: > > Apparently this is due to the fact that the upstream mpfr.info file > > is rebuilt. > > the package is built in a separate build dir. shouldn't the upstream > makefile also build the info file in the build tree? I'm not sure. The issue is th

Bug#1049964: closed by Debian FTP Masters (reply to Georges Khaznadar ) (Bug#1049964: fixed in cron 3.0pl1-169)

On 2023-08-19 13:01:28 +0200, Chris Hofstaedtler wrote: > someone on IRC pointed out, that: > > 1) the original bug report seems to point out something that is not > a problem on supported systems. On such systems, /usr/sbin and > /sbin, and /usr/bin and /bin are equivalent. IMHO, it is too soon

Bug#1049969: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

On 2023-08-19 07:39:24 +0200, Ansgar wrote: > On Fri, 2023-08-18 at 22:45 +0200, Vincent Lefevre wrote: > > On 2023-08-18 07:35:33 +0200, Ansgar wrote: > > > Please investigate why "usrmerge" is not installed (I assume this is an > > > upgraded system).  Or

Bug#1049969: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

On 2023-08-18 07:35:33 +0200, Ansgar wrote: > This seems the be the real issue: > > +--- > | Debian Release: trixie/sid > | [...] > | merged-usr: no > +---[ https://bugs.debian.org/1049969#5 ] > > /bin *must* be a symlink to /usr/bin, so /usr/bin/run-parts must exist > and cron's PATH is sufficie

Bug#1050042: gnupg2: in man pages, U+2010 HYPHEN instead of U+002D HYPHEN-MINUS

Source: gnupg2 Version: 2.2.40-1.1 Severity: normal In various man pages, there are many U+2010 HYPHEN characters while U+002D HYPHEN-MINUS would be expected. For instance, for the gpg(1) man page: If you are going to verify detached signatures, make sure that the pro‐ gram knows

Bug#1049969: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

Control: retitle -1 cron-daemon-common: in /etc/crontab, run-parts is no longer in $PATH That's actually the real reason. /etc/crontab has PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin but zira:~> dlocate =run-parts debianutils: /bin/run-parts -- Vincent Lefèvre - Web:

Bug#1049969: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

Package: cron-daemon-common Version: 3.0pl1-166 Severity: serious (set to serious because this is a regression whose effect will be to send a spurious mail every hour) After upgrading to 3.0pl1-166, I got a mail with Subject: Cron cd / && run-parts --report /etc/cron.hourly /bin/sh: 1: ru

Bug#1018880: under ssh X11 forwarding, apps like nautilus that use xdg-desktop-portal start with 25s delay

On 2023-08-15 11:45:59 -0400, Jim McCann wrote: > Some additional information: this bug also triggers for me without > X11 forwarding. > > I don't run a desktop environment or graphical login (login in text > mode and then `startx` with fluxbox launched from .xinitrc); but I > still have xdg-deskt

Bug#1049423: gnome-calculator: takes 55 seconds to start

Control: reassign -1 src:gtk4 Control: retitle -1 GTK4 applications start with a 25- or 50-second delay when using X11 forwarding Control: found -1 4.10.5+ds-3 On 2023-08-15 15:41:02 -0400, Jeremy Bícha wrote: > On Tue, Aug 15, 2023 at 3:31 PM Vincent Lefevre wrote: > > On 2023-08-15

Bug#824747: gv: incorrect input of non-ASCII characters in the file selector

On 2023-08-15 16:33:53 +0200, наб wrote: > Retitling since you /can/ write the characters in the input, > they just get mangled and displayed byte-wise (bullseye). Yes, for display, but this also affects editing. For instance, "é" emits 2 bytes, which are regarded as 2 latin1 characters, thus one

Bug#1049423: gnome-calculator: takes 55 seconds to start

On 2023-08-15 11:42:53 -0400, Jeremy Bícha wrote: > On Tue, Aug 15, 2023 at 11:09 AM Vincent Lefevre wrote: > > gnome-calculator takes 55 seconds to start! > > > > In case this is related, I'm using X11 forwarding. > > As a blind guess, this may be related to

Bug#1049423: gnome-calculator: takes 55 seconds to start

Package: gnome-calculator Version: 1:44.0-2 Severity: important gnome-calculator takes 55 seconds to start! In case this is related, I'm using X11 forwarding. 1:45~beta-1 has the same issue (with the additional blank window bug, see bug 1043559). -- System Information: Debian Release: trixie/si

Bug#1046055: mpfr4: Fails to build source after successful build

On 2023-08-13 21:21:00 +0200, Lucas Nussbaum wrote: > > dpkg-source: error: aborting due to unexpected upstream changes, see > > /tmp/mpfr4_4.2.0-1.diff.v1TRvW The diff contains the following: --- mpfr4-4.2.0.orig/doc/mpfr.info +++ mpfr4-4.2.0/doc/mpfr.info @@ -1,4 +1,4 @@ -This is mpfr.info, pr

Bug#1043334: urlview is insecure: URL visible to everyone with commands like ps

Package: urlview Version: 0.9-23.1 Severity: important Tags: security upstream X-Debbugs-Cc: Debian Security Team Because urlview passes the URL as an argument, the URL can be visible to everyone with commands like ps, while the URL may contain private information, e.g. used for anthentication. T

Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

On 2023-08-05 13:04:56 +0200, Sven Joachim wrote: > Ah yes, Guillem implemented the "verbose" option three years ago in > reaction to #967911. And it could not be used back then because the > dpkg version offering it was only uploaded several months later, but now > it certainly can be used. :-) >

Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

On 2023-08-04 18:06:24 +0200, Sven Joachim wrote: > On 2023-08-04 01:57 +0200, Vincent Lefevre wrote: > > > On 2023-08-03 16:52:07 +0200, Sven Joachim wrote: [...] > >> It should prevent these errors from showing up in the first place. > > > > If aptitude knows wh

<    1   2   3   4   5   6   7   8   9   10   >