Bug#1037349: (no subject)

2023-07-21 Thread David Raison
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

2020-07-03 Thread David Raison
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

Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error

2019-09-11 Thread David Raison
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 actuall

Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error

2019-09-10 Thread David Raison
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 > ru

Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error

2019-09-09 Thread David Raison
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

Bug#822891: Acknowledgement (spamassassin: Net::DNS query result in spamassassin's do_dns_query returns garbage with libnet-dns-perl-0.81-2)

2016-04-28 Thread David Raison
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 s

Bug#822892: spamassassin: Net::DNS query result in sa-update's do_dns_query() returns garbage with libnet-dns-perl-0.81-2

2016-04-28 Thread David Raison
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. Executin

Bug#822891: spamassassin: Net::DNS query result in spamassassin's do_dns_query returns garbage with libnet-dns-perl-0.81-2

2016-04-28 Thread David Raison
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. Executin

Bug#818758: WordPress plugins depending on libphp-phpmailer > 5.2.10

2016-03-20 Thread David Raison
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 t

Bug#818758: WordPress plugins depending on libphp-phpmailer > 5.2.10

2016-03-20 Thread David Raison
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 b

Bug#765074: Confirming this issue

2014-10-23 Thread David Raison
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 Provid

Bug#754483: network-manager: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/4' failed in libnm-glib.

2014-10-13 Thread David Raison
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

Bug#573073: (no subject)

2010-05-11 Thread David Raison
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' Summ