Re: Very long startup time for an application in Debian testing
On 9/5/25 11:15 PM, Max Nikulin wrote:
sudo journalctl -b --priority=warning
Sep 06 06:35:38 franklin kernel: core: CPUID marked event: 'bus cycles'
unavailable
Sep 06 06:35:38 franklin kernel: MDS CPU bug present and SMT on, data
leak possible. See https://www.kernel.org>
Sep 06 06:35:38 franklin kernel: DMAR: DRHD: handling fault status reg 3
Sep 06 06:35:38 franklin kernel: DMAR: [DMA Write NO_PASID] Request
device [00:02.0] fault addr 0xffffff000 [fa>
Sep 06 06:35:38 franklin kernel: ACPI Warning: SystemIO range
0x0000000000000500-0x000000000000052F conflicts w>
Sep 06 06:35:38 franklin kernel: ACPI Warning: SystemIO range
0x0000000000000500-0x000000000000052F conflicts w>
Sep 06 06:35:38 franklin kernel: sd 7:0:0:0: [sdc] No Caching mode page
found Sep 06 06:35:38 franklin kernel: sd 7:0:0:0: [sdc] Assuming drive
cache: write through
Sep 06 06:35:38 franklin kernel: sd 6:0:0:0: [sdb] No Caching mode page
found Sep 06 06:35:38 franklin kernel: sd 6:0:0:0: [sdb] Assuming drive
cache: write through
Sep 06 06:35:38 franklin systemd-modules-load[302]: Failed to find
module 'vboxdrv'
Sep 06 06:35:38 franklin systemd-udevd[347]:
/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_>
Sep 06 06:35:38 franklin systemd-udevd[347]:
/usr/lib/udev/rules.d/90-alsa-restore.rules:18 The line has no eff>
Sep 06 06:35:38 franklin systemd-udevd[347]:
/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_>
Sep 06 06:35:38 franklin systemd-udevd[347]:
/usr/lib/udev/rules.d/90-alsa-restore.rules:22 The line has no eff>
Sep 06 06:35:39 franklin kernel: at24 0-0050: supply vcc not found,
using dummy regulator
Sep 06 06:35:39 franklin kernel: at24 0-0051: supply vcc not found,
using dummy regulator
Sep 06 06:35:39 franklin kernel: at24 0-0052: supply vcc not found,
using dummy regulator
Sep 06 06:35:39 franklin kernel: at24 0-0053: supply vcc not found,
using dummy regulator
Sep 06 06:35:40 franklin kernel: kvm_intel:
VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using wo>
Sep 06 06:35:41 franklin (smartd)[716]: smartmontools.service:
Referenced but unset environment variable evalua>
Sep 06 06:35:41 franklin su[957]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 06:35:41 franklin udisksd[726]: Error performing housekeeping for
drive /org/freedesktop/UDisks2/drives/>
Sep 06 06:35:42 franklin su[972]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 06:35:42 franklin su[977]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 06:35:43 franklin lightdm[999]: pam_env(lightdm-greeter:session):
Unable to open env file: /etc/environm>
Sep 06 06:35:45 franklin wireplumber[1033]: default: Failed to get
percentage from UPower: org.freedesktop.DBus>
Sep 06 06:35:45 franklin wireplumber[1033]: spa.bluez5: BlueZ system
service is not available
Sep 06 06:35:54 franklin lightdm[1094]:
pam_env(lightdm-autologin:session): Unable to open env file: /etc/envir>
Sep 06 06:35:58 franklin kernel: kauditd_printk_skb: 108 callbacks
suppressed
Sep 06 07:00:01 franklin CRON[2381]: pam_env(cron:session): Unable to
open env file: /etc/environment
Sep 06 07:17:01 franklin CRON[2977]: pam_env(cron:session): Unable to
open env file: /etc/environment
Sep 06 07:17:02 franklin su[2998]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 07:17:02 franklin su[3003]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 07:17:02 franklin systemd-logind[721]: Existing logind session ID
5 used by new audit session, ignoring.
Sep 06 07:17:02 franklin su[3007]: pam_env(su:session): Unable to open
env file: /etc/environment
Sep 06 07:20:02 franklin lightdm[3725]:
pam_env(lightdm-greeter:session): Unable to open env file: /etc/environ>
Sep 06 07:20:03 franklin wireplumber[3761]: default: Failed to get
percentage from UPower: org.freedesktop.DBus>
Sep 06 07:20:03 franklin wireplumber[3761]: spa.bluez5: BlueZ system
service is not available
Sep 06 07:20:04 franklin systemd[3732]: pipewire.service: Main process
exited, code=killed, status=11/SEGV
I am no expert, but I don't see any errors in there that would seem to
relate to the problem
According to APT all gvfs packages are installed
>Next step is busctl to see if org.gtk.vfs.Daemon is there.
I see no org.gtk.vfs.Daemon in that output or the output of busctl --user.
This problem only started about a week ago.
--
Frank
Reply to: