Bug#1072998: Black screen on host during vbox manager startup
Package: virtualbox Version: 7.0.18-dfsg-1+b1 Launching virtualbox manager causes host screen to blink black (like disabling monitor for a sec.). This behavior was observed under wayland/xwayland with kernel 6.7.12 with UHD Graphics 630 - i915 module.
Bug#1072812: Autofocus not working
Package: keepassxc Version: 2.7.7+dfsg.1-3 Autofocus not working after unlocking database. Issue is resolved in 2.7.8. Update is needed.
Bug#1010343: linux-image-5.17.0-1-amd64 ACPI errors
Package: linux-image-5.17.0-1-amd64 Version: 5.17.3-1 After upgrading from kernel 5.16 to 5.17 there are *ACPI* errors like this : kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR08._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR09._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR10._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR11._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Is it caused by *ACPI_PFRUT* ? . If yes maybe this should be disabled on desktop systems by default. Is there any kernel boot option to disable this functionality ? Regards Edi
Bug#1002574: System not supported with v. 3.2
Package: openrazer-driver-dkms Version: 3.2.0+dfsg-1 Driver stop working after upgrade from 3.1 to 3.2 with Razer Basilisk v2. ** Error: kernel: razermouse: system not supported, no HID or USB support Tested with kernel 5.10 and 5.15.5. Dkms tree ok: ** dkms status: openrazer-driver/3.2.0, 5.10.0-8-amd64, x86_64: installed openrazer-driver/3.2.0, 5.15.0-2-amd64, x86_64: installed Regards Edi
Bug#1000643: linux-image-5.15.0-1-amd64 generate samsung nvme errors
Package: linux-image-5.15.0-1-amd64 Version: 5.15.3-1 There are errors increased in smart after every boot in Samsung 970 evo nvme disk. *Error Information Log Entries: 41* <- increased after every boot nvme error-log /dev/nvme0 : status_field :*0x4004(INVALID_FIELD: A reserved coded value or an unsupported value in a defined field) * <- problem Can someone explain if this is a bug ? or maybe kernel try to talk to nvme disk in non supported (by a disk) way ? or maybe there is a need for some kind of exclude samsung disks from this kind of communication ? Regards Edi
Bug#995161: linux-image-5.14.0-1-amd64: SMART error with update to 5.14 and Samsung nvme
Hi, Can someone explain if this is a bug ? or maybe kernel try to talk to nvme disk in non supported (by a disk) way ? or maybe there is a need for some kind of exclude samsung disks from this kind of communication ? Is anybody even working on this ? Regards Edi
Bug#996256: linux-image-5.14.0-2-amd64 generate samsung nvme errors
Package: linux-image-5.14.0-2-amd64 Version: 5.14.9-2 After upgrading from kernel 5.10 to 5.14 there are errors increased in smart after every boot in Samsung 970 evo. Error Information Log Entries: 41 <- increased after every boot nvme error-log /dev/nvme0 : status_field : 0x4004(INVALID_FIELD: A reserved coded value or an unsupported value in a defined field) <- problem Regards Edi
Bug#995161: linux-image-5.14.0-1-amd64: SMART error with update to 5.14 and Samsung nvme
Hi, I have exactly the same error with Samsung 970 EVO and smart error counter is incremented after every boot : error_count : 38 status_field : 0x4004(INVALID_FIELD: A reserved coded value or an unsupported value in a defined field) Best regards Edi
Bug#971635: gnome-shell-extension-autohidetopbar: Not hiding on wayland window in gnome 3.38
Why closed if package gnome-shell-extension-autohidetopbar is still in version 20200921-1 in sid and bullseye so it is not working. When there will be an updated version?
Bug#971635: gnome-shell-extension-autohidetopbar: Not hiding on wayland window in gnome 3.38
Also produced error like this: No signal 'allocation-changed' on object 'StBoxLayout'
Bug#965317: gnome-shell: failed to write to XWayland
Seems problem is resolved probably after some package upgrades (maybe gnome-shell 3.36.4) Regards EdiD
Bug#965317: gnome-shell: failed to write to XWayland
Hi, Thank you for fast reply. I have nothing about xwayland crash in log, only this: gnome-shell[1119]: Connection to xwayland lost Enabled extensions: * gnome-shell-extension-dashtodock ( 68-1) * gnome-shell-extension-autohidetopbar ( 20200627-1 ) * user themes ( minwaita-vanilla theme, not default adwaita ) * workspace indicator Gnome-shell is crashing like this every few days, randomly. Hard to tell what can be related with this issue: running virtualbox, firefox, thunderbird, ... On 19.07.2020 14:02, s...@debian.org wrote: On Sun, 19 Jul 2020 at 12:58:06 +0200, EdiD wrote: Gnome-shell crashes and (systemd) restarts DE. All running applications are killed. Errors from log: gnome-shell[1119]: WL: error in client communication (pid 1119) gnome-shell[1179]: (EE) failed to write to XWayland fd: Broken pipe I suspect this is happening because Xwayland has crashed (you can find out by looking at previous lines in the system log). If it is, please report that as a bug in Xwayland, with a backtrace: https://wiki.debian.org/HowToGetABacktrace It is unlikely to be possible to fix this without either a backtrace, or a sequence of instructions to reproduce the same crash. smcv
Bug#898575: In-memory cache grows almost without bound
The same with mpv 0.32 playing flac stream from online radio Config: cache=no demuxer-max-back-bytes=100KiB demuxer-max-bytes=2MiB Ram usage constantly growing (last seen as much as 700MB and cpu usage is growing with memory). Memory leak ?
Bug#959883: gnome-shell: randomly crashes: segfaults and restarts
Hi, Same problem here: gnome-shell[1153]: segfault at 0 ip 7f989dac846a sp 7ffc28aef5a0 error 4 in libst-1.0.so[7f989daa9000+4a000] Still no gnome-shell 3.36.2 update even in sid Regards, Edi D
Bug#866340: aa-genprof: ERROR: Can't find system log "/var/log/syslog" (journald-only setup)
Hi, Still not working with systemd 245 and apparmor-utils 2.13.4-1+b1 It will be great to redirect like this: aa-genprof -f <(journalctl -b) Is there any chance to work with journald ? Regards, Edi D
Bug#942272: gnome-shell: numlock state is reversed
Hi Sorry for late response. Yes it was fixed after gnome upgrade. Regards, Edi D
