NoisyCoil writes:
> Package: wnpp
> Severity: wishlist
> Owner: NoisyCoil
> X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org,
> noisyc...@tutanota.com
> User: debian-...@lists.debian.org
> Usertags: arm64
>
> * Package name: widevine-installer
> Version : 0
Vincent Lefevre writes:
> What should happen if one has
>
> 192.134.164.161 via 192.168.1.1 dev eth0 src 192.168.1.13 metric 100
> 192.134.164.161 via 192.168.1.1 dev wlp0s20f3 src 192.168.1.14 metric 600
>
> and "ip route del 192.134.164.161" is done?
Thanks. That is indeed interesting. The
Vincent Lefevre writes:
> The documentation of "ip route delete" in the ip-route(8) man page is
> incorrect. The man page says:
>
> ip route delete
> delete route
> ip route del has the same arguments as ip route add, but their
> semantics are a bit different.
>
> Key values
Package: sendmail
Version: 8.18.1-6
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
Quoting from sendmail/conf.c:
#if _FFR_CLIENTCA
/*
** Allow to set client specific CA values.
** CACertFile: see doc/op.*:
** "The DNs of thes
Uwe Kleine-König writes:
> Given that this is a feature addition and the Debian kernel team doesn't
> have the manpower to carry many patches, I'd ask you to use a backports
> kernel which should include these patches soon.
Yes, makes sense to me, even though I guess that backport will have to
w
Package: src:linux
Version: 6.12.22-1
Severity: wishlist
File: /boot/vmlinuz-6.12.22-amd64
Dear Maintainer,
Hans de Goede excellent docs on https://hansdegoede.dreamwidth.org/29477.html
lists a few missing pieces in the ThinkPad X1 Carbon Gen 12 MIPI camera puzzle.
The first is a few ov08x40 sen
Package: rsync
Version: 3.2.7-1+deb12u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
This bug is new with the last security update.
$ cd /tmp
$ mkdir a
$ rsync -vrH a b
sending incremental file list
Internal hasht
Package: sendmail
Version: 8.18.1-6.1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
tl;dr; The _FFR_TLS_USE_CERTIFICATE_CHAIN_FILE build flag is required
See also https://bugzilla.redhat.com/show_bug.cgi?id=1565341
which has a more complete description of th
).
Problem reported by Dilyan Palauzo.
Link:
https://www.novabbs.com/computers/article-flat.php?id=1125&group=comp.mail.sendmail#1125
Signed-off-by: Bjørn Mork
---
cf/m4/proto.m4 | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/cf/m4/proto.m4 b/cf/m4/proto.m4
i
I'm no expert, but I believe this is a firmware problem you just have to
find some acceptable workaround for. It's not a kernel bug.
The differences you have found by comparing kernels and building you own
all boil down to the fact that Debian enables DMAR devices by
default. That's not a regress
Package: nullmailer
Version: 1:2.2+10~g7ed88a0-6
Severity: important
Tags: upstream
Dear Maintainer,
Some messages from nullmailer are rejected by my smart relay running Debian
sendmaili, after it was updated with
https://lists.debian.org/debian-lts-announce/2024/06/msg4.html
The faiing mess
"removing the symlink buys exactly nothing"
Please stop being hostile to users. This change is not justified. It
breaks my scripts. Please stop. Go fix a bug instead.
Bjørn
Leith Bade writes:
> Also, has a public version of the MT7981 Reference Manual been published?
> Google only finds me a pirated partial copy on Scribd. This will be needed
> to get all the memory locations for the DTS file, otherwise we will need to
> steal them from the DTS files in the Mediatek
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 w
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
Wa
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
sin
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
>
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:
>> > https://git.kernel.
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:
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:
Package:
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: N
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 o
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, Dupli
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 2
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 authentica
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
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 only
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 i
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 installe
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 rep
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
https://github.com/merbanan/rtl_433/commit/405df885
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
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 loc
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:
bj
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
>> > e506addeff844237d60545ef4f6141de
"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
> 0226009ce0f6089f9b31211f7a2
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 t
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, regardl
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
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
> usb_f
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 intel_iom
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 enabl
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.
>
> [...]
>
"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.
AF
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 f
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 of
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.
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
> [
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.
>>
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 controller.
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 properl
=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
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 m
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 t
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
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 vers
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?
>>>
>
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 generate
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
Th
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
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"
/dev/nvme0n1
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, bu
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 this
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 mode
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
> verified that
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 *symptom
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 / 82
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 pl
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
unrela
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 e
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 for i
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
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 an issue on IRC where G
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 chang
Горбешко Богдан 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
driver's data.
Bjørn
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 Lang: C
> Description : IrDA subsystem
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
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 bec
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 the
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 these are defaulting to
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 /us
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
> discussion I might have mis
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
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 Lin
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 foll
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
---
login-utils/sulogin.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/login-utils/sulogin.c b/login-utils/sulogin.c
index
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
---
login-utils/sulogin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/login
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 is
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 t
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 which to test.
The new code does the right thing on my /dev/sd?
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 |
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
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 Baytrail hardware.
>>
>> (I
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, but no IP packets
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'
>| model: '
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 repo
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
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 modem-only. cdc_ncm is not.
The reason y
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
>> GTK library. So w
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
- --
1 - 100 of 407 matches
Mail list logo
