XFCE desktop freezes at start - just wallpaper is shown -nothing works

ixefce · 2023-03-31 05:24:57

Hello.
Out of sudden after a crash XFCE desktop freezes at start - just the wallpaper appears - nothing further happens. No symbols, no reaction to any input (really!) from keyboard or mouse except Strg+ALT+F2 or Strg+ALT+F4. I just can run other desktops witout problems (I have installed them BEFORE)
got no idea whats wrong.

Anyone out there who can help me?

regards

my laptop:
Kernel : Linux 6.1.0-2mx-amd64 (x86_64)
Version : #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1~mx21+1 (2023-01-20)
C-Library : GNU C Library / (Debian GLIBC 2.31-13+deb11u5) 2.31
Distribution : Debian GNU/Linux 11 (bullseye)
Processor : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz

ToZ · 2023-03-31 10:28:54

Sounds like a corrupted cache. Before you log in, go to another virtual terminal (Ctrl+Alt+F2), log in to the text session, and delete the contents of ~/.cache/sessions.

ixefce · 2023-03-31 13:53:17

@ToZ: Thanks, but that doesn't change anything.
what else can I try?

ToZ · 2023-03-31 14:26:31

Are you able to post back the contents of your ~/.xsession-errors file?

ToZ · 2023-04-01 18:04:16

This is for kde. I want to see Xfce's. Perhaps its in the ~/.xsession-errors.old file?

If not, try Xfce one more time and when it fails and you log in via kde, it will be in ~/.xsession-errors.old file.

ixefce · 2023-04-01 19:10:31

Xsession: X session started for ixefce at Fr 31. Mär 15:44:24 CEST 2023
WARNING: tempfile is deprecated; consider using mktemp instead.
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/ixefce/.Xauthority
localuser:ixefce being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting GTK_MODULES=canberra-gtk-module:gail:atk-bridge
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_SCALE_FACTOR=1
dbus-update-activation-environment: setting USER=ixefce
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting QT_PLATFORMTHEME=gtk2
dbus-update-activation-environment: setting HOME=/home/ixefce
dbus-update-activation-environment: setting DESKTOP_SESSION=xfce
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting GTK_MODULES=canberra-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-nr7B7pz08n,guid=7ef38f91e8a4881e1a090ee06426e3b8
dbus-update-activation-environment: setting QT_QPA_PLATFORMTHEME=gtk2
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LOGNAME=ixefce
dbus-update-activation-environment: setting GTK_IM_MODULE=ibus
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=de_DE.utf8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=XFCE
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=xfce
dbus-update-activation-environment: setting XAUTHORITY=/home/ixefce/.Xauthority
dbus-update-activation-environment: setting XMODIFIERS=@im=ibus
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/ixefce
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=xfce
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting QT_LOGGING_RULES=qt.qpa.xcb.warning=false
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting QT_IM_MODULE=ibus
dbus-update-activation-environment: setting PWD=/home/ixefce
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/home/ixefce/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting CLUTTER_IM_MODULE=ibus
dbus-update-activation-environment: setting QT_PLATFORM_PLUGIN=gtk2
VirtualBox Additions disabled, not in a Virtual Machine
/usr/bin/startxfce4: X server already running on display :0

(xfce4-session:3692): dbind-WARNING **: 15:44:25.043: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
/usr/bin/iceauth:  creating new authority file /run/user/1000/ICEauthority
xfce4-session: GNOME compatibility is enabled and gnome-keyring-daemon is found on the system. Skipping gpg/ssh-agent startup.
env: „kdeinit4“: Datei oder Verzeichnis nicht gefunden
Cannot find '.setLaunchEnv' in object /KLauncher at org.kde.klauncher

(xfwm4:3988): dbind-WARNING **: 15:44:26.252: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfsettingsd:3991): dbind-WARNING **: 15:44:26.576: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-panel:4053): dbind-WARNING **: 15:44:29.549: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-panel:4053): xfce4-panel-CRITICAL **: 15:44:29.555: Plugin org.xfce.orage.clock-plugin: There was no module found at "/usr/lib/xfce4/panel-plugins/liborageclock.so"

(Thunar:4057): dbind-WARNING **: 15:44:29.604: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfdesktop:4062): dbind-WARNING **: 15:44:29.654: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4065): dbind-WARNING **: 15:44:29.757: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4066): dbind-WARNING **: 15:44:29.775: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4076): dbind-WARNING **: 15:44:29.810: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4069): dbind-WARNING **: 15:44:29.812: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4071): dbind-WARNING **: 15:44:29.835: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4072): dbind-WARNING **: 15:44:29.856: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4075): dbind-WARNING **: 15:44:29.856: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4077): dbind-WARNING **: 15:44:29.857: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4070): dbind-WARNING **: 15:44:29.858: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4089): dbind-WARNING **: 15:44:29.865: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4086): dbind-WARNING **: 15:44:29.866: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (wrapper-2.0:4071): WARNING **: 15:44:29.890: No outputs have backlight property

(wrapper-2.0:4078): dbind-WARNING **: 15:44:29.895: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4095): dbind-WARNING **: 15:44:29.943: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4109): dbind-WARNING **: 15:44:29.954: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4098): dbind-WARNING **: 15:44:29.958: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4104): dbind-WARNING **: 15:44:29.963: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4101): dbind-WARNING **: 15:44:29.971: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:4116): dbind-WARNING **: 15:44:29.996: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

(xfce4-session:3692): xfce4-session-WARNING **: 15:44:30.035: Unable to launch "/usr/bin/skypeforlinux" (specified by autostart/skypeforlinux.desktop): Kindprozess »/usr/bin/skypeforlinux« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)
only one keyboard
No keyboard layout specified on the command line
Trailing -layout option ignored
Tracker-Message: 15:44:30.086: Set scheduler policy to SCHED_IDLE
Tracker-Message: 15:44:30.086: Setting priority nice level to 19
Gtk-Message: 15:44:30.089: Failed to load module "gail"
Gtk-Message: 15:44:30.090: Failed to load module "gail"
Gtk-Message: 15:44:30.110: Failed to load module "gail"

** (mx-tweak:4165): WARNING **: 15:44:30.124: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

** (mx-tweak:4147): WARNING **: 15:44:30.125: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

** (klipper:4129): WARNING **: 15:44:30.125: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

** (wrapper-2.0:4104): WARNING **: 15:44:30.200: application.vala:315: Fehler beim Lesen der Datei »/home/ixefce/.local/share/notes/Notizen/new«: Ist ein Verzeichnis
dbus-daemon[4238]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=4137 comm="synapse --startup ")

** (xfce4-clipman:4153): WARNING **: 15:44:30.332: Unable to register GApplication: Für die Schnittstelle org.gtk.Application auf /org/xfce/clipman wurde bereits ein Objekt exportiert

(xfce4-clipman:4153): GLib-GIO-CRITICAL **: 15:44:30.332: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:4153): GLib-WARNING **: 15:44:30.332: g_set_application_name() called multiple times
dbus-daemon[4238]: Successfully activated service 'org.a11y.atspi.Registry'
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Gtk-Message: 15:44:30.381: Failed to load module "gail"
Gtk-Message: 15:44:30.403: Failed to load module "gail"

** (mx-usb-unmounter:4230): WARNING **: 15:44:30.415: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

** (parcellite:4285): WARNING **: 15:44:30.424: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)
Looking in '/etc/xdg/parcellite/parcelliterc'
Gtk-Message: 15:44:30.446: Failed to load module "gail"
Tracker-Message: 15:44:30.478: Set scheduler policy to SCHED_IDLE
Tracker-Message: 15:44:30.478: Setting priority nice level to 19
Looking in '/etc/xdg/parcellite/parcelliterc'
Looking in '/etc/xdg/parcellite/parcelliterc'
Flag 0x0001, status 0, EXIT 1 STAT 0

** (kdeconnectd:4239): WARNING **: 15:44:30.533: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

(xfce4-power-manager:4241): xfce4-power-manager-WARNING **: 15:44:30.616: could not map keysym 1008ffa8 to keycode


** (xfce4-power-manager:4241): WARNING **: 15:44:30.649: No outputs have backlight property

(wrapper-2.0:4101): Gtk-WARNING **: 15:44:30.674: Negative content width -2 (allocation 16, extents 9x9) while allocating gadget (node entry, owner GtkEntry)

(xfce4-power-manager:4241): xfce4-power-manager-WARNING **: 15:44:30.676: It seems the kernel brightness switch handling value was not restored properly on exit last time, xfce4-power-manager will try to restore it this time.
xfce4-power-manager-Message: 15:44:30.709: Set kernel brightness switch to 0
Baloo File Indexing has been disabled

(xfce4-power-manager:4241): xfce4-power-manager-WARNING **: 15:44:30.714: Failed to get keyboard max brightness level : GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.UPower.KbdBacklight” on object at path /org/freedesktop/UPower/KbdBacklight
Ein anderer Benachrichtigungsdienst läuft – es wird beendet
weather-Message: 15:44:30.912: [url]https://api.met.no/weatherapi/locationforecast/2.0/classic?lat=51.052428&lon=6.852257&altitude=46[/url] wird abgerufen

** (wrapper-2.0:4104): WARNING **: 15:44:30.977: application.vala:315: Fehler beim Lesen der Datei »/home/ixefce/.local/share/notes/Notizen/cur«: Ist ein Verzeichnis
ls: Zugriff auf '/home/ixefce/.config/MX-Linux/MX-Tweak/brightness' nicht möglich: Datei oder Verzeichnis nicht gefunden

(wrapper-2.0:4104): Gtk-CRITICAL **: 15:44:31.074: gtk_text_buffer_emit_insert: assertion 'g_utf8_validate (text, len, NULL)' failed

** (wrapper-2.0:4104): WARNING **: 15:44:31.147: application.vala:315: Fehler beim Lesen der Datei »/home/ixefce/.local/share/notes/Notizen/tmp«: Ist ein Verzeichnis
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.104'

(wrapper-2.0:4089): LIBDBUSMENU-GLIB-WARNING **: 15:44:31.356: Getting layout failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/NO_DBUSMENU'
[94m[INFO 15:44:30.039440][0m [synapse-main:267] Starting up...
[94m[INFO 15:44:30.918248][0m [synapse-main:209] Binding activation to <Control>space
[94m[INFO 15:44:31.237097][0m [view-base:251] Screen is composited.
[94m[INFO 15:44:31.238177][0m [controller:56] Using ibus input method.
[93m[WARN 15:44:31.343346][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/kipiplugins.desktop
[93m[WARN 15:44:31.354450][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/org.kde.mobile.okular_tiff.desktop
[93m[WARN 15:44:31.354684][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/org.kde.mobile.okular_md.desktop
[93m[WARN 15:44:31.354942][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/org.kde.mobile.okular_epub.desktop
[93m[WARN 15:44:31.355240][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/org.kde.mobile.okular_djvu.desktop
[93m[WARN 15:44:31.355454][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/org.kde.mobile.okular_chm.desktop
[93m[WARN 15:44:31.357837][0m [desktop-file-service:76] X-Cinnamon is not understood
[93m[WARN 15:44:31.378130][0m [desktop-file-service:200] Not Application-type desktop entry
[93m[WARN 15:44:31.391200][0m [desktop-file-service:200] Unable to get exec for GNOME Shell integration
[93m[WARN 15:44:31.392358][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/evolution-calendar.desktop
[93m[WARN 15:44:31.392559][0m [desktop-file-service:76] Dawati is not understood
[93m[WARN 15:44:31.398223][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.408549][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.408785][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.409110][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.409387][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.409584][0m [desktop-file-service:76] Budgie is not understood
[93m[WARN 15:44:31.424735][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.425102][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.428708][0m [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/synaptic-kde.desktop
[93m[WARN 15:44:31.442396][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.442584][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.443599][0m [desktop-file-service:200] Not Application-type desktop entry
[93m[WARN 15:44:31.447613][0m [desktop-file-service:76] LXQt is not understood
[93m[WARN 15:44:31.450784][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.452002][0m [desktop-file-service:76] X-Cinnamon is not understood
[93m[WARN 15:44:31.452240][0m [desktop-file-service:200] Die Schlüsselwertedatei enthält den Schlüssel »NoDisplay« mit einem Wert, der nicht interpretiert werden konnte.
[93m[WARN 15:44:31.466823][0m [desktop-file-service:200] Unable to create AppInfo for /home/ixefce/.local/share/applications/org.kde.kate.desktop
[93m[WARN 15:44:31.493109][0m [desktop-file-service:200] Unable to create AppInfo for /home/ixefce/.local/share/applications/userapp-Thunderbird-71SFX1.desktop
[93m[WARN 15:44:31.518313][0m [ssh-plugin:114] /home/ixefce/.ssh/config: Fehler beim Öffnen der Datei »/home/ixefce/.ssh/config«: Datei oder Verzeichnis niccompton            4237
XfceVersion =  4.18
Gtk-Message: 15:44:36.508: Failed to load module "gail"

** (python3:5075): WARNING **: 15:44:36.514: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)
Cleanup-notifier: available space at '/boot' 12685 MiB
Gtk-Message: 15:45:00.516: Failed to load module "gail"

** (kalarm:5135): WARNING **: 15:45:00.525: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root)

(wrapper-2.0:4089): LIBDBUSMENU-GLIB-WARNING **: 15:46:10.592: Getting layout failed: Vorgang wurde abgebrochen
xfce4-power-manager-Message: 15:46:10.615: Restored brightness switch value to: 1
using 4.13
using 4.13
parcellite: Fatal IO error 0 (Erfolg) on X server :0.0.
X connection to :0.0 broken (explicit kill or server shutdown).

** (zeitgeist-datahub:4240): WARNING **: 15:46:10.681: zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!

Received signal:15->'Beendet'

(tracker-miner-fs:4171): GLib-GIO-CRITICAL **: 15:46:10.685: Error while sending AddMatch() message: Verbindung ist geschlossen

(tracker-miner-fs:4171): GLib-GIO-CRITICAL **: 15:46:10.685: Error while sending AddMatch() message: Verbindung ist geschlossen

(tracker-miner-fs:4171): GLib-GIO-CRITICAL **: 15:46:10.685: Error while sending AddMatch() message: Verbindung ist geschlossen

OK

QXcbClipboard: Unable to receive an event from the clipboard manager in a reasonable time

Edit: Added code tags

ToZ · 2023-04-01 19:44:33

The only thing that stands out as a potential problem:

(xfce4-panel:4053): xfce4-panel-CRITICAL **: 15:44:29.555: Plugin org.xfce.orage.clock-plugin: There was no module found at "/usr/lib/xfce4/panel-plugins/liborageclock.so"

Its odd that its a critical error. Do you have orage installed? If so, can you uninstall it?
If its not installed, can you remove any errant orage files in /usr/share/xfce4/panel/plugins and /usr/$(uname -m)-linux-gnu/xfce4/panel/plugins?

ixefce · 2023-04-02 15:05:45

orage uninstalled. no orage files to find in /usr
xfce still doesn't work. sometimes appeares a broken panel and any software seems to work in a invisible way: I can type strg+alt+T and in the expected array of the terminal the mouse pointer turns into textcursor and I can shutdown /reboot the system via text input and return.

ToZ · 2023-04-02 16:18:15

Can you post back the new ~/.xsession-errors or ~/.xsession-errors.old after the orage change?

Also, can you create a second test account on your computer and try logging into Xfce through that account. Lets see if this is a system or profile issue.

ixefce · 2023-04-02 19:51:07

ToZ wrote:

Can you post back the new ~/.xsession-errors or ~/.xsession-errors.old after the orage change?
.

There are no errors-files. Only xfwm4------.state files.

I'll try a second profile. smile

ixefce · 2023-04-02 20:02:59

a second test account works fine. Whats next to solve the problem?

ToZ · 2023-04-03 01:46:51

The next steps would be to look for differences between the two:

Autostart applications (~/.config/autostart)
the contents of the files in ~/.config/xfce4/xfconf/xfce-perchannel-xml/
.xinitrc or .xsession (if used)
~/.cache/session

Worst case would be to migrate over to a new account.

In your current log file, you have alot of kde messages. I wonder if there is some incompatibility there that doesn't exist in the new account.

ixefce · 2023-04-03 03:54:18

\home\...\.config
name size date date size name
akregatorrc 66 30.12.22 19:54:43 ? 02.04.23 21:54:23 66 akregatorrc
apt-notifierrc 145 03.04.23 05:21:40 ≠ 02.04.23 21:58:55 146 apt-notifierrc
emaildefaults 187 30.01.23 01:09:56 ≠ 02.04.23 21:52:46 116 emaildefaults
gtkrc 129 03.04.23 05:21:33 ≠ 02.04.23 21:54:23 52 gtkrc
gtkrc-2.0 87 03.04.23 05:21:33 ≠ 02.04.23 21:54:23 87 gtkrc-2.0
gwenviewrc 4704 02.04.23 21:51:27 ≠ 02.04.23 21:54:23 154 gwenviewrc
kactivitymanagerdrc 120 27.12.22 16:59:53 ? 02.04.23 21:54:24 120 kactivitymanagerdrc
kactivitymanagerd-statsrc 1751 22.03.23 09:21:15 ≠ 02.04.23 21:54:25 547 kactivitymanagerd-statsrc
kalarmrc 2888 02.04.23 17:06:42 ≠ 02.04.23 21:54:24 143 kalarmrc
kateschemarc 56 30.12.22 19:54:43 ? 02.04.23 21:54:23 56 kateschemarc
kcminputrc 135 28.01.23 15:14:56 ≠ 02.04.23 21:54:23 121 kcminputrc
kconf_updaterc 3329 30.12.22 19:54:44 ≠ 02.04.23 21:54:24 3311 kconf_updaterc
kded5rc 776 22.03.23 09:20:12 ≠ 02.04.23 21:54:25 43 kded5rc
kdeglobals 4696 03.04.23 05:34:31 ≠ 02.04.23 21:54:24 3274 kdeglobals
kglobalshortcutsrc 17631 03.04.23 05:21:35 ≠ 02.04.23 21:54:26 15985 kglobalshortcutsrc
khotkeysrc 31892 03.04.23 05:21:34 ≠ 02.04.23 21:54:25 31873 khotkeysrc
klaunchrc 148 22.03.23 09:21:10 = 02.04.23 21:52:46 148 klaunchrc
kmail2rc 149 30.12.22 19:54:44 ? 02.04.23 21:54:24 149 kmail2rc
kmixrc 74 30.12.22 19:54:43 ? 02.04.23 21:54:23 74 kmixrc
komparerc 41 22.03.23 09:21:10 = 02.04.23 21:52:46 41 komparerc
konquerorrc 773 30.01.23 15:24:15 ≠ 02.04.23 21:54:24 70 konquerorrc
korgacrc 87 02.04.23 22:20:38 ≠ 02.04.23 21:54:49 88 korgacrc
kscreenlockerrc 255 22.03.23 09:21:10 ≠ 02.04.23 21:52:46 196 kscreenlockerrc
ksmserverrc 2734 29.03.23 19:25:38 ≠ 02.04.23 21:54:24 179 ksmserverrc
ktimezonedrc 105 28.01.23 13:24:40 ? 02.04.23 21:54:23 105 ktimezonedrc
kwalletrc 23 22.03.23 09:21:10 = 02.04.23 21:52:46 23 kwalletrc
kwinrc 781 03.04.23 05:21:34 ≠ 02.04.23 21:54:24 554 kwinrc
kwinrulesrc 70 30.12.22 19:54:44 ? 02.04.23 21:54:24 70 kwinrulesrc
kxkbrc 184 03.04.23 05:21:34 ? 02.04.23 21:54:23 184 kxkbrc
okularpartrc 120 16.03.23 12:58:31 ≠ 02.04.23 21:54:24 84 okularpartrc
plasma-localerc 27 28.01.23 13:24:39 ? 02.04.23 21:54:22 27 plasma-localerc
plasma-nm 36 28.01.23 13:24:48 ? 02.04.23 21:54:31 36 plasma-nm
plasma-org.kde.plasma.desktop-appletsrc 12853 03.04.23 05:34:31 ≠ 02.04.23 21:54:49 6111 plasma-org.kde.plasma.desktop-appletsrc
plasmarc 5349 03.04.23 05:34:03 ≠ 02.04.23 21:52:46 37 plasmarc
plasmashellrc 3071 03.04.23 05:34:31 ≠ 02.04.23 21:54:49 508 plasmashellrc
powerdevilrc 83 28.01.23 15:20:17 ≠ 02.04.23 21:54:24 44 powerdevilrc
powermanagementprofilesrc 1042 20.02.23 17:08:36 ≠ 02.04.23 21:54:24 775 powermanagementprofilesrc
spectaclerc 103 26.03.23 16:10:53 ≠ 02.04.23 21:54:24 68 spectaclerc
Trolltech.conf 1076 03.04.23 05:21:33 ≠ 02.04.23 21:54:24 1076 Trolltech.conf
user-dirs.dirs 640 26.12.22 01:04:35 ? 02.04.23 21:54:24 640 user-dirs.dirs
user-dirs.locale 5 26.12.22 01:04:35 = 02.04.23 21:54:24 5 user-dirs.locale
webengineurlinterceptoradblockrc 103 30.12.22 19:54:44 ? 02.04.23 21:54:24 103 webengineurlinterceptoradblockrc
yad.conf 699 26.12.22 02:46:10 = 02.04.23 21:58:55 699 yad.conf
yakuakerc 50 22.03.23 09:21:10 ≠ 02.04.23 21:52:46 900 yakuakerc

ixefce · 2023-04-03 03:56:34

\home\...\.autostart\
name size date date size name
blueman.desktop 29 19.03.22 00:59:21 = 02.04.23 21:52:46 29 blueman.desktop
Blueman-start.desktop 231 26.01.23 18:38:28 ≠ 02.04.23 21:52:46 232 Blueman-start.desktop
conky.desktop 179 28.03.23 00:24:58 ≠ 02.04.23 21:52:46 179 conky.desktop
fbxkb.desktop 167 19.03.22 00:59:21 = 02.04.23 21:52:46 167 fbxkb.desktop
gnome-keyring-secrets.desktop 48 19.03.22 00:59:21 = 02.04.23 21:52:46 48 gnome-keyring-secrets.desktop
kbd.desktop 173 19.03.22 00:59:21 = 02.04.23 21:52:46 173 kbd.desktop
keyboard switcher.desktop 231 19.03.22 00:59:21 = 02.04.23 21:52:46 231 keyboard switcher.desktop
org.kde.yakuake.desktop 18451 22.03.23 09:21:10 = 02.04.23 21:52:46 18451 org.kde.yakuake.desktop
xfce4-clipman-plugin-autostart.desktop 3357 02.04.23 18:48:20 = 02.04.23 21:55:20 3357 xfce4-clipman-plugin-autostart.desktop
xfce4-volumed.desktop 28 19.03.22 00:59:21 = 02.04.23 21:52:46 28 xfce4-volumed.desktop

ixefce · 2023-04-03 05:11:30

after disabling conky autostart everything works fine again so far. smile

I can't imagine why, because in the second test account conky autostart is enabled and there is no problem.

I reinstalled conky, now it runs again in the original account and causes no problems so far.

Last edited by ixefce (2023-04-03 06:36:54)

robson75 · 2023-04-03 11:31:44

ixefce wrote:

I reinstalled conky, now it runs again in the original account and causes no problems so far.

Reinstalling the conky package won't change anything here, it largely depends on how you have conky configured. For example, my conky-startup.sh file looks like this

#!/bin/sh
killall conky
conky -c "/home/robson/.conky/conky_info.rc" &
conky -c "/home/robson/.conky/mail_info.rc" &
exit 0

And
/home/.config/autostart/conky.desktop

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Icon=conky-logomark-violet
Name=Conky
Exec=/home/robson/.conky/conky-startup.sh
Hidden=false

Xfce Forum

Sub domains

#1 2023-03-31 05:24:57

XFCE desktop freezes at start - just wallpaper is shown -nothing works

#2 2023-03-31 10:28:54

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#3 2023-03-31 13:53:17

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#4 2023-03-31 14:26:31

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#5 2023-04-01 18:04:16

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#6 2023-04-01 19:10:31

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#7 2023-04-01 19:44:33

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#8 2023-04-02 15:05:45

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#9 2023-04-02 16:18:15

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#10 2023-04-02 19:51:07

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#11 2023-04-02 20:02:59

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#12 2023-04-03 01:46:51

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#13 2023-04-03 03:54:18

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#14 2023-04-03 03:56:34

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#15 2023-04-03 05:11:30

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

#16 2023-04-03 11:31:44

Re: XFCE desktop freezes at start - just wallpaper is shown -nothing works

Board footer