Bug#1071369: python3-minimal: Installation in an emulated arm64 chroot is extremely slow from amd64 host

2024-05-17 Thread Steev Klimaszewski
Package: python3-minimal Version: 3.11.8-1 Severity: important User: de...@kali.org Usertags: origin-kali Dear Maintainer, Apologies for taking so long to track this down... but here we go. In Kali Linux, between 11 November 2023, and 30 November 2023, the installation time of an emulated

Bug#1070150: Loading of expl3.ltx **extremely** slow on emulated runs

2024-05-03 Thread Steev Klimaszewski
On Thu, 2 May 2024 14:47:41 -0600 Karl Berry wrote: > it looks like the LuaTeX binaries were compiled with "-g -O2", but > running "readelf" and "objdump" shows that they're stripped, so I > don't think that that's the issue here. > > FWIW, it's my understanding that what matters for

Bug#1070150: texlive-latex-extra: performance regression under emulation with 2023.20240207-1

2024-05-01 Thread Steev Klimaszewski
Hi Hilmar, On Wed, May 1, 2024 at 4:17 PM Preuße, Hilmar wrote: > > On 01.05.2024 22:46, Steev Klimaszewski wrote: > > Hi, > > > May 01 14:28:46 catcodes, registers, parameters, > > May 01 14:28:46 LaTeX2e <2024-06-01> pre-release-0 (develop 2024-5-1 > >

Bug#1070150: texlive-latex-extra: performance regression under emulation with 2023.20240207-1

2024-05-01 Thread Steev Klimaszewski
On 4/30/24 11:22 PM, Norbert Preining wrote: When running the hook with the 2023.20240207, this step takes around 3 hours. Ouch, that hurts. I'm guessing that this is related to enabling lua on aarch64 finally, but I'm not familiar at all with latex and how to get the smallest possible test

Bug#1070150: texlive-latex-extra: performance regression under emulation with 2023.20240207-1

2024-04-30 Thread Steev Klimaszewski
Package: texlive-latex-extra Version: 2023.20240207-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali Dear Maintainer, Since the 2023.20240207-1 release, there is a major performance regression when running the tex-common postinst hook in an arm64 chroot on amd64 host. This was

Bug#1068740: qemu-user-static: q-u-s > 8.1.3 fails to run amd64 binaries or docker containers on arm64 host

2024-04-11 Thread Steev Klimaszewski
On Wed, Apr 10, 2024 at 3:09 AM Michael Tokarev wrote: > > 10.04.2024 10:55, Steev Klimaszewski wrote: > > I wanted to try if 8.2.2, or 9.0 has a fix, but due to the time64 change, I > > cannot use > > packages from unstable or experimental at this time as Kali

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

2024-01-25 Thread Steev Klimaszewski
Does the cloud kernel even have wireless enabled? My understanding was the cloud kernels do not enable wireless.

Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

2023-10-04 Thread Steev Klimaszewski
Hello! This also affects Postgresql Updates as the timezone is written to the configuration file, so for example Debian testing recently upgraded from postgresql-15 to postgresql-16 and if you attempt to follow the instructions in /usr/share/doc/postgresql-common/README.Debian.gz you end up

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-10-02 Thread Steev Klimaszewski
Hi Yves, > Em seg., 2 de out. de 2023 às 09:25, Yves-Alexis Perez > escreveu: >> >> On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote: >> > Hi. >> > >> > Here are the logs with and without the "logind-check-graphical=false" >> > option. >> > >> > With this opinion, a

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-08-08 Thread Steev Klimaszewski
Hi Yves, I'm running into a very similar issue as the original submitter, however, when I'm running into it, I am *not* using the nVidia binary driver, but I am using a custom 5.15.44 kernel for a Raspberry Pi. What I found after digging for quite a while, was that, yes, downgrading to 1.26 would

Bug#651783: libpcap0.8: libpcap should be linked with libnl

2021-03-24 Thread Steev Klimaszewski
Hi Romain, It has been a "few" years since this bug has seen much action, and I would like to inquire about the possibility of enabling this now that libnl-1 and libnl-2 seem to be gone. There is a project called Nzyme (http://nzyme.org) and it depends on libpcap being able to put a device into

Bug#930395: u-boot-menu doesn't allow setting U_BOOT_MENU_LABEL

2019-06-11 Thread Steev Klimaszewski
Package: u-boot-menu Version: 3 Tags: patch The default file shows that we should be able to set the U_BOOT_MENU_LABEL option in /etc/default/u-boot however, in the actual u-boot-update script, U_BOOT_MENU_LABEL is hardcoded to "Debian GNU/Linux kernel" instead of allowing it to be different

Bug#919452: firmware-misc-nonfree: Please include the mediatek folder for mt7622u usb wifi devices

2019-01-15 Thread Steev Klimaszewski
Package: firmware-misc-nonfree Severity: wishlist As of the 4.19 kernel, support is available for mediatek mt7622u based wireless devices like the Alfa AWUS036ACM usb wireless device via the mt76x2u driver in the mainline kernel, however the firmware-misc-nonfree does not contain the

Bug#799939:

2016-04-21 Thread Steev Klimaszewski
I don't see 50 available for armhf/arm64 at all. It doesn't seem to be in the git repository either.

Bug#791644: xserver-xorg-video-modesetting doesn't support rotation

2015-07-06 Thread Steev Klimaszewski
Package: xserver-xorg-video-modesetting Version: 0.9.0-1 There is a patch in freedesktop git for the modesetting video driver, since the released version does not support rotation. This lead to quite a bit of frustration over here in that when you rotate via xrandr, the screen goes blank. It's

Bug#648325: Fwd: Bug#648325: dreamplug breakage

2013-02-13 Thread Steev Klimaszewski
Regards, Steev Steev Klimaszewski st...@genesi-usa.com Senior Software Engineer, Genesi USA, Inc.

Bug#459799: driftnet: doesn't build anymore

2008-02-15 Thread Steev Klimaszewski
Hi Christoph, I wrote you a while back, since I am the maintainer of driftnet in Gentoo. We also have a bug open about this - specifically, Gentoo bug #192627. http://bugs.gentoo.org/show_bug.cgi?id=192627 There was a flurry of activity earlier from some users, who have done their own