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#971654: gnome-shell-extension-dashtodock: Not working in gnome 3.38
Package: gnome-shell-extension-dashtodock Version: 68-1 Severity: normal Extension not working after upgrade from gnome 3.36 to 3.38 Error: No signal 'allocation-changed' on object 'Gjs_dash-to-dock_micxgx_gmail_com_dash_DashToDock_MyDashActor' -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-dashtodock depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1 ii gir1.2-clutter-1.0 1.26.4+dfsg-1 ii gnome-shell 3.38.0-2 ii gnome-shell-extension-prefs 3.38.0-2 gnome-shell-extension-dashtodock recommends no packages. gnome-shell-extension-dashtodock suggests no packages. -- no debconf information
Bug#971635: gnome-shell-extension-autohidetopbar: Not hiding on wayland window in gnome 3.38
Package: gnome-shell-extension-autohidetopbar Version: 20200921-1 Severity: normal Top bar does not autohide on wayland window after upgrading from gnome 3.36 to 3.38 Autohiding is working as expected with X window -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-autohidetopbar depends on: ii gnome-shell 3.38.0-2 Versions of packages gnome-shell-extension-autohidetopbar recommends: ii gnome-tweaks 3.34.0-4 gnome-shell-extension-autohidetopbar suggests no packages. -- no debconf information
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#965317: gnome-shell: failed to write to XWayland
Package: gnome-shell Version: 3.36.3-1 Severity: grave Justification: causes non-serious data loss 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 Very frustrating because all unsaved work is lost. Seems like this is most problematic release since i can remember. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii evolution-data-server3.36.4-1 ii gir1.2-accountsservice-1.0 0.6.55-2 ii gir1.2-atspi-2.0 2.36.0-2 ii gir1.2-freedesktop 1.64.1-1 ii gir1.2-gcr-3 3.36.0-2 ii gir1.2-gdesktopenums-3.0 3.36.1-1 ii gir1.2-gdm-1.0 3.36.2-1 ii gir1.2-geoclue-2.0 2.5.6-1 ii gir1.2-glib-2.0 1.64.1-1 ii gir1.2-gnomebluetooth-1.03.34.1-1 ii gir1.2-gnomedesktop-3.0 3.36.3.1-2 ii gir1.2-gtk-3.0 3.24.20-1 ii gir1.2-gweather-3.0 3.36.0-1 ii gir1.2-ibus-1.0 1.5.22-5 ii gir1.2-mutter-6 3.36.3-1 ii gir1.2-nm-1.01.26.0-1 ii gir1.2-nma-1.0 1.8.30-1 ii gir1.2-pango-1.0 1.44.7-4 ii gir1.2-polkit-1.00.105-28 ii gir1.2-rsvg-2.0 2.48.7-1 ii gir1.2-soup-2.4 2.70.0-1 ii gir1.2-upowerglib-1.00.99.11-2 ii gjs 1.64.3-1 ii gnome-backgrounds3.36.0-1 ii gnome-settings-daemon3.36.1-1 ii gnome-shell-common 3.36.3-1 ii gsettings-desktop-schemas3.36.1-1 ii libatk-bridge2.0-0 2.34.1-3 ii libatk1.0-0 2.36.0-2 ii libc62.30-8 ii libcairo21.16.0-4 ii libecal-2.0-13.36.4-1 ii libedataserver-1.2-243.36.4-1 ii libgcr-base-3-1 3.36.0-2 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgirepository-1.0-11.64.1-1 ii libgjs0g 1.64.3-1 ii libgles2 1.3.1-1 ii libglib2.0-0 2.64.3-2 ii libglib2.0-bin 2.64.3-2 ii libgnome-autoar-0-0 0.2.4-2 ii libgnome-desktop-3-193.36.3.1-2 ii libgraphene-1.0-01.10.2-1 ii libgstreamer1.0-01.16.2-2 ii libgtk-3-0 3.24.20-1 ii libical3 3.0.8-2 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-6-03.36.3-1 ii libnm0 1.26.0-1 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii libpolkit-agent-1-0 0.105-28 ii libpolkit-gobject-1-00.105-28 ii libpulse-mainloop-glib0 13.0-5 ii libpulse013.0-5 ii libsecret-1-00.20.3-1 ii libsystemd0 245.6-2 ii libwayland-server0 1.18.0-1 ii libx11-6 2:1.6.9-2+b1 ii libxfixes3 1:5.0.3-2 ii mutter 3.36.3-1 ii python3 3.8.2-3 Versions of packages gnome-shell recommends: ii bolt 0.9-1 ii chrome-gnome-shell10.1-5 ii gdm3 3.36.2-1 ii gkbd-capplet 3.26.1-1 ii gnome-control-center 1:3.36.4-1 ii gnome-menus 3.36.0-1 ii gnome-user-docs 3.36.2-1 ii ibus 1.5.22-5 ii iio-sensor-proxy 3.0-1
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#946629: tilix: Same here
Package: tilix Version: 1.9.3-3 Followup-For: Bug #946629 I am wondering why such packages are not tested at all ? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tilix depends on: ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii libc62.29-3 ii libgtkd-3-0 3.9.0-3+b1 ii libphobos2-ldc-shared88 1:1.18.0-2 ii libunwind8 1.2.1-9 ii libvted-3-0 3.9.0-3+b1 ii libx11-6 2:1.6.8-1 ii tilix-common 1.9.3-3 tilix recommends no packages. Versions of packages tilix suggests: pn python-nautilus -- no debconf information
Bug#942272: gnome-shell: numlock state is reversed
Hi Sorry for late response. Yes it was fixed after gnome upgrade. Regards, Edi D
Bug#942272: gnome-shell: numlock state is reversed
Package: gnome-shell Version: 3.34.0-2 Severity: normal Numlock state is reversed after system boot -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii evolution-data-server3.34.1-1 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.34.0-3 ii gir1.2-freedesktop 1.62.0-2 ii gir1.2-gcr-3 3.33.4-2 ii gir1.2-gdesktopenums-3.0 3.34.0-2 ii gir1.2-gdm-1.0 3.34.1-1 ii gir1.2-geoclue-2.0 2.5.5-1 ii gir1.2-glib-2.0 1.62.0-2 ii gir1.2-gnomebluetooth-1.03.34.0-1 ii gir1.2-gnomedesktop-3.0 3.34.0-2 ii gir1.2-gtk-3.0 3.24.12-1 ii gir1.2-gweather-3.0 3.28.3-2 ii gir1.2-ibus-1.0 1.5.19-4+b1 ii gir1.2-mutter-5 3.34.0-4 ii gir1.2-nm-1.01.20.4-2 ii gir1.2-nma-1.0 1.8.22-2 ii gir1.2-pango-1.0 1.42.4-7 ii gir1.2-polkit-1.00.105-26 ii gir1.2-rsvg-2.0 2.44.14-1 ii gir1.2-soup-2.4 2.68.1-2 ii gir1.2-upowerglib-1.00.99.11-1 ii gjs 1.58.1-1 ii gnome-backgrounds3.34.0-1 ii gnome-settings-daemon3.34.0-3 ii gnome-shell-common 3.34.0-2 ii gsettings-desktop-schemas3.34.0-2 ii libatk-bridge2.0-0 2.34.1-1 ii libatk1.0-0 2.34.1-1 ii libc62.29-2 ii libcairo21.16.0-4 ii libcroco30.6.13-1 ii libecal-2.0-13.34.1-1 ii libedataserver-1.2-243.34.1-1 ii libgcr-base-3-1 3.33.4-2 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1 ii libgirepository-1.0-11.62.0-2 ii libgjs0g 1.58.1-1 ii libgles2 1.1.0-1+b1 ii libglib2.0-0 2.62.1-1 ii libglib2.0-bin 2.62.1-1 ii libgnome-autoar-0-0 0.2.3-2 ii libgstreamer1.0-01.16.1-1 ii libgtk-3-0 3.24.12-1 ii libical3 3.0.5-2 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-5-03.34.0-4 ii libnm0 1.20.4-2 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpolkit-agent-1-0 0.105-26 ii libpolkit-gobject-1-00.105-26 ii libpulse-mainloop-glib0 13.0-2 ii libpulse013.0-2 ii libsecret-1-00.19.1-1 ii libsystemd0 242-7 ii libwayland-server0 1.17.0-1 ii libx11-6 2:1.6.8-1 ii libxfixes3 1:5.0.3-1 ii mutter 3.34.0-4 ii python3 3.7.5-1 Versions of packages gnome-shell recommends: ii bolt 0.8-4 ii chrome-gnome-shell10.1-5 ii gdm3 3.34.1-1 ii gkbd-capplet 3.26.1-1 ii gnome-control-center 1:3.34.1-1 ii gnome-user-docs 3.34.0-2 ii ibus 1.5.19-4+b1 ii iio-sensor-proxy 2.4-2+b1 ii switcheroo-control1.3.1-2 ii unzip 6.0-25 Versions of packages gnome-shell suggests: pn gir1.2-telepathyglib-0.12 pn gir1.2-telepathylogger-0.2 Versions of packages gnome-session depends on: ii gnome-session-bin 3.34.1-1 ii gnome-session-common 3.34.1-1 ii gnome-settings-daemon 3.34.0-3 Versions of packages gnome-session suggests: ii desktop-base 10.0.3 ii gnome-keyring 3.34.0-1
