Bug#942047: dnscrypt-proxy doesn't and can't run like this
Package: dnscrypt-proxy
Version: 2.0.19+ds1-2+b11
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer !
Your package doesn't run. Especially the service
"/usr/lib/systemd/system/dnscrypt-proxy-resolvconf.service" does not it's work
and it can not do it in this way. The service is not correctly started up; the
file /etc/resolv.conf remains in the former insecure state and with it all dns-
requests. Please grep for "Datagram" - not for "ListenDatagram" in this file.
... and please, please (I beg to all maintainers): test the package before
publishing it...
Thanks and regards
Harry Haller
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-6-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE=de (charmap=UTF-8) (ignored: LC_ALL set to
de_DE.UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dnscrypt-proxy depends on:
ii adduser 3.118
ii libc6 2.28-10
ii lsb-base 10.2019051400
dnscrypt-proxy recommends no packages.
Versions of packages dnscrypt-proxy suggests:
ii openresolv [resolvconf] 3.8.0-1
-- Configuration Files:
/etc/dnscrypt-proxy/dnscrypt-proxy.toml changed [not included]
-- no debconf information
-- debsums errors found:
debsums: changed file /lib/systemd/system/dnscrypt-proxy-resolvconf.service
(from dnscrypt-proxy package)
[Unit]
Description=DNSCrypt proxy resolvconf support
Documentation=https://github.com/jedisct1/dnscrypt-proxy/wiki
After=dnscrypt-proxy.socket
Requires=dnscrypt-proxy.socket
ConditionFileIsExecutable=/sbin/resolvconf
[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/bin/sh -c 'systemctl show dnscrypt-proxy.socket \
| grep Datagram \
| cut -d "=" -f 2 \
| cut -d ":" -f 1 \
| awk \'{ print "nameserver " $1 }\' \
| /sbin/resolvconf -a lo.dnscrypt-proxy'
ExecStop=/sbin/resolvconf -d lo.dnscrypt-proxy
[Install]
WantedBy=multi-user.target
Also=dnscrypt-proxy.socket
Bug#941998: cruft: does not work at alll
Package: cruft Version: 0.9.38 Severity: normal Dear Maintainer ! I think, it's apparent, that cruft does not work at all... Most of the results are completely incorrect. Especially the "missing"-Section has no valid contents in ponderabel extents - but also the "unexplained"-section. Once again I have here - on two fresh dist-upgraded systems - many thousands of missing files. Is it prepared for the package "usrmerge" ? No need to mention, that most of the "missing" files all exist and the "unexplained" files are registered by dpkg... My call of cruft: #cruft --ignore "/root /home /mnt /proc /sys /Dummy /Schafott /Pax /dev /lost+found /opt /run /srv /tmp" -r ~/Cruft.report Whatever... Sorry, but in most of the debian-doks (especially the release-notes of each stable-release since many years) there are prominent recommendations to use this application (cruft & cruft-common). Since more than 10 years (felt) the debian-users waste their lifetime with this - at best - "sid"-package. Nothing justifies, that cruft finds it's way always into whatever is stable at the moment. Please be consequent and kick it out of the stable releases until it works (some day in a distant future)... Best Regards Harry Haller -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-6-686-pae (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cruft depends on: ii cruft-common 0.9.38 ii file 1:5.35-4 ii libc6 2.28-10 cruft recommends no packages. Versions of packages cruft suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 pn cruft-ng
Bug#831899: This error persists still in Debian stretch
Hi Volker, Hi Maximiliano ! This error is still in stretch. But I've got it in an i386-environment. I don't want to make a new Bug-Report, but document, that it still exists. I described it here: https://bugs.kde.org/show_bug.cgi?id=382635 As I described there, the error occurs always I start kaddressbook. I (can't) use kaddressbook 4:16.04.3-3. My Kernel is linux-image-4.9.0-3-686-pae (4.9.30-2+deb9u). With a new user it starts - as in Jessie. Here are my error- messages, when I start it from Konsole (bash): QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x80663e78) "kaddressbook_9177_mTcCx7" false QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x80663e78) "kaddressbook_9177_e22nIP" false QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x80663e78) "kaddressbook_9177_tOmGTd" false QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x80663e78) "kaddressbook_9177_9QZzTP" false Database "akonadi" opened using driver "QMYSQL" Database "akonadi" opened using driver "QMYSQL" New notification bus: "/subscriber/kaddressbook_9177_mTcCx7" Database "akonadi" opened using driver "QMYSQL" New notification bus: "/subscriber/kaddressbook_9177_e22nIP" org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() Database "akonadi" opened using driver "QMYSQL" New notification bus: "/subscriber/kaddressbook_9177_tOmGTd" Database "akonadi" opened using driver "QMYSQL" Database "akonadi" opened using driver "QMYSQL" New notification bus: "/subscriber/kaddressbook_9177_9QZzTP" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kaddressbook path = /usr/bin pid = 9177 KCrash: Arguments: /usr/bin/kaddressbook KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Shutting down "kaddressbook-1186278907" ... Shutting down "/subscriber/kaddressbook_9177_mTcCx7" ... Shutting down "/subscriber/kaddressbook_9177_e22nIP" ... Shutting down "/subscriber/kaddressbook_9177_tOmGTd" ... Shutting down "KAddressBook::GlobalContactSession" ... Shutting down "/subscriber/kaddressbook_9177_9QZzTP" ... void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kaddressbook_9177_9QZzTP" now serving: () void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kaddressbook_9177_tOmGTd" now serving: () void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kaddressbook_9177_e22nIP" now serving: () [1] Exit 253kaddressbook Regards Juwe (alias Harry Haller)
Bug#869616: Kodi Remote-Control-Interface repeats always the same key
package: kodi version: 2:17.1+dfsg1-3 severity: normal Dear Maintainer ! When I use a key of my my Medion X10-remote-control (compatible to Ati remote- control) the first time after Kodi-start, it is repeated always until I use the same key-function on my keyboard. Maybe it is a problem of Kodi at all, but it is a Debian-package. I have just dist-upgraded from Jessie to Stretch. My Kernel is linux-image-4.9.0-3-686-pae (4.9.30-2+deb9u) with nvidia- legacy-340xx-kernel-dkms (340.102-1) and so on. I use lirc (0.9.4.c-9). Here's a part of lsmod: rc_medion_x10 16384 0 ati_remote 20480 0 rc_core24576 3 rc_medion_x10,ati_remote The error is reproduceable: I just have to start kodi again. Best regards Juwe (Harry Haller)
Bug#869521: fsck from util-linux-2.29.2 checks filesystems on every boot
package: util-linux version: 2.29.2-1 severity: normal Hello ! I observed, that the actual fsck (from stretch) always checks my filesystems each time I boot that System. I dist-upgraded recently and former on Jessie it worked properly. The problem is, that my Mainboard-Battery is empty and it makes no sense to change it, because it will be empty again after three months. So I start my System with default-bios-settings and a wrong hardware- clock (about 01.01,2000). Fsck now seems not to be able to differ between before and after the "last checked"-stanza on the filesystem as reported by tune2fs. Regards Juwe
Bug#869513: console-setup changes remain only till next reboot
package: console-setup version: 1.164 severity: normal Hello Maintainer ! I have here one Desktop-PC-System and one minimal System plus rsnapshot- package. Both are dist-upgraded from Jessie to Stretch with linux- image-4.9.0-3-686-pae (4.9.30-2+deb9u). The bug is reproduceable. The changes of the console after "dpkg-reconfigure console-setup" are as expected, but after next boot they disappear - there is only the small font again, which I can't read well. Always I have to reconfigure the virtual console, when I want to work on it. regards Juwe (alias Harry Haller)
Bug#522108: cruft: reports masses of existing files as missing and even more installed files as unexplained
Package: cruft Version: 0.9.12 Severity: grave Justification: renders package unusable In february, I've upgraded my Etch to Lenny. But (for the results of cruft) I thought, it failed - so I decided recently to make a new install (with nearly the same packages). After this, another check with cruft: the result is nearly identical: masses of files are reported as 'missing' although they exist (as far as I've checked it; mainly from /etc, /usr/lib and /usr/share) and even much more files are reported as 'unexplained' (also mainly from /etc, /usr/lib and /usr/share). The latter also can't be true; there have been hardly any and certainly no severe errors reported while the re-installation. And the re-installation of some critizized/concerned packages couldn't change anything on this result as well. Also the reported errors in /etc/alternatives seem to be none (I can't find anything wrong with these link-chains). Solely the named dead-links seem to be correct (some packages seem to install them routinely). I think, the correct working of cruft is really important for verifying the consistence of a system - therefore here my frst bug-report. Thanks for reading and eventually working on it... Faunus -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cruft depends on: ii file 4.26-1 Determines file type using magic ii libc6 2.7-18 GNU C Library: Shared libraries cruft recommends no packages. cruft suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
