Bug#1061269: nvidia-graphics-drivers: new upstream stable release 535.154.05
On Sun, Jan 21, 2024 at 09:33:16PM +, Simon McVittie wrote: > The beta 535.43.02 currently packaged in experimental has been superseded > by a new "production branch" version 535.154.05. > > [...] > > I've attempted to update the packaging in > <https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers/-/merge_requests/8>. > I don't have a testing/unstable machine with an Nvidia GPU, but it seems to > work OK on bookworm. As it happens, I've done (for my own use) pretty much identical changes (with one exception, discussed below), and am using the resulting driver with so far no problems on a Debian unstable machine with a GeForce 4070 SUPER series GPU. The one exception is -- according to the "Supported Products" tab of <https://www.nvidia.co.uk/Download/driverResults.aspx/217862/en-uk>, the 535.154.05 driver does support the newly released GeForce RTX 4070 SUPER, but Nvidia seem not to have updated the PCI IDs listed in the README.txt file in the driver download itself. I've manually patched in the PCI IDs of the 4070 SUPER, 4070 Ti SUPER and 4080 SUPER (respectively, 10DE:2783, 10DE:2705 and 10DE:2703). The other two GPUs are not listed even on the "Supported Products" tab (they had not been released yet at the time), and I don't have the corresponding hardware, so they may or may not work; the driver binary did seem to have references to all three IDs, though. To be honest, I don't exactly know what the PCI ID lists extracted by the packaging are being used for, so I don't know if updating them is strictly speaking required. Just wanted to give it the best possible chance of working. -- Heikki Kallasjoki
Bug#1057112: z80asm fails to accept the ?foo label test expression
Package: z80asm Version: 1.8-2 Severity: normal Tags: patch Dear Maintainer, The 1.8-2 version of z80asm fails to accept the `? foo` label test expression, despite being documented syntax in the man page. An example test case: $ cat > test.z80 if ?foo endif $ z80asm test.z80 test.z80:1: error: using undefined label foo test.z80:1: error: expression expected (not ) Looking at the source, this seems to be a case of a missing `++*p;` in the case handling the expression, and has been fixed upstream in the following commit: https://git.savannah.nongnu.org/cgit/z80asm.git/commit/?id=320cce79f8ec862fc5d750d05519113d741871b2 As far as I can determine, there have been no official upstream releases as such, but if possible, it would still be convenient to incorporate this fix in the Debian package as well. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages z80asm depends on: ii libc6 2.37-12 z80asm recommends no packages. Versions of packages z80asm suggests: pn openmsx -- no debconf information
Bug#1025171: zfs-dkms FTBFS against 6.0.0-5-amd64
There isn't enough detail to be sure, but this might be the same issue I hit on sid yesterday, so adding it here. It might also count as a dkms bug for all I know. In my case, zfs-dkms fails to build against either of my currently installed kernels (5.19.0-1-amd64, 6.0.0-5-amd64), but only after updating the package dkms to version 3.0.8-2 (from 3.0.8-1). This appears to be the result of the changes to the export-CC.patch: https://sources.debian.org/patches/dkms/3.0.8-2/export-CC.patch/ The 3.0.8-2 version adds the following commands to the prepare_build() function: export CC=$CC export MAKEFLAGS="--environment-overrides" I've verified that zfs-dkms builds fine for me if I temporarily comment out the second line from /usr/sbin/dkms. A build log for a failed attempt (with the flag present) is at: https://0x0.st/o0fu.txt The log also includes a dump of the environment variables at the start of the build, from a command I added to the dkms script. Digging a little deeper, it appears that when `--environment-overrides` is set, a number of required command-line options (in particular, an -I option to add /var/lib/dkms/zfs/2.1.6/build/include in the include search path) fail to be set. I didn't manage to trace why exactly that is, but you can see both a failing and a working example (for one object file) at: https://0x0.st/o0EC.txt FWIW, it seems like the build environment dkms uses inherits whatever was present in the environment when apt was called. If this is the case, then it feels to me including the `--environment-overrides` flag has potential to make things brittle. The effect of the flag is to: "Give variables taken from the environment precedence over variables from makefiles." Any arbitrary environment variables the user may have set for their own purposes might be unexpectedly overriding important variables from the Makefile(s).
Bug#753630: blender: Segfaults on UI actions (e.g. STL exporter options)
Package: blender Version: 2.70a-2+b2 Severity: normal Tags: upstream fixed-upstream Dear Maintainer, Blender has suddenly started segfaulting on some UI actions; most reproducibly, either of the two actions below: 1. Changing any setting of the Export/Stl dialog (such as scale or the apply modifiers option). 2. Expanding any node in the list of topics in the Input tab of File/User preferences... Blender's standard crash log included below. After a quick GDB session, I'm reasonably confident this is exactly same as upstream bug T40224 (https://developer.blender.org/T40224), which has a patch that seems to have been included in the recently released Blender 2.71, so presumably packaging that would also solve the issue. # Blender 2.70 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown bpy.ops.object.editmode_toggle() # Operator # backtrace blender() [0x8eb248] /lib/x86_64-linux-gnu/libc.so.6(+0x35480) [0x7f1d1d03c480] blender(MEM_lockfree_freeN+0x28) [0x11d7718] blender(RNA_path_full_property_py+0x72) [0x141ff22] blender(WM_prop_pystring_assign+0x9e) [0x90196e] blender() [0xa8da3c] blender() [0xa93ab4] blender() [0xa99b1f] blender() [0xa9bbb8] blender() [0x8f4543] blender() [0x8f48c8] blender(wm_event_do_handlers+0x223) [0x8f4c33] blender(WM_main+0x18) [0x8ed568] blender(main+0xd6f) [0x8d58ef] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1d1d028b45] blender() [0x8eacf4] -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blender depends on: ii blender-data 2.70a-2 ii fonts-droid1:4.3-3 ii libavcodec55 6:10.2-1 ii libavdevice54 6:10.2-1 ii libavformat55 6:10.2-1 ii libavutil536:10.2-1 ii libboost-date-time1.55.0 1.55.0+dfsg-2 ii libboost-filesystem1.55.0 1.55.0+dfsg-2 ii libboost-locale1.55.0 1.55.0+dfsg-2 ii libboost-regex1.55.0 1.55.0+dfsg-2 ii libboost-system1.55.0 1.55.0+dfsg-2 ii libboost-thread1.55.0 1.55.0+dfsg-2 ii libc6 2.19-4 ii libfftw3-double3 3.3.4-1 ii libfreetype6 2.5.2-1 ii libgcc11:4.9.0-7 ii libgl1-mesa-glx [libgl1] 10.2.1-2 ii libglew1.101.10.0-3 ii libglu1-mesa [libglu1] 9.0.0-2 ii libgomp1 4.9.0-7 ii libilmbase61.0.1-6 ii libjack0 [libjack-0.116] 1:0.124.1+20140122git5013bed0-3 ii libjpeg8 8d-2 ii libjs-jquery 1.7.2+dfsg-3 ii libopenal1 1:1.14-4 ii libopencolorio11.0.9~dfsg0-2 ii libopenexr61.6.1-7 ii libopenimageio1.4 1.4.10~dfsg0-2 ii libopenjpeg5 1.5.2-2 ii libpng12-0 1.2.50-1 ii libpython3.4 3.4.1-6 ii libsdl1.2debian1.2.15-9 ii libsndfile11.0.25-9 ii libspnav0 0.2.2-1 ii libstdc++6 4.9.0-7 ii libswscale26:10.2-1 ii libtiff5 4.0.3-9 ii libx11-6 2:1.6.2-2 ii libxi6 2:1.7.2-1 ii libxxf86vm11:1.1.3-1 ii zlib1g 1:1.2.8.dfsg-1 blender recommends no packages. Versions of packages blender suggests: pn yafaray-exporter none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753630: Segfaults on UI actions (e.g. STL exporter options)
Hi, One further note: applying the upstream T40224 NONNULL patch to the Debian 2.70a-2 sources does also fix the issue for me. -- Heikki Kallasjoki -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
