Bug#1076478: ffmpeg hevc_vaapi and h264_vaapi stuck at q=-0.0
Package: ffmpeg
Version: 7:7.0.1-2
Actually begins at least Version: 7:6.1.1-4+b4
using any arguments for hevc_vaapi, encoding q stuck at 0, resulting in
extremely high bitrate and huge files.
example command
```
q=32
ffmpeg -i ${v} -vaapi_device /dev/dri/renderD128 -vf
'scale=1920:1080,pad=1920:1088:0:4,format=nv12,hwupload' -c:v hevc_vaapi
-b_depth 2 -async_depth 8 -compression_level 13 -qp ${q} -y
${v%.*}.vaapi.qp${q}.bd2.mp4
```
output
```
...
frame=26500 fps=204 q=-0.0 Lsize=20448421KiB time=00:18:23.47
bitrate=151805.4kbits/s dup=16 drop=5 speed= 8.5x
```
**vainfo**
```
libva info: VA-API version 1.22.0
libva info: Trying to open
/usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 24.1.3-2 for AMD Radeon 780M
(radeonsi, gfx1103_r1, LLVM 17.0.6, DRM 3.57, 6.9.8-amd64)
vainfo: Supported profile and entrypoints
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
VAProfileAV1Profile0: VAEntrypointVLD
VAProfileAV1Profile0: VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc
```
Bug#1076102: xfce4-screenshooter unable to copy to clipboard after a while
Package: xfce4-screenshooter Version: 1.10.5-1 Running xfce desktop for a long while, by guessing, 1day or longer, with or without suspend/wakeup. Launch xfce4-screenshooter, capture whatever region, at whatever dalay, then select `Copy to the clipboard`, click OK. Clipboard has no image. but /tmp/ has a newly created `Screenshot__.png`
Bug#1068408: Kicad bundle broken
Package: kicad Version: 7.0.11+dfsg-1 I am using Debian testing/trixie, the Kicad bundle has multiple issues. 1. kicad-footprints kicad-packages3d kicad-symbols kicad-templates (7.x) are all missing. I also checked stable sources. ``` # apt install kicad-footprints= Completing package version 6.0.11-1 -- http://deb.debian.org/debian stable/main amd64 Packages 8.0.1-1 -- http://deb.debian.org/debian testing/main amd64 Packages ``` 2. I also have "unstable" source for apt, when upgrading, kicad-footprints kicad-packages3d kicad-symbols kicad-templates got upgraded to 8.0, which Kicad 7.0 does not compatible with. Kicad and its footprints packages3d symbols templates 3. kicad-libraries should not Depends kicad-footprints (>= 7.0.0~), kicad-symbols (>= 7.0.0~), kicad-templates (>= 7.0.0~)，rather >= 7.0.0 <8.0.0 Kicad can only access libraries with same or lower major version.
Bug#1068020: Background process seemingly paused
Package: linux-image-amd64 Version: 6.6.15-2 Debian testing/trixie, kernel 6.6.15-2 (2024-02-04) xfce Case 1: Start a command that runs for a long time, say `ffmpeg`. switch to other programs, i.e. web browser or other terminal windows, and keep using the computer. After a while, ffmpeg cpu usage drops to 0%, switch back to ffmpeg's terminal window, it will go back to running. Case 2: start ffmpeg, leave the computer untouched, then screensaver runs, then the display turns off. No suspend, no hibernate, no shutdown. after a while, wake up display, unlock session, ffmpeg is using 0% CPU. switch back to its terminal window, it resumes. I am not sure which package is causing this. This happened long before 6.6.15 kernels.
Bug#1051432: Info received ()
I fixed this, after months of research.
This is not an issue of bluez.
hidp/uhid really IS the problem. I don't know what makes a Linux decide to
load `uhid` or `hidp`, my "good" and "bad" Linux SSD are dd'ed from same
source, and they even have same partition uuid.
long story short, blacklist hidp and force load uhid kernel module, all
mice work happily now!
echo "blacklist hidp" | sudo tee /etc/modprobe.d/blacklist-hidp.conf
echo -e "# Fix BLE mouse issue\nuhid" | sudo tee /etc/modules-load.d/uhid.conf
cp --update=none /etc/bluetooth/input.conf{,backup}
sudo sed -ie "s:.*UserspaceHID=.*:UserspaceHID=true:" /etc/bluetooth/input.conf
then reboot.
On Fri, Jan 26, 2024 at 12:52 PM Terrance Hendrik <
terrance.hend...@gmail.com> wrote:
> Update 2024-01-26
>
> 1. It has nothing to do with GUI. In text mode the issue is the same.
>
> 2. it has nothing to do with DKMS, removing it changes nothing.
>
> 3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
> not a hardware issue
>
> 4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
> them, the issue persists.
>
> 5. I compared files in /etc/udev/rules.d and /lib/modules on both
> computer, they are identical.
> only difference is modules.dep*, modules.symbols* and extra dkms modules.
>
> 6. other info
>
> on the working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
> ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
> probably a LE device.
> ... kernel: input: MX Anywhere 3 Mouse as
> /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
> ... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
> v0.14 Mouse [MX Anywhere 3] on
> ```
>
> on the NOT working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ```
>
> 7. Final Question:
> What else can affect the behavior between bluez and the kernel??
>
>
> On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>> Debian Bluetooth Maintainers
>>
>> If you wish to submit further information on this problem, please
>> send it to 1051...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>
Bug#1051432: Info received ()
Update 2024-01-26 1. It has nothing to do with GUI. In text mode the issue is the same. 2. it has nothing to do with DKMS, removing it changes nothing. 3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's not a hardware issue 4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall them, the issue persists. 5. I compared files in /etc/udev/rules.d and /lib/modules on both computer, they are identical. only difference is modules.dep*, modules.symbols* and extra dkms modules. 6. other info on the working OS, connecting a logitech mouse has 2 syslog messages ``` ... blueman-manager[7228]: blueman-manager 18.32.55 WARNING ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels, probably a LE device. ... kernel: input: MX Anywhere 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37 ... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID v0.14 Mouse [MX Anywhere 3] on ``` on the NOT working OS, connecting a logitech mouse has 2 syslog messages ``` ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog profile accept failed for F6:8C:E4:DD:B8:6B ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog profile accept failed for F6:8C:E4:DD:B8:6B ``` 7. Final Question: What else can affect the behavior between bluez and the kernel?? On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Bluetooth Maintainers > > If you wish to submit further information on this problem, please > send it to 1051...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#1051432:
seems more like an issue with kernel/gui than bluez. checked my modprobe.d blacklists, most are system default. ``` blacklist ath_pci blacklist evbug blacklist usbmouse blacklist usbkbd blacklist eepro100 blacklist de4x5 blacklist eth1394 blacklist snd_intel8x0m blacklist snd_aw2 blacklist prism54 blacklist bcm43xx blacklist garmin_gps blacklist asus_acpi blacklist snd_pcsp blacklist pcspkr blacklist amd76x_edac blacklist ohci1394 blacklist sbp2 blacklist dv1394 blacklist raw1394 blacklist video1394 blacklist aty128fb blacklist atyfb blacklist radeonfb blacklist cirrusfb blacklist cyber2000fb blacklist cyblafb blacklist gx1fb blacklist hgafb blacklist i810fb blacklist intelfb blacklist kyrofb blacklist lxfb blacklist matroxfb_base blacklist neofb blacklist nvidiafb blacklist pm2fb blacklist rivafb blacklist s1d13xxxfb blacklist savagefb blacklist sisfb blacklist sstfb blacklist tdfxfb blacklist tridentfb blacklist vfb blacklist viafb blacklist vt8623fb blacklist udlfb blacklist intel_hid blacklist sparse_keymap blacklist nfc blacklist pn533 blacklist pn533_usb blacklist nouveau blacklist hackrf ``` Is it possible something's wrong with DKMS? the other 3 computers have no DKMS.
Bug#1051432: further info
Thank you, Iwanmatsu san!
But no luck,still logs
```
Nov 14 21:44:49 blueman-manager[10028]: blueman-manager 21.44.49
WARNING ManagerDeviceList:396 _monitor_power_levels: Failed to get power
levels, probably a LE device.
Nov 14 21:44:49 bluetoothd[9996]: src/service.c:service_accept()
input-hog profile accept failed for
Nov 14 21:44:51 bluetoothd[9996]: src/service.c:service_accept()
input-hog profile accept failed for
```
I uncommented those lines and restarted bluetooth.service.
Also tried adding `--experimental` to service execstart, only gets worse.
Strangely, other 3 computers running almost the same kernel 6.3-6.5 and
bluez 5.6x - 5.70, logi mice work perfectly fine.
On Mon, Oct 23, 2023 at 11:10 PM Nobuhiro Iwamatsu
wrote:
> Hi,
>
> 2023年9月8日(金) 6:57 Terrance Hendrik :
> >
> > bluetoothctl
> >
> > [MX Anywhere 3]# info
> > Device E5:9F:06:B5:08:8D (random)
> > Name: MX Anywhere 3
> > Alias: MX Anywhere 3
> > Appearance: 0x03c2 (962)
> > Icon: input-mouse
> > Paired: yes
> > Bonded: yes
> > Trusted: yes
> > Blocked: no
> > Connected: yes
> > WakeAllowed: no
> > LegacyPairing: no
> > UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
> > UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
> > UUID: Device Information(180a--1000-8000-00805f9b34fb)
> > UUID: Battery Service (180f--1000-8000-00805f9b34fb)
> > UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
> > UUID: Vendor specific (0001--1000-8000-011f246d)
> > Modalias: usb:v046DpB025d0014
> > Battery Percentage: 0x4b (75)
>
> Could you please set ClassicBondedOnly=true and LEAutoSecurity=true in
> /etc/bluetooth/input.conf and check?
>
> ```
> [General]
> ClassicBondedOnly = true
> LEAutoSecurity = true
> ```
>
> Best regards,
> Nobuhiro
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org / kernel.org}
>GPG ID: 32247FBB40AD1FA6
>
Bug#1052348: gcc-arm-none-eabi 15:12.3 breaks related latest packages
Package: gcc-arm-none-eabi Version: 15:12.3.rel1-1 upgrade it will remove latest libstdc++-arm-none-eabi-dev libstdc++-arm-none-eabi-newlib
Bug#1051432: further info
bluetoothctl [MX Anywhere 3]# info Device E5:9F:06:B5:08:8D (random) Name: MX Anywhere 3 Alias: MX Anywhere 3 Appearance: 0x03c2 (962) Icon: input-mouse Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: yes WakeAllowed: no LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB025d0014 Battery Percentage: 0x4b (75)
Bug#1051432: bluez 5.6.9 Some bluetooth mouse not working, problem persists
Package: bluez Version: 5.6.9-1 Not sure if this issue is about bluez or other packages or modules System info: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux trixie/sid Release:n/a Codename: trixie $ uname -a Linux 6.4.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.13-1 (2023-08-31) x86_64 GNU/Linux ``` journalctl -f, after connected ``` Sep 08 04:57:06 blueman-manager[11378]: blueman-manager 04.57.06 WARNING ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels, probably a LE device. Sep 08 04:57:06 bluetoothd[1053]: src/service.c:service_accept() input-hog profile accept failed for Sep 08 04:57:06 bluetoothd[1053]: src/service.c:service_accept() input-hog profile accept failed for ``` Bluetooth adapter: 8087:0026 Intel Corp. AX201 Bluetooth Mouse is Logitech MX Anywhere 3, and MX Master 3. connected to Bluetooth.
Bug#1049456: update
after upgrading bluez bundle to ``` Package: bluez Version: 5.69-1 ... ``` now **MX Anywhere 3** disconnect immediately then reconnected for dozens of times every several seconds. While other mice (e.g.UGreen MU002 ) working fine.
Bug#1049456: bluez 5.6.8 Some bluetooth mouse not working
Package: bluez Version: 5.6.8-2 System info: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux trixie/sid Release:n/a Codename: trixie ``` journalctl -f, after connected ``` Aug 16 10:00:43 bluetoothd[1022]: src/service.c:service_accept() input-hog profile accept failed for Aug 16 10:00:45 bluetoothd[1022]: src/service.c:service_accept() input-hog profile accept failed for ``` Bluetooth adapter: 8087:0026 Intel Corp. AX201 Bluetooth Mouse is Logitech MX Anywhere 3, and MX Master 3. connected to Bluetooth.
Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic
;__this_module) | ~^~~ | | | struct module * /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:35: note: in expansion of macro ‘THIS_MODULE’ 1535 | xtrx_class = class_create(THIS_MODULE, CLASS_NAME); | ^~~ In file included from /usr/src/linux-headers-6.4.0-1-common/include/linux/device.h:31, from /usr/src/linux-headers-6.4.0-1-common/include/linux/pci.h:37, from /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:25: /usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’ 230 | struct class * __must_check class_create(const char *name); | ^~~~ /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:22: error: too many arguments to function ‘class_create’ 1535 | xtrx_class = class_create(THIS_MODULE, CLASS_NAME); | ^~~~ /usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:29: note: declared here 230 | struct class * __must_check class_create(const char *name); | ^~~~ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.4.0-1-common/scripts/Makefile.build:257: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.o] Error 1 make: *** [/usr/src/linux-headers-6.4.0-1-common/Makefile:2051: /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.4.0-1-amd64' ``` 2 dkms modules failed to built, xtrx/0.0.1+git20190320.5ae3a3e-3.3 tp_smapi/0.43 quick & dirty fix xtrx 1535 xtrx_class = class_create(THIS_MODULE, CLASS_NAME); 1535 xtrx_class = class_create(/*THIS_MODULE*/, CLASS_NAME); too many errors from tp-smapi-dkms, and I dont't remember using it , so `apt purge tp-smapi-dkms` now /boot/initrd.img-6.4.0-1-amd64 can be built On Wed, Jul 26, 2023 at 11:14 PM Ben Hutchings wrote: > Control: reassign -1 src:linux 6.4.4-1 > Control: tag -1 moreinfo > > On Wed, 2023-07-26 at 10:59 +0800, Terrance Hendrik wrote: > > Package: linux-image-6.4.0-1-amd64 > > Version: 6.4.4-1 > > system info: > > > > ``` > > $ lsb_release -a > > No LSB modules are available. > > Distributor ID: Debian > > Description:Debian GNU/Linux trixie/sid > > Release:n/a > > Codename: trixie > > $ lscpu > > Architecture:x86_64 > > CPU op-mode(s):32-bit, 64-bit > > Address sizes: 39 bits physical, 48 bits virtual > > Byte Order:Little Endian > > CPU(s): 20 > > On-line CPU(s) list: 0-19 > > Vendor ID: GenuineIntel > > Model name:12th Gen Intel(R) Core(TM) i7-12700H > > ... > > ``` > > > > Root FS is **btrfs** > > > > > > Boot log (photo OCR, unable to save log, might have some errors) > [...] > > [0.704503] List of all partitions: > > > > [0.705638] No filesystem could mount root, tried: > [...] > > It seems that your boot loader tried to boot this kernel without an > initramfs. > > - Which boot loader are you using? > - Does /boot/initrd.img-6.4.0-1-amd64 exist? > - Does "dpkg --configure -a" do anything or show any errors? > > Ben. > > -- > Ben Hutchings > Every program is either trivial or else contains at least one bug > >
Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic
Package: linux-image-6.4.0-1-amd64 Version: 6.4.4-1 system info: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux trixie/sid Release:n/a Codename: trixie $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 20 On-line CPU(s) list: 0-19 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-12700H ... ``` Root FS is **btrfs** Boot log (photo OCR, unable to save log, might have some errors) ``` [0.625362] Key type .fscrypt registered [0.625379] Key type fscrypt-provisioning registered [9.626122] Key type encrypted registered [0.626142] AppArmor: AppArmor shal policy hashing enabled [0.626493] integrity: Loading X.509 certificate: UEFI:b [0.626527] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adb43096d82709cBcd54f316ed522988a1bd4' [0.626571] integrity: Loading X.509 certificate: UEF1: db [0.626602] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c4977Bcd90 f99e4f9ae17c55af53' [0.627200] ima: Allocated hash algorithm: sha256 [0.646056] ima: No architecture policies found[ [0.647855] evm: Initialising EVM extended attributes: [0.649888] evm: security. selinux [0.651351] evm: security. SMACK64 (disabled) [0.652752] evm: security. SMACK64EXEC (disabled) [0.653931] evm: security. SMACK64TRANSMUTE (disabled) [0.655031] evm: security. SMACK64MMAP (disabled) [0.656067] evm: security. apparmor [0.657873] evm: security. ima [0.658026] evm: security.capability [0.658966] evm: HMAC attrs: Bx1 [0.703120] clk: Disabling unused clocks [0.704503] List of all partitions: [0.705638] No filesystem could mount root, tried: [8.705639] [0.707504] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.708458] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 6.4.0-1-amd64 #1 Debian 6.4.4-1 [8.709396] Harduare name: MECHREVO WUJIE16 Pro/WUJIE16 Pro. BIOS Q3ANWJ.16 12/09/2022 [0.710369] Call Trace: [0.711305] [0.712215] dump_stack_1v1+0×47/0×60 [0.713148] panic+0x17f/0×330 [0.714067] mount_block_root+0×21f/0x2b@ [0.714981] prepare_namespace+Oxf0/0×170 [8.715888] kernel_init_freeable+Bx417/8×470 [0.716782] ?__pfx_kernel_init+B×10/B×10 [0.717637] kernel_init+Bxla/Bx1cl [0.718583] ret_from_fork+Bx29/0×50 [0.719387] [0.720391] Kernel Offset: Bx3700 from Ox8100 (relocation range: Bx8000-0xbfff) [0.721331]---[ end Kernel panic - not syncing: FS: Unable to mount root fs on unknown-black(0,0) ]-- ``` Thanks!
Bug#1041590: nvidia-installer-cleanup install fail
YES! I did ``` unset DEBIAN_PRIORITY unset DEBIAN_FRONTEND ``` Then a ncurse window popped up and the install finished. Thanks!! On Sat, Jul 22, 2023 at 3:49 AM Andreas Beckmann wrote: > On 21/07/2023 06.41, Terrance Hendrik wrote: > > Unpacking nvidia-installer-cleanup (20220217+3) ... > > Setting up nvidia-installer-cleanup (20220217+3) ... > > dpkg: error processing package nvidia-installer-cleanup (--configure): > > installed nvidia-installer-cleanup package post-installation script > > subprocess returned error exit status 30 > > This sounds like debconf couldn't display a question. > > Did you customize the debconf priority on this system? Or do you use > something like DEBIAN_FRONTEND=noninteractive ? > > Have you ever had the nvidia driver installed from the .run installer on > this machine? > > Andreas >
Bug#1041590: nvidia-installer-cleanup install fail
Package: nvidia-installer-cleanup Version: 20220217+3 system info ``` $ uname-a Linux 6.3.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.11-1 (2023-07-01) x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux trixie/sid Release:n/a Codename: trixie ``` steps to represent ``` # apt install nvidia-installer-cleanup Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: nvidia-installer-cleanup 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/13.3 kB of archives. After this operation, 48.1 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package nvidia-installer-cleanup. (Reading database ... 421224 files and directories currently installed.) Preparing to unpack .../nvidia-installer-cleanup_20220217+3_amd64.deb ... Unpacking nvidia-installer-cleanup (20220217+3) ... Setting up nvidia-installer-cleanup (20220217+3) ... dpkg: error processing package nvidia-installer-cleanup (--configure): installed nvidia-installer-cleanup package post-installation script subprocess returned error exit status 30 Errors were encountered while processing: nvidia-installer-cleanup needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ``` perl trace log in the attachment. Thanks!
