Mein Xfce hat sich gerade aufgehangen, allerdings reagierte die Tastatur noch, weshalb ich es dann mit dem Terminal wieder hinbekommen konnte.
Ich habe jetzt zwar nicht die Ausgabe VOR dem Freeze, aber die danach hilft vielleicht auch, etwas zu identifizieren?
Code: Alles auswählen
debian@debian:~$ pidof xfce4-panel
13559
debian@debian:~$ kill 13559
debian@debian:~$ killall xfce4-panel
xfce4-panel: Kein Prozess gefunden
debian@debian:~$ xfce4-panel &
[1] 47423
debian@debian:~$
(xfce4-panel:47423): dbind-WARNING **: 00:05:35.481: 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:47427): dbind-WARNING **: 00:05:36.099: 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:47429): dbind-WARNING **: 00:05:36.103: 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:47430): dbind-WARNING **: 00:05:36.103: 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:47428): dbind-WARNING **: 00:05:36.106: 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:47439): dbind-WARNING **: 00:05:36.274: 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:47429): WARNING **: 00:05:36.861: No outputs have backlight property
(wrapper-2.0:47430): GLib-GIO-CRITICAL **: 00:05:36.863: g_file_new_for_path: assertion 'path != NULL' failed
(wrapper-2.0:47430): GLib-GIO-CRITICAL **: 00:05:36.863: g_file_monitor_file: assertion 'G_IS_FILE (file)' failed
(wrapper-2.0:47430): GLib-GObject-WARNING **: 00:05:36.863: invalid (NULL) pointer instance
(wrapper-2.0:47430): GLib-GObject-CRITICAL **: 00:05:36.863: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(wrapper-2.0:47430): Gtk-WARNING **: 00:05:36.863: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first.
(wrapper-2.0:47428): Gtk-WARNING **: 00:05:36.909: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner PulseaudioButton)
(wrapper-2.0:47430): Gtk-WARNING **: 00:05:36.953: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
(wrapper-2.0:47429): Gtk-WARNING **: 00:05:37.073: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner PowerManagerButton)
debian@debian:~$
(exo-open:47473): dbind-WARNING **: 00:06:37.353: 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-mime-helper:47475): dbind-WARNING **: 00:06:37.367: 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.