Bug#1067469: script for generating the UI does not work
Hi Daniel, On Fri, Mar 22, 2024 at 12:14:51PM +0100, Daniel Swarbrick wrote: > The generate-ui.sh script was substantially refactored in June 2023. The the patch only works for the script that ships with bookworm's 0.25 version. I have seen that the script has been completely re-done for 0.27, and it looks like that might work ootb. > Can you try the script from the latest package from sid? > > [1]: > https://salsa.debian.org/go-team/packages/prometheus-alertmanager/-/commits/debian/sid/debian/generate-ui.sh?ref_type=heads Ok, I'll give it a try. Thank you, Toni
Bug#1067469: script for generating the UI does not work
Package: prometheus-alertmanager Version: 0.25.0-1+b4 Severity: normal Tags: upstream patch Hi, the included script 'generate-ui.sh' does not work. The attached patch fixes this, at least to a degree. Enjoy, Toni -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prometheus-alertmanager depends on: ii adduser 3.134 ii init-system-helpers 1.65.2 ii libc62.36-9+deb12u4 ii tzdata 2024a-0+deb12u1 prometheus-alertmanager recommends no packages. prometheus-alertmanager suggests no packages. -- no debconf information --- ./usr/share/prometheus/alertmanager/generate-ui.sh 2023-02-03 03:10:24.0 + +++ /tmp/generate-ui.sh 2024-03-21 22:43:52.452041965 + @@ -2,7 +2,7 @@ set -e -ELMDISTURL=https://github.com/elm/compiler/releases/download/0.19.0/binaries-for-linux.tar.gz +ELMDISTURL=https://github.com/elm/compiler/releases/download/0.19.1/binary-for-linux-64-bit.gz SRCDIR=/usr/share/gocode/src/github.com/prometheus/alertmanager/ui/app DSTDIR=/usr/share/prometheus/alertmanager/ui @@ -14,7 +14,8 @@ TMPDIR=$(mktemp -d) echo "Downloading Elm tools..." >&2 -curl --location $ELMDISTURL | tar xz -C $TMPDIR +# curl --location $ELMDISTURL | tar xz -C $TMPDIR +( cd $TMPDIR && curl -L -o - $ELMDISTURL | gzip -d - > elm && chmod 0755 ./elm ) echo "Compiling source code..." >&2 ln -s $SRCDIR/src $SRCDIR/elm.json $TMPDIR @@ -31,7 +32,9 @@ cp $TMPDIR/script.js $DSTDIR cp $SRCDIR/index.html $SRCDIR/favicon.ico $DSTDIR ln -s /usr/share/fonts-font-awesome $DSTDIR/lib/font-awesome +ln -s /usr/share/nodejs/bootstrap/dist $DSTDIR/lib/bootstrap ln -s /usr/share/nodejs/bootstrap/dist $DSTDIR/lib/bootstrap4 +cp -a /usr/share/gocode/src/github.com/prometheus/alertmanager/ui/app/lib/elm-datepicker $DSTDIR/lib rm -rf $TMPDIR
Bug#1064940: vipw's manpage does not document ~/.selected_editor
Package: passwd Version: 1:4.13+dfsg1-1+b1 Severity: minor Tags: patch Hi, the 'vipw' program uses a file that isn't documented. The attached patch should fill this gap, although I haven't tried to build the package with it. Enjoy, Toni -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages passwd depends on: ii libaudit1 1:3.0.9-1 ii libc6 2.36-9+deb12u4 ii libcrypt1 1:4.4.33-2 ii libpam-modules 1.5.2-6+deb12u1 ii libpam0g1.5.2-6+deb12u1 ii libselinux1 3.4-1+b6 ii libsemanage23.4-1+b5 Versions of packages passwd recommends: ii sensible-utils 0.0.17+nmu1 passwd suggests no packages. -- no debconf information diff --git a/man/vipw.8.xml b/man/vipw.8.xml index 4caddcb..9775af7 100644 --- a/man/vipw.8.xml +++ b/man/vipw.8.xml @@ -77,6 +77,11 @@ vi 1. + +On the first run, this program asks you for an editor and stores your +selection in ~/.selected_editor. If the editor mentioned therein does +not exist on your system, the program will fall back to using 'nano'. + @@ -210,6 +215,9 @@ gshadow5 + + ~/.selected_editor5 + login.defs5 ,
Bug#1050724: ignores fcitx 4
Package: terminator Version: 2.1.2-2 Severity: normal Tags: l10n upstream Hi, I have terminator installed, but can't for the life of me get fcitx to activate. Hence, I am unable to write non-ascii characters in Terminator. The problem does seem to be fixed in terminator 2.1.3, where I can activate fcitx so far. For me, this means that I need to use a "foreign" terminator for many things. Thanks, Toni -- System Information: Debian Release: trixie/sid APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages terminator depends on: ii gir1.2-glib-2.01.74.0-3 ii gir1.2-gtk-3.0 3.24.37-2 ii gir1.2-pango-1.0 1.50.14+ds-1 ii gir1.2-vte-2.910.70.6-1 ii gsettings-desktop-schemas 43.0-1 ii python33.11.2-1+b1 ii python3-cairo 1.20.1-5+b1 ii python3-configobj 5.0.8-2 ii python3-dbus 1.3.2-4+b1 ii python3-gi 3.42.2-3+b1 ii python3-gi-cairo 3.42.2-3+b1 ii python3-psutil 5.9.4-1+b1 Versions of packages terminator recommends: ii dbus-user-session [default-dbus-session-bus] 1.14.8-2~deb12u1 ii dbus-x11 [dbus-session-bus] 1.14.8-2~deb12u1 ii gir1.2-keybinder-3.0 0.3.2-1.1 ii gir1.2-notify-0.7 0.8.2-1 ii xdg-utils 1.1.3-4.1 terminator suggests no packages. -- no debconf information
Bug#1036817: missing simplified version for 'sao' (187.8)
Package: fcitx-table Version: 1:4.2.9.8-3 Severity: minor Tags: upstream Hi, I am trying to write the character 'sao' (see attached image), but only get the traditional version of it, which is then mistaken as a Japanese character. It would be nice if you could add this character. Thanks, Toni -- System Information: Debian Release: 11.7 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-22-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fcitx-table depends on: ii fcitx-bin 1:4.2.9.8-3 ii fcitx-data 1:4.2.9.8-3 ii fcitx-modules 1:4.2.9.8-3 ii libc6 2.31-13+deb11u6 Versions of packages fcitx-table recommends: ii fcitx 1:4.2.9.8-3 ii fcitx-pinyin 1:4.2.9.8-3 Versions of packages fcitx-table suggests: ii fcitx-table-all 1:4.2.9.8-3 -- no debconf information
Bug#1032857: please consider adding the jgrpp patches
Package: openttd Version: 13.0-2 Severity: wishlist Tags: upstream Hi, please consider packaging the jgrpp patches, too. https://github.com/JGRennison/OpenTTD-patches Thank you, Toni -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openttd depends on: ii libc62.31-13+deb11u5 pn libfluidsynth3 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1+deb11u1 ii libgcc-s110.2.1-6 ii libicu67 67.1-7 pn libicu72 ii liblzma5 5.2.5-2.1~deb11u1 ii liblzo2-22.10-2 ii libpng16-16 1.6.37-3 ii libsdl2-2.0-02.0.14+dfsg2-3+deb11u1 ii libstdc++6 10.2.1-6 ii libxdg-basedir1 1.2.0-2+b1 pn openttd-data ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages openttd recommends: ii openttd-opengfx 0.6.0-1 pn openttd-openmsx pn openttd-opensfx pn timidity Versions of packages openttd suggests: pn openttd-opensfx pn timidity
Bug#1030356: signature verification issue CVE-2020-16156
Package: perl-base Version: 5.32.1-4+deb11u2 Severity: grave Tags: security upstream X-Debbugs-Cc: Debian Security Team Hi, there's a signature verification problem with the CPAN module shipped with bullseye. The problem seems to be fixed in CPAN 2.29. Enjoy, Toni -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-20-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages perl-base depends on: ii dpkg 1.20.12 ii libc6 2.31-13+deb11u5 ii libcrypt1 1:4.4.18-4 perl-base recommends no packages. Versions of packages perl-base suggests: ii perl5.32.1-4+deb11u2 ii sensible-utils 0.0.14 -- no debconf information
Bug#1030355: heap overflow CVE-2022-3715
Package: bash Version: 5.1-2+deb11u1 Severity: grave Tags: security upstream X-Debbugs-Cc: Debian Security Team Hi, according to RedHat, this bug was corrected in bash 5.1.8, but seems to be usable to conduct at least a local DOS. Enjoy, Toni -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-20-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bash depends on: ii base-files 11.1+deb11u6 ii debianutils 4.11.2 ii libc62.31-13+deb11u5 ii libtinfo66.2+20201114-2 Versions of packages bash recommends: ii bash-completion 1:2.11-2 Versions of packages bash suggests: pn bash-doc -- no debconf information
Bug#1024972: pip asks for a password, waits forever
Package: python3-pip Version: 20.3.4-4+deb11u1 Severity: important Tags: upstream Hi, there is this bug https://github.com/pypa/pip/issues/7883 that affects Debian Bullseye. In a virtualenv, I have installed pip 22.3.1, which does not have this flaw. There is no action required for testing and later, but it would be nice if this problem could be addressed in the next point release of Bullseye. Thanks, Toni -- System Information: Debian Release: 11.5 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-19-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pip depends on: ii ca-certificates 20210119 ii python-pip-whl 20.3.4-4+deb11u1 ii python3 3.9.2-3 ii python3-distutils 3.9.2-1 ii python3-setuptools 52.0.0-4 ii python3-wheel 0.34.2-1 Versions of packages python3-pip recommends: ii build-essential 12.9 ii python3-dev 3.9.2-3 python3-pip suggests no packages. -- no debconf information
Bug#1020981: character missing from Chinese fonts and input methods
Package: task-chinese Severity: normal Hi, I frequently find the character in the attached image somewhere, but can't type it. In Wubi, the character code should probably be NWWI. It would be great if you could add the character to fonts and input methods. Thanks, Toni -- System Information: Debian Release: 11.5 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-18-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1006810: Workaround
Hi, I just ran into the same problem. First off, it's weird that apt fails to properly recognize that it needs to upgrade wacom-common, but manually installing wacom-common did upgrade this package, so that further upgrading was unblocked. Enjoy, Toni
Bug#1012615: Please provide PHP 8.1 as a backport
Package: php8.1 Severity: wishlist Hi, it would be great if PHP 8.1, and possibly other packages related to it, like Symfony, were avialable as backports. ;) Cheers, Toni -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php8.1 depends on: pn libapache2-mod-php8.1 | php8.1-fpm | php8.1-cgi pn php8.1-common php8.1 recommends no packages. php8.1 suggests no packages.
Bug#1009615: forcibly starts chromium on several functions
Package: nextcloud-desktop Version: 3.1.1-2+deb11u1 Severity: important Tags: upstream Hi, I am running nextcloud-desktop in my .xsessionrc. When it starts, it also fires up chromium, which I have installed, but which I rarely use. Also, for a number of other activities, which were formerly part of the nextcloud desktop client, it now also fires up chromium, although chromium is not my standard browser. I have not found a way to make nextcloud-client use my standard browser, which happens to be firefox-esr, for such things, and I am also not prepared to run a second browser in parallel just to interact with Nextcloud. In fact, I interact with Nextcloud just fine using Firefox, and if these functions are only available in the browser these days, they should imho be removed from the menu. I can start a web browser myself, thank you very much! Thanks, Toni -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-13-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nextcloud-desktop depends on: ii libc6 2.31-13+deb11u3 ii libcloudproviders0 0.3.0-3 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii libnextcloudsync0 3.1.1-2+deb11u1 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus55.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5keychain10.10.0-1 ii libqt5network5 5.15.2+dfsg-9 ii libqt5qml5 5.15.2+dfsg-6 ii libqt5quick5 5.15.2+dfsg-6 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5sql5-sqlite 5.15.2+dfsg-9 ii libqt5svg5 5.15.2-3 ii libqt5webenginecore5 5.15.2+dfsg-3 ii libqt5webenginewidgets55.15.2+dfsg-3 ii libqt5webkit5 5.212.0~alpha4-11 ii libqt5widgets5 5.15.2+dfsg-9 ii libstdc++6 10.2.1-6 ii nextcloud-desktop-common 3.1.1-2+deb11u1 ii nextcloud-desktop-l10n 3.1.1-2+deb11u1 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtqml-models2 5.15.2+dfsg-6 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-6 ii qml-module-qtquick-window2 5.15.2+dfsg-6 ii qml-module-qtquick25.15.2+dfsg-6 Versions of packages nextcloud-desktop recommends: ii nextcloud-desktop-doc 3.1.1-2+deb11u1 nextcloud-desktop suggests no packages. -- no debconf information
Bug#998708: Please upgrade to 6.9.1
Package: gradle Version: 4.4.1-13 Severity: wishlist Hi, while trying to create a new version of the groovy package, I noticed, that they ask for version 6.9.1 of gradle. It would be nice to have, given that our current version is already three years old. Thanks, Toni -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gradle depends on: ii default-jre-headless [java8-runtime-headless] 2:1.11-72 ii libgradle-core-java 4.4.1-13 ii libgradle-plugins-java4.4.1-13 ii openjdk-11-jre-headless [java8-runtime-headless] 11.0.13+8-1~deb11u1 ii openjdk-17-jre-headless [java8-runtime-headless] 17~19-1 gradle recommends no packages. Versions of packages gradle suggests: pn gradle-doc -- no debconf information
Bug#951831: Please update to 3.x
Hello, I would also like to see groovy updated to the latest 3.x, because several aspects of Jenkins pipelines do not work with Groovy 2.4, or at least, not as documented. Thanks, Toni
Bug#993274: machine unbootable after upgrade
Hi Paul, On Mon, Aug 30, 2021 at 10:10:12PM +0200, Paul Gevers wrote: > On 29-08-2021 23:39, Toni Mueller wrote: > > I am not sure why the upgrade process didn't handle this case, but think > > the severity of the problem warrants a warning in the release notes. > > Can you give a proposal for some text? After reading the old (closed) > bug report, it's not clear to me what to warn for exactly as it seems > that Colin there claims it's a broken configuration on your system. the system was installed as a standard no-frills Buster system. I haven't read why Colin thought that's a misconfiguration on the system, but in my case, there has been no disk change, the system was installed and then, sometime later, upgraded, which is when the problem occurred. > Nobody brought it up to the release notes, so nothing was added. Of course, I can only suggest something after seeing a problem. I would suggest a text like this: If your system is configured to boot from a RAID array, eg. MDADM, you need to take extra precautions. After the upgrade procedure, but before the reboot, you need to manually ensure that GRUB is properly installed on all relevant disks. In the case of RAID1 (mirrored disks), do this: # lsblk sda... sdc... # or sdb You'll find the boot disks by their partitioning. For this example, it's sda and sdc. Then run these commands: # grub-install /dev/sda # grub-install /dev/sdc The other question is, why did this happen at all? I have previously upgraded other systems with the same RAID configuration (ie, RAID1 via mdadm), and can't remember having seen this problem. It would be better to actually fix the problem, if possible. Cheers, Toni
Bug#993274: machine unbootable after upgrade
Package: upgrade-reports Severity: grave Hi, I have recently upgraded a machine from Buster to Bullseye. The machine runs on an mdadm RAID1. After the upgrade, it had the symptom outlined in #931896. I followed the upgrade process, as described in https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html After completing this procedure, I ran # apt install -f # dpkg --configure -a which both came up empty, suggesting that there was really no problem left. Since the machine didn't boot after upgrade, I'd say that warrants 'grave'. As a fix, once I got access to the machine, running # lsblk to figure out the boot disks, then manually installing grub there like this: # grub-install /dev/sda # grub-install /dev/otherdisk solved the problem. I am not sure why the upgrade process didn't handle this case, but think the severity of the problem warrants a warning in the release notes. Cheers, Toni
Bug#991615: lxc-download: pgp server deprecated
Package: lxc Version: 1:4.0.6-2 Severity: normal File: lxc-download X-Debbugs-Cc: atel...@lacetania.cat -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii bridge-utils 1.7-1 ii debconf [debconf-2.0]1.5.77 ii dnsmasq-base [dnsmasq-base] 2.85-1 ii iproute2 5.10.0-4 ii iptables 1.8.7-1 ii libc62.31-13 ii libcap2 1:2.44-1 ii libgcc-s110.2.1-6 ii liblxc1 1:4.0.6-2 ii libseccomp2 2.5.1-1 ii libselinux1 3.1-3 ii lsb-base 11.1.0 Versions of packages lxc recommends: ii apparmor 2.13.6-10 ii debootstrap1.0.123 ii dirmngr2.2.27-2 ii gnupg 2.2.27-2 ii libpam-cgfs1:4.0.6-2 ii lxc-templates 3.0.4-5 ii lxcfs 4.0.7-1 ii openssl1.1.1k-1 ii rsync 3.2.3-4 ii uidmap 1:4.8.1-1 ii wget 1.21-1+b1 Versions of packages lxc suggests: pn btrfs-progs ii lvm2 2.03.11-2.1 pn python3-lxc -- Configuration Files: /etc/default/lxc-net changed [not included] -- debconf information excluded /usr/share/lxc/templates/lxc-download deprecated server hkp://pool.sks-keyservers.net, you can change for: hkp://keys.openpgp.org
Bug#980227: changed keyboard shortcuts ok
Hi, I just noticed, but am in favour of this change. Makes it much harder to close VM windows by accident, and also removes one collision point, when the VM has windows which want Ctrl-W to be closed. Thanks, Toni
Bug#983244: can't get redshift to obtain the location
Package: redshift Version: 1.12-2 Severity: important Hi, since the latest update, redshift can't get the location anymore and thus exits. I tried several things, like manually running the geoclue agent, or reconfiguring access in /etc/geoclue/geoclue.conf but to absolutely no avail. I'd like to run redshift-gtk in the background, adjusting automatically, but so far, I can only run redshift and xbacklight by hand, which I need to do several times a day. What gives? Thanks, Toni -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-14-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages redshift depends on: ii libc6 2.28-10 ii libdrm22.4.97-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libx11-6 2:1.6.7-1+deb10u1 ii libxcb-randr0 1.13.1-2 ii libxcb11.13.1-2 ii libxxf86vm11:1.1.4-1+b2 Versions of packages redshift recommends: ii geoclue-2.0 2.5.2-1+deb10u1 redshift suggests no packages. -- no debconf information
Bug#979077: On first installation, clamav-daemon fails to start
Package: clamav-daemon
Version: 0.102.4+dfsg-0+deb10u1
Severity: normal
Hi,
when I install clamav-daemon for the first time, the daemon fails to
start. This is intentional, as per the systemd unit file (see below),
but I think the logic is wrong:
The logic is that if there is no database file, clamav-daemon should not
run. However, on first start, there can be no database file, so as a
side effect, while eg. (in my case) clamav-freshclam is trying to fetch
a database, the service just exits and doesn't come back automatically.
In my opinion, this is highly counterintuitive. Instead, the daemon
should start and tell everyone that it can't scan anything, due to the
lack of a database, but automatically resume normal operation as soon as
clamav-freshclam has done it's job and installed a virus database,
instead of requiring (manual?) intervention to start the service.
The offending lines in
/etc/system/multi-user.target.wants/clamav-daemon.service
are:
ConditionPathExistsGlob=/var/lib/clamav/main.{c[vl]d,inc}
ConditionPathExistsGlob=/var/lib/clamav/daily.{c[vl]d,inc}
While I am at it, maybe some "restart on failure" mechanism should also
be included?
Thanks,
Toni
-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav
Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "30"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertEncrypted disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "
Bug#974939: closed by Ben Hutchings (Re: Bug#974939: machine does not boot)
Hi Ben,
On Mon, Nov 23, 2020 at 10:45:09AM +, Debian Bug Tracking System wrote:
> I recommend that you always check the list of packages to be removed in
> a dist-upgrade, if you have some packages installed from
> testing/unstable.
yes. :/
> It doesn't exist in stable. Perhaps you installed something from
> testing/unstable that required it? libgcc-s1 breaks the stable version
> of cryptsetup-initramfs.
I checked. My apt and libc6 are both from stable, and should thus only
have stable dependencies, right?
However, removing libgcc-s1 broke apt ("could not load shared
library...").
Thanks for the heads-ups,
Toni
Bug#974939: machine does not boot
Hi Ben, On Mon, Nov 23, 2020 at 10:12:01AM +, Ben Hutchings wrote: > On Mon, 2020-11-23 at 10:04 +0000, Toni Mueller wrote: > > I agree, but I can only file a bug report against the kernel package. > > Please find the output of this command attached. > cryptsetup support is not included in the newer initramfs images. I saw that, but was not aware of this package: > Did you remove cryptsetup-initramfs by accident? Not that I am aware of, and definitely not intentionally. Until now, I had no idea that it even existed. But I can now see that it was removed in a dist-upgrade run on the 9th of May last year (huh?!?). But there seems to be a problem to re-install it: # apt install cryptsetup-initramfs -y ... The following packages will be REMOVED: libgcc-s1 The following NEW packages will be installed: cryptsetup-initramfs WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! libgcc-s1 0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. Since libgcc-s1 is being provided by libgcc1, I am inclined to run with --allow-remove-essential. But this is still quite scary! (I wasn't aware of libgcc-s1, either. :( ) Thanks, Toni
Bug#974939: machine does not boot
Hi, On Tue, Nov 17, 2020 at 12:50:19PM +0100, Bastian Blank wrote: > On Mon, Nov 16, 2020 at 07:41:05PM +0000, Toni wrote: > > Severity: critical > > Sorry, no. This problem does not break the package for everyone. > > > On the console, after dmesg, these three lines repeat ad nauseum: > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > So it actually boots, but the boot process is not able to find your root > filesystem? It loads the kernel, I can see the dmesg, and then I see an endless loop of these messages. So yes, there's something broken with encrypted partitions, that wasn't broken until the -10 kernel. > Yes, that look pretty normal and like something the Debian installer > would create. It did. > What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf? > What do you have mdadm for? I don't have mdadm devices in this machine (it's a laptop with only one SSD, anyway). I don't know why mdadm is present on this machine, but it has "always" been, with no detrimental effects until possibly recently. Thanks, Toni
Bug#974939: machine does not boot
Package: src:linux Version: 4.19.152-1 Severity: critical Hi, with the two latest kernels, linux-image-4.19.0-12-amd64 and linux-image-4.19.0-11-amd64, my machine does not boot, the reason being that something with cryptsetup is amiss. I used to be asked for a passphrase, but using these two kernels, I'm not, and the machine just cycles trying to find the root partition. I am now running the -10 kernel again, which I would like to get off of. I've tried recovery mode without any success. On the console, after dmesg, these three lines repeat ad nauseum: mdadm: No arrays found in config file or automatically Volume group "ev0" not found Cannot process volume group ev0 mdadm: No arrays found in config file or automatically Volume group "ev0" not found Cannot process volume group ev0 I think this bug is critical, since I can't get to anything with this state of the machine. The disk configuration is pretty straightforward: git:(master*)$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:00 953.9G 0 disk ├─nvme0n1p1 259:10 238.4M 0 part ├─nvme0n1p2 259:20 3.5G 0 part ├─nvme0n1p3 259:30 953M 0 part /boot └─nvme0n1p4 259:40 949.2G 0 part └─nvme0n1p4_crypt 253:00 949.2G 0 crypt ├─ev0-swap 253:10 29.8G 0 lvm [SWAP] ├─ev0-root 253:20 789.4G 0 lvm / There is one other (data) partition, but that's it for what the system has. Cheers, Toni -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision 5530 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 1.13.0 board_vendor: Dell Inc. board_name: 0X78C1 board_version: A02 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07) Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1028:087d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10) Subsystem: Dell Cannon Lake PCH Thermal Controller [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI]) Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B
Bug#788797: rednotebook: crashing at startup with segmentation fault - SOLVED
It's a lot of time that I don't use rednotebook anymore, so I don't have a backup of the old .rednotebook folder to test the bug. Bye, Stefano Il giorno lun 26 ott 2020 alle ore 05:01 Paul Wise ha scritto: > On Mon, 15 Jun 2015 19:02:49 +0200 Stefano De Toni wrote: > > > I moved the old directory .rednotebook in a backup directory and then I > > launched rednotebook to create a new .rednotebook directory. Finally I > > copied the data directory to new .rednotebook folder. > > I know it was a long time ago, but it would be interesting to know if > you can reproduce this issue with the new version of rednotebook in > Debian unstable. If the crash has been solved or is still present, or > if you no longer have a backup of the old .rednotebook folder or are > otherwise unable to test this, please let us know. > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise >
Bug#971535: this package makes my laptop almost unbootable
Package: src:linux Version: 4.19.146-1 Severity: important Hi, I am now running the kernel one version older because I cannot boot my laptop with the newer kernel which I am reporting this bug against. What happens, when it tries to boot, is that it searches for mdadm raids and then falls back into busybox inside initramfs. Normally, my laptop proceeds to ask for a LUKS passphrase to open the container, but somehow, with this package, the initrd was not created correctly (I presume). Thanks, Toni -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision 5530 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 1.13.0 board_vendor: Dell Inc. board_name: 0X78C1 board_version: A02 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07) Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1028:087d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10) Subsystem: Dell Cannon Lake PCH Thermal Controller [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI]) Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10) Subsystem: Dell Cannon Lake PCH Shared SRAM [1028:087d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller [8086:a368] (rev 10) Subsystem: Dell Cannon Lake PCH Serial IO I2C Controller [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Con
Bug#962902: [debian-mysql] Bug#962902: server does not start
Hi Otto, On Tue, Jun 16, 2020 at 12:27:53PM +0300, Otto Kekäläinen wrote: > Can you provide us enough information about your environment so we > could try to reproduce this error? I'm not sure what you are after. The machine in question is a laptop with Buster (latest), and all sorts of stiff. I have other machines, also VMs (KVM), where this problem does not occur. Eg. I have just 'apt dist-upgraded' a KVM VM on the same laptop, which also has this software, and there, it just runs as expected. On the host, which has very similar software, just much, much more, the same thing fails. :( My question is: Why does the server sometimes require this file to be present, and where? I mean, this software has imho no business asking for that file, to begin with. Thanks, Toni
Bug#962902: server does not start
Package: mariadb-server-10.3 Version: 1:10.3.22-0+deb10u1 Severity: important Hi, the server does not start. journalctl -xe says this: Jun 15 18:39:09 debian mysql[17154]: Starting MariaDB database server: mysqldinstall: fatal: unable to read dnsroots.global: file does not exist Jun 15 18:39:09 debian systemd[1]: mysql.service: Control process exited, code=exited, status=111/n/a I could not find a Debian package providing this file, using packages.debian.org. Not sure how this came to pass, though. Cheers, Toni -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mariadb-server-10.3 depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.71 ii galera-3 25.3.25-2 ii gawk 1:4.2.1+dfsg-1 ii iproute2 4.20.0-2 ii libc6 2.28-10 ii libdbi-perl 1.642-1+b1 ii libgnutls30 3.6.7-4+deb10u4 ii libpam0g 1.3.1-5 ii libstdc++68.3.0-6 ii lsb-base 10.2019051400 ii lsof 4.91+dfsg-1 ii mariadb-client-10.3 1:10.3.22-0+deb10u1 ii mariadb-common1:10.3.22-0+deb10u1 ii mariadb-server-core-10.3 1:10.3.22-0+deb10u1 ii passwd1:4.5-1.1 ii perl 5.28.1-6 ii psmisc23.2-1 ii rsync 3.1.3-6 ii socat 1.7.3.2-2 ii zlib1g1:1.2.11.dfsg-1 Versions of packages mariadb-server-10.3 recommends: ii libhtml-template-perl 2.97-1 Versions of packages mariadb-server-10.3 suggests: ii mailutils [mailx] 1:3.5-3 pn mariadb-test ii netcat-openbsd 1.195-2 pn tinyca -- debconf information excluded
Bug#961832: init script fails
Package: openvswitch-switch
Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12+deb10u2
Severity: normal
Hi,
I recently figured that openvswitch would not start. So I tried
# apt install --reinstall openvswitch-switch
and noticed, that it fails. From the journal:
May 30 00:14:17 debian ovs-ctl[21685]: install: fatal: unable to read
dnsroots.global: file does not exist
May 30 00:14:17 debian ovsdb-server[21706]:
ovs|2|daemon_unix|EMER|/var/run/openvswitch/ovsdb-server.pid.tmp: create
failed (No such file or directory)
May 30 00:14:17 debian ovs-ctl[21685]: ovsdb-server:
/var/run/openvswitch/ovsdb-server.pid.tmp: create failed (No such file or
directory)
May 30 00:14:17 debian ovs-ctl[21685]: Starting ovsdb-server ... failed!
May 30 00:14:17 debian systemd[1]: openvswitch-nonetwork.service: Main process
exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
I noticed that the supplied init script does not seem to create the required
directory under /run. Maybe something else is amiss as well, but after I
created the directory manually, openvswitch-switch started normally.
Cheers,
Toni
-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openvswitch-switch depends on:
ii kmod26-1
ii lsb-base10.2019051400
ii netbase 5.6
ii openvswitch-common 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12+deb10u2
ii procps 2:3.3.15-2
ii python 2.7.16-1
ii uuid-runtime2.33.1-0.1
openvswitch-switch recommends no packages.
openvswitch-switch suggests no packages.
-- Configuration Files:
/etc/init.d/openvswitch-switch changed:
(test -x /usr/sbin/ovs-vswitchd && test -x /usr/sbin/ovsdb-server) || exit 0
_SYSTEMCTL_SKIP_REDIRECT=yes
SYSTEMCTL_SKIP_REDIRECT=yes
. /lib/lsb/init-functions
. /usr/share/openvswitch/scripts/ovs-lib
test -e /etc/default/openvswitch-switch && . /etc/default/openvswitch-switch
set -vx
if [ ! -d /run/openvswitch ]; then
mkdir /run/openvswitch
fi
network_interfaces () {
INTERFACES="/etc/network/interfaces"
[ -e "${INTERFACES}" ] || return
bridges=`ifquery --allow ovs --list`
[ -n "${bridges}" ] && $1 --allow=ovs ${bridges}
}
load_kmod () {
ovs_ctl load-kmod || exit $?
}
start () {
if [ ! -d /run/openvswitch ]; then
mkdir /run/openvswitch
fi
if ovs_ctl load-kmod; then
:
else
echo "Module has probably not been built for this kernel."
echo "Please install Linux 3.3 or later with openvswitch kernel
support."
if test X"$OVS_MISSING_KMOD_OK" = Xyes; then
# We're being invoked by the package postinst. Do not
# fail package installation just because the kernel module
# is not available.
exit 0
fi
fi
set ovs_ctl ${1-start} --system-id=random
if test X"$FORCE_COREFILES" != X; then
set "$@" --force-corefiles="$FORCE_COREFILES"
fi
set "$@" $OVS_CTL_OPTS
"$@" || exit $?
if [ "$2" = "start" ] && [ "$READ_INTERFACES" != "no" ]; then
network_interfaces ifup
fi
}
stop () {
[ "$READ_INTERFACES" != "no" ] && network_interfaces ifdown
ovs_ctl stop
}
restart () {
# OVS_FORCE_RELOAD_KMOD can be set by package postinst script.
if [ "$1" = "--save-flows=yes" ] || \
[ "${OVS_FORCE_RELOAD_KMOD}" = "no" ]; then
start restart
elif [ "${OVS_FORCE_RELOAD_KMOD}" = "yes" ]; then
depmod -a
if [ -e /sys/module/openvswitch ]; then
LOADED_SRCVERSION=`cat /sys/module/openvswitch/srcversion \
2>/dev/null`
LOADED_VERSION=`cat /sys/module/openvswitch/version \
2>/dev/null`
elif [ -e /sys/module/openvswitch_mod ]; then
LOADED_SRCVERSION=`cat /sys/module/openvswitch_mod/srcversion \
2>/dev/null`
LOADED_VERSION=`cat /sys/module/openvswitch_mod/version \
2>/dev/null`
fi
SRCVERSION=`modinfo -F srcversion openvswitch 2>/dev/null`
VERSION=`modinfo -F version openvswitch 2>/dev/null`
ovs_ctl_log "Package upgrading:\
Bug#951517: installing this kernel does not cause the ndivida/bumblebee driver to be compiled
Package: src:linux Version: 5.4.8-1~bpo10+1 Severity: normal Hi, usually, installing a kernel results in any DKMS modules being recompiled for this kernel, but for the nvidia driver, this does not seem to happen. As a result, bumblebeed does not start, effectively disabling the nvidia card. Cheers, Toni -- Package-specific info: ** Version: Linux version 5.4.0-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 5.4.8-1~bpo10+1 (2020-01-07) ** Command line: BOOT_IMAGE=/vmlinuz-5.4.0-0.bpo.2-amd64 root=/dev/mapper/ev0-root ro crashkernel=384M-:128M ** Not tainted ** Kernel log: [ 2758.632378] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632378] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632379] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632380] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632381] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632382] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.633344] mce: CPU0: Package temperature/speed normal [ 2758.633345] mce: CPU4: Core temperature/speed normal [ 2758.633346] mce: CPU11: Package temperature/speed normal [ 2758.633347] mce: CPU5: Package temperature/speed normal [ 2758.633347] mce: CPU4: Package temperature/speed normal [ 2758.633348] mce: CPU3: Package temperature/speed normal [ 2758.633348] mce: CPU9: Package temperature/speed normal [ 2758.633349] mce: CPU6: Package temperature/speed normal [ 2758.633349] mce: CPU10: Core temperature/speed normal [ 2758.633350] mce: CPU10: Package temperature/speed normal [ 2758.633382] mce: CPU7: Package temperature/speed normal [ 2758.633383] mce: CPU8: Package temperature/speed normal [ 2758.633383] mce: CPU1: Package temperature/speed normal [ 2758.633384] mce: CPU2: Package temperature/speed normal [ 3120.602728] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602728] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3615) [ 3120.602768] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602769] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602770] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602771] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602772] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602773] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602774] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602775] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602776] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602778] mce: CPU10: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.603737] mce: CPU6: Package temperature/speed normal [ 3120.603737] mce: CPU0: Package temperature/speed normal [ 3120.603782] mce: CPU3: Package temperature/speed normal [ 3120.603783] mce: CPU1: Package temperature/speed normal [ 3120.603784] mce: CPU9: Package temperature/speed normal [ 3120.603785] mce: CPU2: Package temperature/speed normal [ 3120.603785] mce: CPU7: Package temperature/speed normal [ 3120.603786] mce: CPU8: Package temperature/speed normal [ 3120.603787] mce: CPU10: Package temperature/speed normal [ 3120.603787] mce: CPU4: Package temperature/speed normal [ 3120.603788] mce: CPU5: Package temperature/speed normal [ 3120.603789] mce: CPU11: Package temperature/speed normal [ 4810.196840] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 2594) [ 4810.196841] mce: CPU8: Core temperature above threshold, cpu clock throttled (total events = 2594) [ 4810.196841] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196842] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196843] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196844] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196844] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196845] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196881] mce: CPU6: Package temperature above threshold, cpu
Bug#949403: installing this package blocks apt for a long time
Package: samhain Version: 1.10.1-2.1 Severity: normal Hi, when I install this package, the postinst runs 'samhain -t init' in a synchronous fashion. I can't work on other things that require a lock on the apt database until this jobs finishes, because the apt datasb It would be nicer if this were delegated to a batch job. Cheers, Toni -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages samhain depends on: ii debconf [debconf-2.0] 1.5.71 pn libauparse0 ii libc6 2.28-10 ii libgcrypt201.8.4-5 ii libgnutls303.6.7-4 ii libltdl7 2.4.6-9 ii libpcre3 2:8.39-12 pn libprelude23 pn libprelude28 ii zlib1g 1:1.2.11.dfsg-1 samhain recommends no packages. samhain suggests no packages.
Bug#946368: DeprecationWarning for using collections instead of collections.abc
Hi Thomas, On Tue, Dec 10, 2019 at 08:47:02PM +0100, Thomas Goirand wrote: > Do you feel like doing the work yourself for this? I have too many > things to watch for stable updates... I am strongly considering it if it's ok for you. Cheers, Toni
Bug#946368: DeprecationWarning for using collections instead of collections.abc
Package: python3-jsonschema Version: 2.6.0-4 Severity: minor Tags: upstream Hi, please backport this fix from unstable: https://github.com/Julian/jsonschema/blob/master/jsonschema/compat.py#L11 It would kill a warning that is a bit obnoxious, and should have no ill side effect. Thanks, Toni -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-jsonschema depends on: ii python33.7.3-1 ii python3-pkg-resources 40.8.0-1 python3-jsonschema recommends no packages. Versions of packages python3-jsonschema suggests: pn python-jsonschema-doc -- no debconf information
Bug#944022: Make Firehol Read The File
Hi Jerome, On Sat, Nov 23, 2019 at 10:54:29AM +0400, Jerome BENOIT wrote: > On 18/11/2019 21:39, Toni Mueller wrote: > > My patch in Salsa may not yet be quite functional, but it changes the > > 'firehol' script itself to read /etc/default/firehol and then exit if > > this variable is not set to YES. > > This sound as the best option. > > Where is the patch (exactly) ? I've just issued a MR, so you can see it properly. However, this MR does not create a patch, but changes the script directly. Enjoy! Cheers, Toni
Bug#944022: Make Firehol Read The File
Hi Jerome, making the systemd unit file read /etc/default/firehol would not change a thing because there is no logic available to act upon the START_FIREHOL variable. My patch in Salsa may not yet be quite functional, but it changes the 'firehol' script itself to read /etc/default/firehol and then exit if this variable is not set to YES. Cheers, Toni
Bug#944022: suggested patch
Hi Michael, forgot to say: Yes, it used to work in the past, but when firehol gained a systemd service unit file, this functionality was lost. My patch attempts to re-enable this functionality. Cheers, Toni
Bug#944078: [Pkg-utopia-maintainers] Bug#944078: firewall-applet: applet does not appear
Hi Michael, On Sun, Nov 03, 2019 at 11:45:07PM +0100, Michael Biebl wrote: > Am 03.11.19 um 23:28 schrieb Toni Mueller: > > I have tried two versions that don't work. Switching window managers is > > not an option for me, and generally, it should work everywhere (imho). > > > > What would be the way forward? > > If I had to guess I'd say it's either an issue of Qt5 or the tray > application you are using in awesome. Might also be related to compositing. > Maybe those hints help you further investigation this issue. well, I have no clue about Qt, and I am using the standard awesome with no special addons that I am aware of - just as it comes with buster, plus a memory/cpu/battery widget. Every other program, like eg. pavucontrol, screengrab, nm-applet, vlc, radiotray, redshift-gtk etc., has no problems adding itself to the tray. The systray is, to the best of my very limited knowledge, a builtin feature of awesome. You have it if you just install awesome. Now what... Cheers, Toni
Bug#944078: firewall-applet: applet does not appear
EDITOR = binary (Pdb) > /usr/bin/firewall-applet(70)() -> break (Pdb) > /usr/bin/firewall-applet(72)() -> PY2 = sys.version < '3' (Pdb) > /usr/bin/firewall-applet(74)() -> def escape(text): (Pdb) > /usr/bin/firewall-applet(80)() -> def fromUTF8(text): (Pdb) > /usr/bin/firewall-applet(87)() -> class ZoneInterfaceEditor(QtWidgets.QDialog): (Pdb) > /usr/bin/firewall-applet(160)() -> class ZoneConnectionEditor(ZoneInterfaceEditor): (Pdb) > /usr/bin/firewall-applet(185)() -> class ZoneSourceEditor(ZoneInterfaceEditor): (Pdb) > /usr/bin/firewall-applet(201)() -> class ShieldsEditor(QtWidgets.QDialog): (Pdb) > /usr/bin/firewall-applet(336)() -> class AboutDialog(QtWidgets.QDialog): (Pdb) > /usr/bin/firewall-applet(413)() -> class TrayApplet(QtWidgets.QSystemTrayIcon): (Pdb) > /usr/bin/firewall-applet(1116)() -> if len(sys.argv) > 1: (Pdb) > /usr/bin/firewall-applet(1125)() -> signal.signal(signal.SIGINT, signal.SIG_DFL) (Pdb) > /usr/bin/firewall-applet(1127)() -> app = QtWidgets.QApplication(sys.argv) (Pdb) > /usr/bin/firewall-applet(1128)() -> app.setQuitOnLastWindowClosed(False) (Pdb) > /usr/bin/firewall-applet(1130)() -> applet = TrayApplet() (Pdb) > /usr/bin/firewall-applet(1131)() -> applet.show() (Pdb) > /usr/bin/firewall-applet(1132)() -> sys.exit(app.exec_()) (Pdb) p applet <__main__.TrayApplet object at 0x7f00337deca8> (Pdb) n ^C The applet object is apparently being created, but then, it just hangs, so I pressed Control-C to get out of the program. The following additional information might be helpful: * I have just installed the program and eg. not yet configured firewalld. * I am running plain awesome, not Gnome or something like that. * My iptables rules are so far managed with firehol (but I am looking into possible migration). I have other applets running in my systray, so I am a bit confused why this one wouldn't start. Cheers, Toni -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (550, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firewall-applet depends on: ii firewall-config 0.7.2-1 ii firewalld0.7.2-1 ii gir1.2-nm-1.01.14.6-2 ii gir1.2-notify-0.70.7.7-4 ii python3 3.7.3-1 ii python3-dbus 1.2.8-3 ii python3-dbus.mainloop.pyqt5 5.11.3+dfsg-1+b3 ii python3-gi 3.30.4-1 ii python3-pyqt55.11.3+dfsg-1+b3 ii python3-slip-dbus0.6.5-2 firewall-applet recommends no packages. firewall-applet suggests no packages. -- no debconf information
Bug#944022: firehol: default config is unusable for a server
Package: firehol Version: 3.1.6+ds-8 Severity: important Dear Maintainer, as-is, the firehol package installs a set of filters that will disable access to the server. This would not be a problem if the package would not also immediately start firehol, ie, implement this configuration. I found that it shouldn't be started, but it definitely is, despite /etc/defaults/firehol saying "START_FIREHOL=NO". The effect is that if you install this package on a server, you're immediately losing contact and have no remedy to fix that. Suggested fix: Do not enable this service during installation, at least not on a server, or install a default policy like this: interface any world policy accept Cheers, Toni -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (550, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firehol depends on: ii firehol-common 3.1.6+ds-8 ii lsb-base10.2019051400 Versions of packages firehol recommends: ii fireqos 3.1.6+ds-8 Versions of packages firehol suggests: pn firehol-doc pn firehol-tools pn ulogd2 -- Configuration Files: /etc/firehol/firehol.conf changed [not included] -- no debconf information
Bug#942506: program does not recognise GPT table
Package: testdisk Version: 7.0-3+b4 Severity: normal Hello, I wanted to use testdisk on a disk, but it gives me this: -- cut Analyse Disk /dev/sda - 1801 GB / 1678 GiB - CHS 219051 255 63 hdr_size=92 hdr_lba_self=1 hdr_lba_alt=7814037167 (expected 3519069871) hdr_lba_start=34 hdr_lba_end=7814037134 hdr_lba_table=2 hdr_entries=128 hdr_entsz=128 Partition table type (auto): None -- cut In contrast, gdisk gives me this: -- cut Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged ... Recovery/transformation command (? for help): i Using 1 Partition GUID code: ---- (Linux filesystem) Partition unique GUID: ---- First sector: 2048 (at 1024.0 KiB) Last sector: 7814035455 (at 3.6 TiB) Partition size: 7814033408 sectors (3.6 TiB) Attribute flags: Partition name: 'correct-partition-name' -- cut So, there is a GPT table there, somewhere. It would be nice if testdisk would do a better job with disks having a GPT partition table. Cheers, Toni -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages testdisk depends on: ii libc62.28-10 ii libcom-err2 1.44.5-1+deb10u1 ii libext2fs2 1.44.5-1+deb10u1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libncursesw6 6.1+20181013-2+deb10u1 ii libntfs-3g8831:2017.3.23AR.3-3 ii libtinfo66.1+20181013-2+deb10u1 ii libuuid1 2.33.1-0.1 ii ntfs-3g 1:2017.3.23AR.3-3 ii zlib1g 1:1.2.11.dfsg-1 testdisk recommends no packages. testdisk suggests no packages. -- no debconf information
Bug#942505: homepage not set
Package: testdisk Version: 7.0-3+b4 Severity: wishlist Hi, it would be nice to have the homepage directly listed in debian/control. Thanks, Toni -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages testdisk depends on: ii libc62.28-10 ii libcom-err2 1.44.5-1+deb10u1 ii libext2fs2 1.44.5-1+deb10u1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libncursesw6 6.1+20181013-2+deb10u1 ii libntfs-3g8831:2017.3.23AR.3-3 ii libtinfo66.1+20181013-2+deb10u1 ii libuuid1 2.33.1-0.1 ii ntfs-3g 1:2017.3.23AR.3-3 ii zlib1g 1:1.2.11.dfsg-1 testdisk recommends no packages. testdisk suggests no packages. -- no debconf information
Bug#935640: running 'firehol restart' does not always reproduce ruleset
Package: firehol Version: 3.1.6+ds-8 Severity: normal Hi, I am fiddling with my firehol rules, but am encountering a very confusing behaviour. Initially, after system boot, the rules are created with 'iptables'. When I run 'firehol restart', 'firehol' shows that all chains are having only an "ACCEPT" policy and no rules, while all rules are now only visible using 'iptables-legacy', which did not show any rules earlier. This is very confusing, as the rules are also entirely not the same. In my opinion, firehol should only the 'iptables' command and not the 'iptables-legacy' command, if possible, but not change horses midway. Cheers, Toni -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firehol depends on: ii firehol-common 3.1.6+ds-8 ii lsb-base10.2019051400 Versions of packages firehol recommends: ii fireqos 3.1.6+ds-8 Versions of packages firehol suggests: pn firehol-doc pn firehol-tools pn ulogd2 -- Configuration Files: /etc/firehol/firehol.conf changed [not included] -- no debconf information
Bug#932922: repo links should be taken from latest upload, not old versions
Hi Boyuan, On Wed, Jul 24, 2019 at 03:31:33PM -0400, Boyuan Yang wrote: > While what you said is reasonable, where is the latest upload of > virtualenvwrapper? It seems that the package received no upload since 2014. good question. I had to hunt a little myself, and came up with this: https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/src/master/ On PyPI, they mention a package version of 4.8.4, which is also mentioned on the tracker page, but in Debian, the latest version is 4.3.1. Thanks for spotting this! Cheers, Toni
Bug#932923: command 'allvirtualenvs' not implemented
Package: virtualenvwrapper Version: 4.3.1-2 Severity: normal Hi, the documentation for virtualenvwrapper lists a command 'allvirtualenvs', but this command does not seem to be implemented. It would be very handy to actually have this command at hand. Cheers, Toni -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualenvwrapper depends on: ii libjs-sphinxdoc1.8.4-1 ii python 2.7.16-1 ii python-stevedore 1.29.0-2 ii python-virtualenv 15.1.0+ds-2 ii virtualenv 15.1.0+ds-2 ii virtualenv-clone 0.3.0-1.2 Versions of packages virtualenvwrapper recommends: ii bash-completion 1:2.8-6 virtualenvwrapper suggests no packages. -- no debconf information
Bug#932922: repo links should be taken from latest upload, not old versions
Package: tracker.debian.org Severity: minor Hi, while looking at the package 'virtualenvwrapper', I found that the links to the Git repo are wrong: They point to anonscm.debian.org, which is gone, but which is in the package source for the version in Buster. The latest upload for unstable has the correct link to Salsa, though. In my opinion, websites are less "versioned" than our packages, so it imho makes a lot of sense to always look at the repo location in the package with the highest version number, which should be the one in 'unstable' or 'experimental'. Cheers, Toni -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#930854: -n does not seem to work
Package: isc-dhcp-client
Version: 4.4.1-2
Severity: normal
Tags: upstream
Hi,
I am trying to dry-run the dhclient program to request a lease from the
server for debugging purposes. At the same time, I am already holding a
lease on the same interface, which is why I don't want to release the
existing lease, as I have no decent access to the remote machine.
According to the man page, I should be able to run dhclient with "-n" to
do just that, but:
# dhclient -d -v -n -w wlp59s0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
No interfaces command -n and requested interface wlp59s0
Usage: dhclient [-4|-6] [-SNTPRI1dvrxi] [-nw] [-p ] [-D LL|LLT]
[--dad-wait-time ] [--prefix-len-hint ]
[--decline-wait-time ]
[--address-prefix-len ]
[-s server-addr] [-cf config-file]
[-df duid-file] [-lf lease-file]
[-pf pid-file] [--no-pid] [-e VAR=val]
[-sf script-file] [interface]*
dhclient {--version|--help|-h}
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging.
exiting.
I originally stumbled over this bug on a different Linux distro, but
have no good way to report a problem there atm. But that way I am very
confident that this is an upstream problem.
Kind regards,
Toni
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500,
'stable'), (70, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags:
TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages isc-dhcp-client depends on:
ii debianutils4.8.6.1
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii libdns-export1104 1:9.11.5.P4+dfsg-5
ii libisc-export1100 1:9.11.5.P4+dfsg-5
Versions of packages isc-dhcp-client recommends:
ii isc-dhcp-common 4.4.1-2
Versions of packages isc-dhcp-client suggests:
ii avahi-autoipd 0.7-4+b1
pn isc-dhcp-client-ddns
pn resolvconf
-- no debconf information
Bug#930843: service does not start due to missing directory in /run
Package: openvswitch-switch Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12 Severity: normal Hi, first off, I am not sure about the severity, but not bringing up parts of my network is actually pretty damaging, although very easy to fix (mkdir /run/openvswitch is enough). If I want to start openvswitch-switch using systemd, the directory /run/openvswitch does not get created, which results in the daemon not starting. However, running the sysv init script directly creates the directory no problem, and the service and network comes up. I tried inserting a mkdir command as ExecStartPre, or also into the init script, but after running 'systemctl daemon-reload', the directory is still not being created. I would much prefer if the directory would just get created, and the service would come up. Here's a small piece from the journal: Jun 21 12:06:45 debian ovsdb-server[14307]: ovs|2|daemon_unix|EMER|/var/run/openvswitch/ovsdb-server.pid.tmp: create failed (No such file or directory) Jun 21 12:06:45 debian ovs-ctl[14286]: ovsdb-server: /var/run/openvswitch/ovsdb-server.pid.tmp: create failed (No such file or directory) Jun 21 12:06:45 debian ovs-ctl[14286]: Starting ovsdb-server ... failed! Jun 21 12:06:45 debian systemd[1]: openvswitch-nonetwork.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited Here's what iwatch has to say while I run this command: # systemctl restart openvswitch-switch A dependency job for openvswitch-switch.service failed. See 'journalctl -xe' for details. in a different terminal: # iwatch -e all_events /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_OPEN /run/systemd [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run [21/Jun/2019 12:43:46] IN_ISDIR,IN_CLOSE_NOWRITE /run/systemd ^C <--- at this point, the systemctl command has already terminated. Cheers, Toni -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvswitch-switch depends on: ii kmod26-1 ii lsb-base10.2019051400 ii netbase 5.6 ii openvswitch-common 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12 ii procps 2:3.3.15-2 ii python 2.7.16-1 ii uuid-runtime2.33.1-0.1 openvswitch-switch recommends no packages. openvswitch-switch suggests no packages. -- no debconf information
Bug#930629: can't recognize arbitrary text files (eg. Markdown or reStructuredText)
Package: sloccount
Version: 2.26-5.2
Severity: wishlist
Tags: upstream
Hi,
it would be great if the program would be able to handle arbitrary text
files and allow parser specification for them. I am specifically
interested in having support for the usual documentation stuff like
Markdown (".md") and reStructuredText (".rst"), but would also
appreciate if things like SASS (".sass") would be handled.
Kind regards,
Toni
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (70, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sloccount depends on:
ii libc6 2.28-10
ii perl 5.28.1-6
sloccount recommends no packages.
Versions of packages sloccount suggests:
pn doc-base
-- no debconf information
Bug#928894: [pkg-gnupg-maint] Bug#928894: custom keyring is not honoured
Hi Daniel,
On Sun, May 12, 2019 at 06:52:17PM -0400, Daniel Kahn Gillmor wrote:
> I'm not sure that this demonstrates what you're describing.
>
> Here is a run with gpg 2.2.15-1 that demonstrates the key being fetched
> into the extra keyring:
>
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$ export GNUPGHOME=$(pwd)
I did not do this. This variable is unset in my environment.
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$ touch $(pwd)/extra.gpg
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$ gpg --no-default-keyring --keyring
> $(pwd)/extra.gpg --recv-keys CC64B1DB67ABBEECAB24B6455FC346329753F4B0
> gpg: key 2D9AE806EC1592E2: 6 signatures not checked due to missing keys
> gpg: /tmp/cdtemp.AhkyjS/trustdb.gpg: trustdb created
> gpg: key 2D9AE806EC1592E2: public key "Teabot " imported
> gpg: no ultimately trusted keys found
> gpg: Total number processed: 1
> gpg: imported: 1
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$ gpg --list-options show-keyring -k
> tea...@gitea.io
> gpg: keybox '/tmp/cdtemp.AhkyjS/pubring.kbx' created
> gpg: error reading key: No public key
> 2 dkg@alice:/tmp/cdtemp.AhkyjS$ ls -la
> total 24
> drwx-- 4 dkg dkg 160 May 12 18:48 .
> drwxrwxrwt 28 root root 1420 May 12 18:47 ..
> drwx-- 2 dkg dkg60 May 12 18:48 crls.d
> -rw-r--r-- 1 dkg dkg 6467 May 12 18:48 extra.gpg
> -rw-r--r-- 1 dkg dkg 6467 May 12 18:48 extra.gpg~
> drwx-- 2 dkg dkg40 May 12 18:48 private-keys-v1.d
> -rw--- 1 dkg dkg32 May 12 18:48 pubring.kbx
> -rw--- 1 dkg dkg 1200 May 12 18:48 trustdb.gpg
> 0 dkg@alice:/tmp/cdtemp.AhkyjS$
Your experiment only shows that the key did *not* end
up in /tmp/cdtemp.AhkyjS/pubring.kbx. Otherwise, the "gpg -k" above
should have listed it, instead of saying "No public key".
> perhaps the teabot key was already in your default keyring before you
> run the --recv-keys operation? that would certainly explain the
> behavior that you're seeing.
No, it does not. If a key is already there, it would not say
"imported: 1". And since it said "imported: 1" for you, I challenge you
to find the location of that key, because it is obviously not in your
temporary keyring.
For what it's worth, here's another run, setting GNUPGHOME:
$ touch ~/mnt/tools/gitea-keys.gpg
$ GNUPGHOME=`/bin/pwd`
$ echo ${GNUPGHOME}
/home/toni/mnt/tools
$ gpg --list-options show-keyring -k tea...@gitea.io
gpg: please do a --check-trustdb
gpg: error reading key: No public key
$ gpg --keyring ~/mnt/tools/gitea-keys.gpg --list-options show-keyring -k
tea...@gitea.io
gpg: please do a --check-trustdb
gpg: error reading key: No public key
$ gpg --keyring ~/mnt/tools/gitea-keys.gpg --no-default-keyring --recv-keys
CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: key 0x2D9AE806EC1592E2: 6 signatures not checked due to missing keys
gpg: key 0x2D9AE806EC1592E2: public key "Teabot " imported
gpg: Total number processed: 1
gpg: imported: 1
$ gpg --keyring ~/mnt/tools/gitea-keys.gpg --no-default-keyring --recv-keys
CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: key 0x2D9AE806EC1592E2: 6 signatures not checked due to missing keys
gpg: key 0x2D9AE806EC1592E2: "Teabot " not changed
gpg: Total number processed: 1
gpg: unchanged: 1
$ gpg --keyring ~/mnt/tools/gitea-keys.gpg --list-options show-keyring -k
tea...@gitea.io
gpg: please do a --check-trustdb
Keyring: /home/toni/.gnupg/pubring.gpg
--
pub rsa4096/0x2D9AE806EC1592E2 2018-06-24 [SC] [expires: 2020-06-23]
7C9E68152594688862D62AF62D9AE806EC1592E2
uid [ unknown] Teabot
sub rsa4096/0x1FBE01D7CBADB9A0 2018-06-24 [E] [expires: 2020-06-23]
sub rsa4096/0x5FC346329753F4B0 2018-06-24 [S] [expires: 2019-06-24]
$ l `/bin/pwd`/gitea-keys.gpg
-rw-r- 1 toni toni 0 May 13 00:55 /home/toni/mnt/tools/gitea-keys.gpg
$
Enjoy,
Toni
Bug#928894: custom keyring is not honoured
Package: gpg Version: 2.2.12-1 Severity: normal Hi, --recv-keys does not seem to honour the keyring options, so the received key ends up in the wrong keyring: $ touch ~/mnt/tools/gitea-keys.gpg $ gpg --no-default-keyring --keyring ~/mnt/tools/gitea-keys.gpg --recv-keys CC64B1DB67ABBEECAB24B6455FC346329753F4B0 gpg: key 0x2D9AE806EC1592E2: 6 signatures not checked due to missing keys gpg: key 0x2D9AE806EC1592E2: public key "Teabot " imported gpg: Total number processed: 1 gpg: imported: 1 $ gpg --list-options show-keyring -k tea...@gitea.io gpg: please do a --check-trustdb Keyring: /home/toni/.gnupg/pubring.gpg -- pub rsa4096/0x2D9AE806EC1592E2 2018-06-24 [SC] [expires: 2020-06-23] 7C9E68152594688862D62AF62D9AE806EC1592E2 uid [ unknown] Teabot sub rsa4096/0x1FBE01D7CBADB9A0 2018-06-24 [E] [expires: 2020-06-23] sub rsa4096/0x5FC346329753F4B0 2018-06-24 [S] [expires: 2019-06-24] $ Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gpg depends on: ii gpgconf2.2.12-1 ii libassuan0 2.5.2-1 ii libbz2-1.0 1.0.6-9 ii libc6 2.28-10 ii libgcrypt201.8.4-5 ii libgpg-error0 1.35-1 ii libreadline7 7.0-5 ii libsqlite3-0 3.27.2-2 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gpg recommends: ii gnupg 2.2.12-1 gpg suggests no packages. -- no debconf information
Bug#926859: X Server Does Not Start
Package: xserver-xorg Version: 1:7.7+19 Severity: grave Hi, I am not sure whether this is the correct package to report the bug against, since several drivers are involved, and X stopped working for every setup simultanously. On my laptop with an Optimus graphics, X does no longer start after recent upgrades from two days ago until now. The symptom is that the X server briefly starts to draw the desktop, but then immediatly exits "successfully". I have no custom X configuration. The error messages vary, depending on whether I am loading the nouveau driver or not. With the intel driver, I get: xf86EnableIOPorts: failed to setIOPL for I/O (Operation not permitted) With the nouveau driver, I get: Error allocating PGRAPH context for M2MF Running Ubuntu Desktop 18.04.2 from a stick works, and I can work with the Gnome desktop, so I know that it is not a hardware problem. Cheers, Toni -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) Xorg X server log files on system: -- -rw-r--r-- 1 root root 6714 Feb 26 11:51 /var/log/Xorg.0.log -rw-r--r-- 1 toni toni 57580 Apr 10 20:30 /home/toni/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/toni/.local/share/xorg/Xorg.0.log): - [58.210] X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 [58.210] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian [58.211] Current Operating System: Linux laptop-t 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 [58.211] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/ev0-root ro quiet [58.211] Build Date: 25 October 2018 06:15:23PM [58.212] xorg-server 2:1.20.3-1 (https://www.debian.org/support) [58.212] Current version of pixman: 0.36.0 [58.212]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [58.212] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [58.252] (==) Log file: "/home/toni/.local/share/xorg/Xorg.0.log", Time: Wed Apr 10 20:30:45 2019 [58.258] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [58.258] (==) No Layout section. Using the first Screen section. [58.258] (==) No screen section available. Using defaults. [58.258] (**) |-->Screen "Default Screen Section" (0) [58.258] (**) | |-->Monitor "" [58.259] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [58.259] (==) Automatically adding devices [58.259] (==) Automatically enabling devices [58.259] (==) Automatically adding GPU devices [58.259] (==) Max clients allowed: 256, resource mask: 0x1f [58.261] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [58.261]Entry deleted from font path. [58.261] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [58.261]Entry deleted from font path. [58.261] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [58.261]Entry deleted from font path. [58.262] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [58.262]Entry deleted from font path. [58.262] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [58.262]Entry deleted from font path. [58.262] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [58.262] (==) ModulePath set to "/usr/lib/xorg/modules" [58.262] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [58.262] (II) Loader magic: 0x564e0d7c5e20 [58.262] (II) Module ABI versions: [58.262]X.Org ANSI C Emulation: 0.4 [58.262]X.Org Video Driver: 24.0 [58.262]X.Org XInput driver : 24.1 [58.262]X.Org Server Extension : 10.0 [58.263] (++) using VT number 1 [58.264] (II) systemd-logind: took control of session /org
Bug#924669: homepage throws 404
Source: mysqmail Severity: minor Tags: upstream Hi Thomas, the homepage listed in the package is not correct. If you take a look, it will result in a 404. It would be great if you could fix that. Kind regards, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#923318: long-running ping pegs cpu at 100%
Package: iputils-ping Version: 3:20180629-2 Severity: normal Tags: upstream Hi, on my laptop, I usually run ping against a target to see how the connecction quality is, but after a suspend/resume cycle, if the network does not come up (frequently), ping consumes 100% of one core, making the nachine quite hot. This may be related to https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1697646 It would be nice if ping would detect the absence of the network and then wait for a while until the network comes up again. Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iputils-ping depends on: ii libc6 2.28-7 ii libcap2 1:2.25-2 ii libidn2-0 2.0.5-1 ii libnettle6 3.4.1-1 Versions of packages iputils-ping recommends: ii libcap2-bin 1:2.25-2 iputils-ping suggests no packages. -- no debconf information
Bug#923082: can't disable systemd-resolved
Hi Martin,
On Sun, Feb 24, 2019 at 08:03:38AM +0100, Martin Pitt wrote:
> Toni [2019-02-23 23:05 +]:
> > I can't disable systemd-resolved, which prevents me from running my own
> > DNS setup:
>
> systemd-resolved.service is not enabled by default in Debian. If you enabled
> it, what prevents you from disabling it again? (systemctl disable
> systemd-resolved).
I really can't remember having enabled it - and I also don't know why I
would have done it, having my own setup in several of the areas that
systemd is encroaching on. But what prevents me from disabling systemd,
is quite simple: It just does not work:
# systemctl stop systemd-resolved
# lsof -i udp@0.0.0.0:53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 113u IPv4 10583 0t0 UDP localhost:domain
That's why I filed a bug report - it really should be possible to
disable this service.
> resolved doesn't run in pid 1 (that would be a really bad architecture!). This
> just means that pid 1 connected to localhost's name server to resolve a name
> (i. e. a DNS client). A better command to find out which processes are
> *listening* on UDP ports is "ss -ulpen", or for port 53 specifically,
> "ss -ulpen 'sport = 53'".
# ss -ulpen 'sport = 53'
State Recv-QSend-Q Local Address:Port
Peer Address:Port
UNCONN0 0192.168.122.1:53
0.0.0.0:*users:(("dnsmasq",pid=13861,fd=5)) ino:5159825
sk:a1 <->
UNCONN0 0127.0.0.1:53
0.0.0.0:*users:(("systemd",pid=1,fd=113)) ino:10583 sk:a2
<->
UNCONN0 0[::1]:53
[::]:*users:(("systemd",pid=1,fd=111)) ino:362 sk:a3
v6only:1 <->
This I took after trying to stop systemd-resolved.
Other things I tried:
* setting DNSStubListener=no in /etc/systemd/resovled.conf, followed by
* systemctl daemon-reload, followed by
* systemctl daemon-reexec
But it was all for naught.
Kind regards,
Toni
Bug#923081: privacy invasion due to automatic fallback to Cloudflare
Package: systemd Version: 240-6 Severity: important Tags: upstream Hi, I was looking into upstream's changes for the release in unstable to decide, whether or not I should report the problem with stopping systemd-resolved, and found this: --- resolved: use Cloudflare public DNS server as a default fallback alon… …gside Google one Cloudflare public DNS service is currently the fastest one according to https://www.dnsperf.com/#!dns-resolvers. Why not improve the experience for systemd users using this as a default fallback nameserver? --- (Commit #def3c7c) That falls imho under unpleasant surprises. We pretend to be conscious of privacy etc, then underhandedly hand our DNS queries to Google and Cloudflare if something goes wrong (misconfigured router? broken other DNS server?), instead of having the query fail and let the user take a decision. Cheers, Toni -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.13.2-7 ii libaudit11:2.8.4-2 ii libblkid12.33.1-0.1 ii libc62.28-7 ii libcap2 1:2.25-2 ii libcryptsetup12 2:2.1.0-1 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.6-2 ii libgpg-error01.35-1 ii libidn11 1.33-2.2 ii libip4tc01.8.2-3 ii libkmod2 26-1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libmount12.33.1-0.1 ii libpam0g 1.1.8-4 ii libseccomp2 2.3.3-4 ii libselinux1 2.8-1+b1 ii libsystemd0 240-6 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus1.12.12-1 ii libpam-systemd 240-6 Versions of packages systemd suggests: ii policykit-10.105-25 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.133 ii udev 240-6 -- Configuration Files: /etc/systemd/resolved.conf changed [not included] -- no debconf information
Bug#921387: UI on HIDPI too small
On Sat, Feb 09, 2019 at 04:37:17PM +0100, Rene Engelhard wrote: > And then there's the GNOME/Gtk3/Qt/... settings. If these accessibility features would be tunable by environment variables which were interpreted by libraries or config files, that would be perfectly fine by me. If I could just install some libraries or such a settings program and then set those values in a way that I would have them in awesome, but without Gome and friends, that would also be perfectly acceptable. > You have choosen awesome. And for a good reason. For about everything else in those "desktop environments" does not work for me and my workflows. I've lost my desktop environments more often than I can remember, due to profile corruption on every computer and every version I tried, to the point that I could not even run Firefox on a pretty vanilla Gnome in Stretch, where I once arrived in a situation where deleting all dot files and directories under ~user/ did not make it work again. However, shutting down Gnome and starting awesome fixed the problem immediately. This accessibility issue does not outweigh the plethora of problems I experience with "desktop enviromnents" within weeks or days after trying to use them, and should imho be solved in a generic way that's open to every GUI user. Cheers, Toni
Bug#921387: UI on HIDPI too small
Hi Rene, On Sat, Feb 09, 2019 at 11:03:21AM +0100, Rene Engelhard wrote: > Neither do I, but do you really attempt to use 3840x2160 and are suprised > this is small on > a 15"? I don't "really attempt", it just automatically configured itself this way. And I actually welcome the smoother characters. Yes, I am "surprised" this is small, because that's imho the only reason why software would claim abilities to work on HIDPI displays - that it can automatically detect and adapt to different DPI figures to give a similar experience everywhere. That's also the only reason why we measure font sizes in points instead of pixels. Not honouring the screen resolution would imho make a claim to HIDPI compatibility invalid. The only thing I can really see failing here, is that the output of xrandr shows 96x96 dpi, which is patently untrue. If I knew where to look, I would want to fix that (xorg driver? xorg base? elsewhere?). If there was a way to adjust the UI font sizes, that could be a useful band aid, but I largely unaware of such a thing. Cheers, Toni
Bug#921387: UI on HIDPI too small
Hi Rene, On Fri, Feb 08, 2019 at 07:41:58PM +0100, Rene Engelhard wrote: > screen #0: > dimensions:1920x1080 pixels (290x170 millimeters) > resolution:168x161 dots per inch > depths (7):24, 1, 4, 8, 15, 16, 32 > root window id:0x39c > depth of root window:24 planes > number of colormaps:minimum 1, maximum 1 > default colormap:0x23 > default number of colormap cells:256 > preallocated pixels:black 0, white 16777215 > options:backing-store WHEN MAPPED, save-unders NO > largest cursor:1920x1080 $ xrandr --verbose Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192 eDP-1 connected primary 3840x2160+0+0 (0x67) normal (normal left inverted right x axis y axis) 344mm x 194mm Identifier: 0x62 Timestamp: 90357 Subpixel: unknown Gamma: 1.0:1.3:1.7 Brightness: 0.55 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004d108d14 051c0104a52213780ead27a95335bc25 0c51540001010101010101010101 0101010101014dd000a0f0703e803020 350058c21018 00fe0046 4e564452804c513135364431 000241032801120b010a202000b6 scaling mode: Full aspect supported: Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 link-status: Good supported: Good, Bad CONNECTOR_ID: 71 supported: 71 non-desktop: 0 range: (0, 1) (I don't understand everything in there...) > Does export SAL_USE_VCLPLUGIN=gtk3 (install libreoffice-gtk3...) change it? > That would > use the "gtk3" plugin. (As done automatically when LO detects it runs under > GNOME) Yes, texts are now a little larger - but in the UI not very much. Cheers, Toni
Bug#921387: UI on HIDPI too small
Hi Rene, On Wed, Feb 06, 2019 at 08:12:48PM +0100, Rene Engelhard wrote: > On Mon, Feb 04, 2019 at 10:37:38PM +0000, Toni wrote: > > on my HIDPI display, most UI elements, and especially the file dialogue, > > are too small. I tried setting environment variables, as suggested in > > the Arch wiki, but to no avail (I tried both GTK3 and QT settings). > > This is pretty subjective, isn't it? yes, but if things turn out to be maybe 6pt on a "normal" screen, as a rough estimate, I think it is safe to say that this is too small. That'd be too small for latin characters only, but I also have a significant number of more complex chacaters (mostly Chinese), which are absolutely unreadable at that size. > At leat in my GNOME here on my new laptop this is quite small on > 1920x1080 but not unbearable even with my eyes.. I have a 15" laptop and 294 dpi. But I noticed something else, that the resolution is set to 96x96, according to the X11 log file. Maybe there's a bug in the graphics driver, not in the application. > Your scenario is something no-GTk3 and no KDE integration? Maybe. I use plain awesome, which I start with "startx" from a text console. Kind regards, Toni
Bug#921387: UI on HIDPI too small
Package: libreoffice Version: 1:6.1.5~rc1-2 Severity: normal Tags: a11y Hi, on my HIDPI display, most UI elements, and especially the file dialogue, are too small. I tried setting environment variables, as suggested in the Arch wiki, but to no avail (I tried both GTK3 and QT settings). The effect of this problem is that texts and tooltips are so small that it is very difficult for me to read the filenames, dialogues or tooltips. Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-avmedia-backend-gstreamer 1:6.1.5~rc1-2 ii libreoffice-base 1:6.1.5~rc1-2 ii libreoffice-calc 1:6.1.5~rc1-2 ii libreoffice-core 1:6.1.5~rc1-2 ii libreoffice-draw 1:6.1.5~rc1-2 ii libreoffice-impress1:6.1.5~rc1-2 ii libreoffice-math 1:6.1.5~rc1-2 ii libreoffice-report-builder-bin 1:6.1.5~rc1-2 ii libreoffice-writer 1:6.1.5~rc1-2 ii python3-uno1:6.1.5~rc1-2 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu2.37-1 ii fonts-liberation1:1.07.4-9 ii fonts-liberation2 2.00.4-1 ii fonts-linuxlibertine5.3.0-4 ii fonts-noto-hinted 20181227-1 ii fonts-noto-mono 20181227-1 ii fonts-sil-gentium-basic 1.102-1 ii libreoffice-java-common 1:6.1.5~rc1-2 ii libreoffice-librelogo 1:6.1.5~rc1-2 ii libreoffice-nlpsolver 0.9+LibO6.1.5~rc1-2 ii libreoffice-report-builder 1:6.1.5~rc1-2 ii libreoffice-script-provider-bsh 1:6.1.5~rc1-2 ii libreoffice-script-provider-js 1:6.1.5~rc1-2 ii libreoffice-script-provider-python 1:6.1.5~rc1-2 ii libreoffice-sdbc-postgresql 1:6.1.5~rc1-2 ii libreoffice-wiki-publisher 1.2.0+LibO6.1.5~rc1-2 Versions of packages libreoffice suggests: ii cups-bsd2.2.10-3 ii default-jre [java6-runtime] 2:1.11-71 ii firefox 64.0-1 ii ghostscript 9.26a~dfsg-2 ii gnupg 2.2.12-1 pn gpa ii gstreamer1.0-libav 1.15.0.1+git20180723+db823502-2 ii gstreamer1.0-plugins-bad1.14.4-1+b1 ii gstreamer1.0-plugins-base 1.14.4-1 ii gstreamer1.0-plugins-good 1.14.4-1 ii gstreamer1.0-plugins-ugly 1.14.4-1 ii hunspell-en-us [hunspell-dictionary]1:2018.04.16-1 ii hyphen-pt-pt [hyphen-hyphenation-patterns] 1:6.2.0~rc2-1 ii imagemagick 8:6.9.10.23+dfsg-2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2 ii libgl1 1.1.0-1 pn libreoffice-gnome | libreoffice-kde5 pn libreoffice-grammarcheck pn libreoffice-help pn libreoffice-l10n pn libreoffice-officebean ii libsane 1.0.27-3.1 ii libxrender1 1:0.9.10-1 pn myspell-dictionary pn mythes-thesaurus pn openclipart2-libreoffice | openclipart-lib ii openjdk-11-jre [java6-runtime] 11.0.2+9-3 ii openjdk-8-jre [java6-runtime] 8u181-b13-2~deb9u1 ii pstoedit3.73-1+b1 pn unixodbc Versions of packages libreoffice-core depends on: ii fontconfig2.13.1-2 ii fonts-opensymbol 2:102.10+LibO6.1.5~rc1-2 ii libboost-date-time1.67.0 1.67.0-12 ii libboost-locale1.67.0 1.67.0-12 ii libc6 2.28-5 ii libcairo2 1.16.0-2 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups2 2.2.10-3 ii libcurl3-gnutls 7.63.0-1 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-2 0.110-4 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.6-1 ii libexttextcat-2.0-0 3.4.5-1 ii
Bug#920547: Crashes every few hours
Hi Ben, On Mon, Jan 28, 2019 at 12:42:37AM +, Ben Hutchings wrote: > On Sat, 26 Jan 2019 20:03:49 +0000 Toni wrote: > > Package: src:linux > > Version: 4.19.16-1 > > Severity: critical > > File: linux-image-4.19.0-2-amd64 > > Is this a new problem with version 4.19.16-1? Or did it happen with > earlier versions as well? it happened with the 4.18.* kernel as well. The machine came with Ubuntu and 4.13 preinstalled, but I wiped it as soon as I could and installed Debian. So I don't know if it would have worked with Ubuntu - the entire setup was not suitable for my purposes, but I thought that 4.9 might be too old for this hardware. However, the machine came with a 1.3 BIOS, which I updated to 1.6 and then to 1.7. I think, I had 4.18 together with 1.6 running, but closed the corresponding bug report when I noticed that both a newer kernel and a newer BIOS were available. Well, the situation compared has improved a little, compared to that, but it is still very bad. > When you say "data loss", are you talking about data in memory or > corruption of files that were saved and sync'd to disk? I mean, files on disk were destroyed. I noticed some because I use etckeeper with git, and suddenly, I could no longer see my update history because files in /etc/.git were corrupt to the point that no "git fsck" or "git gc" could resurrect the tree. > On x86 laptops thermal management is (by default) done by the system > firmware (BIOS and management engine code). If you didn't override > that, and yet the CPU overheats, this is the manufacturer's fault. Ok... In the BIOS, I set the corresponding parameter from "performance" to "normal", which I hoped would be a more conservative setting, to prevent exactly this problem. Cheers, Toni
Bug#920637: dialogues illegibly small on HIDPI display
Package: imagemagick Version: 8:6.9.10.23+dfsg-2 Severity: normal Tags: a11y Hi, on my 294dpi display, the dialogues are so small that I can't read them. Maybe some Xresources config can alleviate this problem, but the software does not automatically detect and set useful values. Cheers, Toni -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org convert: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org composite: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org conjure: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org display: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org identify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org import: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org mogrify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org montage: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org stream: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick depends on: ii imagemagick-6.q16 8:6.9.10.23+dfsg-2 imagemagick recommends no packages. imagemagick suggests no packages. -- no debconf information
Bug#920636: dialogues illegible on HIDPI display
Package: imagemagick Version: 8:6.9.10.23+dfsg-2 Severity: normal -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org convert: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org composite: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org conjure: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org display: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org identify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org import: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org mogrify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org montage: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org stream: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick depends on: ii imagemagick-6.q16 8:6.9.10.23+dfsg-2 imagemagick recommends no packages. imagemagick suggests no packages. -- no debconf information
Bug#920635: display does not honour -geometry
Package: imagemagick Version: 8:6.9.10.23+dfsg-2 Severity: normal Hi, I like to start display on certain images with a -geometry, but display seems to ignore or misinterpret the geometry. The attached image has 400x400 pixels, but whichever -geometry I specify, display always displays the image at the same size. Also, the position is not honoured properly. With -0-0 for the position, the image ends up in the lower right corner, but with all other positions, the image ends up more or less randomly somewhere on the screen. I reproduced the problem with two different window managers, fvwm and awesome (my main window manager). My monitor has 294 dpi. It would be great if this could be fixed. Cheers, Toni -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org convert: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org composite: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org conjure: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org display: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org identify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org import: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org mogrify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org montage: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org stream: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick depends on: ii imagemagick-6.q16 8:6.9.10.23+dfsg-2 imagemagick recommends no packages. imagemagick suggests no packages. -- no debconf information
Bug#920634: dialogues and general UI unreadably small on HIDPI display
Package: gimp Version: 2.10.8-2 Severity: normal Hi, on my 15" laptop with 294 dpi, the UI of gimp has icons and dialogues (eg. brushes or layers) so small that I can hardly read it. Using these dialogues with the mouse is also almost impossible. Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.8-2 ii libaa1 1.4p5-45 ii libbabl-0.1-00.1.60-2 ii libbz2-1.0 1.0.6-9 ii libc62.28-5 ii libcairo21.16.0-2 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.2.0-14 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libgegl-0.4-00.4.12-2 ii libgexiv2-2 0.10.9-1 ii libgimp2.0 2.10.8-2 ii libglib2.0-0 2.58.2-3 ii libgs9 9.26a~dfsg-2 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b2.3.0-1 ii libheif1 1.3.2-1+b1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3 ii liblzma5 5.2.2-1.3 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2 ii libopenexr23 2.2.1-4 ii libopenjp2-7 2.3.0-1.1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-01.42.4-6 ii libpng16-16 1.6.36-2 ii libpoppler-glib8 0.71.0-2 ii librsvg2-2 2.44.10-1 ii libstdc++6 8.2.0-14 ii libtiff5 4.0.10-3 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-14 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.1.15-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.26a~dfsg-2 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python pn gvfs-backends ii libasound21.1.7-2 -- no debconf information
Bug#920301: indicator bar too small on HIDPI display
Package: fcitx Version: 1:4.2.9.6-5 Severity: normal Tags: upstream Hi, on my 15" laptop with 294 dpi, the indicator bar which shows the currently active input method and details (full-width characters etc.) is so small that I can not really read things. It's also hard to click on, for the same reason. Please see the attached screenshot, which represents about 2-3mm in height. Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fcitx depends on: ii fcitx-bin 1:4.2.9.6-5 ii fcitx-data 1:4.2.9.6-5 ii fcitx-modules 1:4.2.9.6-5 Versions of packages fcitx recommends: ii fcitx-config-gtk0.4.10-2 ii fcitx-frontend-all 1:4.2.9.6-5 ii fcitx-ui-classic1:4.2.9.6-5 ii fcitx-ui-light 0.1.3-3 ii im-config 0.38-1 Versions of packages fcitx suggests: pn fcitx-m17n pn fcitx-tools -- no debconf information
Bug#920300: no way to "close" without exiting the program
Package: screengrab Version: 1.99-1 Severity: normal Hello, I just started to use 'screengrab', but the program has a very strong tendency to quit. At least, there is no, or no obvious way to "close" the program in a way that it does not occypy space in the taskbar, and just stays in the systray, despite the documentation suggesting that the program might just sit in the systray and only pop up when needed. Steps to reproduce: 1. Start 'screengrab --minimized' (I'm running it from my .xsessionrc). 2. Take a screenshot. 3. Try to close/minimize the window. In this case, it takes up a slot in my taskbar and has a systray icon, whereas it shoud only have a systray icon. I am using awesome 4.2 without Gnome or other such stuff. Cheers, Toni -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages screengrab depends on: ii libc62.28-5 ii libgcc1 1:8.2.0-14 ii libkf5windowsystem5 5.51.0-1 ii libqt5core5a 5.11.3+dfsg-2 ii libqt5dbus5 5.11.3+dfsg-2 ii libqt5gui5 5.11.3+dfsg-2 ii libqt5network5 5.11.3+dfsg-2 ii libqt5widgets5 5.11.3+dfsg-2 ii libqt5x11extras5 5.11.3-2 ii libqt5xdg3 3.2.0-2+b3 ii libstdc++6 8.2.0-14 ii libx11-xcb1 2:1.6.7-1 ii libxcb-xfixes0 1.13.1-2 screengrab recommends no packages. screengrab suggests no packages. -- no debconf information
Bug#919919: frequent lockups requiring power off
le+0x2a2/0x870 Jan 13 11:15:37 laptop-t kernel: [123816.027098] ? __prepare_to_swait+0x4b/0x70 Jan 13 11:15:37 laptop-t kernel: [123816.027102] schedule+0x28/0x80 Jan 13 11:15:37 laptop-t kernel: [123816.027105] suspend_devices_and_enter+0x54c/0x7e0 Jan 13 11:15:37 laptop-t kernel: [123816.027110] pm_suspend.cold.7+0x33c/0x392 Jan 13 11:15:37 laptop-t kernel: [123816.027113] state_store+0x80/0xe0 Jan 13 11:15:37 laptop-t kernel: [123816.027119] kernfs_fop_write+0x116/0x190 Jan 13 11:15:37 laptop-t kernel: [123816.027125] vfs_write+0xa5/0x1a0 Jan 13 11:15:37 laptop-t kernel: [123816.027130] ksys_write+0x4f/0xb0 Jan 13 11:15:37 laptop-t kernel: [123816.027136] do_syscall_64+0x53/0x100 Jan 13 11:15:37 laptop-t kernel: [123816.027141] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 13 11:15:37 laptop-t kernel: [123816.027145] RIP: 0033:0x7f583631f874 Jan 13 11:15:37 laptop-t kernel: [123816.027153] Code: Bad RIP value. Jan 13 11:15:37 laptop-t kernel: [123816.027155] RSP: 002b:7fffd2408278 EFLAGS: 0246 ORIG_RAX: 0001 Jan 13 11:15:37 laptop-t kernel: [123816.027159] RAX: ffda RBX: 0004 RCX: 7f583631f874 Jan 13 11:15:37 laptop-t kernel: [123816.027161] RDX: 0004 RSI: 7fffd2408360 RDI: 0004 Jan 13 11:15:37 laptop-t kernel: [123816.027162] RBP: 7fffd2408360 R08: 7f583475fdc0 R09: 5598757f8e90 Jan 13 11:15:37 laptop-t kernel: [123816.027164] R10: R11: 0246 R12: 5598757f7290 Jan 13 11:15:37 laptop-t kernel: [123816.027166] R13: 0004 R14: 7f58363ec760 R15: 0004 Jan 13 11:15:37 laptop-t kernel: [129904.219068] INFO: task dmcrypt_write:315 blocked for more than 120 seconds. Jan 13 11:15:37 laptop-t kernel: [129904.219072] Tainted: G L 4.19.0-1-amd64 #1 Debian 4.19.12-1 Jan 13 11:15:37 laptop-t kernel: [129904.219073] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 13 11:15:37 laptop-t kernel: [129904.219075] dmcrypt_write D0 315 2 0x8000 Jan 13 11:15:37 laptop-t kernel: [129904.219080] Call Trace: Jan 13 11:15:37 laptop-t kernel: [129904.219092] ? __schedule+0x2a2/0x870 Jan 13 11:15:37 laptop-t kernel: [129904.219097] ? __switch_to_asm+0x34/0x70 Jan 13 11:15:37 laptop-t kernel: [129904.219106] ? crypt_alloc_tfms+0x100/0x100 [dm_crypt] Jan 13 11:15:37 laptop-t kernel: [129904.219110] schedule+0x28/0x80 Jan 13 11:15:37 laptop-t kernel: [129904.219115] blk_queue_enter+0x138/0x1c0 Jan 13 11:15:37 laptop-t kernel: [129904.219119] ? finish_wait+0x80/0x80 Jan 13 11:15:37 laptop-t kernel: [129904.219124] generic_make_request+0xf0/0x410 Jan 13 11:15:37 laptop-t kernel: [129904.219129] dmcrypt_write+0x145/0x170 [dm_crypt] Jan 13 11:15:37 laptop-t kernel: [129904.219134] kthread+0x112/0x130 Jan 13 11:15:37 laptop-t kernel: [129904.219138] ? kthread_bind+0x30/0x30 Jan 13 11:15:37 laptop-t kernel: [129904.219142] ret_from_fork+0x35/0x40 Jan 13 11:15:37 laptop-t kernel: [142782.968669] OOM killer enabled. Jan 13 11:15:37 laptop-t kernel: [142782.968670] Restarting tasks ... done. Jan 13 11:15:38 laptop-t kernel: [142783.062223] ata3: SATA link down (SStatus 4 SControl 300) Jan 13 11:15:38 laptop-t kernel: [142783.135840] PM: suspend exit When the system hangs, I cannot shut it down, but have to hold down the power button for extended periods of time to stop the system. Cheers, Toni -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/ev0-root ro quiet ** Not tainted ** Kernel log: [ 994.921350] CPU2: Core temperature above threshold, cpu clock throttled (total events = 159) [ 994.921351] CPU8: Core temperature above threshold, cpu clock throttled (total events = 159) [ 994.921381] CPU8: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921384] CPU2: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921385] CPU6: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921385] CPU7: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921386] CPU0: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921387] CPU9: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921388] CPU3: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921388] CPU1: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921390] CPU5: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921391] CPU11: Package temperature above threshold, cpu clock throttled (total events = 191) [ 994.921392] C
Bug#919920: clock far in the future after suspend/resume
Package: src:linux Version: 4.19.12-1 Severity: important Tags: upstream Hi, usually, after resuming from suspend, the clock on my machine is way ahead, causing all sorts of havoc. Especially when being offline, there is also no good way to correct this issue. Cheers, Toni -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/ev0-root ro quiet ** Not tainted ** Kernel log: [ 49.398869] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 [ 49.398870] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 49.398870] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 49.458102] input: HDA Intel PCH Headphone Mic as /devices/pci:00/:00:1f.3/sound/card0/input28 [ 49.458166] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input29 [ 49.458224] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input30 [ 49.458271] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input31 [ 49.458324] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input32 [ 49.458375] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input33 [ 49.934113] Bluetooth: hci0: Waiting for firmware download to complete [ 49.934183] Bluetooth: hci0: Firmware loaded in 1552005 usecs [ 49.934227] Bluetooth: hci0: Waiting for device to boot [ 49.947398] Bluetooth: hci0: Device booted in 12885 usecs [ 49.947444] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.ddc [ 49.947446] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc [ 49.952704] Bluetooth: hci0: Applying Intel DDC parameters completed [ 50.417916] Console: switching to colour frame buffer device 480x135 [ 50.449962] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 57.269823] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready [ 57.966244] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready [ 66.863361] wlp59s0: authenticate with c0:3e:0f:ac:54:8d [ 66.880393] wlp59s0: send auth to c0:3e:0f:ac:54:8d (try 1/3) [ 66.919492] wlp59s0: authenticated [ 66.923155] wlp59s0: associate with c0:3e:0f:ac:54:8d (try 1/3) [ 66.927698] wlp59s0: RX AssocResp from c0:3e:0f:ac:54:8d (capab=0x1411 status=0 aid=1) [ 66.934797] wlp59s0: associated [ 66.965915] IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready [ 66.975044] DROP UNMATCHED OUT-world:IN= OUT=wlp59s0 SRC=::::::: DST=ff02:::::::0016 LEN=76 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=143 CODE=0 MARK=0x94 [ 66.983873] wlp59s0: Limiting TX power to 20 (20 - 0) dBm as advertised by c0:3e:0f:ac:54:8d [ 75.739408] pci_raw_set_power_state: 19 callbacks suppressed [ 75.739413] nouveau :01:00.0: Refused to change power state, currently in D3 [ 76.172896] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_bl.bin [ 76.173220] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_inst.bin [ 76.173372] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_data.bin [ 76.173388] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_sig.bin [ 76.173406] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_bl.bin [ 76.173615] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_inst.bin [ 76.173766] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_data.bin [ 76.173781] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_sig.bin [ 76.174174] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/image.bin [ 76.174210] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/desc.bin [ 76.174228] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/sig.bin [ 76.175037] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/ucode_load.bin [ 76.175292] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/ucode_unload.bin [ 76.175357] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/bl.bin [ 76.175387] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/unload_bl.bin [ 76.175638] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/nvdec/scrubber.bin [ 76.175764] nouveau :01:00.0: secboot: VPR scrubber binary failed! [ 76.175776] nouveau :01:00.0: gr: init failed, -22 ** Model information sys_vendor: Dell Inc. product_name: Precision 5530 product_version: chassis_vendor: Dell Inc
Bug#917383: Precision 5530 unbootable
Package: debian-installer Version: Buster Alpha 4 Severity: critical Tags: d-i Hello, after installing a Precision 5530 with the Alpha 4 version of Buster, the system is unbootable, except for a grub without any configuraiton. Ie, to boot Linux, you need to enter all the partition, modules, kernel and initrd information manually. Cheers, Toni -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#842015: one more data point
Hi, I am not a Gnome user, but somehow had this package installed on machine A. I was logged in on machine A, but had a screen lock on. On machine B, I was also logged in, running something like "ssh -XCA machineA" where I tried to "gbp buildpackage". This got stuck at the signing phase, with no output on my terminal (ie, in the SSH session). If I typed something, I had local echo. I could kill the program by typing Ctrl-C. Both machines are running the latest Stretch/amd64. Thanks, Toni
Bug#892275: Problem exists in Buster
Hi, I can say that the problem exists in version 1.11-2. On my system, the output from the systemctl command is as follows: $ systemctl --user status redshift ● redshift.service - Redshift display colour temperature adjustment Loaded: loaded (/usr/lib/systemd/user/redshift.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: http://jonls.dk/redshift/ I tried to start the process by hand, and it sort of worked. But redshift still hangs with the message that it is trying to figure out the location using geoclue2. Cheers, Toni
Bug#901930: [pkg-wicd-maint] Bug#901930: crash upon trying to enter "Config"
Hi Axel, On Wed, Jun 20, 2018 at 02:06:41PM +0200, Axel Beckert wrote: > On a first glance it looks as if this issue only happens if a specific > flow path is taken in wicd-curses. It would be interesting to know > under which circumstances it exactly happens for you. > > I assume it's reproducible for you. yes, it is: On a buster machine, installed yesterday and today, I can do the following: * as root, start wicd-curses. * press the right arrow key * crash! Cheers, Toni
Bug#901930: crash upon trying to enter "Config"
Package: wicd-curses
Version: 1.7.4+tb2-6
Severity: important
Tags: upstream
Hi,
I am trying to run wicd-curses, but it crashes hard. I've culled the
control characters and the boilerplate ("About" etc.) from the
typescript:
root@nutshell:~# wicd-curses
... Not connected ...
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 1149, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 1162, in update_ui
self.handle_keys(input_data)
File "/usr/share/wicd/curses/wicd-curses.py", line 1040, in handle_keys
self.diag = WirelessSettingsDialog(pos, self.frame)
File "/usr/share/wicd/curses/netentry_curses.py", line 503, in __init__
self.set_values()
File "/usr/share/wicd/curses/netentry_curses.py", line 539, in set_values
self.bitrates.append('auto')
AttributeError: 'dbus.String' object has no attribute 'append'
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: Apparmor: enabled
Versions of packages wicd-curses depends on:
ii python2.7.15-3
ii python-urwid 2.0.1-2
ii wicd-daemon 1.7.4+tb2-6
Versions of packages wicd-curses recommends:
ii sudo 1.8.2301
wicd-curses suggests no packages.
Versions of packages wicd-daemon depends on:
ii adduser 3.117
ii dbus 1.12.8-2
ii debconf 1.5.67
ii iputils-ping 3:20161105-1
ii isc-dhcp-client 4.3.5-4
ii lsb-base 9.20170808
ii psmisc 23.1-1+b1
ii python 2.7.15-3
ii python-dbus 1.2.8-2
ii python-gobject-2 2.28.6-13+b1
ii python-wicd 1.7.4+tb2-6
ii wireless-tools 30~pre9-12+b1
ii wpasupplicant2:2.6-16
Versions of packages wicd-daemon recommends:
ii rfkill 0.5-1+b1
Versions of packages wicd-daemon suggests:
ii pm-utils 1.4.1-17
Versions of packages python-wicd depends on:
ii python 2.7.13-2
-- debconf information excluded
Bug#901448: search generates broken URL
Package: python-flask-doc Version: 1.0.2-1 Severity: normal Hi, when I conduct a search, at least some of the results are wrong. Eg. searching for "session" yields a list, which contains this link: http://localhost/Flask/api.rst.html?highlight=session#flask.session Please note the ".rst" part in there. If I strip this out, the resulting URL works just fine: http://localhost/Flask/api.html?highlight=session#flask.session It would be nice if the search could generate proper links in the first place. Cheers, --Toni++ -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-flask-doc depends on: ii libjs-sphinxdoc 1.4.9-2 Versions of packages python-flask-doc recommends: ii python-flask 0.12.1-1 python-flask-doc suggests no packages. -- no debconf information
Bug#898718: pressing the 'Escape' key while editing a title causes terminator to exit
Package: terminator Version: 1.90+bzr-1705-1 Severity: normal Hi! I am using terminator under awesome (no Gnome or so), and frequently inadvertantly end up having my mouse on the title bar with the option to edit the window title. In such a situation, the title bar appears to be a litte bit enlarged, and there is a text input window with a white background, and the existing text in this input field, provided by the original window title, appears to be selected (white on blue). When I just want to exit this dialogue in the way I exist most dialogues, by pressing the Escape key, the entire terminal vanishes, together with all other tabs and shells inside. I find this pretty annoying, but have no real idea on how to fix it, except for changing my behaviour. But I would like the terminal program to at least ask for confirmation before killing all my even unrelated shells. If you want to reproduce the bug, just open terminator, then double click on the window title, then press Escape. Cheers, Toni -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages terminator depends on: ii gir1.2-glib-2.0 1.50.0-1+b1 ii gir1.2-gtk-3.03.22.11-1 ii gir1.2-pango-1.0 1.40.5-1 ii gir1.2-vte-2.91 0.46.1-1 ii python2.7.13-2 ii python-cairo 1.8.8-2.2 ii python-dbus 1.2.4-1+b1 ii python-gi 3.22.0-2 ii python-gi-cairo 3.22.0-2 ii python-psutil 5.0.1-1 Versions of packages terminator recommends: ii gir1.2-keybinder-3.0 0.3.1-1 ii gir1.2-notify-0.7 0.7.7-2 ii xdg-utils 1.1.1-1 terminator suggests no packages. -- no debconf information
Bug#815037: problem still present in Stretch and stretch-backports?
kernel: [ 1003.669983] iwlwifi :01:00.0: 0x000F | l2p_mhvalid Apr 30 23:43:38 debian kernel: [ 1003.669989] iwlwifi :01:00.0: 0x001050C0 | l2p_addr_match Apr 30 23:43:38 debian kernel: [ 1003.669996] iwlwifi :01:00.0: 0x0005 | lmpm_pmg_sel Apr 30 23:43:38 debian kernel: [ 1003.670004] iwlwifi :01:00.0: 0x13011136 | timestamp Apr 30 23:43:38 debian kernel: [ 1003.670009] iwlwifi :01:00.0: 0xA8C0 | flow_handler Apr 30 23:43:38 debian kernel: [ 1003.670105] iwlwifi :01:00.0: Start IWL Event Log Dump: display last 1 entries Apr 30 23:43:38 debian kernel: [ 1003.670160] iwlwifi :01:00.0: EVT_LOGT:0007362647:0x010c:0123 Apr 30 23:43:38 debian kernel: [ 1003.682688] ieee80211 phy0: Hardware restart was requested Cheers, Toni -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.130 -- no debconf information $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QS77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
Bug#892955: [Pkg-mongodb-maintainers] Bug#892955: mongodb-server: enabling the 'oplog' config option makes server fail to start
Hi Apollon, On Thu, Mar 15, 2018 at 09:38:17AM +0200, Apollon Oikonomopoulos wrote: > Indeed, it appears the option has been called "diaglog" for the past 9 > years, can you give it a try? We need to update the package's default > config I guess... ;} I changed the config to say "diaglog=7", and the server starts with that. Cheers, Toni
Bug#892955: mongodb-server: enabling the 'oplog' config option makes server fail to start
Package: mongodb-server Version: 1:3.2.11-2+deb9u1 Severity: normal Hi, I just installed mongodb and wanted to get more detailed logging, so I removed the comment from 'oplog = 0' and switched to 7: # Set oplogging level where n is # 0=off (default) # 1=W # 2=R # 3=both # 7=W+some reads oplog = 7 After that, the server refused to start, and I found this in the log: ... mongod[385]: Error parsing INI config file: unrecognised option 'oplog' Cheers, --Toni++ -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mongodb-server depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libboost-chrono1.62.0 1.62.0+dfsg-4 ii libboost-filesystem1.62.0 1.62.0+dfsg-4 ii libboost-program-options1.62.0 1.62.0+dfsg-4 ii libboost-regex1.62.01.62.0+dfsg-4 ii libboost-system1.62.0 1.62.0+dfsg-4 ii libboost-thread1.62.0 1.62.0+dfsg-4 ii libc6 2.24-11+deb9u3 ii libgcc1 1:6.3.0-18+deb9u1 ii libgoogle-perftools42.5-2.2 ii libpcre32:8.39-3 ii libpcrecpp0v5 2:8.39-3 ii libsnappy1v51.1.3-3 ii libssl1.0.2 1.0.2l-2+deb9u2 ii libstdc++6 6.3.0-18+deb9u1 ii libstemmer0d0+svn585-1+b2 ii libyaml-cpp0.5v50.5.2-4 ii lsb-base9.20161125 ii mongodb-clients 1:3.2.11-2+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 mongodb-server recommends no packages. mongodb-server suggests no packages. -- Configuration Files: /etc/mongodb.conf changed: dbpath=/var/lib/mongodb logpath=/var/log/mongodb/mongodb.log logappend=true bind_ip = 127.0.0.1 journal=true cpu = true verbose = true objcheck = true quota = true -- no debconf information
Bug#891621: xfonts-intl-chinese: non-standard glyph for U+840D ('ping2')
Package: xfonts-intl-chinese Version: 1.2.1-10 Severity: normal Hi, I'm not sure that this is the right package to report the bug against, and I am not really sure that my assessment of the problem is correct, but I do have the strong suspicion that I am. Anyway, when I write the character 萍, I got the 'wrong' glyph in Anki and eg. terminator, but got the right glyph inside Chromium. In both cases, fcitx is showing the wrong glyph in the preview window. I have attached two screenshots showing the two glyphs. The 'right' glyph seems to be the one which is contained in the image that also contains the pronounciation, which happens to be the bigger image. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfonts-intl-chinese depends on: ii xfonts-utils 1:7.7+4 xfonts-intl-chinese recommends no packages. Versions of packages xfonts-intl-chinese suggests: ii emacs-intl-fonts 1.2.1-10 pn xfonts-cjk ii xfonts-intl-chinese-big 1.2.1-10 ii xserver-xephyr [xserver] 2:1.19.2-1+deb9u2 ii xserver-xorg [xserver]1:7.7+19 -- no debconf information
Bug#891049: pgmodeler: version in stretch incompatible with db version in stretch
Package: pgmodeler Version: 0.8.2-1+b1 Severity: normal Hi! I would like to use pgmodeler in Stretch, but the program can't work with PostgreSQL 9.6, also in Stretch. I get an error message that only versions up to 9.5 are supported, and that's the end of the story. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgmodeler depends on: ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libpq59.6.6-0+deb9u1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5network55.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5svg55.7.1~20161021-2+b2 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii pgmodeler-common 0.8.2-1 pgmodeler recommends no packages. pgmodeler suggests no packages. -- no debconf information
Bug#890772: python-httplib2: homepage needs updating
Package: python-httplib2 Version: 0.9.2+dfsg-1 Severity: minor Tags: patch Hi, the homepage of this package has changed. I've seen that the old source code has not seen updates in years, but at the new location, some bugs have been fixed, and documentation has been improved. I've attached a patch that updates the homepage. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-httplib2 depends on: ii ca-certificates 20161130+nmu1 ii python 2.7.13-2 python-httplib2 recommends no packages. python-httplib2 suggests no packages. -- no debconf information commit aa2bf6627e8dacbda999df4d70bda8fa10299589 Author: Toni Mueller <t...@debian.org> Date: Sun Feb 18 18:29:54 2018 +0100 updated homepage diff --git a/debian/control b/debian/control index b421211..b89f7a7 100644 --- a/debian/control +++ b/debian/control @@ -9,7 +9,7 @@ Build-Depends: debhelper (>= 9), python3-all (>= 3.1.2-10) Standards-Version: 3.9.8 X-Python-Version: >= 2.4 -Homepage: https://github.com/jcgregorio/httplib2 +Homepage: https://github.com/httplib2/httplib2 Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/python-httplib2.git Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/python-httplib2.git
Bug#888209: isc-dhcp-client: hammers DHCP server if it cannot write lease file
Package: isc-dhcp-client Version: 4.3.5-3+b2 Severity: normal Hi, I recently experienced a problem with dhclient issuing a ton of requests in rapid fire mode in an endless loop because the file system where it wanted to write its lease file, was mounted read-only. It got a new IP everytime and added them all to the interface. It would be nice if dhclient could just be content with having one IP address, and then stop asking until the lease expires, regardless of the state of the file system, instead of issuing dozens of DHCP requests per second. I experien Cheers, --Toni++ -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages isc-dhcp-client depends on: ii debianutils 4.8.4 ii iproute2 4.14.1-1 ii libc6 2.26-4 ii libdns-export169 1:9.11.2+dfsg-5 ii libisc-export166 1:9.11.2+dfsg-5 Versions of packages isc-dhcp-client recommends: ii isc-dhcp-common 4.3.5-3+b2 Versions of packages isc-dhcp-client suggests: pn avahi-autoipd pn isc-dhcp-client-ddns pn resolvconf -- no debconf information
Bug#887787: lxc: CentOS 7 amd64 container can't be stopped
Hi, the problem is not limited to CentOS. I just had a Debian container lock up the same way, on the same host. Cheers, Toni
Bug#887787: lxc: CentOS 7 amd64 container can't be stopped
.500055] Call Trace: Jan 19 22:22:38 debian kernel: [39390.500061] [] ? __schedule+0x233/0x6d0 Jan 19 22:22:38 debian kernel: [39390.500066] [] ? schedule+0x32/0x80 Jan 19 22:22:38 debian kernel: [39390.500071] [] ? rwsem_down_read_failed+0xf0/0x150 Jan 19 22:22:38 debian kernel: [39390.500076] [] ? iput+0x7e/0x210 Jan 19 22:22:38 debian kernel: [39390.500082] [] ? SyS_tee+0x390/0x390 Jan 19 22:22:38 debian kernel: [39390.500088] [] ? call_rwsem_down_read_failed+0x14/0x30 Jan 19 22:22:38 debian kernel: [39390.500092] [] ? down_read+0x1c/0x30 Jan 19 22:22:38 debian kernel: [39390.500098] [] ? iterate_supers+0x9c/0x100 Jan 19 22:22:38 debian kernel: [39390.500103] [] ? sys_sync+0x42/0xb0 Jan 19 22:22:38 debian kernel: [39390.500107] [] ? do_syscall_64+0x7c/0xf0 Jan 19 22:22:38 debian kernel: [39390.500112] [] ? entry_SYSCALL64_slow_path+0x25/0x25 Jan 19 22:22:38 debian kernel: [39390.500127] INFO: task halt:7352 blocked for more than 120 seconds. Jan 19 22:22:38 debian kernel: [39390.500132] Tainted: G O 4.9.0-5-amd64 #1 Debian 4.9.65-3+deb9u2 Jan 19 22:22:38 debian kernel: [39390.500135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 22:22:38 debian kernel: [39390.500138] haltD0 7352 7211 0x0100 Jan 19 22:22:38 debian kernel: [39390.500143] 976554b1 97650de10200 97655fc18940 Jan 19 22:22:38 debian kernel: [39390.500149] a6e11500 a7a7059bfdf0 a6802923 9765500a5760 Jan 19 22:22:38 debian kernel: [39390.500154] 0286 97655fc18940 a7a7059bfdf8 97650de10200 Jan 19 22:22:38 debian kernel: [39390.500159] Call Trace: Jan 19 22:22:38 debian kernel: [39390.500165] [] ? __schedule+0x233/0x6d0 Jan 19 22:22:38 debian kernel: [39390.500169] [] ? schedule+0x32/0x80 Jan 19 22:22:38 debian kernel: [39390.500174] [] ? rwsem_down_read_failed+0xf0/0x150 Jan 19 22:22:38 debian kernel: [39390.500179] [] ? iput+0x7e/0x210 Jan 19 22:22:38 debian kernel: [39390.500184] [] ? SyS_tee+0x390/0x390 Jan 19 22:22:38 debian kernel: [39390.500189] [] ? call_rwsem_down_read_failed+0x14/0x30 Jan 19 22:22:38 debian kernel: [39390.500194] [] ? down_read+0x1c/0x30 Jan 19 22:22:38 debian kernel: [39390.500199] [] ? iterate_supers+0x9c/0x100 Jan 19 22:22:38 debian kernel: [39390.500204] [] ? sys_sync+0x42/0xb0 Jan 19 22:22:38 debian kernel: [39390.500208] [] ? do_syscall_64+0x7c/0xf0 Jan 19 22:22:38 debian kernel: [39390.500213] [] ? entry_SYSCALL64_slow_path+0x25/0x25 Trying to 'lxc-stop -n centos' (name of the container) also does not work. A KVM machine with CentOS 7 on the same host works without problems. From the host machine, the container's processes look like this: $ ps auwwx|grep 231072 2310726381 0.0 0.0 42544 2100 ?Ds 22:10 0:00 /sbin/init 2310726708 0.0 0.1 113380 14640 ?Ss 22:12 0:00 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient--eth0.lease -pf /var/run/dhclient-eth0.pid -H centos eth0 2310726951 0.0 0.0 115396 3160 pts/17 Ss 22:15 0:00 /bin/bash 2310726958 0.0 0.0 107912 616 pts/17 D+ 22:15 0:00 sync 2310727211 0.0 0.0 115396 3168 pts/18 Ss 22:16 0:00 /bin/bash 2310727352 0.0 0.0 128432 2576 pts/18 D+ 22:18 0:00 halt -f 2310727525 0.0 0.0 115396 3116 pts/20 Ss 22:19 0:00 /bin/bash 2310727589 0.0 0.0 128432 2796 pts/20 D+ 22:19 0:00 halt -n -f toni 10162 0.0 0.0 12720 980 pts/5S+ 22:49 0:00 grep --color=auto 231072 231072 27515 0.0 0.0 1508 8 ?Ss 18:55 0:00 /sbin/init 231072 27827 0.0 0.0 150848 ?Ss 18:55 0:00 /sbin/syslogd -Z 231072 27848 0.0 0.0 151248 ?Ss 18:55 0:00 /usr/sbin/crond -c /etc/crontabs 231072 27917 0.0 0.0 150848 ?Ss 18:56 0:00 udhcpc -b -p /var/run/udhcpc.eth0.pid -i eth0 -x hostname:alpine 231072 27944 0.0 0.0 7320 308 ?S18:56 0:00 /usr/sbin/sshd 231072 27948 0.0 0.0 1508 4 pts/0Ss+ 18:56 0:00 /sbin/getty 38400 tty1 231072 27949 0.0 0.0 1508 4 pts/1Ss+ 18:56 0:00 /sbin/getty 38400 tty2 231072 27950 0.0 0.0 1508 4 pts/2Ss+ 18:56 0:00 /sbin/getty 38400 tty3 231072 27951 0.0 0.0 1508 4 pts/3Ss+ 18:56 0:00 /sbin/getty 38400 tty4 231072 27952 0.0 0.0 1508 4 pts/9Ss+ 18:56 0:00 /sbin/getty 38400 console It would be great if lxc could prevent a container misbehaving like that. There's a side effect on the host machine: Since the 'init' process of the container hangs, the host machine cannot shut down properly anymore. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Loc
Bug#887764: dnsmasq: please add the homepage to the package
Package: dnsmasq Version: 2.76-5+deb9u1 Severity: minor Tags: patch Hi, I would like to have the homepage added to the package. The attached patch accomplishes that. Thanks, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnsmasq depends on: ii dnsmasq-base 2.76-5+deb9u1 ii init-system-helpers 1.48 ii netbase 5.4 dnsmasq recommends no packages. Versions of packages dnsmasq suggests: pn resolvconf -- no debconf information commit 378b03da2b0cd79d688bf00e051521628e475bf7 Author: Toni Mueller <t...@debian.org> Date: Fri Jan 19 19:17:43 2018 +0100 adding a homepage diff --git a/debian/control b/debian/control index 035c830..e540918 100644 --- a/debian/control +++ b/debian/control @@ -5,6 +5,7 @@ Build-depends: gettext, libnetfilter-conntrack-dev [linux-any], libidn11-dev, libdbus-1-dev (>=0.61), libgmp-dev, nettle-dev (>=2.4-3), libbsd-dev [!linux-any] Maintainer: Simon Kelley <si...@thekelleys.org.uk> +Homepage: http://www.thekelleys.org.uk/dnsmasq/doc.html Standards-Version: 3.9.8 Package: dnsmasq
Bug#887109: postfix: missing /etc/postfix/postfix-files causes config check to always fail
Package: postfix Version: 3.1.6-0+deb9u1 Severity: normal Hi, I read that in 3.1.4, you split the file /etc/postfix/postfix-files into snippets which are then placed in /etc/postfix/postfix-files.d, but this directory is also empty. I've just checked with the package in unstable, and the situation is the same in that package, too. Cheers, Toni -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfix depends on: ii adduser3.115 ii cpio 2.11+dfsg-6 ii debconf [debconf-2.0] 1.5.61 ii dpkg 1.18.24 ii init-system-helpers1.48 ii libc6 2.24-11+deb9u1 ii libdb5.3 5.3.28-12+deb9u1 ii libicu57 57.1-6+deb9u1 ii libsasl2-2 2.1.27~101-g0780600+dfsg-3 ii libssl1.1 1.1.0f-3+deb9u1 ii lsb-base 9.20161125 ii netbase5.4 ii postfix-sqlite 3.1.6-0+deb9u1 ii ssl-cert 1.0.39 Versions of packages postfix recommends: ii python3 3.5.3-1 Versions of packages postfix suggests: ii bsd-mailx [mail-reader]8.1.2-0.20160123cvs-4 ii dovecot-core [dovecot-common] 1:2.2.27-3+deb9u1 ii emacs25-lucid [mail-reader]25.1+1-4+deb9u1 ii evolution [mail-reader]3.22.6-1+deb9u1 ii libsasl2-modules 2.1.27~101-g0780600+dfsg-3 ii mutt [mail-reader] 1.7.2-1 pn postfix-cdb ii postfix-doc3.1.6-0+deb9u1 pn postfix-ldap pn postfix-lmdb pn postfix-mysql pn postfix-pcre ii postfix-pgsql 3.1.6-0+deb9u1 pn procmail pn resolvconf pn sasl2-bin ii sup-mail [mail-reader] 0.22.1-2 ii ufw0.35-4 ii wl-beta [mail-reader] 2.15.9+0.20161228-1 -- debconf information excluded
Bug#885896: RFP: ptunnel-ng -- Ptunnel-NG is a bugfixed and refactored version of Ptunnel with some additional features e.g. change the magic value without recompiling (bypass Cisco IPS).
Package: wnpp Severity: wishlist * Package name : ptunnel-ng Version : 1.1 Upstream Author : Toni Uhlig <matze...@googlemail.com> * URL : https://github.com/lnslbrty/ptunnel-ng * License : BSD Programming Lang: C Description : Ptunnel-NG is a bugfixed and refactored version of Ptunnel with some additional features e.g. change the magic value without recompiling (bypass Cisco IPS). What is ptunnel-ng? Ptunnel-NG is a bugfixed and refactored version of Ptunnel with some additional features e.g. change the magic value without recompiling (bypass Cisco IPS). What is ptunnel? Ptunnel is an application that allows you to reliably tunnel TCP connections to a remote host using ICMP echo request and reply packets, commonly known as ping requests and replies.
Bug#849703: ITP: ansible-doc -- Documentation for Ansible
Hi Harlan, On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote: > It's been a while since we made the decision not to pull from upstream's > git; Toni, I'd be happy to work with you on seeing if it's doable now. I think I have a suitable package now, being as cheap as possible, but it's off your git tree, which I took from https://anonscm.debian.org/git/collab-maint/ansible.git I had to change some things, though: * retrofit the docsite directory * adjust debian/control * adjust debian/rules It's for 2.4.1, and it's lintian clean. My changes build both packages. How can I best upload this stuff without disrupting yours, and without creating an entirely new repository? TIA! Cheers, --Toni++
Bug#879109: mutt: crash when pressing the wrong keys
Package: mutt
Version: 1.7.2-1
Severity: normal
Hi,
I am using awesome, but sometimes mistype something - eg. instead of
"Mod-4" for selecting the 4th label, I type "Ctrl-4". As a result, mutt
crashes. I get this error message while in the index:
$ mutt
GPGME: CMS protocol not available
Caught signal 3... Exiting.
Cheers,
--Toni++
-- Package-specific info:
NeoMutt 20170113 (1.7.2)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 4.9.0-4-amd64 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet
Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-2'
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--with-target-sy
stem-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20161229 (Debian 6.3.0-2)
Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man'
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu'
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode'
'--disable-dependency-tracking' '--with-mailpath=/var/mail'
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache'
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop'
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen'
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster'
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm'
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-Wdate-time -D
_FORTIFY_SOURCE=2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong
-Wformat -Werror=format-security -fno-delete-null-pointer-checks
Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_FUTIMENS
+HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR +HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM
+HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS
+USE_COMPRESSED +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX
+USE_GSS +USE_HCACHE +USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL
+USE_SETGID +USE_SIDEBAR +USE_SMTP +USE_SSL_GNUTLS -USE_SSL_OPENSSL
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
patch-attach-headers-color-neomutt
patch-compose-to-sender-neomutt
patch-compress-neomutt
patch-cond-date-neomutt
patch-encrypt-to-self-neomutt
patch-fmemopen-neomutt
patch-forgotten-attachments-neomutt
patch-forwref-neomutt
patch-ifdef-neomutt
patch-index-color-neomutt
patch-initials-neomutt
patch-keywords-neomutt
patch-kyoto-neomutt
patch-limit-current-thread-neomutt
patch-lmdb-neomutt
patch-multiple-fcc-neomutt
patch-nested-if-neomutt
patch-new-mail-neomutt
patch-nntp-neomutt
patch-notmuch-neomutt
patch-progress-neomutt
patch-quasi-delete-neomutt
patch-reply-with-xorig-neomutt
patch-sensible-browser-neomutt
patch-si
Bug#878303: genrsa manpage suggests using 1024 bit keys
Hi Sebastian, On Fri, Oct 13, 2017 at 01:16:56PM +0200, Sebastian Andrzej Siewior wrote: > On 2017-10-12 14:49:31 [+0100], Toni Mueller wrote: > > I'm not suggesting a code change, but that the man page be updated to > > suggest using 2048 bit keys instead. > > That is one way to interpret it. The default is setting are 2048 bits. > The paragraph describes a problem keys that 64bit in size or less. I > would just drop the last sentence. that's also one way to go about it, but while we are at it, can we change the "should" to a "must"? Or can the software actually generate primes which are even smaller than 64 bits? And what would be the applicability of such small keys, anyway? Cheers, --Toni++
Bug#849086: small patch
Hi, there are a ton of deprecation warnings in radiotray. I've just created a small patch to silence one of them. Works for me - please test. Cheers, --Toni++ Index: radiotray-0.7.3/src/DbusFacade.py === --- radiotray-0.7.3.orig/src/DbusFacade.py +++ radiotray-0.7.3/src/DbusFacade.py @@ -19,7 +19,9 @@ ## import dbus import dbus.service -import dbus.glib +from dbus.mainloop.glib import DBusGMainLoop + +DBusGMainLoop(set_as_default=True) class DbusFacade(dbus.service.Object):
Bug#878303: genrsa manpage suggests using 1024 bit keys
Package: openssl Version: 1.1.0f-3 Severity: normal Tags: security upstream Hi, the genrsa(1) manpage suggests that 1024 bits may be a typical key size for RSA keys. I have to object - the Debian project deprecated 1024 bit keys in GnuPG for a reason, and recently, there was also a bug in GnuPG that allowed for 1024 bit keys to be broken. I'm not suggesting a code change, but that the man page be updated to suggest using 2048 bit keys instead. Cheers, --Toni++ -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openssl depends on: ii libc6 2.24-11+deb9u1 ii libssl1.1 1.1.0f-3 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20161130+nmu1 -- no debconf information
Bug#878075: high cpu load w/o any action
Package: circus Version: 0.12.1+dfsg-1 Severity: normal Hi, I have a circus installation running, and it uses an inordinate amount of CPU for itself - 5% for basically being idle. I find this very hard to accept. I've attached a screenshot which shows the situation. Cheers, Toni -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages circus depends on: ii init-system-helpers 1.48 ii python 2.7.13-2 ii python-iowait0.1-1.1 ii python-psutil5.0.1-1 ii python-tornado 4.4.3-1 ii python-zmq 16.0.2-2 Versions of packages circus recommends: ii python-gevent1.1.2-1 ii python-gevent-websocket 0.9.3-1 ii python-yaml 3.12-1 Versions of packages circus suggests: ii python-pygments 2.2.0+dfsg-1 pn python-redis -- no debconf information
Bug#613892: git should only Recommend: git-man instead of Depends: git-man
Hi Jonathan, On Wed, Oct 04, 2017 at 10:28:12AM -0700, Jonathan Nieder wrote: > Thanks! This is an excellent starting point. I'll be happy to tweak > this to make it configurable enough for upstream. I'll also look into > getting the Debian-specific text translated, which will be a new > adventure for me. thanks for the flowers! > May I have your sign-off? (See Documentation/SubmittingPatches > section 5 "Certify your work" for what this means.) Yes, of course. For me, it's 5(a). You can add this line at the appropriate location: Signed-off-by: Toni Mueller <m...@tonimueller.org> Cheers, --Toni++ signature.asc Description: PGP signature
Bug#613892: git should only Recommend: git-man instead of Depends: git-man
Hi Jonathan,
On Tue, Oct 03, 2017 at 03:15:26PM -0700, Jonathan Nieder wrote:
> Have you read https://bugs.debian.org/613892#10? Would you be
> interested in working on a patch for upstream Git to do that? We can
> make the error message printed when manpages are missing a value set
> at compile time (see the Makefile for existing compile-time parameters
> like DEFAULT_EDITOR). I'm happy to give pointers, etc. to anyone
> wanting to work on this.
I actually followed a different route and created a patch which is
Debian-specific. Please have a look - it is not yet polished in any way,
esp. all the translations are missing. The patch is against git in
unstable.
Cheers,
--Toni++
diff --git a/builtin/help.c b/builtin/help.c
index 334a849..c2a3670 100644
--- a/builtin/help.c
+++ b/builtin/help.c
@@ -32,6 +32,8 @@ enum help_format {
HELP_FORMAT_WEB
};
+static const char *manpage_canary = "/usr/share/doc/git-man/copyright";
+
static const char *html_path;
static int show_all = 0;
@@ -342,8 +344,15 @@ static void show_man_page(const char *git_cmd)
struct man_viewer_list *viewer;
const char *page = cmd_to_page(git_cmd);
const char *fallback = getenv("GIT_MAN_VIEWER");
+ struct stat throwaway;
+ int find_canary = 0;
setup_man_path();
+ find_canary = stat(manpage_canary, );
+ if (find_canary == -1) {
+ printf(_("git: no man pages installed, please ask your system administrator to install the git-man package.\n"));
+ exit(0);
+ }
for (viewer = man_viewer_list; viewer; viewer = viewer->next)
{
exec_viewer(viewer->name, page); /* will return when unable */
diff --git a/debian/control b/debian/control
index 5c2eb20..bc8fc8b 100644
--- a/debian/control
+++ b/debian/control
@@ -27,9 +27,9 @@ Package: git
Architecture: any
Multi-Arch: foreign
Depends: ${misc:Depends}, ${shlibs:Depends}, perl, liberror-perl,
- git-man (>> ${source:Upstream-Version}), git-man (<< ${source:Upstream-Version}-.)
Pre-Depends: ${misc:Pre-Depends}
-Recommends: patch, less, ssh-client
+Recommends: patch, less, ssh-client, git-man (>> ${source:Upstream-Version}),
+ git-man (<< ${source:Upstream-Version}-.)
Suggests: gettext-base, git-daemon-run | git-daemon-sysvinit,
git-doc, git-el, git-email, git-gui, gitk, gitweb,
git-cvs, git-mediawiki, git-svn
Bug#613892: git should only Recommend: git-man instead of Depends: git-man
Hi, I can only agree with Nelson. These days, a lot of git installations are non-interactive to begin with, as part of some service or so. Nobody is ever going to read the manual pages in such use cases. It's just a waste - and if the packages are being generated separately, anyway, weakening the dependency seems to be just a logical consequence. It would be nice if you could do it. TIA! Cheers, --Toni++
Bug#869814: listens on *:67 regardless of configuration
Package: dnsmasq Version: 2.76-5 Severity: normal Hi, I am running dnsmasq to provide DNS and DHCP services to some virtual machines. Now, I want dnsmasq to listen *only* on the specified interfaces. My configuration file thus reads: cut log-queries=extra log-facility=/var/log/dnsmasq.log interface=docker0,virbr0 except-interface=lo,ovsbr0 bind-interfaces server=10.99.1.1 rebind-localhost-ok dhcp-range=172.17.42.10,172.17.42.253 dhcp-range=192.168.122.10,192.168.122.250 dhcp-host=fe:c9:3f:13:28:8a,192.168.122.10,stretch1 dhcp-host=fe:c9:3f:13:28:8b,192.168.122.11,stretch2 cut According to the documentation, that should make dnsmasq to open sockets only on those two interfaces, for *any* services. But instead, I get something like this (11322 is the PID of dnsmasq): # lsof -p 11322 |grep -E 'UDP|TCP' dnsmasq 11322 dnsmasq4u IPv4 13538201 0t0 UDP *:bootps dnsmasq 11322 dnsmasq6u IPv4 13538204 0t0 UDP 172.17.42.1:domain dnsmasq 11322 dnsmasq7u IPv4 13538205 0t0 TCP 172.17.42.1:domain (LISTEN) dnsmasq 11322 dnsmasq8u IPv4 13538206 0t0 UDP mirror:domain dnsmasq 11322 dnsmasq9u IPv4 13538207 0t0 TCP mirror:domain (LISTEN) dnsmasq 11322 dnsmasq 10u IPv6 13538208 0t0 UDP [fe80::bc9d:d8ff:fe13:394f]:domain dnsmasq 11322 dnsmasq 11u IPv6 13538209 0t0 TCP [fe80::bc9d:d8ff:fe13:394f]:domain (LISTEN) # As you can see, the interface restriction for DNS works, but the it does not work for DHCP. I tried adding a 'no-dhcp-interface' statement to my configuration, but it had no effect. This prevents a second dnsmasq server from starting on the same machine. Cheers, --Toni++ -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnsmasq depends on: ii dnsmasq-base 2.76-5+b1 ii init-system-helpers 1.48 ii netbase 5.4 dnsmasq recommends no packages. Versions of packages dnsmasq suggests: ii resolvconf 1.79 -- Configuration Files: /etc/default/dnsmasq changed [not included] /etc/dnsmasq.conf changed [not included] -- no debconf information
Bug#868706: no UI after minimizing and unminimizing in Awesome WM
Package: inkscape Version: 0.92.1-1 Severity: important Hi, I'm using Awesome, the window manager, and ran into a big problem using Inkscape. I actually can't remember having had this problem before, because I have been using both Inkscape and Awesome for a long time, although I use Inkscape only rarely. The scenario: I start Inscape. Most things work nicely, but then, I decided to minimize Inkscape, so it is only visible in the task bar at the top of the screen. Then I tried to unminimize Inkscape again, to continue to work on that image I was working on The expected result: I would have expected Inkscape to properly display again, and let me continue with my work. The result: Inkscape did get as far as drawing a large grey rectangle where Inkscape has been visible before, plus some white rectangles for what were probably input windows (for eg. the font size), and that's it. Please see the attached screenshot of the Inkscape window at that point. As a consequence, I am unable to use Inkscape at this point. Cheers, --Toni++ -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages inkscape depends on: ii libaspell150.60.7~20110707-3+b2 ii libatk1.0-02.22.0-1 ii libatkmm-1.6-1v5 2.24.2-2 ii libc6 2.24-11+deb9u1 ii libcairo2 1.14.8-1 ii libcairomm-1.0-1v5 1.12.0-1+b1 ii libcdr-0.1-1 0.1.3-3+b1 ii libdbus-1-31.10.18-1 ii libdbus-glib-1-2 0.108-2 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgc1c2 1:7.4.2-8 ii libgcc11:6.3.0-18 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libglibmm-2.4-1v5 2.50.0-1 ii libgomp1 6.3.0-18 ii libgsl22.3+dfsg-1 ii libgtk2.0-02.24.31-2 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libgtkspell0 2.0.16-1.1 ii libjpeg62-turbo1:1.5.1-2 ii liblcms2-2 2.8-4 ii libmagick++-6.q16-78:6.9.7.4+dfsg-11 ii libmagickcore-6.q16-3 8:6.9.7.4+dfsg-11 ii libmagickwand-6.q16-3 8:6.9.7.4+dfsg-11 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-01.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libpangomm-1.4-1v5 2.40.1-3 ii libpng16-161.6.28-1 ii libpoppler-glib8 0.48.0-2 ii libpoppler64 0.48.0-2 ii libpopt0 1.16-10+b2 ii libpotrace01.13-3 ii librevenge-0.0-0 0.0.4-6 ii libsigc++-2.0-0v5 2.10.0-1 ii libstdc++6 6.3.0-18 ii libvisio-0.1-1 0.1.5-4+b1 ii libwpg-0.3-3 0.3.1-3 ii libx11-6 2:1.6.4-3 ii libxml22.9.4+dfsg1-2.2 ii libxslt1.1 1.1.29-2.1 ii python 2.7.13-2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages inkscape recommends: ii aspell 0.60.7~20110707-3+b2 ii fig2dev [transfig] 1:3.2.6a-2 ii imagemagick 8:6.9.7.4+dfsg-11 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11 ii libimage-magick-perl 8:6.9.7.4+dfsg-11 ii libwmf-bin 0.2.8.4-10.6 ii python-lxml 3.7.1-1 ii python-numpy 1:1.12.1-3 ii python-scour 0.32-2 ii transfig 1:3.2.6a-2 Versions of packages inkscape suggests: pn dia | dia-gnome pn libsvg-perl pn libxml-xql-perl ii pstoedit 3.70-3+b2 pn python-uniconvertor ii ruby 1:2.3.3 -- no debconf information
