Xfce Forum

Sub domains
 

You are not logged in.

Pages: 1

#1 2025-03-16 00:23:47

Xexan
Member
Registered: 2019-03-11
Posts: 10
LinuxFirefox 128.0

[SOLVED] Multiple interface bugs with new installation

My fresh installation of XFCE on Debian Trixie has several problems, possibly related.

1. Random screen freezing
2. Random loss of audio
3. Always locking screen on suspend
4. Sometimes will not wake from suspend

I have been watching xsession-errors, but I don't see any obvious reasons for the issues.

Here are more detailed explanations.

1. The screen will sometimes randomly freeze and the computer won't respond to keyboard commands. It seems to usually happen while I'm moving the mouse. No unusual errors are reported in xsession-errors afterward. In fact, when it once froze immediately after login, I hard-rebooted the computer and xsession-errors.old was completely empty. Below is the xsession-errors from that reboot.

Xsession: X session started for base at Fri Mar 14 10:04:18 PM UTC 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/base/.Xauthority
localuser:base being added to access control list
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
** Message: 22:04:18.974: Failed to fetch _NET_NUMBER_OF_DESKTOPS; assuming 1
** Message: 22:04:18.974: Failed to get _NET_WORKAREA; using full screen dimensions
** Message: 22:04:18.974: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
** Message: 22:04:18.974: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
/usr/bin/iceauth:  creating new authority file /run/user/1000/ICEauthority
xfce4-session-Message: 22:04:18.979: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one
** Message: 22:04:19.261: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0

2. I'm outputting audio through "Cannon Lake PCH cAVS Headphones" and setting volume through the Volume Control dialog. It randomly either looses the volume setting or the audio source entirely. The volume can be reset with the slider, but the audio source has to be refound by rebooting the computer.

3. Although I have unchecked "Lock screen when system is going to sleep" in the Power Manager dialog, it always requires login after return from suspend.

4. Sometimes when the computer has been sitting for hours, it will not wake from suspend and I have to do a hard-reboot.

Added later 6 h 14 min 08 s:
A further observation on the audio. When the audio output is lost, video playback in the browser is affected. In both Chrome and Firefox, videos with play only if the volume button in the playback window is muted.

Last edited by Xexan (2025-03-18 22:17:57)

Offline

#2 2025-03-16 09:39:51

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,815
LinuxFirefox 136.0

Re: [SOLVED] Multiple interface bugs with new installation

For # 1,2,4, instead of ~/.xsession-errors (because they don't seem to be session or interface errors), look at your journal for system messages:

sudo journalctl -b 0

...for current boot, or:

sudo journalctl - b -1

...for previous boot. Or if you want to see if running live:

sudo journalctl -f

For #3, make sure you don't have a screensaver running and active.

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#3 2025-03-16 14:52:04

Xexan
Member
Registered: 2019-03-11
Posts: 10
LinuxFirefox 128.0

Re: [SOLVED] Multiple interface bugs with new installation

About the screensaver. I didn't think I had one installed. I tried xfce4-screensaver-preferences but got "command not found". I looked in ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-screensaver.xml and found this. So doesn't that mean locking is disabled?

<?xml version="1.1" encoding="UTF-8"?>

<channel name="xfce4-screensaver" version="1.0">
  <property name="lock" type="empty">
    <property name="sleep-activation" type="bool" value="false"/>
  </property>
</channel>

Added later 43 min 08 s:
On the event of starting a video with loss of audio volume setting, I ran "journalctl -f" and got this.

Mar 16 15:10:10 Trixie xdg-desktop-por[15522]: AT-SPI: Could not obtain desktop path or name
Mar 16 15:10:10 Trixie at-spi-bus-launcher[1118]: dbus-daemon[1118]: Activating service name='org.a11y.atspi.Registry' requested by ':1.189' (uid=1000 pid=17892 comm="xfce4-terminal")
Mar 16 15:10:10 Trixie at-spi-bus-launcher[17914]: Authorization required, but no authorization protocol specified
Mar 16 15:10:10 Trixie at-spi2-registr[17914]: Could not open X display
Mar 16 15:10:10 Trixie at-spi-bus-launcher[1118]: dbus-daemon[1118]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 16 15:10:10 Trixie at-spi-bus-launcher[17914]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 16 15:10:10 Trixie at-spi-bus-launcher[17914]: Authorization required, but no authorization protocol specified
Mar 16 15:10:10 Trixie at-spi2-registr[17914]: AT-SPI: Cannot open default display
Mar 16 15:10:10 Trixie xfce4-notifyd[15317]: AT-SPI: Could not obtain desktop path or name
Mar 16 15:10:10 Trixie xdg-desktop-por[15522]: AT-SPI: Could not obtain desktop path or name

Offline

#4 2025-03-16 16:26:25

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,815
LinuxFirefox 136.0

Re: [SOLVED] Multiple interface bugs with new installation

Xexan wrote:

About the screensaver. I didn't think I had one installed.

Something has to be locking the screen.

I looked in ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-screensaver.xml and found this. So doesn't that mean locking is disabled?

No thats just a placeholder. Can you post back the output of:

ps -ef | grep -E 'screensaver|locker'

On the event of starting a video with loss of audio volume setting, I ran "journalctl -f" and got this.

Can you post back the full journal of the current boot:

sudo journalctl -b 0 --no-pager

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#5 2025-03-16 17:20:15

Xexan
Member
Registered: 2019-03-11
Posts: 10
LinuxFirefox 128.0

Re: [SOLVED] Multiple interface bugs with new installation

From ps -ef | grep -E 'screensaver|locker'

linda       6486    6341  0 07:07 ?        00:00:00 light-locker
base       15318   15153  0 14:21 ?        00:00:00 light-locker
base       20863   20843  0 17:09 pts/0    00:00:00 grep -E screensaver|locker

"linda" and "base" are the user accounts on this machine.

From journalctl -b 0 --no-pager

Mar 16 17:12:43 Trixie systemd[1014]: Queued start job for default target default.target.
Mar 16 17:12:43 Trixie systemd[1014]: Created slice app.slice - User Application Slice.
Mar 16 17:12:43 Trixie systemd[1014]: Created slice session.slice - User Core Session Slice.
Mar 16 17:12:43 Trixie systemd[1014]: Reached target paths.target - Paths.
Mar 16 17:12:43 Trixie systemd[1014]: Reached target timers.target - Timers.
Mar 16 17:12:43 Trixie systemd[1014]: Starting dbus.socket - D-Bus User Message Bus Socket...
Mar 16 17:12:43 Trixie systemd[1014]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Mar 16 17:12:43 Trixie systemd[1014]: Starting gcr-ssh-agent.socket - GCR ssh-agent wrapper...
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gnome-keyring-daemon.socket - GNOME Keyring daemon.
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 16 17:12:43 Trixie systemd[1014]: Starting gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Mar 16 17:12:43 Trixie systemd[1014]: Starting gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Mar 16 17:12:43 Trixie systemd[1014]: Listening on pulseaudio.socket - Sound System.
Mar 16 17:12:43 Trixie systemd[1014]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 16 17:12:43 Trixie systemd[1014]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 16 17:12:43 Trixie systemd[1014]: Reached target sockets.target - Sockets.
Mar 16 17:12:43 Trixie systemd[1014]: Reached target basic.target - Basic System.
Mar 16 17:12:43 Trixie systemd[1014]: Starting pulseaudio.service - Sound Service...
Mar 16 17:12:43 Trixie systemd[1014]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.
Mar 16 17:12:43 Trixie gnome-keyring-daemon[1038]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 16 17:12:43 Trixie systemd[1014]: Starting dbus.service - D-Bus User Message Bus...
Mar 16 17:12:43 Trixie systemd[1014]: Started dbus.service - D-Bus User Message Bus.
Mar 16 17:12:43 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.7' (uid=1000 pid=1045 comm="xfce4-session")
Mar 16 17:12:43 Trixie systemd[1014]: Starting at-spi-dbus-bus.service - Accessibility services bus...
Mar 16 17:12:43 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.a11y.Bus'
Mar 16 17:12:43 Trixie systemd[1014]: Started at-spi-dbus-bus.service - Accessibility services bus.
Mar 16 17:12:43 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.xfce.Xfconf' unit='xfconfd.service' requested by ':1.9' (uid=1000 pid=1045 comm="xfce4-session")
Mar 16 17:12:43 Trixie systemd[1014]: Starting xfconfd.service - Xfce configuration service...
Mar 16 17:12:43 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.xfce.Xfconf'
Mar 16 17:12:43 Trixie systemd[1014]: Started xfconfd.service - Xfce configuration service.
Mar 16 17:12:43 Trixie at-spi-bus-launcher[1111]: dbus-daemon[1111]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1045 comm="xfce4-session")
Mar 16 17:12:43 Trixie at-spi-bus-launcher[1111]: dbus-daemon[1111]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 16 17:12:43 Trixie at-spi-bus-launcher[1127]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 16 17:12:43 Trixie systemd[1014]: Started pulseaudio.service - Sound Service.
Mar 16 17:12:43 Trixie systemd[1014]: Reached target default.target - Main User Target.
Mar 16 17:12:43 Trixie systemd[1014]: Startup finished in 425ms.
Mar 16 17:12:43 Trixie systemd[1014]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Mar 16 17:12:43 Trixie gpg-agent[1137]: gpg-agent (GnuPG) 2.2.46 starting in supervised mode.
Mar 16 17:12:43 Trixie gpg-agent[1137]: using fd 3 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Mar 16 17:12:43 Trixie gpg-agent[1137]: using fd 4 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Mar 16 17:12:43 Trixie gpg-agent[1137]: using fd 5 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Mar 16 17:12:43 Trixie gpg-agent[1137]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Mar 16 17:12:43 Trixie gpg-agent[1137]: listening on: std=6 extra=4 browser=5 ssh=3
Mar 16 17:12:43 Trixie systemd[1014]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Mar 16 17:12:43 Trixie gpg-agent[1141]: gpg-agent (GnuPG) 2.2.46 starting in supervised mode.
Mar 16 17:12:43 Trixie gpg-agent[1141]: using fd 3 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Mar 16 17:12:43 Trixie gpg-agent[1141]: using fd 4 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Mar 16 17:12:43 Trixie gpg-agent[1141]: using fd 5 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Mar 16 17:12:43 Trixie gpg-agent[1141]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Mar 16 17:12:43 Trixie gpg-agent[1141]: listening on: std=6 extra=4 browser=5 ssh=3
Mar 16 17:12:44 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.12' (uid=1000 pid=1144 comm="xfwm4")
Mar 16 17:12:44 Trixie systemd[1014]: Starting gvfs-daemon.service - Virtual filesystem service...
Mar 16 17:12:44 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.gtk.vfs.Daemon'
Mar 16 17:12:44 Trixie systemd[1014]: Started gvfs-daemon.service - Virtual filesystem service.
Mar 16 17:12:44 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.14' (uid=1000 pid=1160 comm="xfsettingsd")
Mar 16 17:12:44 Trixie systemd[1014]: Starting dconf.service - User preferences database...
Mar 16 17:12:44 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'ca.desrt.dconf'
Mar 16 17:12:44 Trixie systemd[1014]: Started dconf.service - User preferences database.
Mar 16 17:12:45 Trixie systemd[1014]: Starting xfce4-notifyd.service - XFCE notifications service...
Mar 16 17:12:45 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.freedesktop.thumbnails.Thumbnailer1' unit='tumblerd.service' requested by ':1.18' (uid=1000 pid=1179 comm="xfdesktop")
Mar 16 17:12:45 Trixie systemd[1014]: Starting tumblerd.service - Thumbnailing service...
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: Failed to create virtgpu AddressSpaceStream
Mar 16 17:12:45 Trixie tumblerd[1211]: MESA: error: vulkan: Failed to get host connection
Mar 16 17:12:46 Trixie systemd[1014]: Started xfce4-notifyd.service - XFCE notifications service.
Mar 16 17:12:46 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.22' (uid=1000 pid=1206 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd")
Mar 16 17:12:46 Trixie systemd[1014]: Starting gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor...
Mar 16 17:12:46 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Mar 16 17:12:46 Trixie systemd[1014]: Started gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor.
Mar 16 17:12:46 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Mar 16 17:12:46 Trixie systemd[1014]: Started tumblerd.service - Thumbnailing service.
Mar 16 17:12:46 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.18' (uid=1000 pid=1179 comm="xfdesktop")
Mar 16 17:12:46 Trixie systemd[1014]: Starting gvfs-metadata.service - Virtual filesystem metadata service...
Mar 16 17:12:46 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.gtk.vfs.Metadata'
Mar 16 17:12:46 Trixie systemd[1014]: Started gvfs-metadata.service - Virtual filesystem metadata service.
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.34' (uid=1000 pid=1324 comm="pavucontrol")
Mar 16 17:12:53 Trixie systemd[1014]: Starting xdg-desktop-portal.service - Portal service...
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.35' (uid=1000 pid=1333 comm="/usr/libexec/xdg-desktop-portal")
Mar 16 17:12:53 Trixie systemd[1014]: Starting xdg-permission-store.service - sandboxed app permission store...
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Mar 16 17:12:53 Trixie systemd[1014]: Started xdg-permission-store.service - sandboxed app permission store.
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.35' (uid=1000 pid=1333 comm="/usr/libexec/xdg-desktop-portal")
Mar 16 17:12:53 Trixie systemd[1014]: Starting xdg-document-portal.service - flatpak document portal service...
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.freedesktop.portal.Documents'
Mar 16 17:12:53 Trixie systemd[1014]: Started xdg-document-portal.service - flatpak document portal service.
Mar 16 17:12:53 Trixie xdg-document-portal[1350]: Ignoring invalid max threads value 4294967295 > max (100000).
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.35' (uid=1000 pid=1333 comm="/usr/libexec/xdg-desktop-portal")
Mar 16 17:12:53 Trixie systemd[1014]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Mar 16 17:12:53 Trixie systemd[1014]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Mar 16 17:12:53 Trixie xdg-desktop-portal[1333]: pw.conf: can't load config client.conf: No such file or directory
Mar 16 17:12:53 Trixie xdg-desktop-portal[1333]: pw.conf: can't load config client.conf: No such file or directory
Mar 16 17:12:53 Trixie xdg-desktop-por[1333]: Failed connect to PipeWire: Couldn't create PipeWire context
Mar 16 17:12:53 Trixie dbus-daemon[1043]: [session uid=1000 pid=1043 pidfd=5] Successfully activated service 'org.freedesktop.portal.Desktop'
Mar 16 17:12:53 Trixie systemd[1014]: Started xdg-desktop-portal.service - Portal service.

This is from a fresh boot-up. The volume setting is lost, but no other bugs manifest yet.

Added later 1 h 57 min 29 s:
I tried "light-locker --no-lock-on-suspend" and got

** (light-locker:7372): WARNING **: 19:15:30.096: screensaver already running in this session

Offline

#6 2025-03-16 20:19:26

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,815
LinuxFirefox 136.0

Re: [SOLVED] Multiple interface bugs with new installation

light-locker is a locking program - thats why your computer is locking. If you want to run "light-locker --no-lock-on-suspend", then make sure the existing process of light-locker isn't running (kill it).

Mar 16 17:12:53 Trixie xdg-desktop-por[1333]: Failed connect to PipeWire: Couldn't create PipeWire context

Might be why you are having audio problems, but this isn't really an Xfce problem. You should post in the Debian forums about audio problems and see if someone can help there. Xfce doesn't create audio sinks, it just uses whats there.

And finally, make sure you run "journalctl" with sudo so you can see system messages as well.

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#7 2025-03-17 04:19:10

Xexan
Member
Registered: 2019-03-11
Posts: 10
LinuxFirefox 128.0

Re: [SOLVED] Multiple interface bugs with new installation

It seems that configuring light-locker with XFCE has long been an issue. Following a discussion at Debian User Forums, I uninstalled light-locker and installed xfce4-screensaver. That fixed the locking issue.

Added later 21 h 51 min 43 s:
Since uninstalling light-locker and installing xfce4-screensaver, all of the problems noted have stopped, so I guess I have to mark the issue solved. I can't believe the screensaver was affecting the audio.

Anyway I'm still getting a lot of errors regarding MESA, but it doesn't seem to affect operation. Here is the current xsession-errors.

Xsession: X session started for base at Tue Mar 18 01:13:58 AM UTC 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/base/.Xauthority
localuser:base being added to access control list
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
** Message: 01:13:58.984: Failed to fetch _NET_NUMBER_OF_DESKTOPS; assuming 1
** Message: 01:13:58.984: Failed to get _NET_WORKAREA; using full screen dimensions
** Message: 01:13:58.984: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
** Message: 01:13:58.984: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
xfce4-session-Message: 01:13:58.990: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one
** Message: 01:13:59.323: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0

(xfce4-session:53987): xfce4-session-WARNING **: 01:14:00.608: Unable to launch "light-locker" (specified by autostart/light-locker.desktop): Failed to execute child process “light-locker” (No such file or directory)
Process already running (98:Address already in use). Exiting.
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
[54260:54266:0318/011444.804101:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -100
[54260:54266:0318/011444.968339:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -100
Fontconfig error: Cannot load default config file: No such file: (null)

(xfce4-panel:54083): Gtk-WARNING **: 01:15:00.419: Failed to set text '<b><i>Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos - Google Chrome</i></b>' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as &amp;

(xfce4-panel:54083): Gtk-WARNING **: 01:15:00.419: Failed to set text '<b><i>Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos - Google Chrome</i></b>' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as &amp;
Warning: failed to launch javaldx - java may not function correctly
thunar-volman: Unsupported USB device type "usb".
Warning: failed to launch javaldx - java may not function correctly
thunar-volman: Unsupported USB device type "usb".
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).

Edit: Right after posting that, the system froze when I changed user accounts. I hard-rebooted and here is .xsession-errors-old.

Xsession: X session started for base at Tue Mar 18 01:13:58 AM UTC 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/base/.Xauthority
localuser:base being added to access control list
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
** Message: 01:13:58.984: Failed to fetch _NET_NUMBER_OF_DESKTOPS; assuming 1
** Message: 01:13:58.984: Failed to get _NET_WORKAREA; using full screen dimensions
** Message: 01:13:58.984: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
** Message: 01:13:58.984: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
xfce4-session-Message: 01:13:58.990: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one
** Message: 01:13:59.323: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0

(xfce4-session:53987): xfce4-session-WARNING **: 01:14:00.608: Unable to launch "light-locker" (specified by autostart/light-locker.desktop): Failed to execute child process “light-locker” (No such file or directory)
Process already running (98:Address already in use). Exiting.
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
[54260:54266:0318/011444.804101:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -100
[54260:54266:0318/011444.968339:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -100
Fontconfig error: Cannot load default config file: No such file: (null)

(xfce4-panel:54083): Gtk-WARNING **: 01:15:00.419: Failed to set text '<b><i>Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos - Google Chrome</i></b>' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as &amp;

(xfce4-panel:54083): Gtk-WARNING **: 01:15:00.419: Failed to set text '<b><i>Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos - Google Chrome</i></b>' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as &amp;
Warning: failed to launch javaldx - java may not function correctly
thunar-volman: Unsupported USB device type "usb".
Warning: failed to launch javaldx - java may not function correctly
thunar-volman: Unsupported USB device type "usb".
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Permission denied
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Permission denied, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Permission denied
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#-1 is a dynamic-sized tensor).
X connection to :0.0 broken (explicit kill or server shutdown).

Here are the last lines of "sudo journalctl -b -1" from the time of the freeze.

Mar 18 02:38:32 Trixie systemd[1019]: app-com.google.Chrome-61103.scope: Consumed 8.396s CPU time, 87.1M memory peak.
Mar 18 02:38:36 Trixie dbus-daemon[1048]: [session uid=1000 pid=1048 pidfd=5] Activating via systemd: service name='org.freed>
Mar 18 02:38:36 Trixie systemd[1019]: Starting tumblerd.service - Thumbnailing service...
Mar 18 02:38:36 Trixie dbus-daemon[1048]: [session uid=1000 pid=1048 pidfd=5] Successfully activated service 'org.freedesktop>
Mar 18 02:38:36 Trixie systemd[1019]: Started tumblerd.service - Thumbnailing service.
Mar 18 02:38:38 Trixie dbus-daemon[1048]: [session uid=1000 pid=1048 pidfd=5] Activating via systemd: service name='org.xfce.>
Mar 18 02:38:38 Trixie systemd[1019]: Starting xfconfd.service - Xfce configuration service...
Mar 18 02:38:38 Trixie dbus-daemon[1048]: [session uid=1000 pid=1048 pidfd=5] Successfully activated service 'org.xfce.Xfconf'
Mar 18 02:38:38 Trixie systemd[1019]: Started xfconfd.service - Xfce configuration service.
Mar 18 02:38:39 Trixie lightdm[53976]: Failed to write utmpx: No such file or directory
Mar 18 02:38:39 Trixie lightdm[53976]: pam_unix(lightdm:session): session closed for user base
Mar 18 02:38:39 Trixie at-spi-bus-launcher[54054]: X connection to :0 broken (explicit kill or server shutdown).
Mar 18 02:38:39 Trixie systemd-logind[757]: Session 75 logged out. Waiting for processes to exit.
Mar 18 02:38:39 Trixie systemd[1019]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Mar 18 02:38:39 Trixie systemd[1019]: xfce4-notifyd.service: Failed with result 'exit-code'.
Mar 18 02:38:39 Trixie systemd[1019]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 18 02:38:39 Trixie systemd[1019]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Mar 18 02:38:39 Trixie kernel: audit: type=1400 audit(1742265519.964:162): apparmor="ALLOWED" operation="capable" class="cap">
Mar 18 02:38:41 Trixie lightdm[62544]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBu>
Mar 18 02:38:41 Trixie lightdm[62544]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=107) by (uid=0)
Mar 18 02:38:41 Trixie systemd[1]: Created slice user-107.slice - User Slice of UID 107.
Mar 18 02:38:41 Trixie systemd[1]: Starting user-runtime-dir@107.service - User Runtime Directory /run/user/107...
Mar 18 02:38:41 Trixie systemd-logind[757]: New session c14 of user lightdm.
Mar 18 02:38:41 Trixie systemd[1]: Finished user-runtime-dir@107.service - User Runtime Directory /run/user/107.
Mar 18 02:38:41 Trixie systemd[1]: Starting user@107.service - User Manager for UID 107...
Mar 18 02:38:41 Trixie (systemd)[62550]: pam_unix(systemd-user:session): session opened for user lightdm(uid=107) by lightdm(>
Mar 18 02:38:41 Trixie systemd-logind[757]: New session 78 of user lightdm.
Mar 18 02:38:41 Trixie systemd-xdg-autostart-generator[62557]: Exec binary 'light-locker' does not exist: No such file or dir>
Mar 18 02:38:41 Trixie systemd-xdg-autostart-generator[62557]: /etc/xdg/autostart/light-locker.desktop: not generating unit, >
Mar 18 02:38:41 Trixie systemd[62550]: Queued start job for default target default.target.
Mar 18 02:38:42 Trixie systemd[62550]: Created slice app.slice - User Application Slice.
Mar 18 02:38:42 Trixie systemd[62550]: Created slice session.slice - User Core Session Slice.
Mar 18 02:38:42 Trixie systemd[62550]: Reached target paths.target - Paths.
Mar 18 02:38:42 Trixie systemd[62550]: Reached target timers.target - Timers.
Mar 18 02:38:42 Trixie systemd[62550]: Starting dbus.socket - D-Bus User Message Bus Socket...
Mar 18 02:38:42 Trixie systemd[62550]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Mar 18 02:38:42 Trixie systemd[62550]: Starting gcr-ssh-agent.socket - GCR ssh-agent wrapper...
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gnome-keyring-daemon.socket - GNOME Keyring daemon.
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache>
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (>
Mar 18 02:38:42 Trixie systemd[62550]: Starting gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Mar 18 02:38:42 Trixie systemd[62550]: Starting gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Mar 18 02:38:42 Trixie systemd[62550]: Listening on pulseaudio.socket - Sound System.
Mar 18 02:38:42 Trixie systemd[62550]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 18 02:38:42 Trixie systemd[62550]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 18 02:38:42 Trixie systemd[62550]: Reached target sockets.target - Sockets.
Mar 18 02:38:42 Trixie systemd[62550]: Reached target basic.target - Basic System.
Mar 18 02:38:42 Trixie systemd[1]: Started user@107.service - User Manager for UID 107.
Mar 18 02:38:42 Trixie systemd[62550]: Starting pulseaudio.service - Sound Service...
Mar 18 02:38:42 Trixie systemd[1]: Started session-c14.scope - Session c14 of User lightdm.
Mar 18 02:38:42 Trixie lightdm[62544]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=107) by (uid=0)
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Successfully made thread 62573 of process 62573 owned by '107' high priority at nic>
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 15 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie systemd[62550]: Starting dbus.service - D-Bus User Message Bus...
Mar 18 02:38:42 Trixie systemd[62550]: Started dbus.service - D-Bus User Message Bus.
Mar 18 02:38:42 Trixie dbus-daemon[62577]: [session uid=107 pid=62577 pidfd=5] Activating via systemd: service name='org.a11y>
Mar 18 02:38:42 Trixie systemd[62550]: Starting at-spi-dbus-bus.service - Accessibility services bus...
Mar 18 02:38:42 Trixie dbus-daemon[62577]: [session uid=107 pid=62577 pidfd=5] Successfully activated service 'org.a11y.Bus'
Mar 18 02:38:42 Trixie systemd[62550]: Started at-spi-dbus-bus.service - Accessibility services bus.
Mar 18 02:38:42 Trixie dbus-daemon[62577]: [session uid=107 pid=62577 pidfd=5] Activating via systemd: service name='org.gtk.>
Mar 18 02:38:42 Trixie systemd[62550]: Starting gvfs-daemon.service - Virtual filesystem service...
Mar 18 02:38:42 Trixie dbus-daemon[62577]: [session uid=107 pid=62577 pidfd=5] Successfully activated service 'org.gtk.vfs.Da>
Mar 18 02:38:42 Trixie systemd[62550]: Started gvfs-daemon.service - Virtual filesystem service.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 15 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Successfully made thread 62608 of process 62573 owned by '107' RT at priority 5.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 16 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 16 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Successfully made thread 62610 of process 62573 owned by '107' RT at priority 5.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 17 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 17 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Successfully made thread 62612 of process 62573 owned by '107' RT at priority 5.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 18 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 18 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Successfully made thread 62614 of process 62573 owned by '107' RT at priority 5.
Mar 18 02:38:42 Trixie rtkit-daemon[946]: Supervising 19 threads of 3 processes of 3 users.
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30030000 (msg/reply size: 16/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: sof_ipc3_route_setup: route BUF2.1 -> PGA2.0 failed
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30020000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30210000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget BUF2.2
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30020000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget EQIIR2.0
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30210000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget BUF2.1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30020000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget PGA2.0
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30210000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget BUF2.0
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30020000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget PCM0C
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30110000 (msg/reply size: 12/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: failed to free widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to free connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.2.HDA1.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at __soc_pcm_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel:  HDA Analog: ASoC: error at dpcm_fe_dai_hw_params on HDA Analog: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: empty reply received
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ipc tx error for 0x30100000 (msg/reply size: 48/0): -22
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to setup widget PIPELINE.10.DMIC0.IN
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Failed to set up connected widgets
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed widget list set up for pcm 6 dir 1
Mar 18 02:38:42 Trixie kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:0>
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie kernel:  DMIC: ASoC: error at dpcm_fe_dai_hw_params on DMIC: -22
Mar 18 02:38:42 Trixie systemd[62550]: Started pulseaudio.service - Sound Service.
Mar 18 02:38:42 Trixie systemd[62550]: Reached target default.target - Main User Target.
Mar 18 02:38:42 Trixie systemd[62550]: Startup finished in 717ms.
Mar 18 02:38:42 Trixie at-spi-bus-launcher[62587]: dbus-daemon[62587]: Activating service name='org.a11y.atspi.Registry' requ>
Mar 18 02:38:42 Trixie at-spi-bus-launcher[62587]: dbus-daemon[62587]: Successfully activated service 'org.a11y.atspi.Registr>
Mar 18 02:38:42 Trixie at-spi-bus-launcher[62618]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Regist>
lines 7574-7621/7621 (END)

Last edited by Xexan (2025-03-18 03:08:12)

Offline

#8 2025-03-18 22:06:09

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,815
LinuxFirefox 136.0

Re: [SOLVED] Multiple interface bugs with new installation

The MESA errors would be related to your video driver and sof-audio-pci-intel-cnl errors with your audio card. Unfortunately, I'm not well-versed with either audio or video troubleshooting and this is probably out of scope for an Xfce forum. Googling doesn't really bring up anything relevant.

However, when your computer freezes there are alot of audio card errors, so its most probably the likely cause and you should start your investigations there.

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#9 2025-03-18 22:22:06

Xexan
Member
Registered: 2019-03-11
Posts: 10
LinuxFirefox 128.0

Re: [SOLVED] Multiple interface bugs with new installation

OK, I'm marking this solved, because the XFCE specific issues of screen locking and wake-up were resolved by replacing the screensaver.

The problems with MESA and audio are more general Debian issues, so I'll pursue them in a more appropriate forum.

Thank you.

Last edited by Xexan (2025-03-18 22:24:46)

Offline

Pages: 1

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.009 seconds, 7 queries executed - Memory usage: 910.66 KiB (Peak: 999.51 KiB) ]