Mär 16 13:55:04 username-debian kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Mär 16 13:55:04 username-debian kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Mär 16 13:55:04 username-debian kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 Mär 16 13:55:04 username-debian kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Mär 16 13:55:04 username-debian kernel: nvme nvme0: missing or invalid SUBNQN field. Mär 16 13:55:04 username-debian kernel: ata5.00: supports DRM functions and may not be fully accessible Mär 16 13:55:04 username-debian kernel: ata5.00: supports DRM functions and may not be fully accessible Mär 16 13:55:04 username-debian kernel: ata6.00: supports DRM functions and may not be fully accessible Mär 16 13:55:04 username-debian kernel: ata6.00: supports DRM functions and may not be fully accessible Mär 16 13:55:04 username-debian systemd[1]: Current system time is further ahead 15y after build time, but cannot correct: Invalid argument Mär 16 13:55:04 username-debian systemd-udevd[443]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[447]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[460]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[468]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[450]: sdc: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdc' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[443]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[457]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[479]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[460]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[450]: sdc1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdc1' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[452]: sdc2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdc2' failed with exit code 1. Mär 16 13:55:04 username-debian systemd-udevd[458]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1. Mär 16 13:55:04 username-debian kernel: amdgpu 0000:2b:00.0: amdgpu: PSP runtime database doesn't exist Mär 16 13:55:04 username-debian systemd-udevd[440]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Mär 16 13:55:05 username-debian kernel: amdgpu: SRAT table not found Mär 16 13:55:05 username-debian systemd-udevd[457]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1. Mär 16 13:55:05 username-debian systemd-udevd[445]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1. Mär 16 13:55:05 username-debian systemd-udevd[446]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code 1. Mär 16 13:55:05 username-debian kernel: razermouse: loading out-of-tree module taints kernel. Mär 16 13:55:05 username-debian kernel: usb 3-1: 3:1: cannot get freq at ep 0x86 Mär 16 13:55:05 username-debian kernel: usb 3-1: 3:2: cannot get freq at ep 0x86 Mär 16 13:55:05 username-debian kernel: usb 3-1: 3:3: cannot get freq at ep 0x86 Mär 16 13:55:05 username-debian udisksd[1165]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Mär 16 13:55:05 username-debian udisksd[1165]: Failed to load the 'mdraid' libblockdev plugin Mär 16 13:55:05 username-debian kernel: usb 3-1: Warning! Unlikely big volume range (=4096), cval->res is probably wrong. Mär 16 13:55:05 username-debian kernel: usb 3-1: [7] FU [Mic Capture Volume] ch = 1, val = 0/4096/1 Mär 16 13:55:06 username-debian gnome-session-binary[1365]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mär 16 13:55:06 username-debian gnome-session-binary[1365]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mär 16 13:55:06 username-debian systemd[1318]: openrazer-daemon.service: Failed with result 'exit-code'. Mär 16 13:55:06 username-debian systemd[1318]: Failed to start Daemon to manage razer devices in userspace. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. Mär 16 13:55:06 username-debian tracker-miner-f[1453]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. Mär 16 13:55:06 username-debian gnome-shell[1396]: Could not open device /dev/input/event2: GDBus.Error:System.Error.ENODEV: No such device Mär 16 13:55:06 username-debian dbus-daemon[1530]: writing oom_score_adj error: Permission denied Mär 16 13:55:06 username-debian dbus-daemon[1544]: writing oom_score_adj error: Permission denied Mär 16 13:55:06 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=126 pid=1396 comm="/usr/bin/gnome-shell ") Mär 16 13:55:06 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Successfully activated service 'org.a11y.Bus' Mär 16 13:55:06 username-debian org.gnome.Shell.desktop[1587]: (WW) Option "-listen" for file descriptors is deprecated Mär 16 13:55:06 username-debian org.gnome.Shell.desktop[1587]: Please use "-listenfd" instead. Mär 16 13:55:06 username-debian org.gnome.Shell.desktop[1587]: (WW) Option "-listen" for file descriptors is deprecated Mär 16 13:55:06 username-debian org.gnome.Shell.desktop[1587]: Please use "-listenfd" instead. Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=126 pid=1396 comm="/usr/bin/gnome-shell ") Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=126 pid=1396 comm="/usr/bin/gnome-shell ") Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1565]: dbus-daemon[1565]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=126 pid=1396 comm="/usr/bin/gnome-shell ") Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1565]: dbus-daemon[1565]: Successfully activated service 'org.a11y.atspi.Registry' Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1396]: Window manager warning: Failed to parse saved session file: Datei »/var/lib/gdm3/.config/mutter/sessions/10a8e9fc8aff120e4c164743530625409400000013650000.ms« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=126 pid=1645 comm="/usr/libexec/gsd-sharing ") Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:07 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:07 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:07 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Successfully activated service 'org.gnome.Shell.Notifications' Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: The XKEYBOARD keymap compiler (xkbcomp) reports: Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86BrightnessAuto Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86DisplayOff Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Info Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AspectRatio Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86DVD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Audio Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ChannelUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ChannelDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Break Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86VideoPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ZoomReset Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Editor Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86GraphicsEditor Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Presentation Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Database Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Voicemail Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Addressbook Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86DisplayToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86SpellCheck Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ContextMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MediaRepeat Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF8610ChannelsUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF8610ChannelsDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Images Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NotificationCenter Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86PickupPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86HangupPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Fn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Fn_Esc Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86FnRightShift Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric0 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric6 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric7 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric8 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric9 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericStar Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericPound Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericA Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericB Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericC Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NumericD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraFocus Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86WPSButton Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraZoomIn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraZoomOut Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraLeft Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86CameraRight Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AttendantOn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AttendantOff Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AttendantToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86LightsToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ALSToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Buttonconfig Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Taskmanager Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Journal Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86ControlPanel Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AppSelect Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Screensaver Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86VoiceCommand Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Assistant Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86BrightnessMin Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86BrightnessMax Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistPrev Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistNext Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistPrevgroup Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistNextgroup Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistAccept Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdInputAssistCancel Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86RightUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86RightDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86LeftUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86LeftDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86RootMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MediaTopMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric11 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Numeric12 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86AudioDesc Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF863DMode Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86NextFavorite Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86StopRecord Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86PauseRecord Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86VOD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Unmute Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86FastReverse Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86SlowReverse Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Data Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86OnScreenKeyboard Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86PrivacyScreenToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86SelectiveScreenshot Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro6 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro7 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro8 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro9 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro10 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro11 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro12 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro13 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro14 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro15 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro16 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro17 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro18 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro19 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro20 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro21 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro22 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro23 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro24 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro25 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro26 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro27 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro28 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro29 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86Macro30 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroRecordStart Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroRecordStop Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroPresetCycle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroPreset1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroPreset2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86MacroPreset3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdLcdMenu1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdLcdMenu2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdLcdMenu3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdLcdMenu4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: > Internal error: Could not resolve keysym XF86KbdLcdMenu5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1775]: Errors from xkbcomp are not fatal to the X server Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.gnome.Shell.Screencast' requested by ':1.21' (uid=126 pid=1667 comm="/usr/libexec/gsd-media-keys ") Mär 16 13:55:07 username-debian xbrlapi.desktop[1795]: openConnection: connect: Datei oder Verzeichnis nicht gefunden Mär 16 13:55:07 username-debian xbrlapi.desktop[1795]: Kann nicht mit Braillegerätedienst brltty via :0 verbinden Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.gnome.ScreenSaver' requested by ':1.22' (uid=126 pid=1690 comm="/usr/libexec/gsd-power ") Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:window-screenshot Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:screenshot Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:screencast Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:hibernate Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:area-screenshot Mär 16 13:55:07 username-debian gsd-media-keys[1667]: Failed to grab accelerator for keybinding settings:playback-repeat Mär 16 13:55:07 username-debian gnome-shell[1396]: ATK Bridge is disabled but a11y has already been enabled. Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Successfully activated service 'org.gnome.ScreenSaver' Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: The XKEYBOARD keymap compiler (xkbcomp) reports: Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Warning: Unsupported maximum keycode 708, clipping. Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > X11 cannot support keycodes above 255. Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86BrightnessAuto Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86DisplayOff Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Info Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AspectRatio Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86DVD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Audio Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ChannelUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ChannelDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Break Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86VideoPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ZoomReset Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Editor Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86GraphicsEditor Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Presentation Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Database Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Voicemail Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Addressbook Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86DisplayToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86SpellCheck Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ContextMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MediaRepeat Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF8610ChannelsUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF8610ChannelsDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Images Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NotificationCenter Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86PickupPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86HangupPhone Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Fn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Fn_Esc Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86FnRightShift Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric0 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric6 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric7 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric8 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric9 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericStar Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericPound Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericA Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericB Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericC Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NumericD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraFocus Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86WPSButton Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraZoomIn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraZoomOut Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraLeft Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86CameraRight Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AttendantOn Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AttendantOff Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AttendantToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86LightsToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ALSToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Buttonconfig Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Taskmanager Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Journal Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86ControlPanel Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AppSelect Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Screensaver Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86VoiceCommand Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Assistant Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86BrightnessMin Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86BrightnessMax Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistPrev Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistNext Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistPrevgroup Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistNextgroup Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistAccept Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdInputAssistCancel Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86RightUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86RightDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86LeftUp Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86LeftDown Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86RootMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MediaTopMenu Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric11 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Numeric12 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86AudioDesc Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF863DMode Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86NextFavorite Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86StopRecord Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86PauseRecord Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86VOD Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Unmute Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86FastReverse Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86SlowReverse Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Data Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86OnScreenKeyboard Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86PrivacyScreenToggle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86SelectiveScreenshot Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro6 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro7 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro8 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro9 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro10 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro11 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro12 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro13 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro14 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro15 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro16 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro17 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro18 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro19 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro20 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro21 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro22 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro23 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro24 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro25 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro26 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro27 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro28 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro29 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86Macro30 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroRecordStart Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroRecordStop Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroPresetCycle Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroPreset1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroPreset2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86MacroPreset3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdLcdMenu1 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdLcdMenu2 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdLcdMenu3 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdLcdMenu4 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: > Internal error: Could not resolve keysym XF86KbdLcdMenu5 Mär 16 13:55:07 username-debian org.gnome.Shell.desktop[1831]: Errors from xkbcomp are not fatal to the X server Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Mär 16 13:55:07 username-debian gnome-shell[1396]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Mär 16 13:55:07 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Successfully activated service 'org.gnome.Shell.Screencast' Mär 16 13:55:08 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=126 pid=1645 comm="/usr/libexec/gsd-sharing ") Mär 16 13:55:08 username-debian /usr/libexec/gdm-wayland-session[1363]: dbus-daemon[1363]: [session uid=126 pid=1363] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:08 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:08 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:08 username-debian gsd-sharing[1645]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mär 16 13:55:08 username-debian systemd[1]: kerneloops.service: Found left-over process 1889 (kerneloops) in control group while starting unit. Ignoring. Mär 16 13:55:08 username-debian systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:55:18 username-debian gdm-password][2193]: gkr-pam: unable to locate daemon control file Mär 16 13:55:19 username-debian dbus-daemon[2265]: writing oom_score_adj error: Permission denied Mär 16 13:55:19 username-debian dbus-daemon[2272]: writing oom_score_adj error: Permission denied Mär 16 13:55:19 username-debian systemd[2201]: app-gnome-xdg\x2duser\x2ddirs-2343.scope: Failed to add PIDs to scope's control group: No such process Mär 16 13:55:19 username-debian systemd[2201]: app-gnome-xdg\x2duser\x2ddirs-2343.scope: Failed with result 'resources'. Mär 16 13:55:19 username-debian systemd[2201]: Failed to start Application launched by gnome-session-binary. Mär 16 13:55:19 username-debian systemd[2201]: org.gnome.Shell@x11.service: Start request repeated too quickly. Mär 16 13:55:20 username-debian dbus-daemon[2398]: writing oom_score_adj error: Permission denied Mär 16 13:55:20 username-debian dbus-daemon[2442]: writing oom_score_adj error: Permission denied Mär 16 13:55:20 username-debian dbus-daemon[2459]: writing oom_score_adj error: Permission denied Mär 16 13:55:20 username-debian at-spi-dbus-bus.desktop[2351]: dbus-daemon[2351]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=2344 comm="/usr/bin/gnome-shell ") Mär 16 13:55:20 username-debian at-spi-dbus-bus.desktop[2461]: dbus-daemon[2461]: writing oom_score_adj error: Permission denied Mär 16 13:55:20 username-debian at-spi-dbus-bus.desktop[2351]: dbus-daemon[2351]: Successfully activated service 'org.a11y.atspi.Registry' Mär 16 13:55:20 username-debian systemd[2201]: Dependency failed for GNOME XSettings service. Mär 16 13:55:20 username-debian dbus-daemon[2605]: writing oom_score_adj error: Permission denied Mär 16 13:55:20 username-debian dbus-daemon[2461]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client Mär 16 13:55:20 username-debian dbus-daemon[2461]: Unable to register client with session manager Mär 16 13:55:20 username-debian gnome-session-binary[2328]: GnomeDesktop-WARNING: Could not create transient scope for PID 2529: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2529 does not exist. Mär 16 13:55:20 username-debian systemd[2201]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2535.scope: Failed to add PIDs to scope's control group: No such process Mär 16 13:55:20 username-debian systemd[2201]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2535.scope: Failed with result 'resources'. Mär 16 13:55:20 username-debian systemd[2201]: Failed to start Application launched by gnome-session-binary. Mär 16 13:55:20 username-debian kernel: kauditd_printk_skb: 34 callbacks suppressed Mär 16 13:55:20 username-debian ubuntu-software-service.desktop[2692]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/var/lib/app-info /var/lib/app-info none bind,ro 0 0): cannot use "/var/lib/snapd/hostfs/var/lib/app-info" as bind-mount source: not a directory Mär 16 13:55:21 username-debian dbus-daemon[2788]: writing oom_score_adj error: Permission denied Mär 16 13:55:21 username-debian dbus-daemon[2937]: writing oom_score_adj error: Permission denied Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:playback-repeat Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:hibernate Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:screenshot Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:screencast Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:area-screenshot Mär 16 13:55:21 username-debian gsd-media-keys[2491]: Failed to grab accelerator for keybinding settings:window-screenshot Mär 16 13:55:21 username-debian gsd-rfkill[1657]: Error releasing name org.gnome.SettingsDaemon.Rfkill: Verbindung ist geschlossen Mär 16 13:55:21 username-debian gsd-screensaver[1670]: Error releasing name org.freedesktop.ScreenSaver: Verbindung ist geschlossen Mär 16 13:55:21 username-debian gnome-shell[1396]: Connection to xwayland lost Mär 16 13:55:21 username-debian gsd-sound[1675]: Error releasing name org.gnome.SettingsDaemon.Sound: Verbindung ist geschlossen Mär 16 13:55:21 username-debian gdm-launch-environment][1308]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Mär 16 13:55:21 username-debian gsd-color[2482]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Acer_Technologies_Acer_KG271_A_1918922177_gdm_126 Mär 16 13:55:21 username-debian gsd-color[2482]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Ancor_Communications_Inc_ASUS_VP247_G9LMTF117006_gdm_126 Mär 16 13:55:21 username-debian gnome-shell[2344]: ATK Bridge is disabled but a11y has already been enabled. Mär 16 13:55:21 username-debian dbus-daemon[3050]: writing oom_score_adj error: Permission denied Mär 16 13:55:22 username-debian polychromatic-autostart.desktop[2716]: /usr/bin/polychromatic-tray-applet:224: DeprecationWarning: Gtk.ImageMenuItem.set_image is deprecated Mär 16 13:55:22 username-debian polychromatic-autostart.desktop[2716]: item.set_image(img) # GTK3: Deprecated, no replacement! Mär 16 13:55:22 username-debian discord-canary.desktop[3102]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Mär 16 13:55:22 username-debian ubuntu-appindicators@ubuntu.com[2344]: unable to update icon for polychromatic-tray-applet Mär 16 13:55:22 username-debian ubuntu-appindicators@ubuntu.com[2344]: unable to update icon for discord1 Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.locale« hat den Pfad »/system/locale/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.proxy« hat den Pfad »/system/proxy/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.proxy.http« hat den Pfad »/system/proxy/http/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.proxy.https« hat den Pfad »/system/proxy/https/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.proxy.ftp« hat den Pfad »/system/proxy/ftp/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian ubuntu-software-service.desktop[3096]: Warnung: Schema »org.gnome.system.proxy.socks« hat den Pfad »/system/proxy/socks/«. Mit »/apps/«, »/desktop/« oder »/system/« beginnende Pfade gelten jedoch als veraltet. Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.238] [3204] (engine.cpp:236): Time: Wed Mar 16 13:55:23 2022 CET logLevel:2 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:77): Create Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:85): CreateForTest Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_buffer.cc:64): AudioDeviceBuffer::ctor Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:123): AudioDeviceModuleImpl Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:127): CheckPlatform Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:138): current platform is Linux Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:157): CreatePlatformSpecificObjects Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:982): PlatformAudioLayer Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:289): PulseAudio support is enabled. Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_mixer_manager_pulse_linux.cc:57): AudioMixerManagerLinuxPulse created Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_pulse_linux.cc:81): AudioDeviceLinuxPulse created Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:294): Linux PulseAudio APIs will be utilized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:335): AttachAudioBuffer Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_buffer.cc:180): SetRecordingSampleRate(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_buffer.cc:186): SetPlayoutSampleRate(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_buffer.cc:200): SetRecordingChannels(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_buffer.cc:206): SetPlayoutChannels(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_engine.cpp:48): Creating audio engine: standard Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.241] [3204] (audio_device_impl.cc:355): Init Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.244] [3204] (audio_processing_impl.cc:274): Injected APM submodules: Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Echo control factory: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Echo detector: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Capture analyzer: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Capture post processor: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Render pre processor: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.245] [3204] (audio_processing_impl.cc:274): Injected APM submodules: Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Echo control factory: 1 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Echo detector: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Capture analyzer: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Capture post processor: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: Render pre processor: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.246] [3204] (audio_processing_impl.cc:531): AudioProcessing::ApplyConfig: AudioProcessing::Config{ pipeline: { maximum_internal_processing_rate: 48000, multi_channel_render: 0, multi_channel_capture: 0 }, pre_amplifier: { enabled: 0, fixed_gain_factor: 1 }, high_pass_filter: { enabled: 1 }, echo_canceller: { enabled: 0, mobile_mode: 0, enforce_high_pass_filtering: 1 }, noise_suppression: { enabled: 0, level: Moderate }, transient_suppression: { enabled: 0 }, voice_detection: { enabled: 0 }, gain_controller1: { enabled: 0, mode: AdaptiveAnalog, target_level_dbfs: 3, compression_gain_db: 9, enable_limiter: 1, analog_level_minimum: 0, analog_level_maximum: 255 }, gain_controller2: { enabled: 0, fixed_digital: { gain_db: 0 }, adaptive_digital: { enabled: 0, level_estimator: { vad_probability_attack: 1, type: Rms, adjacent_speech_frames_threshold: 1, initial_saturation_margin_db: 20, extra_saturation_margin_db: 2 }, gain_applier: { adjacent_speech_frames_threshold: 1, max_gain_change_db_per_second: 3, max_output_noise_level_dbfs: -50 }}}, residual_echo_detector: { enabled: 1 }, level_estimation: { enabled: 0 }} Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.246] [3204] (audio_device_impl.cc:886): RegisterAudioCallback Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.246] [3204] (audio_device_buffer.cc:81): RegisterAudioCallback Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.324] [3204] (audio_device_impl.cc:345): ActiveAudioLayer Mär 16 13:55:23 username-debian gnome-keyring-daemon[2216]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.438] [3204] (audio_engine.cpp:127): Setting audio input device: 'FIFINE K670 Microphone Analog Stereo' Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.438] [3204] (audio_device_impl.cc:569): SetStereoRecording(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.438] [3204] (audio_device_buffer.cc:200): SetRecordingChannels(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.438] [3204] (audio_device_impl.cc:779): SetRecordingDevice Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.438] [3204] (audio_device_generic.cc:67): SetRecordingDevice: Not supported on this platform Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3183] (discord.cpp:516): JS console: ["%c[default]","[BUILD INFO] Release Channel: canary, Build Number: 119169, Version Hash: d1cdcaa285c0e3988c5501cd1156f78e60485c4a"] Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_impl.cc:557): StereoRecordingIsAvailable Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_mixer_manager_pulse_linux.cc:196): MicrophoneIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_impl.cc:564): output: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_impl.cc:569): SetStereoRecording(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_buffer.cc:200): SetRecordingChannels(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_mixer_manager_pulse_linux.cc:669): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_impl.cc:538): SetMicrophoneVolume(255) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_mixer_manager_pulse_linux.cc:575): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_engine.cpp:138): Setting audio output device: 'Starship/Matisse HD Audio Controller Analog Stereo' Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_impl.cc:711): SetPlayoutDevice Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.443] [3204] (audio_device_generic.cc:62): SetPlayoutDevice: Not supported on this platform Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.444] [3204] (audio_device_impl.cc:699): SetPlayoutDevice(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.444] [3204] (audio_device_impl.cc:603): StereoPlayoutIsAvailable Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.444] [3204] (audio_mixer_manager_pulse_linux.cc:189): SpeakerIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_device_impl.cc:610): output: 1 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_device_impl.cc:615): SetStereoPlayout(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_device_buffer.cc:206): SetPlayoutChannels(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_mixer_manager_pulse_linux.cc:669): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_device_impl.cc:538): SetMicrophoneVolume(255) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.445] [3204] (audio_mixer_manager_pulse_linux.cc:575): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.491] [3183] (discord.cpp:516): JS console: ["%c[default]","[NATIVE INFO] host 0.0.134, modules: discord_desktop_core: 61, discord_erlpack: 61, discord_spellcheck: 61, discord_utils: 61, discord_voice: 61, discord_game_utils: 61, discord_rpc: 61"] Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.588] [3183] (discord.cpp:516): JS console: ["[FAST CONNECT] connected in 841ms"] Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.591] [3204] (audio_engine.cpp:127): Setting audio input device: 'default' Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.591] [3204] (audio_device_impl.cc:817): RecordingIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.591] [3204] (audio_device_impl.cc:569): SetStereoRecording(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.591] [3204] (audio_device_buffer.cc:200): SetRecordingChannels(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.591] [3204] (audio_device_impl.cc:767): SetRecordingDevice(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:557): StereoRecordingIsAvailable Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_mixer_manager_pulse_linux.cc:196): MicrophoneIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:564): output: 0 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:569): SetStereoRecording(0) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_buffer.cc:200): SetRecordingChannels(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_mixer_manager_pulse_linux.cc:669): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:538): SetMicrophoneVolume(255) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_mixer_manager_pulse_linux.cc:575): input device index has not been set Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_engine.cpp:138): Setting audio output device: 'Starship/Matisse HD Audio Controller Analog Stereo' Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:811): PlayoutIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_impl.cc:711): SetPlayoutDevice Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.592] [3204] (audio_device_generic.cc:62): SetPlayoutDevice: Not supported on this platform Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_device_impl.cc:699): SetPlayoutDevice(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_device_impl.cc:603): StereoPlayoutIsAvailable Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_mixer_manager_pulse_linux.cc:189): SpeakerIsInitialized Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_device_impl.cc:610): output: 1 Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_device_impl.cc:615): SetStereoPlayout(1) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.593] [3204] (audio_device_buffer.cc:206): SetPlayoutChannels(2) Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.630] [3183] (discord.cpp:516): JS console: ["%c[Spellchecker]","sh is not a valid locale."] Mär 16 13:55:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:23.631] [3183] (discord.cpp:516): JS console: ["%c[Spellchecker]","Switching to de-DE","(available)"] Mär 16 13:55:24 username-debian gnome-software[2538]: plugin appstream took 2,0 seconds to do setup Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.258] [3183] (discord.cpp:516): JS console: ["%c[CloudSyncUtils]","CloudSync is not supported on this platform"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.472] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zlib-stream"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.472] [3183] (discord.cpp:516): JS console: ["[FAST CONNECT] successfully took over websocket, state:","[object Object]"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.472] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[CONNECTED] wss://gateway.discord.gg/?encoding=etf&v=9&compress=zlib-stream in 0 ms"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.472] [3183] (discord.cpp:516): JS console: ["%c[ConnectionStore]","handleIdentify called","[object Object]"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.472] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[IDENTIFY]"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.479] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[HELLO] via [\"gateway-prd-main-0m4p\",{\"micros\":0.0}], heartbeat interval: 41250, took 7 ms"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.484] [3183] (discord.cpp:516): JS console: ["%c[RPCServer:WSS]","Starting on 6463"] Mär 16 13:55:24 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:24.486] [3183] (discord.cpp:516): JS console: ["%c[RPCServer:IPC]","Starting on /run/user/1000/discord-ipc-0"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.423] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[READY] took 951ms, via [\"gateway-prd-main-0m4p\",{\"micros\":410016,\"calls\":[\"discord-sessions-blue-prd-2-168\",{\"micros\":388331,\"calls\":[\"start_session\",{\"micros\":160524,\"calls\":[\"discord-api-7b5457cbd4-chvk7\",{\"micros\":148397,\"calls\":[\"get_user\",{\"micros\":19441},\"add_authorized_ip\",{\"micros\":9957},\"get_guilds\",{\"micros\":5655},\"private_channels\",{\"micros\":41407},\"read_states\",{\"micros\":19748},\"coros_wait\",{\"micros\":12358},\"aliases\",{\"micros\":4064},\"affine_user_ids\",{\"micros\":2957},\"experiments\",{\"micros\":4986}]}]},\"guilds_connect\",{\"micros\":8785,\"calls\":[]},\"presence_connect\",{\"micros\":1,\"calls\":[]}]}]}] as cd744d43154260c399ccbae1d441da1e"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.444] [3183] (discord.cpp:516): JS console: ["%c[AuthenticationStore]","handleConnectionOpen called","[object Object]"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.482] [3183] (discord.cpp:516): JS console: ["%c[Spotify]","WS Connecting"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.482] [3183] (discord.cpp:516): JS console: ["%c[Spotify]","Added account: loch-jannick"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.484] [3183] (discord.cpp:516): JS console: ["%c[NativeDispatchUtils]","Tried getting Dispatch instance before instantiated"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.683] [3183] (discord.cpp:516): JS console: ["%c[Flux]","Slow batch emitChanges took 191ms recentActions:","EXPERIMENT_TRIGGER -> EXPERIMENT_TRIGGER -> EXPERIMENT_TRIGGER -> USER_SETTINGS_UPDATE -> CHANNEL_SELECT -> EXPERIMENT_TRIGGER -> TRACK -> NOW_PLAYING_MOUNTED -> APP_VIEW_SET_HOME_LINK -> BILLING_PAYMENT_SOURCES_FETCH_START"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.747] [3183] (discord.cpp:516): JS console: ["%c[GatewaySocket]","[READY_SUPPLEMENTAL] took 1275ms"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.898] [3183] (discord.cpp:516): JS console: ["%c[Spotify]","WS Connected"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.965] [3183] (discord.cpp:516): JS console: ["%c[RunningGameStore]","games","[object Object]"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.976] [3183] (discord.cpp:516): JS console: ["%c[NativeDispatchUtils]","Tried getting Dispatch instance before instantiated"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.977] [3183] (discord.cpp:516): JS console: ["%c[Spotify]","Profile updated for loch-jannick: isPremium = false"] Mär 16 13:55:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:25.997] [3183] (discord.cpp:516): JS console: ["%c[Spotify]","Devices updated for loch-jannick:",""] Mär 16 13:55:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:26.003] [3183] (discord.cpp:516): JS console: ["%c[AutoAnalytics]","Cannot identify game","Error: Error 1 when fetching info on 2288"] Mär 16 13:55:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:26.246] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:26.246] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:26.247] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:26 username-debian snap-store[2644]: /etc/PackageKit/Vendor.conf file not found Mär 16 13:55:27 username-debian snap-store[2644]: lost session service Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://archive.canonical.com/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-security/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/apt-fast/stable/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://brave-browser-apt-beta.s3.brave.com/dists/stable/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/canonical-kernel-team/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/dreibh/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.javinator9889.com/dists/canary/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/libreoffice/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/linrunner/tlp/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mamarley/updates/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://packages.microsoft.com/repos/edge/dists/stable/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mmk2410/intellij-idea/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/openjdk-r/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/openrazer/stable/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/polychromatic/testing/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/ubuntu-mozilla-daily/ppa/ubuntu/dists/jammy/InRelease Mär 16 13:55:28 username-debian packagekitd[1625]: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. Mär 16 13:55:28 username-debian snap-store[2644]: not handling error failed for action refresh: E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease E: Fehlschlag beim Holen von http://archive.canonical.com/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-updates/InRelease E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-backports/InRelease E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-security/InRelease E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/apt-fast/stable/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://brave-browser-apt-beta.s3.brave.com/dists/stable/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/canonical-kernel-team/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/dreibh/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.javinator9889.com/dists/canary/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/libreoffice/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/linrunner/tlp/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mamarley/updates/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://packages.microsoft.com/repos/edge/dists/stable/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mmk2410/intellij-idea/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/openjdk-r/ppa/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/openrazer/stable/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/polychromatic/testing/ubuntu/dists/jammy/InRelease E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/ubuntu-mozilla-daily/ppa/ubuntu/dists/jammy/InRelease E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Builder.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Calculator.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.clocks.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Dictionary.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Documents.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Evince/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.gedit.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Maps.desktop/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: adding wildcard app */*/*/org.gnome.Weather/* to plugin cache Mär 16 13:55:28 username-debian snap-store[2644]: Only 0 apps for recent list, hiding Mär 16 13:55:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:29.250] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:29.370] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:29.371] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:29.905] [3183] (discord.cpp:516): JS console: ["%c[RTCLatencyTestManager]","RTC cached preferred region is rotterdam"] Mär 16 13:55:31 username-debian nautilus[2442]: Could not delete '.meta.isrunning': Datei oder Verzeichnis nicht gefunden Mär 16 13:55:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:32.374] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:32.494] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:32.495] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:35.498] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:35.619] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:35.619] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:39 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:39.424] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:39 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:39.545] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:39 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:39.545] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:42 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:42.548] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:42 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:42.677] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:42 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:42.677] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:45.680] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:45.805] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:45.805] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:48.808] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:48.932] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:48.933] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:51 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:51.936] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:52 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:52.061] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:52 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:52.061] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:55 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:55.064] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:55 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:55.185] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:55 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:55.185] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:55:58 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:58.188] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:58 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:58.309] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:55:58 username-debian discord-canary.desktop[3183]: [2022-03-16 13:55:58.309] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:01 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:01.313] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:01 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:01.438] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:01 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:01.438] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:04 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:04.441] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:04 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:04.565] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:04 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:04.565] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:07 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:07.568] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:07 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:07.688] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:07 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:07.689] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:10.692] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:10.816] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:10.816] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:12 username-debian gnome-shell[2344]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:12 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:13.817] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:13.941] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:13.941] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:16 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:16.944] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:17 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:17.073] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:17 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:17.073] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:20 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:20.076] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:20 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:20.201] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:20 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:20.201] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:21 username-debian gnome-shell[2344]: Object 0x7f10b01ad6d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:21 username-debian gnome-shell[2344]: Object 0x55b864ac24c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:21 username-debian gnome-shell[2344]: Object 0x55b863878d20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:23.204] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:23.325] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:23 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:23.325] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:23 username-debian ubuntu-appindicators@ubuntu.com[2344]: unable to update icon for software-update-available Mär 16 13:56:24 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Mär 16 13:56:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:26.328] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:26.457] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:26 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:26.457] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:29.459] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:29.583] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:29.583] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:31 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b8647d2f30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b863e8c9a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b8644b7ac0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x7f10b01ad840 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b861bd0cd0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b8644b7ac0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b863b0f530 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b8644b7ac0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:31 username-debian gnome-shell[2344]: Object 0x55b863b0f450 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:32 username-debian gnome-shell[2344]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Mär 16 13:56:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:32.586] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:32.709] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:32.709] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:35.712] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:35.845] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:35.845] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian gnome-shell[2344]: setup_framebuffers: assertion 'width > 0' failed Mär 16 13:56:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:38.848] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:38.977] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:38.977] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b863878e70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b863cef570 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b8643c5b00 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b863b0fa90 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b863cef570 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b8643c5860 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b8646bfd40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian gnome-shell[2344]: Object 0x55b863cef6c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:41 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:41.980] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:42 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:42.104] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:42 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:42.104] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:45.108] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:45.229] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:45 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:45.229] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:46 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Mär 16 13:56:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:48.232] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:48.353] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:48 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:48.353] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:51 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:51.356] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:51 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:51.489] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:51 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:51.489] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d246f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b8643c5a20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b8646bfa10 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d242e0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d24040 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d24120 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d24270 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x7f10b01ad8b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b863d24040 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b8630d2920 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:51 username-debian gnome-shell[2344]: Object 0x55b8643c5940 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:56:54 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:54.492] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:54 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:54.616] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:54 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:54.616] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:56:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:57.620] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:57.740] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:56:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:56:57.741] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:00.744] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:00.869] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:00.869] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:03.871] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:03.993] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:03.993] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:04 username-debian pkexec[12916]: username: Error executing command as another user: Request dismissed [USER=root] [TTY=unknown] [CWD=/home/username] [COMMAND=/usr/share/apport/root_info_wrapper /tmp/tmpb2dhmg4g/:script:] Mär 16 13:57:04 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Mär 16 13:57:06 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:06.996] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:07 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:07.117] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:07 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:07.117] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:10.120] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:10.244] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:10 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:10.245] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:13.248] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:13.369] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:13 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:13.369] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:13 username-debian gnome-shell[2344]: Object 0x55b863e8ca10 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:13 username-debian gnome-shell[2344]: Object 0x55b863d73df0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:13 username-debian gnome-shell[2344]: Object 0x55b8647d2c20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:13 username-debian gnome-shell[2344]: Object 0x55b863cef5e0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:13 username-debian gnome-shell[2344]: Object 0x55b863cef5e0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:16 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:16.373] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:16 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:16.498] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:16 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:16.498] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:19 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:19.501] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:19 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:19.629] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:19 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:19.629] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:22 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:22.632] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:22 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:22.753] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:22 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:22.753] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:25.756] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:25.876] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:25 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:25.877] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:27 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Mär 16 13:57:27 username-debian gnome-shell[2344]: Object 0x55b8646bfaf0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:27 username-debian gnome-shell[2344]: Object 0x55b863cef6c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:27 username-debian gnome-shell[2344]: Object 0x55b863d244c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:27 username-debian gnome-shell[2344]: Object 0x55b864729ad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:27 username-debian gnome-shell[2344]: Object 0x55b864729ad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:28 username-debian ubuntu-advantag[8086]: Failed to parse UA status: Vorgang wurde abgebrochen Mär 16 13:57:28 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:28.880] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:29.000] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:29 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:29.001] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:32.004] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:32.125] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:32 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:32.125] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:35.128] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:35.248] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:35 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:35.249] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:37 username-debian gnome-shell[2344]: Object 0x55b863b0fa20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:37 username-debian gnome-shell[2344]: Object 0x55b863f93ad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:37 username-debian gnome-shell[2344]: Object 0x55b863d73e60 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:37 username-debian gnome-shell[2344]: Object 0x55b8647298a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:37 username-debian gnome-shell[2344]: Object 0x55b866abc850 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mär 16 13:57:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:38.252] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:38.377] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:38 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:38.377] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:41 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:41.380] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:41 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:41.501] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:41 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:41.501] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:44 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:44.503] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:44 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:44.624] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:44 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:44.625] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:47 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:47.628] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:47 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:47.749] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:47 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:47.749] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:50 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:50.752] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:50 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:50.873] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:50 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:50.873] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:53 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:53.877] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:54 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:54.001] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:54 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:54.002] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:57:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:57.005] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:57.129] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:57:57 username-debian discord-canary.desktop[3183]: [2022-03-16 13:57:57.129] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:00.132] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:00.252] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:00 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:00.253] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11141 (firefox-trunk) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11238 (Socket Process) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11409 (WebExtensions) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11553 (Privileged Cont) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11700 (Isolated Web Co) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 11877 (Web Content) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 12065 (Web Content) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:00 username-debian systemd[2201]: update-notifier-crash.service: Found left-over process 13107 (Web Content) in control group while starting unit. Ignoring. Mär 16 13:58:00 username-debian systemd[2201]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mär 16 13:58:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:03.256] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:03.384] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:03 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:03.384] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:06 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:06.385] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:06 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:06.513] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:06 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:06.513] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:09 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:09.516] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:09 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:09.638] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:09 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:09.639] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:12 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:12.641] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:12 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:12.765] [3205] (device_info_linux.cc:45): NumberOfDevices Mär 16 13:58:12 username-debian discord-canary.desktop[3183]: [2022-03-16 13:58:12.766] [3205] (device_info_linux.cc:78): GetDeviceName Mär 16 13:58:12 username-debian gnome-shell[2344]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed