On 2/10/22 3:27 AM, Paul Gevers wrote:
On 10-02-2022 01:34, Chuck Zmudzinski wrote:
Do I need to file another bug in addition to #983357 to get this
problem listed on the bullseye (and also RC versions) d-i errata pages?
This is the most establish process, so yes, I suggest you just go
On 2/10/2022 3:27 AM, Paul Gevers wrote:
Hi Chuck,
On 10-02-2022 01:34, Chuck Zmudzinski wrote:
The problem as I see it is that the debian installer team is already
aware of the problem and has been aware of it for over six months
because #983357 is marked as affecting d-i. So I do not
On 2/9/2022 3:43 PM, Paul Gevers wrote:
Hi,
Subject: 983357: Why is it not mentioned in bullseye release notes /
installation guide?
For at least the release notes, because nobody asked the editors to
include it.
On 09-02-2022 21:04, Chuck Zmudzinski wrote:
However, this is a well-known
nstall
Bullseye in a Xen HVM domain to the workarounds that have been
identified for this problem that has not yet been fixed?
Regards,
Chuck Zmudzinski
On 8/26/2021 7:18 PM, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
severity 983357 important
Bug
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
doesn't have, stop it doing that.
b. Change the implem
On 8/26/2021 8:01 AM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ).� That seems like it
*might* be easier to change, so long as user-space doesn't have a
similar
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ). That seems like it
*might* be easier to change, so long as user-space doesn't have a
similar limit.
I looked into systemd/udev, and it seems to use a
On 8/25/2021 4:16 PM, Phillip Susi wrote:
Chuck Zmudzinski writes:
If it doesn't work, I am also willing to try approach a by patching
the Linux kernel xen-kbdfront driver by removing the for loops that
advertise those 654 keys. I tend to agree with Philip that this is
totally unnecessary
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
Text-based sysfs attributes are limited to a page, but udev receives
uevents through netlink, not sysfs.
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ). That seems like it
*might* be easier to chan
On 8/25/2021 12:45 PM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
��ï
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
doesn't have, stop it doing that.
b. Change the implem
On 8/24/2021 1:12 PM, Ben Hutchings wrote:
On Tue, 2021-08-24 at 10:56 -0400, Chuck Zmudzinski wrote:
On 5/24/2021 3:30 AM, Michael Biebl wrote:
Hi Phillip
Am 24.05.2021 um 06:19 schrieb Cyril Brulebois:
trigger to cold plug all devices. Both scripts are set -e. The Xen
Virtual Keyboard
to
update old device drivers so they are compatible with the
modern version? Does the Xen virtual keyboard need to be
managed by udev? Is there a simple way to disable incompatible
devices so udev ignores them?
Chuck Zmudzinski
on media is for.
Chuck Zmudzinski
14 matches
Mail list logo
