Bug#621807: rpcbind should not bind to wildcard

; rpcbind 18484 _rpc 14u IPv6 6261782 0t0 TCP *:sunrpc (LISTEN) Have you tried reporting this upstream, to either SF project bug-tracker <https://sourceforge.net/p/rpcbind/bugs/>, or bu sending an e-mail to <mailto:libtirpc-de...@lists.sourceforge.net> or <mailto:linux-..

Bug#962988: When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists

Related to bug #962989 . signature.asc Description: OpenPGP digital signature

Bug#962989: Please enhance /etc/init.d/X11-common script to additionally manage /tmp/.font-unix socket directory

Package: x11-common Version: 1:7.7+19 Severity: normal Tags: patch Currently, xfstt package manages the /tmp/.font-unix socket directory privately, creating it during start-up and removing during its shutdown (see bug #962988 ). This may c

Bug#962988: When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists

Package: xfstt Version: 1.10-1 Severity: grave Tags: upstream During its start-up, xfstt creates the `/tmp/.font-unix/` directory in order to place its socket there. If, however, the above directory already exists, xfstt: - doesn't create the unix socket there if the socket file doesn't exist,

Bug#927375: [libxfont1] Please re-build libxfont1 with --enable-fc

Apparently, this bug is also causing bug #858512 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858512>. -- Regards, Andrey ``Bass'' Shcheglov.

Bug#858512: xfstt: xset fp+ unix/:7101 -> Incorrect font server address or syntax

, and, until it's fixed, both `libxfont1` and `libxfont2` packages should claim they're breaking `xfstt` in exactly the same manner they're currently breaking `xfs` (from Debian 7). -- Regards, Andrey ``Bass'' Shcheglov.

Bug#858512: xfstt: xset fp+ unix/:7101 -> Incorrect font server address or syntax

path element (#16), possible causes are: > Directory does not exist or has wrong permissions > Directory missing fonts.dir > Incorrect font server address or syntax This problem, until fixed, basically renders the package useless. -- Regards, Andrey ``Bass'' Shcheglov. signature.asc Description: OpenPGP digital signature

Bug#959050: [vlc-plugin-qt] VLC Qt UI doesn't start in the presense of QT_QPA_PLATFORMTHEME, GTK_CSD and LD_PRELOAD

Rémi Denis-Courmont wrote: > As far as I know, loading GTK2 and GTK3 in the same process is not > supported by the GTK libraries (much like you can't have multiple Qt > versions). There's nothing for VLC or even gtk3-nocsd to do here. > > You just can't load gtk3-nocsd in a program that uses GTK

Bug#959050: [vlc-plugin-qt] VLC Qt UI doesn't start in the presense of QT_QPA_PLATFORMTHEME, GTK_CSD and LD_PRELOAD

Thank you for your response Sebastian. On Tue, 28 Apr 2020 at 23:25, Sebastian Ramacher wrote: > That's some issue with something Gtk related. Nothing in vlc does Gtk. > This looks more like an issue in libgtk3-nocsd0 to me that messes up > Gtk. Reassigning accordingly. FWIW, this issue does not

Bug#959050: [vlc-plugin-qt] VLC Qt UI doesn't start in the presense of QT_QPA_PLATFORMTHEME, GTK_CSD and LD_PRELOAD

One more update. svlc from vlc-plugin-skins2 package is affected in equally the same way as qvlc from vlc-plugin-qt.

Bug#959050: [vlc-plugin-qt] VLC Qt UI doesn't start in the presense of QT_QPA_PLATFORMTHEME, GTK_CSD and LD_PRELOAD

One minor correction: the problem has been reported to Devuan as bug #433 , not 432. Regards, Andrey.

Bug#959050: [vlc-plugin-qt] VLC Qt UI doesn't start in the presense of QT_QPA_PLATFORMTHEME, GTK_CSD and LD_PRELOAD

Package: vlc-plugin-qt Version: 3.0.8-0+deb10u1 Severity: grave Dear Maintainer, I have all my Qt 5 applications rendering their UI via GTK2 (this means I have qt5-style-plugins package installed): > QT_QPA_PLATFORMTHEME=gtk2 > QT_STYLE_OVERRIDE=gtk2 Additionally, for my GTK3 applications, I

Bug#927375: [libxfont1] Please re-build libxfont1 with --enable-fc

Package: libxfont1 Version: 1:1.5.2-4 Severity: normal --- Please enter the report below this line. --- I still use xfs, the X Font Server (from Debian Wheezy), and share my core X fonts between hosts on the local network, meaning some font path entries still use the "tcp/somehost:7100" notation.

Bug#924475: [xterm] ATR_ITALIC is not always rendered properly when using core X fonts

Package: xterm Version: 327-2 Severity: normal --- Please enter the report below this line. --- When using core X fonts (from the X server), Xterm attempts to infer the oblique (-o-) version from the regular font in order to render italicized text. Not all fonts, however, have the oblique versio

Bug#920336: [xterm] Xterm doesn't support double-sized characters (DECDHL) when using Xft (client-side) fonts

Package: xterm Version: 327-2 Severity: normal --- Please enter the report below this line. --- Whenever I configure xterm to use core X11 fonts: > *.vt100.renderFont: False > *.vt100.locale: False > *.vt100.font:   -monotype-courier > new-medium-r-nor

Bug#901135: [ddd] Should require remake

Package: ddd Version: 1:3.3.12-5.1+b1 Severity: normal --- Please enter the report below this line. --- DDD can run as a Makefile debugger: > ddd --debugger make /path/to/Makefile In this case it requires the "remake" utility . So remake should be adde

Bug#900521: [dia] The application hangs when "help()" is entered in the Python console

Package: dia Version: 0.97.3+git20160930-6 Severity: important --- Please enter the report below this line. --- The Python console works perfectly fine except when a user attempts to invoke `help()` -- without arguments. In this case Dia freezes, and there's no obvious way to revert it to the no

Bug#894802: Found the workaround

Hello, The issue is actually locale-dependent: ksh infers the decimal separator from LC_NUMERIC, and since my locale is ru_RU.UTF-8, it expects a comma (,) instead of a dot (.). Strange thing is, LC_NUMERIC affects neither zsh nor bc -- only ksh. I believe this behaviour should be at least docu

Bug#894802: [ksh] floating point arithmetic is broken

Package: ksh Version: 93u+20120801-3.1 Severity: normal --- Please enter the report below this line. --- Floating point arithmetic no longer works in ksh. Here's how it used to work: > $ echo $((1./2)) > 0.5 ... and this is how it works now: > $ echo $((1./2)) > ksh: 1./2: arithmetic syntax er

Bug#888094: [xdg-utils] xdg-open uses the deprecated ~/.local/share/applications/mimeapps.list instead of ~/.config/mimeapps.list

Package: xdg-utils Version: 1.1.1-1 Severity: normal --- Please enter the report below this line. --- Whenever I run xdg-mime to set the default application: xdg-mime default foo.desktop 'foo/bar' -- it updates the [deprecated][1] ~/.local/share/applications/mimeapps.list instead of ~/.conf

Bug#887519: [libguestfs0] Replace the dependency on sysvinit with sysvinit-core

Package: libguestfs0 Version: 1:1.34.6-2 Severity: normal --- Please enter the report below this line. --- libguestfs0 depends on "systemd | sysvinit", but sysvinit package was a transitional dummy package in Debian 8 and is completely removed in Debian 9. Therefore it's no longer possible to

Bug#886762: [java-package] oracle-java6-doc package creation for jdk-6u10-docs.zip fails

Package: java-package Version: 0.62 Severity: normal --- Please enter the report below this line. --- The manual page states that the following documentation versions are eligible for packaging: - The Java API Javadoc, version 6, 7 and 8 Still, when I try to package the documentation for 1.

Bug#886759: [java-package] oracle-java8-doc package creation fails when TMPDIR is overridden

Package: java-package Version: 0.62 Severity: normal --- Please enter the report below this line. --- When TMPDIR is overridden, oracle-java8-doc package creation fails: $ TMPDIR=. make-jpkg jdk-8u152-docs-all.zip Creating temporary directory: ./make-jpkg.a07AYJSHcz Loading plugins: /usr/share/

Bug#886757: [java-package] oracle-java7-doc package creation for jdk-7u76-docs-all.zip fails

Package: java-package Version: 0.62 Severity: normal --- Please enter the report below this line. --- Creating temporary directory: /tmp/make-jpkg.UPcfPELT77 Loading plugins: /usr/share/java-package/common.sh /usr/share/java-package/javase.sh /usr/share/java-package/jdk-doc.sh /usr/share/java-

Bug#886751: [java-package] Unable to create an i386 package when current architecture is amd64

Package: java-package Version: 0.62 Severity: normal --- Please enter the report below this line. --- As a Java developer, I often need to have a zoo of multiple JDK packages, incl. i386 versions (certain corner cases are only reproducible when running a 32 bit JVM). Still, despite I have multi

Bug#885164: tmux always sets the iutf8 flag, even for non-Unicode locales

The corresponding upstream issue is https://github.com/tmux/tmux/issues/1211 smime.p7s Description: S/MIME Cryptographic Signature

Bug#885164: tmux always sets the iutf8 flag, even for non-Unicode locales

Package: tmux Version: 2.3-4 Severity: important Tags: l10n Starting with Debian 9, tmux (2.3-4) always sets the iutf8 flag, rendering it unusable in non-ASCII (i. e. 8 bit) non-Unicode locales like ru_RU.KOI8-R. The problem is easy to reproduce using a ru_RU.KOI8-R environment or, alternatively,

Bug#621807: Feature is available

No, actually it is *not* configurable (despite it seems it is). I'm running rpcbind 0.2.3-0.6 (Debian Stretch) with the following config file: OPTIONS='-w' OPTIONS="${OPTIONS} -h 127.0.0.1 -h ::1" OPTIONS="${OPTIONS} -l" The rpcbind service is indeed using the above options: # ps -ef | gre

Bug#815144: Acknowledgement (Add support for more Cyrillic locales)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This has been forwarded to ICS/MotifZone as bug #1652 http://bugs.motifzone.net/long_list.cgi?buglist=1652 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlb9WpMACgkQFX2weoTrDGeL7ACeMJA84UwTHfAm0BXilkZeLnPB CjcAn1xiQZar39EtIjvH9PRh52M9bT

Bug#815144: Add support for more Cyrillic locales

Package: uil Version: 2.3.4-6+deb8u1 Motif's UIL compiler has long had an annoying problem: it often reports "$LANG contains an unknown character set" error message for syntactically correct *.uil files (see , more examples can be easil