Bug#1070716: /usr/libexec/gvfsd-trash: GFileInfo created without standard::name, should not be reached
Package: gvfs-daemons Version: 1.53.90-3 Severity: important File: /usr/libexec/gvfsd-trash X-Debbugs-Cc: kspalaiolo...@gmail.com Dear Maintainer, Casually using Thunar causes the following errors to be logged in journalctl: May 07 20:07:17 laplace gvfsd-trash[2996]: GFileInfo created without standard::name May 07 20:07:17 laplace gvfsd-trash[2996]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached May 07 20:07:17 laplace gvfsd-trash[2996]: GFileInfo created without standard::name May 07 20:07:17 laplace gvfsd-trash[2996]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached Because of this, every time I delete a file (i.e. move it to trash), coincidentally my whole system including my desktop significantly slows down and on one occasion has forced me to reboot by holding the power button. I am not exactly sure of what could be the issue here, but it hinders my workflow significantly and judging by the error message, an assertion in the source code is not being fulfilled. If I can provide any additional information, please let me know. Yours, Kamila Szewczyk -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gvfs-daemons depends on: ii gvfs-common 1.53.90-3 ii gvfs-libs1.53.90-3 ii libbluray2 1:1.3.4-1+b1 ii libc62.38-8 ii libglib2.0-0t64 2.80.0-9 ii libgudev-1.0-0 238-5 ii libsecret-1-00.21.4-1+b1 ii libsystemd0 255.5-1 ii libudisks2-0 2.10.1-7 ii lsof 4.95.0-1 ii udisks2 2.10.1-7 Versions of packages gvfs-daemons recommends: ii dbus 1.14.10-4+b1 ii gvfs 1.53.90-3 Versions of packages gvfs-daemons suggests: ii gvfs-backends 1.53.90-3 -- no debconf information
Bug#1067202: linux-image-6.7.9-amd64: ACPI errors
Package: src:linux Version: 6.7.9-2 Severity: important X-Debbugs-Cc: kspalaiolo...@gmail.com Dear Maintainer, I am struggling with ACPI issues on my laptop. As of recent, my laptop refuses to charge while turned on and booted into the Linux kernel specifically. The battery starts charging for a second, then starts discharging (thinking that the charging cable has been removed) repeatedly regardless of the position of the cable. When the computer is turned off/not booted into the Linux kernel, the charging light turns on and stays on, meaning that the charging process is otherwise uninterrupted. I have started experiencing this issue since upgrading from kernel version "linux-image-6.6.15" to "6.7.9-2". Since the upgrade I do not observe some problems with ACPI that I had before (primarily waking up from S3 sleep and resetting the status of mute/mic mute keys, etc), but this new issue is preventing me from using my computer. -- Package-specific info: ** Version: Linux version 6.7.9-amd64 (debian-ker...@lists.debian.org) (x86_64-linux-gnu-gcc-13 (Debian 13.2.0-18) 13.2.0, GNU ld (GNU Binutils for Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.7.9-2 (2024-03-13) ** Command line: BOOT_IMAGE=/vmlinuz-6.7.9-amd64 root=/dev/mapper/laplace--vg-root ro quiet ** Not tainted ** Kernel log: [ 1685.874076] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1685.874097] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1685.874118] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1685.909762] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1685.909784] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1685.909798] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1685.909819] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1685.909835] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.625710] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1686.625730] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1686.625742] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.625760] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.625777] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.661710] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1686.661725] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1686.661736] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.661753] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1686.661767] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.625944] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1688.625967] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1688.625980] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.626001] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.626022] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.661941] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1688.661963] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1688.661977] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.661997] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1688.662013] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1689.190075] ACPI Error: No handler for Region [ECSI] (ebf69c05) [EmbeddedControl] (20230628/evregion-130) [ 1689.190097] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261) [ 1689.190110] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529) [ 1689.190130] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error
Bug#1026870: linux-image-6.0.0-6-amd64 - significant performance degradation
Package: src:linux
Version: 6.0.12-1
Severity: important
X-Debbugs-Cc: kspalaiolo...@gmail.com
Dear Maintainer,
I have recently upgraded my Linux kernel to package version 6.0.12-1
(6.0.0-6) from version 6.0.8 (6.0.0-4). Since then I am experiencing
significant performance degradation. I have tried to observe the
cause of it using the `perf' tool, however, I haven't had any luck
with this so far, and the kernel has been logging the following
messages throughout the procedure:
>>>
Message from syslogd@laplace at Dec 22 21:51:20 ...
kernel:[ 5212.738589] Uhhuh. NMI received for unknown reason 2d on CPU 9.
Message from syslogd@laplace at Dec 22 21:51:20 ...
kernel:[ 5212.738607] Dazed and confused, but trying to continue
Message from syslogd@laplace at Dec 22 21:51:21 ...
kernel:[ 5214.422563] Uhhuh. NMI received for unknown reason 2d on CPU 7.
Message from syslogd@laplace at Dec 22 21:51:21 ...
kernel:[ 5214.422582] Dazed and confused, but trying to continue
<<<
So far I have observed that returning to the previously installed
kernel version solves most of my problems. I have also compared the
execution times using `perf' on both of the kernels.
New kernel:
<<<
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package asdfghjkl
Performance counter stats for 'apt install asdfghjkl':
2,409.28 msec task-clock #0.999 CPUs
utilized
11 context-switches #4.566 /sec
4 cpu-migrations #1.660 /sec
2,526 page-faults #1.048 K/sec
961,017,382 cycles #0.399 GHz
(83.39%)
15,353,337 stalled-cycles-frontend #1.60% frontend
cycles idle (83.40%)
226,730,321 stalled-cycles-backend # 23.59% backend
cycles idle (83.40%)
2,018,766,682 instructions #2.10 insn per
cycle
#0.11 stalled cycles per
insn (83.39%)
383,290,701 branches # 159.089 M/sec
(83.35%)
1,819,464 branch-misses#0.47% of all
branches (83.24%)
2.411797623 seconds time elapsed
2.349918000 seconds user
0.062534000 seconds sys
>>>
Old kernel:
<<<
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package asdfghjkl
Performance counter stats for 'apt install asdfghjkl':
852.22 msec task-clock #0.940 CPUs
utilized
392 context-switches # 459.975 /sec
3 cpu-migrations #3.520 /sec
2,548 page-faults #2.990 K/sec
1,172,831,665 cycles #1.376 GHz
(83.08%)
43,524,987 stalled-cycles-frontend #3.71% frontend
cycles idle (83.76%)
412,509,320 stalled-cycles-backend # 35.17% backend
cycles idle (82.83%)
2,060,235,707 instructions #1.76 insn per
cycle
#0.20 stalled cycles per
insn (83.60%)
396,100,764 branches # 464.786 M/sec
(83.18%)
1,892,879 branch-misses#0.48% of all
branches (83.77%)
0.906939283 seconds time elapsed
0.795226000 seconds user
0.059521000 seconds sys
>>>
If there is any troubleshooting or important information
I could provide, please let me know.
I have noticed that the clock speeds tend to be much lower
on the new Linux kernel, however, I don't know the cause of it.
All the system data (including e.g. CPU governor configuration)
stays the same.
Yours, Kamila Szewczyk.
-- Package-specific info:
** Version:
Linux version 6.0.0-6-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-9.1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP
PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09)
** Command line:
BOOT_IMAGE=/vmlinuz-6.0.0-6-amd64 root=/dev/mapper/laplace--vg-root ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 290.013257] snd_hda_intel :04:00.1: Handle vga_switcheroo audio client
[ 290.013307] snd_hda_intel :04:00.6: enabling device ( -> 0002)
[ 290.047532] snd_hda_intel :04:00.1: bound :04:00.0 (ops
amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 290.065328] input: HD-Audio Generic HDMI/DP,pcm=3 as
/devices/pci:00/:00:0
Bug#1025696: bzip3: The version that the CLI tools and manpages report is "UNKNOWN".
Package: bzip3 Version: 1.2.1 Severity: minor X-Debbugs-Cc: kspalaiolo...@gmail.com Dear Maintainer, The version that the bzip3 CLI tool and the manpages seem to report is listed as "UNKNOWN" as can be seen here: https://manpages.debian.org/testing/bzip3/bzip3.1.en.html The problem seems to be caused by some mistake during packaging. Yours, Kamila Szewczyk. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bzip3 depends on: pn libbzip3-0 ii libc6 2.36-5 bzip3 recommends no packages. bzip3 suggests no packages.
