Bug#1037349: (no subject)
I'm seeing the same issue after an upgrade from Debian 11 to Debian 12. Manually stopping and starting the service, as Eric suggests gets me a working audio-system. Please let me know if additional logs or configuration data may be useful to anyone looking into this.
Bug#964177: chromium: high cpu load and frequent crashes
We have a number of workstations running Debian 10 in our office and all have exhibited the same behavior after an upgrade to 83.0.4103.116-2 from buster-security. 100% CPU usage on all available cores for tabs and extensions even if there is no specific activity in them. I have no stack traces to offer, but can confirm that downgraded back to version 80 from stable gives us a usable browser again and I will happily supply whatever further information is required. signature.asc Description: OpenPGP digital signature
Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error
On 11/09/2019 17:30, Daniel Kahn Gillmor wrote: > > It sounds to me like you and David are saying this report is specific to > an interaction with 4.19.0-5 and wireguard 0.0.20190905-1, not that the > problem has to do with a generic upgrade path. > > But hm, maybe the 4.19.0-5 ABI wasn't actually stable? do either of you > (Matthew or David) know what version of 4.19.0-5 was actually running on > your system, vs. what version of linux-headers-4.19.0-5 you had > installed when it was built? That would be a useful datapoint. I have these. IMHO they haven't changed since: root@mazer:~# apt-cache policy linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-amd64: Installed: 4.19.37-5+deb10u2 Candidate: 4.19.37-5+deb10u2 Version table: *** 4.19.37-5+deb10u2 990 990 http://security.debian.org buster/updates/main amd64 Packages 100 /var/lib/dpkg/status
Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error
Thanks for looking into this, Daniel. On 10/09/2019 02:24, Daniel Kahn Gillmor wrote: > I note here that you're not running the latest kernel -- 4.19.0-5-amd64 > is not 4.19.0-6-amd64. is it possible that you don't have > linux-image-4.19.0-5-amd64 or its headers installed any more, despite > running that kernel? I did, and still do have the headers for the currently running kernel installed: linux-headers-4.19.0-5-amd64/stable,now 4.19.37-5+deb10u2 amd64 [installed,automatic] linux-headers-4.19.0-6-amd64/stable,now 4.19.67-2 amd64 [installed,automatic] However, I rebooted the machine since to boot into 4.19.0-6, re-installed wireguard-dkms and have a successful build this time. I could have tried that earlier but I'm not in a habit of rebooting my machine. Regards, David
Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error
Package: wireguard-dkms Version: 0.0.20190905-1 Severity: normal Dear Maintainer, I upgraded the wireguard-dkms package during a regular apt upgrade, which seems to have produced an invalid module: Unpacking wireguard-dkms (0.0.20190905-1) over (0.0.20190702-3) ... Setting up wireguard-dkms (0.0.20190905-1) ... Loading new wireguard-0.0.20190905 DKMS files... Reloading wireguard module... modprobe: ERROR: could not insert 'wireguard': Exec format error dpkg: error processing package wireguard (--configure): installed wireguard package post-installation script subprocess returned error exit status 1 -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-dkms depends on: ii dkms 2.6.1-4 ii perl 5.28.1-6 Versions of packages wireguard-dkms recommends: ii wireguard-tools 0.0.20190905-1 wireguard-dkms suggests no packages. -- no debconf information
Bug#822891: Acknowledgement (spamassassin: Net::DNS query result in spamassassin's do_dns_query returns garbage with libnet-dns-perl-0.81-2)
Due to a mail apparently not being as undeliverable as the mailserver claimed, this is a duplicate of #822892. I would prefer the other one to remain and this one to be closed since #822892 has more complete data. Thanks and sorry for the duplicate. signature.asc Description: OpenPGP digital signature
Bug#822892: spamassassin: Net::DNS query result in sa-update's do_dns_query() returns garbage with libnet-dns-perl-0.81-2
Package: spamassassin Version: 3.4.0-6 Severity: important Dear Maintainer, sa-update fails to detect rule updates due to do_dns_query() in the sa-update script not returning a numeric value but a weird result that does not match the /^(\d+)/ regex used when checking the value of $dnsV. Executing sa-update with the following command line displays the value that is being returned from $rr->rdatastr inside do_dns_query. $ sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys/ -vv --debug […] Apr 28 20:46:21.161 [4409] dbg: channel: metadata version = 1736402, from file /var/lib/spamassassin/3.004000/updates_spamassassin_org.cf DNS TXT query: 0.4.3.updates.spamassassin.org -> \# 8 0731373336343032 Currently, the expected output of the command should be 1736402 which is also what one gets with a TXT query using dig. Version 3.3.2 of spamassassin (on an oldstable installation) works fine, but uses a different function named do_txt_query. However, the contents of $rr->rdatastr in the 3.3.2 version are correct as well. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 pn libarchive-tar-perl ii libhtml-parser-perl 3.71-1+b3 ii libnet-dns-perl 0.81-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.2-3+deb8u4 ii perl-modules [libio-zlib-perl] 5.20.2-3+deb8u4 Versions of packages spamassassin recommends: ii gnupg 1.4.18-7+deb8u1 ii libio-socket-inet6-perl2.72-1 ii libmail-spf-perl 2.9.0-3 ii perl [libsys-syslog-perl] 5.20.2-3+deb8u4 ii sa-compile 3.4.0-6 ii spamc 3.4.0-6 Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-socket-ssl-perl 2.002-2+deb8u1 ii libmail-dkim-perl 0.40-1 ii perl [libcompress-zlib-perl] 5.20.2-3+deb8u4 ii pyzor 1:0.5.0-2 ii razor 1:2.85-4.1+b1 -- Configuration Files: /etc/default/spamassassin changed: ENABLED=0 OPTIONS="--create-prefs --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 /etc/spamassassin/local.cf changed: trusted_networks 31.22.xxx.yyy required_score 5.0 use_bayes 1 use_razor2 1 razor_timeout 15 use_pyzor 1 pyzor_timeout 15 ifplugin Mail::SpamAssassin::Plugin::Shortcircuit shortcircuit USER_IN_BLACKLIST on shortcircuit SUBJECT_IN_BLACKLISTon shortcircuit BAYES_99spam shortcircuit BAYES_00ham endif # Mail::SpamAssassin::Plugin::Shortcircuit -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#822891: spamassassin: Net::DNS query result in spamassassin's do_dns_query returns garbage with libnet-dns-perl-0.81-2
Package: spamassassin Version: 3.4.0-6 Severity: important Dear Maintainer, sa-update fails to detect rule updates due to do_dns_query() in the sa-update script not returning a numeric value but a weird result that does not match the /^(\d+)/ regex used when checking the value of $dnsV. Executing sa-update with the following command line displays the values that is being returned from $rr->rdatastr inside do_dns_query. $ sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys/ -vv --debug […] Apr 28 20:46:21.161 [4409] dbg: channel: metadata version = 1736402, from file /var/lib/spamassassin/3.004000/updates_spamassassin_org.cf DNS TXT query: 0.4.3.updates.spamassassin.org -> \# 8 0731373336343032 The expected output of the command should be 1736402 Version 3.3.2 of spamassassin (on an oldstable installation) works fine, but uses a different function named do_txt_query. However, the contents of $rr->rdatastr in the 3.3.2 version are fine as well. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 pn libarchive-tar-perl ii libhtml-parser-perl 3.71-1+b3 ii libnet-dns-perl 0.81-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.2-3+deb8u4 ii perl-modules [libio-zlib-perl] 5.20.2-3+deb8u4 Versions of packages spamassassin recommends: ii gnupg 1.4.18-7+deb8u1 ii libio-socket-inet6-perl2.72-1 ii libmail-spf-perl 2.9.0-3 ii perl [libsys-syslog-perl] 5.20.2-3+deb8u4 ii sa-compile 3.4.0-6 ii spamc 3.4.0-6 Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-socket-ssl-perl 2.002-2+deb8u1 ii libmail-dkim-perl 0.40-1 ii perl [libcompress-zlib-perl] 5.20.2-3+deb8u4 ii pyzor 1:0.5.0-2 ii razor 1:2.85-4.1+b1 -- Configuration Files: /etc/default/spamassassin changed: ENABLED=0 OPTIONS="--create-prefs --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" CRON=1 /etc/spamassassin/local.cf changed: trusted_networks 31.22.124.145 required_score 5.0 use_bayes 1 use_razor2 1 razor_timeout 15 use_pyzor 1 pyzor_timeout 15 ifplugin Mail::SpamAssassin::Plugin::Shortcircuit shortcircuit USER_IN_BLACKLIST on shortcircuit SUBJECT_IN_BLACKLISTon shortcircuit BAYES_99spam shortcircuit BAYES_00ham endif # Mail::SpamAssassin::Plugin::Shortcircuit -- no debconf information
Bug#818758: WordPress plugins depending on libphp-phpmailer > 5.2.10
On 20/03/16 15:21, Rodrigo Campos wrote: > On Sun, Mar 20, 2016 at 02:20:31PM +0100, David Raison wrote: >> Package: wordpress >> Version: 4.4.2+dfsg-1~bpo8+1 > > Please report bugs that you found in the packages to the backports mailing > list > and NOT to the Debian BTS, it says here: > > http://backports.debian.org/Instructions/#index6h2 All right, sorry for that. I had read the guidelines on reporting bugs, but not the backports instructions. David signature.asc Description: OpenPGP digital signature
Bug#818758: WordPress plugins depending on libphp-phpmailer > 5.2.10
Package: wordpress Version: 4.4.2+dfsg-1~bpo8+1 Upstream WordPress includes phpmailer as class-phpmailer.php in its wp-includes directory. In the Debian package for Jessie backports, this class is provided by the libphp-phpmailer package, currently in version 5.2.9 Wordpress 4.4.2 an even 4.4.1 before however, is shipping with version 5.2.14 of phpmailer which brings an extended API, for example the method getCustomHeaders(). Some WordPress plugins begin to rely on this API and will break (ending the entire PHP process with a Fatal Error) when WordPress has been installed from the Debian repositories rather than the upstream sources. I know libphp-phpmailer is being used from the repositories rather than included with the wordpress package for security reasons. I also do not have any recommendation on how to solve this issue. See also: https://wordpress.org/support/topic/broken-with-wp-441-which-ships-with-phpmailer-529 signature.asc Description: OpenPGP digital signature
Bug#765074: Confirming this issue
I can also confirm this issue for vagrant-1.6.5+dfsg1-1 in testing and unstable: kwisatz@mazer:~/1024/projects/foire$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'wheezy64' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: >= 0 ==> default: Adding box 'wheezy64' (v0) for provider: virtualbox default: Downloading: http://vagrant.1024.lu/wheezy64.box An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. The requested URL returned error: 400 Bad Request I can download the file just fine using curl/wget or a fully-fledged browser, or, as was previously said, using the upstream .deb: root@mazer:~# dpkg -i vagrant_1.6.5_x86_64.deb (Reading database ... 122977 files and directories currently installed.) Preparing to unpack .../vagrant_1.6.5_x86_64.deb ... Unpacking vagrant (1:1.6.5) over (1.6.5+dfsg1-1) ... Which works: ==> default: Adding box 'wheezy64' (v0) for provider: virtualbox default: Downloading: http://vagrant.1024.lu/wheezy64.box default: Progress: 87% (Rate: 3347k/s, Estimated time remaining: 0:00:12) BR, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754483: network-manager: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/4' failed in libnm-glib.
I experience the same issue than the OP on current testing (jessie) using systemd. In my case, this occurs when selecting a "Wired connection" in the Network-Manager applet. I'm using network-manager 0.9.10.0-3 and network-manager-gnome (for the nm-applet binary) 0.9.10.0-2 Connecting to a wireless network works fine. Here's the output of systemctl status. root@mazer:~# systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Fri 2014-10-10 18:14:35 CEST; 2 days ago Main PID: 8721 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─ 8721 /usr/sbin/NetworkManager --no-daemon └─30108 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-ee9a7... Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) Stage 2 of 5 (Device Configure) successful. Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) Stage 2 of 5 (Device Configure) complete. Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Oct 13 12:39:43 mazer NetworkManager[8721]: (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Oct 13 12:39:43 mazer NetworkManager[8721]: (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) failed for connection 'eth0' Oct 13 12:39:43 mazer NetworkManager[8721]: Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Oct 13 12:39:43 mazer NetworkManager[8721]: (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 13 12:39:43 mazer NetworkManager[8721]: (eth0): deactivating device (reason 'none') [0] The issue seems to be a configuration issue though. Editing the connections in the applet and setting the method in the "IPv4 Settings" for the wired connection to "Automatic (DHCP)" worked for me. It was initially set to "Ignore". best regards, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573073: (no subject)
I have the exact same problem here. I don't really know how services dependency is handled in debian yet but isn't there a way to specify that udev absolutely has to have finished (i.e. reported successful start) before cryptdisks gets called? cheers, David -- HaxoGreen 2010 - the Hackers' Summercamp in Luxembourg July 22nd till July 25th 2010, in Dudelange, Luxembourg Register Now: http://events.hackerspace.lu/camp/2010/ mailto:da...@hackerspace.lu xmpp:kwis...@jabber.hackerspaces.org mobile: +43 650 73 63 834 | +352 691 44 23 24 Wear your geek: http://syn2cat.spreadshirt.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
