Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

2019-06-14 Thread Vincent Lefevre
Package: src:linux Version: 4.19.37-3 Severity: grave Tags: security Justification: user security hole When logging out, a part of the previous session is still visible. This might be used to compromise the user's account or leak other private information, depending on what was written on the

Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Vincent Lefevre
On 2019-06-12 17:23:31 +0200, Ivo De Decker wrote: > Hi, > > On Thu, Jun 13, 2019 at 12:13:30AM +0900, Vincent Lefevre wrote: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930430 contains: > > > > "Package: libasan5; Maintainer for libasan5 is Deb

Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Vincent Lefevre
Package: bugs.debian.org Severity: normal https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930430 contains: "Package: libasan5; Maintainer for libasan5 is Debian GCC Maintainers ; Source for libasan5 is src:gcc-9 (PTS, buildd, popcon). [...] Found in version gcc-8/8.3.0-7" The "src:gcc-9" is

Bug#930430: libasan5: AddressSanitizer breaks when LD_PRELOAD is defined

2019-06-12 Thread Vincent Lefevre
Package: libasan5 Version: 8.3.0-7 Severity: normal When LD_PRELOAD is defined (which can be a consequence of gtk3-nocsd being installed and the user being in an X11 session), I get: zira:~> gcc -fsanitize=address t.c zira:~> ./a.out ==11059==ASan runtime does not come first in initial library

Bug#930256: Ignoring Provides line with non-equal DepCompareOp for package firefox-l10n-bn-bd

2019-06-09 Thread Vincent Lefevre
On 2019-06-09 19:32:25 +0800, 積丹尼 Dan Jacobson wrote: > # apt-get update > W: Ignoring Provides line with non-equal DepCompareOp for package > firefox-l10n-bn-bd > W: Ignoring Provides line with non-equal DepCompareOp for package > firefox-l10n-bn-in Same problem (and ditto with aptitude, which

Bug#929567:

2019-06-07 Thread Vincent Lefevre
On 2019-06-06 09:31:28 +0200, Andreas Henriksson wrote: > On Wed, Jun 05, 2019 at 03:51:47PM +, J. Smith wrote: > > See https://debbugs.gnu.org/30045 (fixed in Emacs 26.2). > > According to the merged upstream duplicates these should be the relevant > fixes: > >

Bug#917314: Emacs 26 nXML bugs fixed with attached patch

2019-05-30 Thread Vincent Lefevre
Control: tags 917314 patch Control: tags 917398 patch I'm using the attached patch formed by various patches from the emacs-26 branch and others posted upstream[*]. It fixes both bugs 917314 and 917398 and some other issues. [*] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18871

Bug#929777: gcc-6: output errors to .gcda file are not checked

2019-05-30 Thread Vincent Lefevre
Package: gcc-6 Version: 6.3.0-18+deb9u1 Severity: normal When executing a program compiled with profile generation (-fprofile-generate), the obtained .gcda file is sometimes empty (apparently due to write errors). The problem is that the program terminates successfully, so that the issue is not

Bug#929712: perlfunc: "do EXPR" documentation issues concerning error checking

2019-05-29 Thread Vincent Lefevre
Package: perl-doc Version: 5.28.1-6 Severity: normal In the perlfunc(1) man page (or with "perldoc -f do"): If "do" can read the file but cannot compile it, it returns "undef" and sets an error message in $@. If "do" cannot read the file, it returns undef and sets $! to the error. Always

Bug#929696: inkscape: LaTeX renderer does not work

2019-05-29 Thread Vincent Lefevre
Control: tags -1 upstream Control: forwarded -1 https://gitlab.com/inkscape/extensions/issues/73 On 2019-05-29 09:52:27 +0200, Jonas Smedegaard wrote: > This is https://gitlab.com/inkscape/extensions/issues/73 upstream - but > unfortunately closed which seems wrong to me: Thanks for the

Bug#929696: inkscape: LaTeX renderer does not work

2019-05-29 Thread Vincent Lefevre
Package: inkscape Version: 0.92.4-3 Severity: normal If I try Extensions -> Render -> LaTeX, even on a simple formula like $x^3$ (or even just the letter x), I get a dialogue box with: Inkscape has received additional data from the script executed. The script did not return an error, but this

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

2019-05-26 Thread Vincent Lefevre
Testcase: $ printf '\u26D4\n' > test $ emacs -Q test It is U+26D4 NO ENTRY that triggers the crash. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

2019-05-26 Thread Vincent Lefevre
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/221 (This is the new upstream bug URL.) -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP,

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

2019-05-26 Thread Vincent Lefevre
On 2019-05-26 11:05:01 +0200, Vincent Lefevre wrote: > Package: libgtk-3-0 > Version: 3.24.5-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > When starting Emacs on a large file, I always get the following error. > This makes Emacs imposs

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

2019-05-26 Thread Vincent Lefevre
Package: libgtk-3-0 Version: 3.24.5-1 Severity: grave Tags: upstream Justification: renders package unusable When starting Emacs on a large file, I always get the following error. This makes Emacs impossible to use. X protocol error: BadLength (poly request too large or internal Xlib length

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

2019-05-23 Thread Vincent Lefevre
On 2019-05-20 15:54:42 +0200, Vincent Lefevre wrote: > Things have changed again with FreeType 2.9 (libfreetype6 2.9.1-3). [...] Sorry, I think that the change was just due to a different Xft.dpi value (as I did the test on a different machine): 132 instead of 88. Anyway, the problem is the s

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

2019-05-20 Thread Vincent Lefevre
Control: found -1 344-1 Control: found -1 345-1 Things have changed again with FreeType 2.9 (libfreetype6 2.9.1-3). I now get with "DejaVu Sans Mono" and size 10 (-fs 10): Xft metrics screen->renderFontNorm[0] = 21 (18,5)* advance 11, actual 11 Xft metrics screen->renderFontBold[0] = 21 (18,5)*

Bug#909750: applications tries to write to /usr/* directories via libfontconfig1

2019-05-20 Thread Vincent Lefevre
After upgrading fontconfig to 2.13.1-2, I now have lots of .uuid files: -rw-r--r-- 1 root staff 36 2019-05-20 13:08:26 /usr/local/share/fonts/.uuid -rw-r--r-- 1 root root 36 2019-05-20 13:08:26 /usr/share/fonts/.uuid -rw-r--r-- 1 root root 36 2019-05-20 13:08:27 /usr/share/fonts/X11/.uuid

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-05-20 Thread Vincent Lefevre
On 2019-05-14 15:33:45 +0200, Tobias Eliasson wrote: > Are you able to reproduce this error with the latest fontconfig 2.13.1 in > buster? I've just tried, and I no longer get a failure. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-17 Thread Vincent Lefevre
On 2019-05-16 18:36:09 +0200, Michael Biebl wrote: > Am 16.05.19 um 18:17 schrieb Vincent Lefevre: > > On 2019-05-16 17:52:03 +0200, Michael Biebl wrote: > >> I would suggest the following: If there is a local nameserver but no > >> network connectivity, quer

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 17:52:03 +0200, Michael Biebl wrote: > I would suggest the following: If there is a local nameserver but no > network connectivity, query the local nameserver only. OK, I can do that. Indeed, the default behavior of "host" is to try every server in /etc/resolv.conf until it

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 16:54:26 +0200, Michael Biebl wrote: > I'm happy to review a tested patch, which considers your specific use case. Would one of the following behaviors be OK? 1. If there is no default route, then assume that we can't reach any nameservers (there's potentially a local nameserver,

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 16:25:01 +0200, Michael Biebl wrote: > What happens, if you only list your local 127.0.0.1 in /etc/resolv.conf? See my other mail, i.e. no problems. FYI, I use 192.168.1.1 just as a fallback. > Well, the assumption that /usr/lib/avahi/avahi-daemon-check-dns.sh makes > is, that if a

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 16:09:04 +0200, Vincent Lefevre wrote: > On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote: > > On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > > > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > > > On 2019-05-16 14:15:37 +0200, Michael Biebl

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote: > On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > > >> Looks like you have a local resolver

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 14:41:44 +0200, Michael Biebl wrote: > Am 16.05.19 um 14:22 schrieb Vincent Lefevre: > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > >> Looks like you have a local resolver configured in /etc/resolv.conf > >> (which should be reachable v

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-16 Thread Vincent Lefevre
On 2019-05-16 14:15:37 +0200, Michael Biebl wrote: > Looks like you have a local resolver configured in /etc/resolv.conf > (which should be reachable via lo, even if eth0 is down). Yes, /etc/resolv.conf contains nameserver 127.0.0.1 nameserver 192.168.1.1 as I use "unbound". -- Vincent

Bug#929010: [Pkg-utopia-maintainers] Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-15 Thread Vincent Lefevre
On 2019-05-15 12:50:49 +0200, Michael Biebl wrote: > Which part of /usr/lib/avahi/avahi-daemon-check-dns.sh is taking so long? > Can you add a "set -x" and then manually invoke "ifdown eth0" I get: + PATH=/bin:/usr/bin:/sbin:/usr/sbin + RUNDIR=/var/run/avahi-daemon/ +

Bug#929017: mutt: undefined behavior on huge integer in a RFC 2231 header

2019-05-15 Thread Vincent Lefevre
Package: mutt Version: 1.10.1-2 Severity: serious Tags: security upstream fixed-upstream The rfc2231.c file contains: index = atoi (s); where the string s is part of a RFC 2231 parameter in a header. For instance, if in a message (invalid, but which can occur due to spam, attack, etc.),

Bug#929010: avahi-daemon: /etc/network/if-post-down.d/avahi-daemon is slow on eth0

2019-05-15 Thread Vincent Lefevre
Package: avahi-daemon Version: 0.7-4+b1 Severity: normal /etc/network/if-post-down.d/avahi-daemon takes 12 seconds to complete, slowing the shutdown: [...] May 15 10:23:47 zira dhclient[19399]: DHCPRELEASE of 192.168.1.3 on eth0 to 192.168.1.1 port 67 May 15 10:23:47 zira ifdown[19369]:

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-05-14 Thread Vincent Lefevre
On 2019-05-14 12:37:57 +0200, Tobias Eliasson wrote: > Den tis 14 maj 2019 kl 11:14 skrev Vincent Lefevre : > > (BTW, the bug did not appear to be fixed according to the fontconfig > > changelog, but the changelog does not actually seem to be up-to-date!) > > > > I

Bug#928973: snapshot.debian.org: internal server error (Error 500)

2019-05-14 Thread Vincent Lefevre
Control: severity -1 grave Raising the severity since the packages are themselves affected by the internal errors, making the service impossible to use. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA -

Bug#928973: snapshot.debian.org: internal server error (Error 500)

2019-05-14 Thread Vincent Lefevre
Package: snapshot.debian.org Severity: important I sometimes get internal server errors (Error 500) on various snapshot.debian.org URLs, e.g. https://snapshot.debian.org/package/fontconfig/ -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500,

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-05-14 Thread Vincent Lefevre
On 2019-05-13 14:23:03 +0200, Tobias Eliasson wrote: > Perhaps this defect can be closed? I can't try with fontconfig from buster, but I suppose it can. (BTW, the bug did not appear to be fixed according to the fontconfig changelog, but the changelog does not actually seem to be up-to-date!) --

Bug#680263: Illegal number - maybe already fixed

2019-05-03 Thread Vincent Lefevre
On 2019-05-03 16:17:06 +0200, Marcos Fouces wrote: > Since 0.50 release, the test to check the name of the file (ksysm or > kallsyms) is the following: > >  KALLSYMS="/proc/kallsyms" >  [ -f /proc/ksysm ] && KALLSYMS="/proc/$KALLSYMS" > > so i believe that it is not a problem anymore. Anyway I

Bug#751161: Bug#928254: gcc-8: -static-libasan does not work with GNU MPFR

2019-05-03 Thread Vincent Lefevre
Control: tags 751161 patch On 2019-05-02 14:29:40 +0200, Vincent Lefevre wrote: > Bug 751161 concerns the same issue. It mentions the -fsanitizer= flags, > which had been fixed some time ago in libtool, but -static-libasan is > still stripped. > > The gcc man page says: >

Bug#912335: gnome-terminal: minor redraw issue when moving a window over the terminal

2019-05-03 Thread Vincent Lefevre
This bug is still present in version 390.116-1, now provided by nvidia-graphics-drivers-legacy-390xx. I couldn't try with Liberation since this font is no longer available in GNOME Terminal (while it still appears in fc-list). Anyway, the font itself does not seem to matter, only its size, so that

Bug#928254: gcc-8: -static-libasan does not work with GNU MPFR

2019-05-02 Thread Vincent Lefevre
-Xlinker option -u symbol -z keyword so that some other options may also be concerned (see below the current list of flags that are passed through unchanged). On 2019-05-02 14:06:03 +0200, Vincent Lefevre wrote: > On 2019-05-02 10:10:33 +0200, Vincent Lefevre wrote: > > On 2019-05-01 20:54

Bug#928254: gcc-8: -static-libasan does not work with GNU MPFR

2019-05-02 Thread Vincent Lefevre
Control: reassign -1 libtool 2.4.6-10 Control: retitle -1 libtool: "Flags to be passed through unchanged" should include -static-libasan Control: severity -1 normal On 2019-05-02 10:10:33 +0200, Vincent Lefevre wrote: > On 2019-05-01 20:54:05 +0200, Matthias Klose wrote: > &g

Bug#928254: gcc-8: -static-libasan does not work with GNU MPFR

2019-05-02 Thread Vincent Lefevre
On 2019-05-01 20:54:05 +0200, Matthias Klose wrote: > the linker never sees your CFLAGS. At least -static-libasan needs to > be added to LDFLAGS. Indeed, I can see -static-libasan in the "libtool --mode=link" line, but libtool drops this option in the gcc call: /bin/sh ../libtool --tag=CC

Bug#928254: gcc-8: -static-libasan does not work with GNU MPFR

2019-04-30 Thread Vincent Lefevre
Package: gcc-8 Version: 8.3.0-7 Severity: minor When I build and check GNU MPFR with: ./configure CFLAGS="-fsanitize=address -static-libasan" make make check I get lots of failure with the error: Your application is linked against incompatible ASan runtimes. Though -static-libasan has

Bug#923510: bugs.debian.org: 500 Internal Server Error when accessing bugs for 'linux'

2019-04-28 Thread Vincent Lefevre
On 2019-03-01 10:27:20 +0200, Teemu Ikonen wrote: > BTS returns a '500 Internal Server Error' response for any kind of > attempt to view bugs on the 'linux' source package, see this URL for > example: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=linux This issue still occurs. -- Vincent

Bug#928034: lightdm: acknowledge of shutdown is not visible immediately

2019-04-26 Thread Vincent Lefevre
Package: lightdm Version: 1.26.0-4 Severity: minor I have the following issue with a machine using sysvinit (I don't think that sysvinit is the culprit, just that it makes the problem visible). This has occurred for several months now (perhaps after the upgrade from 1.18.3 to 1.26, but I'm not

Bug#927877: unbound: "Warning: query response not set" with dig, i.e. QR bit not set in the response

2019-04-24 Thread Vincent Lefevre
Package: unbound Version: 1.9.0-2 Severity: normal I got the following issue with unbound as the local DNS server, for about 20 minutes: zira:~> dig -t any fisglobal.com ;; Warning: query response not set ; <<>> DiG 9.11.5-P4-3-Debian <<>> -t any fisglobal.com ;; global options: +cmd ;; Got

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-16 Thread Vincent Lefevre
Control: reassign -1 fontconfig 2.12.6-0.1 Control: retitle -1 fontconfig: fc-cache with -y option is broken Control: affects -1 plymouth On 2019-04-16 15:33:04 +0200, Sven Hartge wrote: > On 16.04.19 15:12, Vincent Lefevre wrote: > > > access("/var/tmp/mkinitramfs_0BRFs9//et

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-16 Thread Vincent Lefevre
On 2019-04-16 14:56:12 +0200, Sven Hartge wrote: > Interesting. Care to run it with strace to see exactly where it barfs? execve("/usr/bin/fc-cache", ["fc-cache", "-v", "-s", "-y", "/var/tmp/mkinitramfs_0BRFs9"], 0x7ffed17f88b0 /* 131 vars */) = 0 brk(NULL) =

Bug#927222: unison: should not output trailing spaces, which can yield blank lines in the terminal

2019-04-16 Thread Vincent Lefevre
Package: unison Version: 2.48.3-1+b1 Severity: minor I got the following output: Connected [//cventin//home/vlefevre/Mail -> //joooj//srv/d_joooj/home/vinc17/Mail] Looking for changes Waiting for changes from server Reconciling changes local joooj deleted

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-16 Thread Vincent Lefevre
On 2019-04-16 01:53:03 +0200, Sven Hartge wrote: > Try running the following commands as root: > > mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d > cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts > cp -rL /etc/fonts/conf.d/60-latin.conf >

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Vincent Lefevre
On 2019-04-15 23:07:02 +0200, Sven Hartge wrote: > In my case the reason was fc-cache was failing because of a very very > old directory /usr/X11R6/lib/X11 containing old left over fonts. I don't have such a directory. /usr/X11R6 doesn't even exist. But... > Could you add "set -x" to the top of

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Vincent Lefevre
Package: plymouth Version: 0.9.4-1.1 Severity: grave Justification: renders package unusable I got the following error during upgrade: [...] E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up initramfs-tools (0.133) ... update-initramfs: deferring update (trigger activated)

Bug#646174: coreutils: date prints wrong time zone for UTC+/-x and GMT+/-x

2019-04-10 Thread Vincent Lefevre
On 2011-10-21 23:20:21 +0200, W. Martin Borgert wrote: > Maybe this is only my misunderstanding or a documentation > omission. But I'm under the impression, that date prints > the timezone incorrect in some cases: > > $ for tz in UTC UTC+2 UTC-2 ; do TZ=$tz date ; done > Fri Oct 21 20:55:45 UTC

Bug#926713: cron(8) man page: missing .dpkg-old in the list of dpkg files

2019-04-09 Thread Vincent Lefevre
Package: cron Version: 3.0pl1-133 Severity: minor The cron(8) man page says: [...] system when handling files in /etc/cron.d/ as configuration files (i.e. files ending in .dpkg-dist, .dpkg-orig, and .dpkg-new). [...] .dpkg-old is missing (alternatively, "i.e." could be replaced by "e.g." if

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

2019-04-09 Thread Vincent Lefevre
Control: retitle -1 dpkg: package install can be very slow with some disks due to too frequent fsync Hi, On 2019-04-09 00:33:27 +0200, Guillem Jover wrote: > On Tue, 2019-03-05 at 15:43:05 +0100, Vincent Lefevre wrote: > > zira:~>

Bug#901040: libapt-pkg5.0: systemd in Triggers-pending state after upgrade with aptitude

2019-04-05 Thread Vincent Lefevre
On 2019-04-05 15:56:25 +0200, David Kalnischkies wrote: > Hence closing as not-a-bug, but following a user request to the letter. OK, but then this should be documented. Reported: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926472 for the documentation. -- Vincent Lefèvre - Web:

Bug#926472: dpkg(1) man page: should document that putting a package on hold will require to process triggers manually

2019-04-05 Thread Vincent Lefevre
Package: dpkg Version: 1.19.6 Severity: wishlist When a package is on hold, its triggers are not processed automatically, and this is regarded as a feature[*]. It should be documented that triggers need to be processed manually. [*] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901040 --

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-04-03 Thread Vincent Lefevre
On 2019-04-03 13:42:50 +0200, Vincent Lefevre wrote: > On 2019-02-07 13:43:20 +0100, Egmont Koblinger wrote: > > You can disable this behavior with: > > > > printf '\e[?1007l' > > This has no effect when using GNU Screen. For instance: > > $ printf '\e[?1007l'

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-04-03 Thread Vincent Lefevre
On 2019-02-07 13:43:20 +0100, Egmont Koblinger wrote: > You can disable this behavior with: > > printf '\e[?1007l' This has no effect when using GNU Screen. For instance: $ printf '\e[?1007l' ; screen sleep 20 then when using the mouse wheel:

Bug#925927: libgmp10:amd64: failure with Clang's memory sanitizer: use-of-uninitialized-value

2019-03-28 Thread Vincent Lefevre
Control: tags -1 upstream Control: forwarded -1 https://gmplib.org/list-archives/gmp-bugs/2019-March/004525.html I also reported the bug upstream. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA -

Bug#925927: libgmp10:amd64: failure with Clang's memory sanitizer: use-of-uninitialized-value

2019-03-28 Thread Vincent Lefevre
Package: libgmp10 Version: 2:6.1.2+dfsg-4 Severity: important The following program #include int main (void) { mpz_t z; mpz_init (z); mpz_set_ui (z, 1); mpz_dump (z); mpz_clear (z); return 0; } compiled with: clang-7 -fsanitize=memory -o tst tst.c -lgmp gives the following

Bug#924545: linux-image-4.19.0-4-amd64: many errors "PKCS#7 signature not signed with a trusted key"

2019-03-14 Thread Vincent Lefevre
Package: src:linux Version: 4.19.28-1 Severity: important With this new kernel, I get the following error 487 times! PKCS#7 signature not signed with a trusted key cventin:~> journalctl -b | grep -c 'PKCS#7 signature not signed with a trusted key' 487 There were no such errors with previous

Bug#924301: e2fsprogs: e2scrub failure on /

2019-03-12 Thread Vincent Lefevre
On 2019-03-11 15:10:25 -0400, Theodore Ts'o wrote: > Hmm, that message is coming from the lvcreate command. I'm not sure > why it is failing. Can you try running: > > sudo bash -vx /sbin/e2scrub / #!/bin/bash # Copyright (C) 2018 Oracle. All Rights Reserved. # # Author: Darrick J.

Bug#924301: e2fsprogs: e2scrub failure on /

2019-03-11 Thread Vincent Lefevre
Package: e2fsprogs Version: 1.45.0-1 Severity: normal I got the following mail: Date: Sun, 10 Mar 2019 03:10:04 +0100 (CET) From: e2sc...@zira.vinc17.org To: r...@zira.vinc17.org Subject: e2scrub failure on / So sorry, the

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

2019-03-05 Thread Vincent Lefevre
I've done a test with "iozone -a -e", and with this -e option (to include fsync), the operations are much slower than on the other machine. zira:~> iozone -a -e [...] randomrandom bkwdrecordstride

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

2019-03-05 Thread Vincent Lefevre
On 2019-03-05 15:43:05 +0100, Vincent Lefevre wrote: > I've done a test with "iozone -a -e", and with this -e option > (to include fsync), the operations are much slower than on the > other machine. >

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

2019-03-05 Thread Vincent Lefevre
On 2019-03-05 13:52:27 +0100, Guillem Jover wrote: > Hi! > > On Sun, 2019-03-03 at 02:38:10 +0100, Vincent Lefevre wrote: > > On 2019-03-03 00:15:13 +0100, Guillem Jover wrote: > > > Did this start happening due to the new kernel version? > > > > In March 2

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

2019-03-02 Thread Vincent Lefevre
On 2019-03-03 00:15:13 +0100, Guillem Jover wrote: > Did this start happening due to the new kernel version? In March 2018, this was already slow, but much less: [...] 2018-03-08 00:55:55 status unpacked texlive-fonts-extra:all 2017.20180225-1 2018-03-08 00:55:55 status half-installed

Bug#923423: texlive-fonts-extra installation hangs

2019-02-28 Thread Vincent Lefevre
In short: [...] 2019-02-28 00:51:01 status half-installed texlive-fonts-extra:all 2018.20190207-1 2019-02-28 01:10:50 status unpacked texlive-fonts-extra:all 2018.20190227-1 [...] And ditto in the past: [...] 2019-02-02 16:21:55 status half-installed texlive-fonts-extra:all 2018.20190126-1

Bug#923423: texlive-fonts-extra installation hangs

2019-02-27 Thread Vincent Lefevre
Control: severity -1 important Control: retitle -1 texlive-fonts-extra installation hangs for 19 minutes On 2019-02-28 01:06:28 +0100, Vincent Lefevre wrote: > Package: texlive-fonts-extra > Version: 2018.20190227-1 > Severity: serious > > Installation of texlive-fonts-extra

Bug#923423: texlive-fonts-extra installation hangs

2019-02-27 Thread Vincent Lefevre
Package: texlive-fonts-extra Version: 2018.20190227-1 Severity: serious Installation of texlive-fonts-extra 2018.20190227-1 hangs. Here's px information: # px 5553 /usr/bin/dpkg --status-fd 80 --no-triggers --unpack --auto-deconfigure --recursive /tmp/apt-dpkg-install-mos7uq

Bug#922874: file: mistakes Xorg.0.log file as JSON data

2019-02-27 Thread Vincent Lefevre
Control: tags -1 upstream Control: forwarded -1 https://bugs.astron.com/view.php?id=69 On 2019-02-21 17:02:15 +0100, Vincent Lefevre wrote: > file mistakes Xorg.0.log file as JSON data (which breaks viewing > with "less" + LESSOPEN). [...] I've reported the bug upstream. --

Bug#922869: libtool: file date issue

2019-02-27 Thread Vincent Lefevre
On 2019-02-27 15:12:24 +, Alastair McKinstry wrote: > Where did you see this error ? I cannot repeat it. Builds work fine locally > / pdebuild, and it appears the buildds ? When attempting to rebuild libtool on a machine. A second build (after a reboot due to an issue with the nouveau driver

Bug#923399: texlive-base: uninstallable due to versioned conflicts

2019-02-27 Thread Vincent Lefevre
Package: texlive-base Version: 2018.20190227-1 Severity: serious texlive-base 2018.20190227-1 has versioned conflicts: Conflicts: luasseq (<< 2018.20190227), prosper (<< 2018.20190227), tex4ht (<< 20160814), texlive (<< 2018.20190227), texlive-base (<< 2018.20190227), texlive-bibtex-extra (<<

Bug#923396: file -e should silently ignore nonexistent testnames

2019-02-27 Thread Vincent Lefevre
Package: file Version: 1:5.35-2 Severity: wishlist I get the following error: $ file -e foo /dev/null Usage: file [-bcCdEhikLlNnprsvzZ0] [--apple] [--extension] [--mime-encoding] [--mime-type] [-e ] [-F ] [-f ] [-m ] [-P ] ... file -C [-m ] file [--help]

Bug#919029: grub-pc: meaningless message "RUB boot loader was previously installed..."

2019-02-26 Thread Vincent Lefevre
On 2019-02-26 15:20:10 +, Colin Watson wrote: > On Tue, Feb 26, 2019 at 04:01:33PM +0100, Vincent Lefevre wrote: > > On 2019-02-26 12:44:41 +, Colin Watson wrote: > > > Of course, the grub-pc maintainer script doesn't know either. All it > > > has available

Bug#919029: grub-pc: meaningless message "RUB boot loader was previously installed..."

2019-02-26 Thread Vincent Lefevre
On 2019-02-26 12:44:41 +, Colin Watson wrote: > Of course, the grub-pc maintainer script doesn't know either. All it > has available to it is a /dev/disk/by-id/ path that no longer points to > a disk. The case I had in mind when writing that code, and I think > almost certainly the

Bug#922863: tomcat8: post-installation script subprocess failed during upgrade

2019-02-24 Thread Vincent Lefevre
On 2019-02-24 19:36:16 +0100, Dominik George wrote: > Can you please provide more details from your system that show why this > might fail? You can edit /var/lib/dpkg/info/tomcat8.postinst and add a > set -x near the set -e at the top, then dpkg-reconfigure tomcat8, for > example.

Bug#922153: ncurses-base: for screen and variants, please change smacs and rmacs to \E(0 and \E(B respectively

2019-02-24 Thread Vincent Lefevre
On 2019-02-23 21:17:38 -0500, Thomas Dickey wrote: > On Sun, Feb 24, 2019 at 01:56:06AM +0100, Vincent Lefevre wrote: > > No, "tput enacs" returns an error in Linux consoles, and has no effect > > there. For instance, in xterm: > > not so (see screenshot). This is

Bug#922153: ncurses-base: for screen and variants, please change smacs and rmacs to \E(0 and \E(B respectively

2019-02-23 Thread Vincent Lefevre
On 2019-02-23 17:37:19 -0500, Thomas Dickey wrote: > On Tue, Feb 12, 2019 at 06:48:19PM +0100, Vincent Lefevre wrote: > > Package: ncurses-base > > Version: 6.1+20181013-2 > > Severity: wishlist > > > > terminfo description of screen and variants have: &

Bug#922874: file: mistakes Xorg.0.log file as JSON data

2019-02-21 Thread Vincent Lefevre
Package: file Version: 1:5.35-2 Severity: normal file mistakes Xorg.0.log file as JSON data (which breaks viewing with "less" + LESSOPEN). Example on the first 5 lines: [105215.998] X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 [105215.998] Build Operating System: Linux 4.9.0-8-amd64

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

2019-02-21 Thread Vincent Lefevre
Package: src:linux Version: 4.19.20-1 Severity: important Tags: upstream Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=93828 I get lots of errors with nouveau, and I assume that this is what makes the machine unresponsive (via ssh): Feb 21 15:01:30 ypig kernel: [ 266.270272] nouveau

Bug#922869: FTBFS: test failures / newly created file is older than distributed files

2019-02-21 Thread Vincent Lefevre
Source: libtool Version: 2.4.6-10 Severity: serious I got the following error: ## - ## ## Test results. ## ## - ## ERROR: 150 tests were run, 15 failed (4 expected failures). 20 tests were skipped. ## ## ## Summary of the failures. ## ##

Bug#922863: tomcat8: post-installation script subprocess failed during upgrade

2019-02-21 Thread Vincent Lefevre
Package: tomcat8 Version: 8.5.38-1 Severity: grave Justification: renders package unusable During upgrade: [...] Setting up tomcat8 (8.5.38-1) ... [ ok ] Stopping Tomcat servlet engine: tomcat8. [FAIL] Starting Tomcat servlet engine: tomcat8 failed! invoke-rc.d: initscript tomcat8, action

Bug#922735: aptitude truncates the version number in the visual interface

2019-02-19 Thread Vincent Lefevre
Package: aptitude Version: 0.8.11-7 Severity: normal aptitude truncates the version number of packages, even when the window width is large: i A --\ wpasupplicant

Bug#922499: spamassassin: sa-update fails with error "Cannot open file ..."

2019-02-18 Thread Vincent Lefevre
On 2019-02-18 19:05:00 +0100, Jörg Sommrey wrote: > I'm faced with a similar issue. Starting sa-update from a terminal > revealed more details. The update file was claimed to be signed by an > unknown gpg key. However, the mentionded key exists in the pubring. I > was able to update using

Bug#922550: ifupdown: network hangs for 5 minutes at startup / Failed to start Wait for network to be configured by ifupdown

2019-02-17 Thread Vincent Lefevre
On 2019-02-17 23:50:34 +0100, Vincent Lefevre wrote: > After the ifupdown upgrade from 0.8.33 to 0.8.35, I now need to wait > for 5 minutes before eth0 is up. This problem occurs only when an Ethernet cable is already plugged in before the boot. Downgrading to 0.8.33 made the problem dis

Bug#922550: ifupdown: network hangs for 5 minutes at startup / Failed to start Wait for network to be configured by ifupdown

2019-02-17 Thread Vincent Lefevre
Package: ifupdown Version: 0.8.35 Severity: important After the ifupdown upgrade from 0.8.33 to 0.8.35, I now need to wait for 5 minutes before eth0 is up. I've attached the beginning of "journalctl -b -1" output. At the end of these 5 minutes, one can see: Feb 17 23:15:24 zira systemd[1]:

Bug#902204: monit: spurious "monit alert -- Link up eth0" messages

2019-02-17 Thread Vincent Lefevre
On 2019-02-17 14:13:45 +0300, Sergey B Kirpichev wrote: > On Sat, 22 Dec 2018 03:17:27 +0100 Vincent Lefevre wrote: > > So, it seems to be a bug in the monit code that makes it think that > > the link is up while it is not. > > >

Bug#922443: texlive-extra-utils: latexpand script: detection of comments is buggy

2019-02-15 Thread Vincent Lefevre
Package: texlive-extra-utils Version: 2018.20190131-1 Severity: normal Tags: patch upstream Forwarded: https://gitlab.com/latexpand/latexpand/merge_requests/6 In the latexpand script, the detection of comments is buggy: if a % is not at the beginning of a line, it will not be regarded as

Bug#922278: mpfr4: please update the www.mpfr.org URLs to use https

2019-02-13 Thread Vincent Lefevre
Source: mpfr4 Version: 4.0.2-1 Severity: normal The www.mpfr.org URLs under the debian directory should be updated to use https: debian/control:Homepage: http://www.mpfr.org/ debian/copyright:MPFR was downloaded from http://www.mpfr.org/. debian/watch:http://www.mpfr.org/mpfr-current/

Bug#922153: ncurses-base: for screen and variants, please change smacs and rmacs to \E(0 and \E(B respectively

2019-02-12 Thread Vincent Lefevre
Package: ncurses-base Version: 6.1+20181013-2 Severity: wishlist terminfo description of screen and variants have: smacs=^N rmacs=^O One issue is that these sequences are not recognized by "less -R". A workaround would be to change them to: smacs=\E(0 rmacs=\E(B as in various other

Bug#403612: "less -R" doesn't take rmacs into account (regression)

2019-02-12 Thread Vincent Lefevre
difference between these two bugs. They look the same. So let's merge them. On 2006-12-18 14:10:58 +0100, Vincent Lefevre wrote: > $ echo "`tput smacs`mq`tput rmacs`> foo" > > outputs an arrow and "foo". But if I type > > echo "`tput smacs`mq`tput rmacs`&

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-02-08 Thread Vincent Lefevre
On 2019-02-08 15:21:00 +0100, Egmont Koblinger wrote: > > Perhaps it should have generated scroll-backward (kR) and > > scroll-forward (kF) keys, and provided a terminfo that defines > > them. That way, this wouldn't mix up with the and > > keys. > > There would be no point in that either: if

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-02-08 Thread Vincent Lefevre
On 2019-02-08 14:02:14 +0100, Egmont Koblinger wrote: > > Yes, but my point is that the default should not be broken. > > One could argue that the wheels working in "less" (or any other > similar app) is the expected behavior, and not working at all is the > broken one... No, that's just a

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-02-07 Thread Vincent Lefevre
On 2019-02-08 02:14:45 +0100, Egmont Koblinger wrote: > > But this one is really special as specific to GNOME Terminal. > > No, not at all. At least I get this behavior in xterm and konsole, too. I don't get it in xterm, rxvt and mlterm. > > Well, for applications that do not have any support,

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-02-07 Thread Vincent Lefevre
On 2019-02-07 20:15:11 +0100, Egmont Koblinger wrote: > > I'm wondering why this isn't documented in the GNOME Terminal help. > > Because the help pages document the UI, and not the terminal > emulation behavior. > > It would be practically impossible to provide an exhaustive > description of

Bug#436186: less: scrollwheel doesn't work in xterm

2019-02-07 Thread Vincent Lefevre
On 2019-02-07 09:58:00 -0800, Jonathan Nieder wrote: > Vincent Lefevre wrote: > > On 2010-11-03 02:49:47 -0500, Jonathan Nieder wrote: > >> Thomas Dickey wrote: > > >>> (e)links(2) is using a different mechanism: it's turned on xterm's > >>> any-eve

Bug#436186: #436186 - less: scrollwheel doesn't work in xterm

2019-02-07 Thread Vincent Lefevre
Control: severity -1 wishlist Control: forcemerge -1 330241 On 2010-11-03 02:49:47 -0500, Jonathan Nieder wrote: > Thomas Dickey wrote: > > > strace shows that gnome-terminal is sending cursor-key escape sequences > > to less. This is not documented in gnome-terminal (of course - vte is > >

Bug#921537: gnome-terminal: mouse wheel scrolling sends 6 key up / key down escape sequences (kcuu1 / kcud1) in alternate screen

2019-02-07 Thread Vincent Lefevre
Hi, On 2019-02-07 13:43:20 +0100, Egmont Koblinger wrote: > You can disable this behavior with: > > printf '\e[?1007l' > > See "Alternate Scroll Mode" at > https://invisible-island.net/xterm/ctlseqs/ctlseqs.html . Thanks for the information. I'm wondering why this isn't documented in the

Bug#539912: reassign to gcc-8, which is now the default compiler

2019-02-07 Thread Vincent Lefevre
Control: reopen -1 Control: reassign -1 gcc-8 8.2.0-17 Control: retitle -1 gcc-8: for c99, POSIX requires that option -D have a lower precedence than -U as this is now the default compiler, and the bug still occurs with it. -- Vincent Lefèvre - Web: 100% accessible

Bug#921585: "wdiff -d" output is incorrect

2019-02-06 Thread Vincent Lefevre
Control: tags -1 upstream I've reported the bug upstream. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  1   2   3   4   5   6   7   8   9   10   >