Bug#707564: minicom: please show config or device name in status bar

Package: minicom Version: 2.6.2-1 Severity: wishlist Dear Maintainer, I'm often using multiple minicom instances to work on multiple serial ports (connected both to different devices and to different ports of the same device) in parallel. Currently, it's hard to distinguish these instances as

Bug#707564: minicom: please show config or device name in status bar

Adam Lackorzynski a...@os.inf.tu-dresden.de writes: Starting minicom with -T will show the device name instead of the online time. I guess that's what you're looking for. Thanks for the hint; I wouldn't have expected the option to have this effect, based on the description in the manual page

Bug#687250: scdaemon: spamming syslog if reader cannot be found

Package: scdaemon Version: 2.0.19-1 Severity: important Dear Maintainer, If scdaemon cannot find the configured reader, it will flood syslog: Sep 11 09:17:42 twin pcscd: winscard.c:241:SCardConnect() Reader Gemalto USB Shell Token V2 01 00 Not Found Sep 11 09:17:42 twin pcscd:

Bug#689499: python-notmuch: Please install Python 3 bindings

Package: python-notmuch Version: 0.13.2-1 Severity: normal Dear Maintainer, notmuch ships with Python 3 bindings, but the Debian package doesn't install them. Some third-party tools (that use the notmuch bindings) work better with Python 3 than with Python 2.x. There may even be some that don't

Bug#696989: policykit-1: refuses all actions if user is member of a large number of groups

Package: policykit-1 Version: 0.105-1 Severity: important Dear Maintainer, PolicyKit refuses all actions for my own user account, but works fine for other accounts: === Begin SSH session as sascha.silbe === sascha.silbe@twin:~$ cat

Bug#696989: policykit-1: refuses all actions if user is member of a large number of groups

of groups before, barring all access to users with a large number of groups. . Dynamically allocate the list instead, potentially resizing it based on what getgroupslist() tells us. Author: Sascha Silbe sascha-...@silbe.org --- The information above should follow the Patch Tagging Guidelines

Bug#697624: minicom: can't use /dev/serial/by-path/*usb* device names

Package: minicom Version: 2.6.1-1 Severity: normal Dear Maintainer, 123456789012345678901234567890123456789012345678901234567890123456789012 minicom cuts off the name of the serial device file at the first colon, so by-path persistent serial device names can't be used; at least not for USB

Bug#699205: linux-image-3.7-trunk-amd64: ps, pgrep and pkill segfault after upgrade from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1

Package: src:linux Version: 3.7.3-1~experimental.1 Severity: important Dear Maintainer, after updating the linux-image-3.7-trunk-amd64 from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting, the tools ps, pgrep and pkill (package procps) are always segfaulting: === Begin ===

Bug#699218: procps: FTBFS with test suite error: testsuite/lib.test/fileutils_badfd.sh missing

Package: procps Version: 1:3.3.3-2 Severity: serious Justification: FTBFS Dear Maintainer, in order to help diagnosing #699205, I need to rebuild procps with debugging options as there's no pre-built -dbg package (hint, hint). Unfortunately that fails with a test suite error, despite nocheck

Bug#699205: linux-image-3.7-trunk-amd64: ps, pgrep and pkill segfault after upgrade from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1

Jonathan Nieder jrnie...@gmail.com writes: after updating the linux-image-3.7-trunk-amd64 from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting, the tools ps, pgrep and pkill (package procps) are always segfaulting: Just to check: if you downgrade to 3.7.1 again, do the

Bug#699914: python3-serial: TCP mode: data loss, timeout handling broken

Package: python3-serial Version: 2.5-2.1 Severity: normal Dear Maintainer, when used in TCP mode ('socket://address:port'), python3-serial will loose most of the received characters. This is because SocketSerial.read() _replaces_ the buffer instead of appending to it: [...] data =

Bug#706518: python3-serial: rfc2217 support broken (cannot even import serial.rfc2217)

Package: python3-serial Version: 2.5-2.1 Severity: important Dear Maintainer, the RFC2217 support of pyserial, at least when used with Python 3, is completely broken. Even just importing serial.rfc2217 fails: === Begin === sascha.silbe@twin:~$ python3 Python 3.2.3 (default, Feb 20 2013,

Bug#706518: python3-serial: rfc2217 support broken (cannot even import serial.rfc2217)

Sascha Silbe sascha-debian-bugs-pyserial-2013-05...@silbe.org writes: the RFC2217 support of pyserial, at least when used with Python 3, is completely broken. Even just importing serial.rfc2217 fails: [...] I managed to fix that part by replacing serial.serialutil.to_bytes

Bug#699205: [3.7.1-3.7.3 regression] ps, pgrep and pkill segfault

Version: 3.8.5-1~experimental.1 This doesn't happen with linux-image-3.8-trunk-amd64 3.8.5-1~experimental.1 (currently available from experimental). The problematic kernel version (linux-image-3.7-trunk-amd64 3.7.3-1~experimental.1) isn't available from experimental anymore, so I'm considering

Bug#710672: python-webdav: Unsolicited use of persistent connections causes HTTP/1.0 clients to hang

Package: python-webdav Version: 0.9.8-3 Severity: normal Dear Maintainer, pywebdav uses persistent connections even for HTTP/1.0 GET requests without a Connection: Keep-Alive header. This causes the client to hang waiting for the connection to close. RFC2616 explicitly states HTTP/1.1 servers

Bug#710690: python-webdav: recursive allprops only yields a subset of properties

Package: python-webdav Version: 0.9.8-3 Severity: normal Dear Maintainer, when all properties for a resource and its children are requested, pywebdav only returns the value of those properties that are also set on requested collection itself. It does not return the properties that are only on

Bug#710697: python-webdav: no support for properties that are not plain XML-safe character strings (binary data, XML nodes)

Package: python-webdav Version: 0.9.8-3 Severity: wishlist Dear Maintainer, there's currently no way to return property values from dav_interface.get_prop() that are anything else than plain characters strings with no XML-unsafe characters. While PROPFIND.mk_prop_response() would accept a

Bug#696176: No problem here

Filipus Klutiero chea...@gmail.com writes: I also use a Radeon HD 7660D (on A10-5700) and do not experience this issue on my wheezy install (using Linux 3.8). Can you reproduce with current versions? Yes, I can still reproduce this using xserver-xorg-video-radeon 1:6.14.4-8 and

Bug#696176: [Fwd: Undelivered Mail Returned to Sender]

Michel Dänzer daen...@debian.org writes: Not very nice... sascha-debian-bugs-xserver-xorg-video-radeon-2012-12...@silbe.org: host b.mx.chost.de[87.106.8.89] said: 534 Message header size, or recipient list, exceeds policy limit. (in reply to end of DATA command) Not sure how you've

Bug#738556: libaqbanking: Please package and backport 5.3.6beta

Package: libaqbanking Version: 5.3.5beta-2 Severity: important Dear Maintainer, please package 5.3.6beta and provide a backport of it for wheezy. Aqbanking 5.3.6beta [1] fixes a bug that prevented interoperation with some banks when using RDH-10. In addition, the aqbanking 5.2 and 5.3 series

Bug#747871: mkinitramfs: breaks with LUKS root on MMC (mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry) and MODULES=dep

Package: initramfs-tools Version: 0.109.1 Severity: normal File: /usr/sbin/mkinitramfs Dear Maintainer, on a system with the rootfs living inside LUKS on an SD card, mkinitramfs (and thus update-initramfs) fails with: === Begin === root@mimosa:/boot# update-initramfs -k

Bug#766867: python-gevent: SSL support broken with current Python in Jessie (2.7.8)

Package: python-gevent Version: 1.0.1-1 Severity: normal Dear Maintainer, with current python2.7 (2.7.8-10) from Jessie, the SSL support in python-gevent is broken for at least two reasons: 1. References no longer existing ssl._ssl.sslwrap() gevent.ssl.SSLSocket.connect() tries to use

Bug#775953: openntpd if-up.d hook can cause system boot to hang indefinitely

Package: openntpd Version: 20080406p-4 Severity: critical Justification: breaks the whole system Dear Maintainer, when a) openntpd is configured to listen on some interface and b) openntpd is configured to step the time on start-up and c) the DNS servers are not reachable for any reason, the

Bug#775953: openntpd: no longer happens with wheezy-backports version

Package: openntpd Followup-For: Bug #775953 Dear Maintainer, after upgrading to the openntpd version from wheezy-backports (no other changes), the indefinite hang no longer occurs. Kind regards, Sascha -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500,

Bug#775953: openntpd if-up.d hook can cause system boot to hang indefinitely

Hello Dererk, Dererk der...@debian.org writes: I'm trying to reproduce this, and trying to understand your working environment, which seems to be an armel architecture of an ARMv5tel device. Is your device being able to be emulated by qemu or some equivalent tool? What physical device is

Bug#787001: pgrep/pkill: incorrect return code on syntax error

Package: procps Version: 1:3.3.3-3 Severity: normal File: /usr/bin/pgrep Dear Maintainer, the manual page states that in case of a syntax error, pgrep / pkill with return with an exit status of 2. This is useful to distinguish between proper operation (but no match found) and incorrect usage.

Bug#581039: tightvnc: Version 2.7.10 available by now; fixes key bindings for Mac OS X vnc server

Dear Ola, Ola Lundqvist o...@inguza.com writes: I'll see what I can do. The package is up for adoption as I have little spare time (kids...), but I'll see if I can get some free time some day. TL;DR: TightVNC 2.x is Windows-only. Cannot send Option key with any non-Apple VNC viewer to

Bug#581039: tightvnc: Version 2.7.10 available by now; fixes key bindings for Mac OS X vnc server

Source: tightvnc Followup-For: Bug #581039 Dear Maintainer, it would be really great to have the latest upstream release (version 2.7.10 from 2013-07-24) packaged. Besides tons of other changes compared to 1.3.9, it supposedly fixes sending Option key presses (Windows key on the local side) to

Bug#825861: freecad: After update to 0.16 design contents are "invisible", ViewProvider2DObjectPython on console

Package: freecad Version: 0.16+dfsg2-1~bpo8+1 Severity: important Dear Maintainer, thanks for providing a backport for 0.16! Unfortunately after updating, I cannot load my document created with the 0.15.4671 backport anymore. When loading my "old" document, the 3D view continues to show the

Bug#854499: git-daemon-sysvinit: unconditionally enables --verbose, causing IP addresses to be logged

Package: git-daemon-sysvinit Version: 1:2.1.4-2.1+deb8u2 Severity: normal Dear Maintainer, /etc/init.d/git-daemon always passes the --verbose option to git-daemon. Since there is no corresponding option like --quiet that would be able to counter it, there's no way to disable IP address logging

Bug#854313: bleygraph needs python-matplotlib, cannot handle dbconfig-common.conf

Package: bley Version: 2.0.0-2 Severity: normal Dear Maintainer, tried to run bleygraph; ran into two issues: 1. bleygraph needs python-matplotlib, but the bley package doesn't depend on (or even just suggest) it: sascha@outpost:~$ sudo -u bley bleygraph -d /tmp/bley Traceback (most

Bug#853185: gatling: No simple way to disable logging of IP addresses

Package: gatling Version: 0.13-5+b3 Severity: normal Dear Maintainer, there's no way to disable logging of IP addresses in gatling itself as all the logging is hard-coded. As logging is done to a custom log file rather than via syslog, filtering via the syslog daemon isn't possible either. The

Bug#853216: rsyslog: mmanom does not anonymise IPv6 addresses

Package: rsyslog Version: 8.4.2-1+deb8u2 Severity: normal Dear Maintainer, rsyslog ships the mmanom module which is useful for stripping IP addresses from log messages for services that do not offer log format customisation themselves. Unfortunately it doesn't support IPv6, so it's of no use for

Bug#548880: closed by Julien Cristau <jcris...@debian.org> (Bug#548880: fixed in debootstrap 1.0.85)

Dear Ansgar, dear Julien, Debian Bug Tracking System <ow...@bugs.debian.org> writes: [...] > debootstrap (1.0.85) unstable; urgency=medium [...] >[ Ansgar Burchardt ] [...] >* Error out when seeing short options. (Closes: #548880) Kudos! Sascha -- Softwareentwicklu

Bug#858048: tigervnc: Outdated build dependencies

Source: tigervnc Version: 1.7.0+dfsg-6~bpo8+1 Severity: minor Dear Maintainer, while building a local backport of tigervnc to jessie, I noticed that some of the build dependencies were too lax. At least the following are now required: === Begin === x11proto-core-dev (>= 7.0.31),

Bug#858048: [Pkg-tigervnc-devel] Bug#858048: tigervnc: Outdated build dependencies

Dear Ola, Ola Lundqvist writes: > Thank you for the report. > > Just a check. These two problems you reported, they are specific to jessie, > right? I suppose so. Haven't tried building on Stretch or Sid. But since both ship recent enough versions of the relevant packages, it

Bug#857031: cabal-install: Please update backport to 1.24.x

Package: cabal-install Version: 1.22.6.0-2~bpo8+1 Severity: normal Dear Maintainer, the versions of cabal-install in jessie and jessie-backports contain severe memory leaks, causing systems with "only" 512MiB RAM (e.g. ARM based servers, some VMs / virtual servers) to run out of memory during

Bug#868352: linux: Please enable USB_SERIAL_CONSOLE

Source: linux Version: 4.11.6-1 Severity: normal Dear Maintainer, on some amd64 systems no native or PCI(e) serial ports are available resp. possible. USB serial adapters are the only option to get a serial console for debugging boot problems in this case. Unfortunately the Debian amd64 kernels

Bug#861272: fdroidserver: Backport of fdroidserver does not work with aapt from Jessie

Package: fdroidserver Version: 0.7.0-1~bpo8+1 Severity: important Dear Maintainer, the Jessie backport of fdroidserver has only an unversioned recommend on aapt, so the Jessie version gets pulled in. "fdroid update" chokes on the output of "aapt dump badging ", particularly the

Bug#862083: firejail: crashes when using --allow-debuggers ("free(): invalid pointer")

Dear Reiner, Reiner Herrmann writes: [...] > I was able to reproduce the issue in a jessie chroot with the bpo package. > After some debugging I found that it is a memory corruption in fs.c. > Fortunately it has also already been fixed upstream [1], which is > already part

Bug#862218: mumble: spams console with "warning: Unknown speex_preprocess_ctl request: 26" (and 35)

Package: mumble Version: 1.2.8-2 Severity: normal Dear Maintainer, on all the ARM based systems that I've tried (OLPC XO-1.75 (*), Wandboard Quad, OpenRD Base) mumble spams stdout or stderr with these lines: === Begin === warning: Unknown speex_preprocess_ctl request: 26 warning: Unknown

Bug#862083: firejail: crashes when using --allow-debuggers ("free(): invalid pointer")

Package: firejail Version: 0.9.44.8-1~bpo8+1 Severity: normal Dear Maintainer, when passing --allow-debuggers to firejail to enable strace or gdb to work inside firejail (in order to figure out why the sandboxed application doesn't work), firejail crashes immediately on start-up:

Bug#862085: spice-client: Doesn't start at all: crtc_overlap_test: unsupported partial overlap

Package: spice-client Version: 0.12.5-1+deb8u4 Severity: important Dear Maintainer, not sure exactly when it broke (upgrade to jessie or some later update), but spicec doesn't work at all anymore on my system: === Begin === sascha.silbe@twin:~$ spicec -h localhost -p 1234

Bug#596334: dnsutils: Still happens in Stretch

Package: dnsutils Version: 1:9.10.3.dfsg.P4-12.3+deb9u3 Followup-For: Bug #596334 Control: found 596334 1:9.10.3.dfsg.P4-12.3+deb9u3 Dear Maintainer, I'm not the original reporter but I can still reproduce this bug in Stretch: sascha@vorratskeller3:~$ dig +sigchase +dnssec +topdown -t MX

Bug#901675: notion: Unconditionally uses /bin/sh instead of user shell

Package: notion Version: 3+2015061300-2+b1 Severity: normal Dear Maintainer, I'm defining a couple of shell functions in my ~/.bash_profile and export them so I can use them in xterms started from within notion. This worked fine in jessie, but broke with the update to stretch. Apparently in

Bug#846175: gnupg-agent: Unable to use SSH key with empty passphrase since upgrade to Stretch

Package: gnupg-agent Version: 2.1.18-8~deb9u2 Followup-For: Bug #846175 Dear Maintainer, after the upgrade to Stretch we're hitting this bug, too. We have an SSH key that's shared between a group of users and used by automated processes, too (so it cannot be password-protected). The OpenSSH

Bug#944518: linux-image-4.19.0-6-armmp: please enable CONFIG_INPUT_TPS65218_PWRBUTTON

Source: linux Version: 4.19.67-2+deb10u1 Severity: wishlist Dear Maintainer, currently it's impossible to use the power button on the BeagleBone Black when running the Debian kernel. Please enable CONFIG_INPUT_TPS65218_PWRBUTTON. Kind regards, Sascha Silbe -- Package-specific info: ** Version

Bug#944256: linux-image-4.19.0-6-armmp: please enable cpufreq for AM335x (BBB)

. For starters enabling CONFIG_ARM_TI_CPUFREQ will be required; not sure if other options are missing, too. Kind regards, Sascha Silbe -- Package-specific info: ** Version: Linux version 4.19.0-6-armmp (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2 (2019-08

Bug#950508: debos: broken in Buster: libresolv.so.2: cannot open shared object file

Package: debos Version: 1.0.0+git20190123.d6e16be-1 Severity: grave Justification: renders package unusable Dear Maintainer, after the upgrade to Buster debos stopped working. This happens even with the minimal example from the man page. The output when run with --show-boot suggests a shared

Bug#971696: linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after upgrade

Sascha Silbe writes: > since the last kernel update (from linux-image-armmp:armhf > 4.19+105+deb10u5 / linux-image-4.19.0-10-armmp 4.19.132-1 to > linux-image-armmp 4.19+105+deb10u6 / linux-image-4.19.0-11-armmp > 4.19.146-1) our BeagleBone Black systems with AR9271 based

Bug#971696: linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after upgrade

Package: src:linux Version: 4.19.146-1 Severity: important Dear Maintainer, since the last kernel update (from linux-image-armmp:armhf 4.19+105+deb10u5 / linux-image-4.19.0-10-armmp 4.19.132-1 to linux-image-armmp 4.19+105+deb10u6 / linux-image-4.19.0-11-armmp 4.19.146-1) our BeagleBone Black

Bug#994093: libgradle-android-plugin-java: tries to use removed method setDependencyCacheDir()

Package: libgradle-android-plugin-java Version: 2.2.2-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sascha-debian-bugs-libgradle-android-plugin-java-2021-09...@silbe.org Dear Maintainer, the Android Gradle Plugin version in sid (2.2.2-3) does not work with the Gradle

Bug#995444: bsdutils: "script" no longer prints output file name at the end

Package: bsdutils Version: 1:2.36.1-8 Severity: normal Tags: upstream Dear Maintainer, since Bullseye, probably caused by upstream commit d805688afc0c709154c9c6f29383b175c05ffc92 ("script: report also timing file, do it only once"), "script" no longer outputs the file name at the end. I'm using

Bug#999772: limesuite-udev: replaces entire /dev/serial directory with single symlink

Package: limesuite-udev Version: 20.10.0+dfsg-2 Severity: important X-Debbugs-Cc: sascha-debian-bugs-2021-11-16-limesuite-u...@silbe.org Dear Maintainer, the udev rules contained in limesuite-udev cause *all* USB serial adapters using the default vendor / product id of several FTDI chips

Bug#1008762: debos: does not work with Linux 5.13+

Package: debos Version: 1.0.0+git20201203.e939090-4+b3 Severity: important Tags: upstream X-Debbugs-Cc: sascha-debian-bugs-debos-2022-03...@silbe.org Dear Maintainer, debos does not work on systems running a 5.13 or newer kernel because the 9pnet_virtio and virtio_pci modules cannot be loaded:

Bug#1010391: afew: missing dependency on python3-dnspython

Package: afew Version: 3.0.1-1 Severity: normal X-Debbugs-Cc: sascha-debian-bugs-afew-2022-04...@silbe.org Dear Maintainer, after a fresh installation afew fails to start because it cannot find the "dns" module: === Begin === Traceback (most recent call last): File "/usr/bin/afew", line 33,

Bug#1010605: pytest: please package pytest 7.1.x

Source: pytest Version: 6.0.2-2 Severity: wishlist X-Debbugs-Cc: sascha-debian-bugs-pytest-2022-05...@silbe.org Dear Maintainer, pytest 7.0.0 introduced a couple useful new features. It would be great to have the latest upstream version (7.1.2 at the time of writing) in Debian. Thanks in

Bug#1036457: flash-kernel: please add BeagleBone AI-64 support

Package: flash-kernel Version: 3.107 Severity: wishlist X-Debbugs-Cc: sascha-debian-bugs-flash-kernel-20230...@silbe.org Dear Maintainer, I successfully tested flash-kernel on a BeagleBone AI-64 running Bookworm with the following entry in /etc/flash-kernel/db: === Begin === Machine:

<    1   2   3   4