Bug#1058806: HP EliteBook 860 G9 (4C148AV)

Paul van der Vlis writes: > I've tried it again now and found in the bios an option "use Microsoft > UEFI CA key". This option was off, when I turn it on the Debian > installer did start with secure boot on. Yes, this is a problem with many modern PCs. Quite frustrating as the failure mode is

Bug#990298: conserver-server: console type 'ipmi' is not recognised.

Package: conserver-server Version: 8.2.7-2+b1 Followup-For: Bug #990298 Control: tags -1 patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I just created a pull request on salsa adding the requested IPMI support: https://salsa.debian.org/debian/conserver/-/merge_requests/3

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

Salvatore Bonaccorso writes: > AFAIK there is no commit upstream with fixes tag on that commit. But > Bjorn suspects that might be the suspicious commit introducing the > issue. Yes, I noticed that, so I could very well be wrong... But it stood out as the only change to any x86 IOAPIC stuff

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

Guy Durrieu writes: > > [ 0.117782] Kernel panic — not syncing: timer doesn’t work through > Interrupt- > remapped I0-APIC > [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 > Debian > 6.1.20-1 > [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming

Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others)

Chris Hofstaedtler writes: > * Diederik de Haas [221019 00:07]: >> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote: >> > it appears quite some new btusb hardware was released recently. >> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c: >> >

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

Hank Barta writes: > ** Kernel log: > [ 723.735217] mmc0: sdhci: Timeout: 0x | Int stat: 0x00018000 > [ 723.741743] mmc0: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 > [ 723.748270] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x0001 > [ 723.754797] mmc0: sdhci: Caps:

Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'

Hefee writes: >> Why do you insist on keeping broken packages in Debian? > > because pysrs is more than these two scripts - the core part is the python > library supporting handle SRS. Please read the subject and/or "Package" field before replying. This is what I reported as broken:

Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'

Hefee writes: > Control: severity -1 normal Why do you insist on keeping broken packages in Debian? >> # envfrom2srs >> Traceback (most recent call last): >> File "/usr/bin/envfrom2srs", line 14, in >> from ConfigParser import ConfigParser, DuplicateSectionError >> ModuleNotFoundError:

Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)

Cyril Brulebois writes: > Cyril Brulebois (2022-04-29): >> > I'll try and pinpoint when it broke using the various intermediary >> > versions: >> > >> > - 5.17~rc3-1~exp1 >> >> The first attempt was sufficient: it breaks as early as that version. > > Using the same base image as before, and

Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'

Package: pysrs-bin Version: 1.0.3-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, # envfrom2srs Traceback (most recent call last): File "/usr/bin/envfrom2srs", line 14, in from ConfigParser import ConfigParser,

Bug#1008828: python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util'

Package: python3-spf-engine Version: 2.9.2-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Installing pyspf-milter with default dependencies and settings results in # journalctl -u pyspf-milter - -- Journal begins at Sat

Bug#1006729: nullmailer: Add "AUTH EXTERNAL" option for certificate authentication

Package: nullmailer Version: 1:2.2-3 Severity: wishlist Tags: upstream patch Forwarded: https://github.com/bruceg/nullmailer/pull/80 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please implement AUTH EXTERNAL so that nullmailer can be used against smarthosts using client certificate

Bug#1002465: /boot/vmlinuz-5.10.0-10-amd64: btusb: CSR clone fails with "debugfs: File 'dut_mode' in directory 'hci1' already present!"

Package: src:linux Version: 5.10.84-1 Severity: normal File: /boot/vmlinuz-5.10.0-10-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just got a couple of CSR clones of a type I haven't tried before. Unfortunately they fail with the error message: "debugfs: File 'dut_mode' in directory

Bug#998308: /usr/bin/drill: drill does not respect the /etc/resolv.conf nameserver order

Package: ldnsutils Version: 1.7.1-2+b1 Severity: normal File: /usr/bin/drill -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NetworkManager will add nameservers for all connected links to /etc/resolv.conf using the same priority given to the associated default routes. Name servers are often

Bug#998069: openssh-server: sshd_config(5) documentation of ListenAddress refers to OpenBSD only option "rdomain"

Package: openssh-server Version: 1:8.4p1-5 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The sshd_config(5) manual page refers to an optional "[rdomain domain]" qualifier for ListenAddress, with a pointer to the non-existing rdomain(4) manual page for further informaion. This

Bug#992997: milter-greylist: segfault in libGeoIP

Sudip Mukherjee writes: > I just updated the package to latest 4.6.4, can you please try with that > and check if you still get the same problem. If you still the same problem > the a coredump or some way to reproduce the problem will be needed. Thanks. I've not seen the problem since I

Bug#990868: lenovo T460 Shutdown Problem

Faustin Lammler writes: > Hi! > I seem to have the same problem on my T460s and it is impossible to > suspend the laptop (lid close or systemctl suspend). > > As far as I can remember, the problem appeared with kernel 5 branch (bpo > on buster). > > At that time I did not wanted to open a bug

Bug#992723: rtl-433: spewing debug log in a tight loop on USB errors

Package: rtl-433 Version: 20.11-1 Severity: normal Dear Maintainer, This version of rtl-433 will spew out two log lines in a very tight loop after some USB cable issues. This is https://github.com/merbanan/rtl_433/issues/1581 which was fixed by

Bug#992400: fetchmail: segfault with specific .fetchmailrc

Package: fetchmail Version: 6.4.16-4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, fetchmail started SEGFAULTing after upgrading from buster to bullseye. This is an example config which causes this: test@canardo:~$ cat .fetchmailrc set invisible defaults

Bug#987778: texlive-latex-extra: fails to declare dependency on libspreadsheet-parseexcel-perl

Package: texlive-latex-extra Version: 2020.20210202-3 Severity: serious Justification: Policy 3.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libspreadsheet-parseexcel-perl is required to run the exceltex binary, but is not declared as a dependency. bjorn@miraculix:~$ exceltex Can't

Bug#977804: xscreensaver: systemd integration conflicts with existing Xsession based activation

Package: xscreensaver Version: 5.44+dfsg1-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The latest xsreensaver is broken, failing to start on a system where it was configured to start without the systemd unit. I endend up with a zombie instead of the expected daemon:

Bug#965074: Patches to make multicast proccesing on CDC NCM drivers

Santiago Ruano Rincón writes: > El 02/09/20 a las 17:45, Greg KH escribió: >> On Wed, Sep 02, 2020 at 03:27:28PM +0200, Santiago Ruano Rincón wrote: >> >> > This: >> > >> > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 >> > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 >> >

Bug#969365: USB-C dock lacks multicast Ethernet functionality (so IPv6 is broken)

"Santiago R.R." writes: > The patches proposed by Miguel Rodríguez have been merged upstream, and > are part of 5.9-rc1 now. C.f. commits: > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 > e506addeff844237d60545ef4f6141de21471caf >

Bug#969144: systemd: serial-getty@.service should support 57600 baud

Package: systemd Version: 241-7~deb10u4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, My BIOS provides pre-boot access to the system over serial, and sets the port up for 57600. So I have configured the client (conserver) to use that speed. This has happened

Bug#967115: refind: unexpected and unwanted boot order changes on upgrade

Package: refind Version: 0.12.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The postinst script unconditionally deletes and recreates the existing NVRAM entry for rEFInd on upgrades if "install_to_esp" is enabled. This moves the rEFInd entry first in the boot order,

Bug#965074: cdc_ncm: ethernet multicast traffic is filtered out

FWIW, I made an attempt resubmitting these patches since it looked like I was part of the problem back in 2018 ;-) I'd CCed you, and would appreciate it if you could test the series. I don't have any cdc_ncm devices with multicast filter support AFAIK. Bjørn

Bug#964480: linux: ath9k (USB) broken in upstresm linux 5.7.3 after commit 6602f080cb

Juergen writes: > In 5.7 reverting 6602f080cb is known to fix the problem, but it hasn't yet > been > analyzed by an expert, therefore I'd like to report my findings to perhaps get > an expert interested:-) > > At least one problem is in function ath9k_hif_usb_reg_in_cb(). In the call to >

Bug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure

Package: src:linux Followup-For: Bug #949020 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just confirming that this issue is still present, causing a terrible user experience when upgrading from Buster to Bullseye on a Lenovo laptop. Verified on a 4th Gen Thinkpad X1 Carbon. Setting

Bug#961459: linux-signed-arm64: option that might support raspberry pi 4 usb

Rob Browning writes: > If I get a chance and figure out how, I can try to build a local kernel > with that option and test it, or I could fairly quickly test any version > uploaded somewhere like experimental. I have done this, and verified that the USB ports work if CONFIG_PCIE_BRCMSTB is

Bug#961130: ethtool can read DOM values

Ben Hutchings writes: > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: >> Package: ethtool >> Version: 1:4.19-1 >> Severity: important >> The command ethtool -m is unable to read the transceiver DOM values. > > Again, this is a driver or hardware issue, not a bug in ethtool. > > [...]

Bug#960702: ethtool -m values change when output is redirected

"Yannis Aribaud" writes: > Package: ethtool > Version: 1:4.19-1 > Severity: important > I'm facing a very strange behavior. The command ethtool -m report the > transceiver DOM values correctly, but when the command output is redirected > to an other program, values change to somthing else.

Bug#960390: x86_64: No serial port output

Geert Stappers writes: > Virtual Machines (Qemu, KVM, Xen, ... ) and OCI containters ( "Docker > images") are the new serial port only computers. > > In other words: There are many servers without video hardware. (Un)fortunately, depending how you look at it, running a remote qemu machine with

Bug#960390: x86_64: No serial port output

john doe writes: > Unless I'm missing something, it does work for me with something like: > > -nographic -cdrom *.iso -kernel kernel-path -append > "console=ttyS0,115200n8 ..." > > > '-serial' might also be needed. Try repeating that when installing on bare metal without a monitor. The lack

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Bjørn Mork writes: > Note that I found that I had to remove the cma=xx option raspi-firmware > wants to put into the cmdline.txt. This messed up mailbox access to the > firmware, and took several drivers/devices with it in the fall. Don't > think the SD card was one one them. But

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Lucas Nussbaum writes: > I am trying to boot a RPI4 with the 5.6 kernel from unstable, but it > fails to boot (while it worked with 5.5 from unstable). > > What I'm seeing with 5.5, but not with 5.6, is: > [4.500333] mmc1: SDHCI controller on fe34.emmc2 [fe34.emmc2] > using ADMA > [

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Lucas Nussbaum writes: > On 09/05/20 at 20:44 +0200, Bjørn Mork wrote: >> Please enable CONFIG_PCIE_BRCMSTB on arm64. >> >> The Raspberry Pi 4 has a VL805 xhci controller connected to the >> PCIe bus on the SoC. All USB ports are connected to this controller. >>

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Package: src:linux Version: 5.6.7-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Please enable CONFIG_PCIE_BRCMSTB on arm64. The Raspberry Pi 4 has a VL805 xhci controller connected to the PCIe bus on the SoC. All USB ports are connected to this

Bug#951744: raspi-firmware: current cmdline defaults prevents RPi4 from working

Package: raspi-firmware Followup-For: Bug #951744 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Adding this info here since it is really about having a more flexible cmdline generator, with fewer hardcoded defaults. The current CMA=64M prevents the 4GB RPi4 from working

Bug#949370: Info received (Bug#949370: Acknowledgement (spamass-milter: synthesized received header sometimes use the sendmail start time instead of current time))

=20Mork?= Date: Tue, 21 Jan 2020 13:04:55 +0100 Subject: [PATCH] milter: update macros before calling milter_envrcpt MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Bjørn Mork --- sendmail/srvrsmtp.c | 6 -- 1 file changed, 4 insertions

Bug#949370: Acknowledgement (spamass-milter: synthesized received header sometimes use the sendmail start time instead of current time)

Based on my understanding of the milter API docs, I believe this is a spamass-milter bug aided by confusing sendmail docs and API. I looked at the sendmail code and did some additional milter tests. Both confirm the root cause: The "$b" macro is not necessarily updated the when the first envrcpt

Bug#949370: Acknowledgement (spamass-milter: synthesized received header sometimes use the sendmail start time instead of current time)

Control: clone -1 -2 Control: reassign -2 sendmail Control: severity -2 normal Control: retitle -2 sendmail: milter expansion of "$b" macro is unreliable Control: found -2 8.15.2-14~deb10u1 The underlying bug appears to be in sendmail. But I'm keeping the spamass-milter bug open since the use of

Bug#949370: spamass-milter: synthesized received header sometimes use the sendmail start time instead of current time

Package: spamass-milter Version: 0.4.0-1+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I recently became aware that spamassassin reports a large number of false DATE_IN_FUTURE_96_Q positives. Being a pretty good spam indicator, this test has a relatively

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Pierrick CHANTEUX writes: > This bug resulted in complete system breakage and I couldn't boot > anymore (systemd failing to load Kernel modules). I can guarantee that > this isn't only cosmetic. > > I believe this isn't related to initramfs-tools, because downgrading > kmod and libkmod2 from

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Bjørn Mork writes: > Marco d'Itri writes: > >> Control: severity -1 normal >> Control: tags -1 patch >> Control: reassign -1 initramfs-tools >> >> On Jan 06, crvi wrote: >> >>>* What outcome did you expect instead? >>> >>

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Marco d'Itri writes: > Control: severity -1 normal > Control: tags -1 patch > Control: reassign -1 initramfs-tools > > On Jan 06, crvi wrote: > >>* What outcome did you expect instead? >> >> Successful ramfs generation > Do you have any reason to believe that the initrfamfs was not

Bug#903161: changing socket permissions seems to be the best solution for now

I tried the different methods suggested in this bug report, but had no success with any of them. Using stats_writer_socket_path= causes "doveadm index" to fail with bjorn@canardo:~$ doveadm index -q -u bjorn INBOX.Spam doveadm(bjorn): Error: net_connect_unix() failed: Connection refused

Bug#939753: systemd fails to deactivate swap on reboot

Michael Biebl writes: > I'd say fixing up your GPT information is what you should do. Sure. If I only knew how. What's wrong with my GPT? Bjørn

Bug#939753: systemd fails to deactivate swap on reboot

Michael Biebl writes: > Control: tags -1 moreinfo > > Can you attach the output of blkid please. canardo:/tmp# blkid /dev/nvme0n1: PTUUID="397e5dc0-a3b9-42b1-a964-55fa71c8f070" PTTYPE="gpt" /dev/nvme0n1p1: UUID="0759-95BE" TYPE="vfat" PARTUUID="6750d885-492b-4e6b-9ee1-2db6762b28e2"

Bug#935589: cdimage.debian.org: xserver-xorg-input-synaptics package missing in xfce-CD-1 iso

Julien Cristau writes: > Users shouldn't have to think about it. It's our job to make our > install process do the right thing in the first place. Well, it doesn't, and most users are aware of that. DTRT is hard. It's almost impossible when hardware is part of the equation. Debian is good,

Bug#935589: cdimage.debian.org: xserver-xorg-input-synaptics package missing in xfce-CD-1 iso

Julien Cristau writes: > The synaptics Xorg driver is obsolete and should not be installed by > default. Maybe the xserver-xorg-input-synaptics package could hint about this and point to xserver-xorg-input-libinput? As it is now, I don't understand how anyone is supposed to figure out that

Bug#926261: closed by Ben Hutchings (Re: Bug#926261: linux-image-4.19.0-4-amd64: fan continiously spinning above 6900 RPM after resume on lenovo carbon x1 thinkpad with isa adap

Not going to argue against this being a firmware bug. I'm sure that is true. But Linux must deal with buggy firmware. Else it cannot run on any real system :-) And this bug (or at least the bad effect on Linux) is a regression introduced by commit c3a696b6e8f8 ("ACPI / EC: Use busy polling

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Bjørn Mork writes: > Given this, there is an extremely suspicious commit added in v4.18.20: > > 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for > gen4/gen5") > > I do have an old laptop with an affected chipset generation, and > verifie

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Ben Hutchings writes: > On Mon, 2018-12-03 at 23:08 +0100, TS wrote: > >> Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to >> unstable. This issue here seems not to be wide spread, or reproducible? > > Hard to tell. There are a few people that reported the same

Bug#906593: Crash with intel 8265

Hugo Mercier writes: > It seems I have a similar problem on a Thinkpad X1 4th generation. So, since I also run Debian sid on one of those, and haven't got any issues, I thought I would compare firmware versions etc > $ lspci -v > 04:00.0 Network controller: Intel Corporation Wireless 8265 /

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

Phil writes: > Hi, I hope you're all doing well. > > Shall we/I maybe reopen a new issue? I believe so. I am almost sure we fixed the original memset BUG in cdc_ncm_fill_tx_frame. Or at least one of them... So you are probably seeing another issue if you still have problems with that fix in

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

This issue should be fixed by commit 49c2c3f246e2 ("cdc_ncm: avoid padding beyond end of skb") which has been backported to v4.17.3, v4.16.18 and v4.14.52. Please check again with one of those kernel versions (or newer). I see now that the fix doesn't apply cleanly to v4.9 stable due to

Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

Samuel Thibault writes: > It's a matter of someone fixing the code. It seems Igor Scheller is > happy to work on it, he just needs a way forward, not being only told > that what is currently there is nonsense. Well, using fe80::1 as default gateway would not be a problem if it weren't for the

Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

Samuel Thibault writes: > Bjørn Mork, le mar. 12 juin 2018 13:30:39 +0200, a ecrit: >> But this will: >> >> frtest3:~# ip route add 2001:db8:f00::1/128 dev eth1 > > So this is a route, which can be checked for. No, it is a route you can safely add. Checking f

Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

Samuel Thibault writes: > Bjørn Mork, le mar. 12 juin 2018 10:52:30 +0200, a ecrit: >> Huh? What is this? There is no "gateway must be in subnet" requirement >> in IPv6. The gateway must only be reachable, which means that you must >> be able to resolve the

Bug#897572: urandom hang in early boot

Ben Hutchings writes: > On Tue, 2018-05-08 at 11:12 +1200, Ben Caradoc-Davies wrote: >> On 08/05/18 05:34, Laurent Bigonville wrote: >> > Apparently it's also happening for other applications that are starting >> > later during the boot like GDM. >> > Somebody has reported

Bug#897408: python3-attr: upstream changelog is missing

Package: python3-attr Version: 17.4.0-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is obviously not very useful without including CHANGELOG.rst: bjorn@miraculix:~$ zcat /usr/share/doc/python3-attr/changelog.gz .. include:: ../CHANGELOG.rst If the real upstream

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

Горбешко Богдан writes: > vboxdrv(O) > binder_linux(O) > ashmem_linux(O) Can you reproduce the problem without these modules loaded? AFAICS there is no way the only memset in cdc_ncm can be called with crashing input parameters. Unless something is scribbling over the

Bug#891502: ITP: irda-dkms -- IrDA subsystem and device drivers

Christopher Schramm writes: > Package: wnpp > Severity: wishlist > Owner: Christopher Schramm > > * Package name: irda-dkms > Version : 0.1 > * URL : https://github.com/cschramm/irda > * License : GPL > Programming

Bug#875851: emacs25: gnus + epg needs gpgsm for S/MIME verfication

Package: emacs25 Version: 25.1+1-4 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please add a depends or recommends on gpgsm. Opening an S/MIME signed email in gnus will result in the rather cryptic message epg-context--make: GPG error: "no usable configuration", CMS if

Bug#871639: NULL pointer dereference in reset_common_ring+0xc3/0x170 [i915]

Package: src:linux Version: 4.9.30-2+deb9u3 Severity: normal File: /boot/vmlinuz-4.9.0-3-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've been having issues with the i915 driver ever since I got this Skylake laptop. The GPU is hanging every now and then. But the error handling has

Bug#864878: /boot/vmlinuz-4.9.0-3-amd64: Please enable CONFIG_HPFS_FS as a module

Package: src:linux Version: 4.9.30-2 Severity: wishlist File: /boot/vmlinuz-4.9.0-3-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, it's hard to claim this is important to me since I haven't noticed it was gone until today. But could you please re-enable CONFIG_HPFS_FS unless

Bug#859641: Please increase USBIP_VHCI_HC_PORTS and USBIP_VHCI_NR_HCS

Steve McIntyre writes: > In Linaro we're making a lot of use of USB-over-IP devices these days > for our testing lab. We've hit a (very small!) limit defined in kernel > config for the number of virtual host controllers and the ports > allowed per controller. > > Currently

Bug#852802: dnsrecon: please remove misleading mDNS refererence from package description

Package: dnsrecon Version: 0.8.9-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I installed dnsrecon for its advertised "Enumerate Common mDNS records in the Local Network" feature. After looking around for it, I finally found this: bjorn@miraculix:~$ zgrep -i mdns

Bug#846002: Debian Installer Stretch RC 1 release

Andreas Tille writes: >> Since this is still an open discussion in #846002, I would have >> preferred if you would not try to force your own preference here before >> the CTTE made its decision. > > While I'm not sure whether its a personal preference or whether some >

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

OK, this looks like a known v4.8 stable regression, caused by the backport of commit 5d41ce29e3b9 ("net: icmp6_send should use dst dev to determine L3 domain") introduced in v4.8.10. Should be fixed by commit 79dc7e3f1cd3 ("net: handle no dst on skb in icmp6_send") as soon as Debian moves to v4.9

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

The first crash dumps were from my console, which was overwritten by the later boot process and therefore incomplete. Should have dug up the complete logs from the console server in the first place.. Anyways, here are the complete stack traces: [509753.194825] ixgbe :02:00.0 uplink: NIC

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

Package: src:linux Version: 4.8.11-1 Severity: important File: /boot/vmlinuz-4.8.0-2-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I just had two crashes in a row in icmp6_send while rebooting a switch in the other end of one of the br0 bridge ports. Both crash dumps

Bug#846112: Acknowledgement (/sbin/sulogin: sulogin does not exit on first Control-D)

reated as a password to be verified, and will end up with Login incorrect and a repeated password prompt. (unless the root password happened to be Control-D :) Signed-off-by: Bjørn Mork <bj...@mork.no> --- login-utils/sulogin.c | 1 + 1 file changed, 1 insertion(+) diff --git a/login-utils/sulog

Bug#846107: Acknowledgement (/sbin/sulogin: sulogin with timeout fails, causing boot failure if SULOGIN=yes)

e: Mon, 28 Nov 2016 16:27:19 +0100 Subject: [PATCH 1/2] sulogin: make --timeout actually time out MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Bjørn Mork <bj...@mork.no> --- login-utils/sulogin.c | 2 +- 1 file changed, 1 ins

Bug#846112: /sbin/sulogin: sulogin does not exit on first Control-D

Package: util-linux Version: 2.29-1 Severity: important File: /sbin/sulogin -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Must press Control-D twice to exit sulogin. The first attempt to press Control-D will erronously report 'Login incorrect'. The second attempt succeeds, *unless* sulogin

Bug#846107: /sbin/sulogin: sulogin with timeout fails, causing boot failure if SULOGIN=yes

Package: util-linux Version: 2.29-1 Severity: important File: /sbin/sulogin -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 sulogin does not exit after timeout expires. This is serious for any remote system configured with SULOGIN=yes since it means that manual intervention is required to boot

Bug#843000: refind: fails to install on NVMe

Rod Smith writes: > On 11/03/2016 01:29 PM, Tianon Gravi wrote: >> On 3 November 2016 at 10:28, Tianon Gravi wrote: >>> On 3 November 2016 at 10:19, Rod Smith wrote: Note, however, that I have no NVMe or similar devices on

Bug#843000: refind: fails to install on NVMe

Package: refind Version: 0.10.4-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The refind-install script makes bogus assumptions: InstallDisk=`grep "$InstallDir" /etc/mtab | cut -d " " -f 1 | cut -c 1-8` PartNum=`grep "$InstallDir" /etc/mtab | cut -d " " -f 1

Bug#824981: EM7455 in Thinkpads should work now

With these versions we should now have all parts of the puzzle in place: linux-image-* 4.7.2-1 modemmanager 1.6.0-1 Bjørn

Bug#832458: linux-image-4.6.0-0.bpo.1-amd64: Please enable SND_SOC_INTEL_BYT_MAX98090_MACH, needed for some Baytrail devices

Ben Hutchings writes: > On Mon, 2016-07-25 at 13:10 -0600, Ivan M wrote: >> Package: src:linux >> Version: 4.6.3-1~bpo8+1 >> Severity: normal >> >> Dear Maintainer, >> >> Please enable CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m - it is >> necessary for audio on certain

Bug#828820: Dell DW5811e should be working with the latest MM and supporting packages

Luc Bégault writes: > The dump file is attached, everything looks fine except I don't > receive any datagrams. tcpdump on the interface only shows outgoing > packets without any answer. This is the exact symptoms caused by the firmware issue I mentioned. Connection looks fine,

Bug#828820: Dell DW5811e should be working with the latest MM and supporting packages

Luc Bégault writes: > here is the output of: > # mmcli -m /org/freedesktop/ModemManager1/Modem/0 > > /org/freedesktop/ModemManager1/Modem/0 (device id > 'abcc5d4e7daab7bd404d58f7ca9c6e799fe47155') > - > Hardware | manufacturer: 'Dell' >

Bug#790109: Please test with sid packages if possible

Hello, I asked ModemManager upstream about this. The problem is in the libqmi library, and it is *supposed* to be fixed in libqmi version 1.12. I cannot verify this myself though, as I don't think I have an old enough Gobi device (found nothing pre Gobi 2k in my box of modems). As your bug

Bug#828820: Dell DW5811e should be working with the latest MM and supporting packages

Hello, I noticed this bug which I believe should be resolved. In case it isn't I'd very much like to have some details. I believe the DW5811e might be configured for multiple alternative USB configurations, which means that we cannot necessarily guess with drivers you are using. Could you do a

Bug#833918: linux: Please enable cdc_ncm and cdc_mbim in d-i to support 'Dell 4-in-1 Adapter' Ethernet

John Paul Adrian Glaubitz writes: > This adapter uses the cdc_ncm/cdc_mbim kernel modules which are currently > being disabled for > debian-installer as those were suspected to be used by modems only [2], which > is not the > case, however. cdc_mbim is

Bug#830624: ITP: xplayer -- Simple media player based on GStreamer.

Emilio Pozuelo Monfort writes: > On 09/07/16 22:31, Franciscarlos Santos Soares wrote: >> Hi Emilio! >> >> Thank you for contacting us. In fact, like independent application of any >> DE, >> but they were compatible with the traditional look of windows and based on >> the

Bug#824795: smartmontools: remove obsolete /usr/share/man/man8/update-smart-drivedb.8.gz man page

Package: smartmontools Version: 6.4+svn4214-1 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looks like this was left over when removing the update-smart-drivedb script: bjorn@nemi:~$ dpkg -L smartmontools|grep update /usr/share/man/man8/update-smart-drivedb.8.gz Bjørn - --

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

Ben Hutchings <b...@decadent.org.uk> writes: > On Wed, 2016-04-20 at 20:51 +0200, Bjørn Mork wrote: >> Ben Hutchings <b...@decadent.org.uk> writes: >> >> > >> > Our upstream is linux-firmware.git, not a hundred vendor web sites. >> > Fran

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

Ben Hutchings writes: > Our upstream is linux-firmware.git, not a hundred vendor web sites. > Frankly I'm quite sick of the iwlwifi maintainers thinking their > firmware is special and should be distributed differently from every. Huh? I always though they sent a pull

Bug#821005: libnet-dns-perl: runtime dependency on Net::DNS::SEC::Private cannot be fulfilled

Package: libnet-dns-perl Version: 1.05-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As has been noted in bug #820332, this version conflicts with libnet-dns-sec-perl because all the DNSSEC RR classes have been transferred to libnet-dns-perl. There is still a runtime

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Ben Hutchings <b...@decadent.org.uk> writes: > On Mon, 2016-04-11 at 09:55 +0200, Bjørn Mork wrote: >> Ben Hutchings <b...@decadent.org.uk> writes: >> > >> > On Sun, 2016-04-10 at 11:15 -0700, Vagrant Cascadian wrote: >> > > >> > &

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Ben Hutchings writes: > On Sun, 2016-04-10 at 11:15 -0700, Vagrant Cascadian wrote: >> It works for the most part, but floods syslog with messages: >> >> [501966.870273] net_ratelimit: 35702 callbacks suppressed >> [501966.875438] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

Ben Hutchings <b...@decadent.org.uk> writes: > On Wed, 2016-04-06 at 16:51 +0200, Bjørn Mork wrote: >> Antonis Christofides <anth...@itia.ntua.gr> writes: >> >> > >> > Apr  5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel >&g

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

Antonis Christofides writes: > Apr 5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel > paging request at eba40a800380 > Apr 5 13:32:47 thames kernel: [86003.994005] IP: [] > kfree+0x76/0x220 .. > Apr 5 13:32:47 thames kernel: [86003.994679] Call

Bug#820061: linux-image-amd64: kernel hangs since debian 8.4

Benoît Tonnerre writes: > Apr 4 18:52:55 pci003-01 kernel: [ 79.329223] RIP: > 0010:[] > [] radeon_fence_ref+0xd/0x50 [radeon] > Apr 4 18:52:55 pci003-01 kernel: [ 79.330192] RSP: 0018:88003639fb18 > EFLAGS: 00010292 > Apr 4 18:52:55 pci003-01 kernel: [ 79.331154]

Bug#819703: xscreensaver: "This version of XScreenSaver is very old! Please upgrade!" message

Package: xscreensaver Version: 5.34-1 Followup-For: Bug #819703 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why is this a bug? Is there something not working? AFAICS, this is a documented feature. Whether you like the feature or not is irrelevant. In any case, how the heck can anyone justify

Bug#814785: ifupdown: fails to bring up "wpa-roam" interfaces on boot

Package: ifupdown Version: 0.8.10 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There appears to be a bit of a chicken-n-egg problem with "wpa-roam" type interfaces, and any other type of interface which need ifup before a carrier can be detected:

Bug#813381: fonts-wine: freetype_SelectFont can't find a single appropriate font

Jens Reyer writes: > prefix and update to 1.8-7 or 1.8.1-1. I also don't get the fixme > warnings (although enabled in WINEDEBUG). > > But other Windows applications indeed also miss the text in their > windows. Creating the link doesn't help though for that. Thanks for

Bug#813381: [pkg-wine-party] Bug#813381: fonts-wine: freetype_SelectFont can't find a single appropriate font

Michael Gilbert <mgilb...@debian.org> writes: > On Mon, Feb 1, 2016 at 9:21 AM, Bjørn Mork wrote: >> Running e.g. winefile with WINEDEBUG=warn+all results in lots of >> warnings like this: >> >> fixme:font:freetype_SelectFont can't find a single appropriate fo

Bug#812575: udev: predictable network device names fails for USB devices without a permanent hw address

Michael Biebl writes: >> But even with this in place, the new logic should be prepared for >> duplicate mac addresses. There are plenty of USB devices with non- >> unique mac addresses out there. It's more of a rule than an exception >> for GSM/LTE modem devices... > > Please

  1   2   3   4   >