You are not logged in.
- Topics: Active | Unanswered
#1 2025-12-10 19:17:34
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Filezilla and xfce4-power-manager cause X to crash to login screen
Hello everybody,
I have an issue with Filezilla in XFCE 4.20. When I try to log into a FTP site with Filezilla, after I enter the password (any password, correct or incorrect), the whole X crashes back to login screen, so it's difficult to debug. I'm running latest Debian Trixie on a 32-bit Thinkpad X60s, but I believe this would happen on a similar 64-bit Thinkpad X60s also.
After experimenting for quite some time, I ran "filezilla" from terminal and noted that there was an error related to xfce-power-manager just before the display returned to login screen.
I tried kernel 6.1 (from Debian Bookworm) and 6.12, no difference. I tried Filezilla from apt-get and building latest Filezilla from source, no difference. I removed ~/.cache and ~/.config/xfce, no difference.
Only when I turn off the power manager with
xfce4-power-manager -qthen Filezilla doesn't crash the X system.
The X crashes each time I don't turn off XFCE power manager.
Some logs follow. The actual X server crash happens at about 20:52:21 (I guess).
.xsession-errors.old (edited, because .old is the correct one probably):
Xsession: X session started for jaan at Wed Dec 10 08:51:17 PM EET 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/jaan/.Xauthority
localuser:jaan being added to access control list
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
** Message: 20:51:18.096: Failed to fetch _NET_NUMBER_OF_DESKTOPS; assuming 1
** Message: 20:51:18.096: Failed to get _NET_WORKAREA; using full screen dimensions
** Message: 20:51:18.096: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
** Message: 20:51:18.096: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
xfce4-session-Message: 20:51:18.106: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one
** Message: 20:51:18.485: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
(xfwm4:3389): xfwm4-WARNING **: 20:51:18.646: Unsupported GL renderer (llvmpipe (LLVM 19.1.7, 128 bits)).
(xfsettingsd:3399): xfsettingsd-WARNING **: 20:51:19.125: Stored Xfconf properties disable all outputs, aborting.
Xfce power manager is not running
(xfce4-session:3312): xfce4-session-WARNING **: 20:51:20.949: Unable to launch "/usr/lib/policykit-1-gnome/polkit-gnome-auth
entication-agent-1" (specified by autostart/polkit-gnome-authentication-agent-1.desktop): Failed to execute child process “/
usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1” (No such file or directory)
** Message: 20:51:21.045: Another instance of GeoClue DemoAgent is running.
(polkit-mate-authentication-agent-1:3478): GLib-CRITICAL **: 20:51:21.462: g_variant_new_string: assertion 'string != NULL'
failed
Xfce Power Manager: Another power manager is already running
(polkit-mate-authentication-agent-1:3478): polkit-mate-1-WARNING **: 20:51:21.475: Failed to register client: GDBus.Error:or
g.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Process already running (98:Address already in use). Exiting.
(redshift-gtk:3460): libayatana-appindicator-WARNING **: 20:51:23.595: libayatana-appindicator is deprecated. Please use lib
ayatana-appindicator-glib in newly written code.
X connection to :0.0 broken (explicit kill or server shutdown)..xsession-errors (probably not relevant, but giving it here):
Xsession: X session started for jaan at Wed Dec 10 08:54:16 PM EET 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/jaan/.Xauthority
localuser:jaan being added to access control list
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
** Message: 20:54:17.237: Failed to fetch _NET_NUMBER_OF_DESKTOPS; assuming 1
** Message: 20:54:17.237: Failed to get _NET_WORKAREA; using full screen dimensions
** Message: 20:54:17.237: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
** Message: 20:54:17.237: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
xfce4-session-Message: 20:54:17.248: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one
** Message: 20:54:17.642: Failed to fetch _NET_CURRENT_DESKTOP; assuming 0
(xfwm4:4058): xfwm4-WARNING **: 20:54:17.802: Unsupported GL renderer (llvmpipe (LLVM 19.1.7, 128 bits)).
(xfsettingsd:4068): xfsettingsd-WARNING **: 20:54:18.252: Stored Xfconf properties disable all outputs, aborting.
Xfce power manager is not running
(xfce4-session:3981): xfce4-session-WARNING **: 20:54:20.037: Unable to launch "/usr/lib/policykit-1-gnome/polkit-gnome-auth
entication-agent-1" (specified by autostart/polkit-gnome-authentication-agent-1.desktop): Failed to execute child process “/
usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1” (No such file or directory)
** Message: 20:54:20.076: Another instance of GeoClue DemoAgent is running.
Xfce Power Manager: Another power manager is already running
(polkit-mate-authentication-agent-1:4144): GLib-CRITICAL **: 20:54:20.709: g_variant_new_string: assertion 'string != NULL'
failed
(polkit-mate-authentication-agent-1:4144): polkit-mate-1-WARNING **: 20:54:20.724: Failed to register client: GDBus.Error:or
g.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
(redshift-gtk:4123): libayatana-appindicator-WARNING **: 20:54:22.484: libayatana-appindicator is deprecated. Please use lib
ayatana-appindicator-glib in newly written code.
Process already running (98:Address already in use). Exiting.
Reading locale option from /home/jaan/.config/filezilla/filezilla.xml
wxD-Bus: Signal from /org/freedesktop/DBus, member NameAcquired
wxD-Bus: Reply with serial 3
wxD-Bus: Signal: Error: The name org.gnome.SessionManager was not provided by any .service filesOutput of command
xfce4-power-manager --no-daemon --debug > xfce-power-log.txt 2>&1is the following
TRACE[xfpm-main.c:178] xfpm_start(): Starting the power manager
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for general-notification
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for lock-screen-suspend-hibernate
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for critical-power-level
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for show-brightness-popup
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for handle-brightness-keys
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-step-count
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-exponential
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for critical-power-action
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for hibernate-button-action
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for sleep-button-action
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for battery-button-action
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for lid-action-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for lid-action-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-level-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-level-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-slider-min-level
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for dpms-on-battery-sleep
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for dpms-on-battery-off
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for dpms-sleep-mode
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for inactivity-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for inactivity-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for inactivity-sleep-mode-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for inactivity-sleep-mode-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for brightness-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for logind-handle-power-key
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for logind-handle-suspend-key
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for logind-handle-hibernate-key
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for logind-handle-lid-switch
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for heartbeat-command
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for profile-on-ac
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for profile-on-battery
TRACE[xfpm-xfconf.c:151] xfpm_xfconf_load(): Using default configuration for show-presentation-indicator
TRACE[xfpm-power.c:840] xfpm_power_get_power_devices(): Power device detected at : /org/freedesktop/UPower/devices/battery_B
AT0
TRACE[xfpm-power.c:805] xfpm_power_add_device(): 'battery' device added
TRACE[xfpm-power.c:814] xfpm_power_add_device(): Battery device type 'battery' detected at: /org/freedesktop/UPower/devices/
battery_BAT0
TRACE[xfpm-button.c:180] xfpm_button_xevent_key(): Grabbed key 124 : ((XfpmButtonKey) BUTTON_POWER_OFF)
TRACE[xfpm-button.c:173] xfpm_button_xevent_key(): could not map keysym 1008ffa8 to keycode
TRACE[xfpm-button.c:180] xfpm_button_xevent_key(): Grabbed key 213 : ((XfpmButtonKey) BUTTON_HIBERNATE)
TRACE[xfpm-button.c:180] xfpm_button_xevent_key(): Grabbed key 150 : ((XfpmButtonKey) BUTTON_SLEEP)
TRACE[
(xfce4-power-manager:3835): libxfce4ui-WARNING **: 20:52:21.660: ICE I/O Error
(xfce4-power-manager:3835): libxfce4ui-WARNING **: 20:52:21.660: Disconnected from session manager.(yes, the last TRACE is missing info in brackets and lines after that are coming from error output of this command)
And finally, journalctl -f is showing this:
Dec 10 20:50:54 thinkpadx60j at-spi-bus-launcher[3262]: dbus-daemon[3262]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=108 pid=3251 comm="/usr/sbin/lightdm-gtk-greeter")
Dec 10 20:50:54 thinkpadx60j at-spi-bus-launcher[3262]: dbus-daemon[3262]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 10 20:50:54 thinkpadx60j at-spi-bus-launcher[3289]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 10 20:51:17 thinkpadx60j lightdm[3302]: gkr-pam: unable to locate daemon control file
Dec 10 20:51:17 thinkpadx60j lightdm[3302]: gkr-pam: stashed password to try later in open session
Dec 10 20:51:17 thinkpadx60j systemd[1]: session-c2.scope: Killing process 3221 (lightdm) with signal SIGTERM.
Dec 10 20:51:17 thinkpadx60j systemd[1]: session-c2.scope: Killing process 3251 (lightdm-gtk-gre) with signal SIGTERM.
Dec 10 20:51:17 thinkpadx60j systemd[1]: Stopping session-c2.scope - Session c2 of User lightdm...
Dec 10 20:51:17 thinkpadx60j lightdm[3221]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dec 10 20:51:17 thinkpadx60j lightdm[3221]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dec 10 20:51:17 thinkpadx60j lightdm[3221]: pam_systemd(lightdm-greeter:session): Failed to release session: Transport endpoint is not connected
Dec 10 20:51:17 thinkpadx60j systemd[1]: session-c2.scope: Deactivated successfully.
Dec 10 20:51:17 thinkpadx60j systemd[1]: Stopped session-c2.scope - Session c2 of User lightdm.
Dec 10 20:51:17 thinkpadx60j systemd[1]: session-c2.scope: Consumed 1.985s CPU time, 28.4M memory peak.
Dec 10 20:51:17 thinkpadx60j lightdm[3302]: pam_unix(lightdm:session): session opened for user jaan(uid=1000) by jaan(uid=0)
Dec 10 20:51:17 thinkpadx60j systemd-logind[582]: Removed session c2.
Dec 10 20:51:17 thinkpadx60j systemd-logind[582]: New session 8 of user jaan.
Dec 10 20:51:17 thinkpadx60j systemd[1]: Started session-8.scope - Session 8 of User jaan.
Dec 10 20:51:17 thinkpadx60j lightdm[3302]: gkr-pam: unlocked login keyring
Dec 10 20:51:17 thinkpadx60j lightdm[3302]: Failed to write utmpx: No such file or directory
Dec 10 20:51:18 thinkpadx60j at-spi-bus-launcher[1107]: dbus-daemon[1107]: Activating service name='org.a11y.atspi.Registry' requested by ':1.51' (uid=1000 pid=3312 comm="xfce4-session")
Dec 10 20:51:18 thinkpadx60j at-spi-bus-launcher[1107]: dbus-daemon[1107]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 10 20:51:18 thinkpadx60j at-spi-bus-launcher[3375]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 10 20:51:18 thinkpadx60j systemd[1011]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: gpg-agent (GnuPG) 2.4.7 starting in supervised mode.
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: using fd 3 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: using fd 4 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: using fd 5 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Dec 10 20:51:18 thinkpadx60j gpg-agent[3386]: listening on: std=6 extra=4 browser=5 ssh=3
Dec 10 20:51:20 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Activating via systemd: service name='org.freedesktop.thumbnails.Thumbnailer1' unit='tumblerd.service' requested by ':1.136' (uid=1000 pid=3415 comm="xfdesktop --display :0.0 --sm-client-id 231d8768d-")
Dec 10 20:51:20 thinkpadx60j systemd[1011]: Starting tumblerd.service - Thumbnailing service...
Dec 10 20:51:20 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.138' (uid=1000 pid=3419 comm="xfce4-power-manager --restart --sm-client-id 28b11")
Dec 10 20:51:20 thinkpadx60j systemd[1011]: Starting xfce4-notifyd.service - XFCE notifications service...
Dec 10 20:51:20 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Successfully activated service 'org.freedesktop.Notifications'
Dec 10 20:51:20 thinkpadx60j systemd[1011]: Started xfce4-notifyd.service - XFCE notifications service.
Dec 10 20:51:20 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Dec 10 20:51:20 thinkpadx60j systemd[1011]: Started tumblerd.service - Thumbnailing service.
Dec 10 20:51:21 thinkpadx60j polkitd[667]: Registered Authentication Agent for unix-session:8 (system bus name :1.98 [/usr/libexec/polkit-mate-authentication-agent-1], object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Dec 10 20:51:22 thinkpadx60j NetworkManager[654]: <info> [1765392682.6011] agent-manager: agent[8de4683f7be54a1c,:1.101/org.freedesktop.nm-applet/1000]: agent registered
Dec 10 20:51:27 thinkpadx60j systemd[1]: Stopping user@108.service - User Manager for UID 108...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Activating special unit exit.target...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped target default.target - Main User Target.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping at-spi-dbus-bus.service - Accessibility services bus...
Dec 10 20:51:27 thinkpadx60j gvfsd[3265]: A connection to the bus can't be made
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping dbus.service - D-Bus User Message Bus...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping gvfs-daemon.service - Virtual filesystem service...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped pulseaudio.service - Sound Service.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped at-spi-dbus-bus.service - Accessibility services bus.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped gvfs-daemon.service - Virtual filesystem service.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped dbus.service - D-Bus User Message Bus.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Removed slice session.slice - User Core Session Slice.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped target basic.target - Basic System.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped target paths.target - Paths.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped target sockets.target - Sockets.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopped target timers.target - Timers.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed dbus.socket - D-Bus User Message Bus Socket.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gnome-keyring-daemon.socket - GNOME Keyring daemon.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed keyboxd.socket - GnuPG public key management service.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed pulseaudio.socket - Sound System.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed speech-dispatcher.socket - Speech Dispatcher Socket.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Stopping ssh-agent.socket - OpenSSH Agent socket...
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed ssh-agent.socket - OpenSSH Agent socket.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Removed slice app.slice - User Application Slice.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Reached target shutdown.target - Shutdown.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Finished systemd-exit.service - Exit the Session.
Dec 10 20:51:27 thinkpadx60j systemd[3227]: Reached target exit.target - Exit the Session.
Dec 10 20:51:27 thinkpadx60j systemd-logind[582]: Removed session 7.
Dec 10 20:51:27 thinkpadx60j systemd[1]: user@108.service: Deactivated successfully.
Dec 10 20:51:27 thinkpadx60j systemd[1]: Stopped user@108.service - User Manager for UID 108.
Dec 10 20:51:27 thinkpadx60j systemd[1]: user@108.service: Consumed 1.136s CPU time, 11.5M memory peak.
Dec 10 20:51:27 thinkpadx60j systemd[1]: Stopping user-runtime-dir@108.service - User Runtime Directory /run/user/108...
Dec 10 20:51:27 thinkpadx60j systemd[1]: run-user-108.mount: Deactivated successfully.
Dec 10 20:51:27 thinkpadx60j systemd[1]: user-runtime-dir@108.service: Deactivated successfully.
Dec 10 20:51:27 thinkpadx60j systemd[1]: Stopped user-runtime-dir@108.service - User Runtime Directory /run/user/108.
Dec 10 20:51:27 thinkpadx60j systemd[1]: Removed slice user-108.slice - User Slice of UID 108.
Dec 10 20:51:27 thinkpadx60j systemd[1]: user-108.slice: Consumed 3.177s CPU time, 37M memory peak.
Dec 10 20:52:14 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.45' (uid=1000 pid=1384 comm="/usr/libexec/xdg-desktop-portal")
Dec 10 20:52:14 thinkpadx60j systemd[1011]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Dec 10 20:52:14 thinkpadx60j dbus-daemon[1035]: [session uid=1000 pid=1035 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Dec 10 20:52:14 thinkpadx60j systemd[1011]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Dec 10 20:52:21 thinkpadx60j pulseaudio[1034]: X11 I/O error handler called
Dec 10 20:52:21 thinkpadx60j pulseaudio[1034]: X11 I/O error exit handler called, preparing to tear down X11 modules
Dec 10 20:52:21 thinkpadx60j systemd[1011]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 20:52:21 thinkpadx60j systemd[1011]: xfce4-notifyd.service: Failed with result 'exit-code'.
Dec 10 20:52:21 thinkpadx60j at-spi-bus-launcher[3375]: X connection to :0 broken (explicit kill or server shutdown).
Dec 10 20:52:21 thinkpadx60j systemd[1011]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 20:52:21 thinkpadx60j systemd[1011]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Dec 10 20:52:21 thinkpadx60j polkitd[667]: Unregistered Authentication Agent for unix-session:8 (system bus name :1.98, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Dec 10 20:52:21 thinkpadx60j lightdm[3302]: Failed to write utmpx: No such file or directory
Dec 10 20:52:21 thinkpadx60j lightdm[3302]: pam_unix(lightdm:session): session closed for user jaan
Dec 10 20:52:21 thinkpadx60j systemd-logind[582]: Session 8 logged out. Waiting for processes to exit.
Dec 10 20:52:22 thinkpadx60j lightdm[3877]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=108) by (uid=0)
Dec 10 20:52:22 thinkpadx60j systemd[1]: Created slice user-108.slice - User Slice of UID 108.
Dec 10 20:52:22 thinkpadx60j systemd[1]: Starting user-runtime-dir@108.service - User Runtime Directory /run/user/108...
Dec 10 20:52:22 thinkpadx60j systemd-logind[582]: New session c3 of user lightdm.
Dec 10 20:52:22 thinkpadx60j systemd[1]: Finished user-runtime-dir@108.service - User Runtime Directory /run/user/108.
Dec 10 20:52:22 thinkpadx60j systemd[1]: Starting user@108.service - User Manager for UID 108...
Dec 10 20:52:22 thinkpadx60j (systemd)[3883]: pam_unix(systemd-user:session): session opened for user lightdm(uid=108) by lightdm(uid=0)
Dec 10 20:52:22 thinkpadx60j systemd-logind[582]: New session 9 of user lightdm.
Dec 10 20:52:23 thinkpadx60j systemd-xdg-autostart-generator[3889]: Exec binary '/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1' does not exist: No such file or directory
Dec 10 20:52:23 thinkpadx60j systemd-xdg-autostart-generator[3889]: /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop: not generating unit, executable specified in Exec= does not exist.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Queued start job for default target default.target.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Created slice app.slice - User Application Slice.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Created slice session.slice - User Core Session Slice.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Reached target paths.target - Paths.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Reached target timers.target - Timers.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting dbus.socket - D-Bus User Message Bus Socket...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting gcr-ssh-agent.socket - GCR ssh-agent wrapper...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gnome-keyring-daemon.socket - GNOME Keyring daemon.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on keyboxd.socket - GnuPG public key management service.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on pulseaudio.socket - Sound System.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on speech-dispatcher.socket - Speech Dispatcher Socket.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting ssh-agent.socket - OpenSSH Agent socket...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Listening on ssh-agent.socket - OpenSSH Agent socket.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Reached target sockets.target - Sockets.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Reached target basic.target - Basic System.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: mpris-proxy.service - Bluetooth mpris proxy was skipped because of an unmet condition check (ConditionUser=!@system).
Dec 10 20:52:23 thinkpadx60j systemd[1]: Started user@108.service - User Manager for UID 108.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting pulseaudio.service - Sound Service...
Dec 10 20:52:23 thinkpadx60j systemd[1]: Started session-c3.scope - Session c3 of User lightdm.
Dec 10 20:52:23 thinkpadx60j lightdm[3877]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=108) by (uid=0)
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Successfully made thread 3905 of process 3905 owned by '108' high priority at nice level -11.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Supervising 4 threads of 2 processes of 2 users.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting dbus.service - D-Bus User Message Bus...
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Started dbus.service - D-Bus User Message Bus.
Dec 10 20:52:23 thinkpadx60j dbus-daemon[3908]: [session uid=108 pid=3908 pidfd=5] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.2' (uid=108 pid=3907 comm="/usr/sbin/lightdm-gtk-greeter")
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting at-spi-dbus-bus.service - Accessibility services bus...
Dec 10 20:52:23 thinkpadx60j dbus-daemon[3908]: [session uid=108 pid=3908 pidfd=5] Successfully activated service 'org.a11y.Bus'
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Started at-spi-dbus-bus.service - Accessibility services bus.
Dec 10 20:52:23 thinkpadx60j dbus-daemon[3908]: [session uid=108 pid=3908 pidfd=5] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=108 pid=3907 comm="/usr/sbin/lightdm-gtk-greeter")
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Starting gvfs-daemon.service - Virtual filesystem service...
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Supervising 4 threads of 2 processes of 2 users.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Successfully made thread 3921 of process 3905 owned by '108' RT at priority 5.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Supervising 5 threads of 2 processes of 2 users.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Supervising 5 threads of 2 processes of 2 users.
Dec 10 20:52:23 thinkpadx60j dbus-daemon[3908]: [session uid=108 pid=3908 pidfd=5] Successfully activated service 'org.gtk.vfs.Daemon'
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Started gvfs-daemon.service - Virtual filesystem service.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Successfully made thread 3925 of process 3905 owned by '108' RT at priority 5.
Dec 10 20:52:23 thinkpadx60j rtkit-daemon[1046]: Supervising 6 threads of 2 processes of 2 users.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Started pulseaudio.service - Sound Service.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Reached target default.target - Main User Target.
Dec 10 20:52:23 thinkpadx60j systemd[3883]: Startup finished in 834ms.
Dec 10 20:52:24 thinkpadx60j at-spi-bus-launcher[3917]: dbus-daemon[3917]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=108 pid=3907 comm="/usr/sbin/lightdm-gtk-greeter")
Dec 10 20:52:24 thinkpadx60j at-spi-bus-launcher[3917]: dbus-daemon[3917]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 10 20:52:24 thinkpadx60j at-spi-bus-launcher[3944]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.RegistryDoes anyone have some ideas? How could I debug it further?
Last edited by jaan513 (2025-12-10 19:39:40)
Offline
#2 2025-12-10 22:57:53
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 12,383
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Hello and welcome.
This is a strange problem.
and noted that there was an error related to xfce-power-manager just before the display returned to login screen.
What was the error message?
Can you uncheck the "Prevent the system from entering sleep mode..." in Settings > Interface? See if that makes a difference. Maybe its related to power management inhibiting functionality?
It looks like in Filezilla Settings > Debug you can specify "4 - Debug" logging, but for some reason on my system (Arch) the setting doesn't hold. See if you can enable debug logging and logging to a file (Settings > Logging) to see if you can get some filezilla logs as to whats happening?
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#3 2025-12-11 18:22:54
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
What was the error message?
Because X11 is killed, it's very difficult to see. I managed to redirect output to /dev/tty2:
filezilla > /dev/tty2 2>&1Then I saw:
Reading locale option from /home/jaan/.config/filezilla/filezilla.xml
wxD-Bus: Signal from /org/freedesktop/DBus, member NameAcquired
wxD-Bus: Reply with serial 2
wxD-Bus: Signal: Error: The name org.gnome.SessionManager was not provided by any .service files
wxD-Bus: CPowerManagementInhibitor: Requesting busySo it looks like I didn't see xfce-power-manager, but I saw that something was related to power, so I that's why I closed the xfce-power-manager for using Filezilla (and it worked!). I think the only line that appears during the crash is the last one. Writing this to a regular file from a terminal window creates an empty file, as the X11 tears down everything before the file is synced.
Can you uncheck the "Prevent the system from entering sleep mode..." in Settings > Interface? See if that makes a difference. Maybe its related to power management inhibiting functionality?
I don't see this option. I have Settings > Power Manager, I don't see it there, and don't see Settings > Interface. Alphabetically, I have Settngs > Display before and Settings > Keyboard after where it should be.
For the second question, it looks like yes, CPowerManagementInhibitor sounds like inhibiting functionality, as seen from the wxD-Bus lines.
It looks like in Filezilla Settings > Debug you can specify "4 - Debug" logging, but for some reason on my system (Arch) the setting doesn't hold. See if you can enable debug logging and logging to a file (Settings > Logging) to see if you can get some filezilla logs as to whats happening?
I usually get empty logs, I think it's the same reason as before - file will not be synced, the X11 will be killed too fast.
However, I can make the X11 crash when I uncheck "Display Power Management" in the Power Manager > Display tab. Then I'm not able to log in any more unless I delete the text config for xfce4-power-manager.xml. If I use some Sleep time (Put to sleep after) in Display Power Management, the X11 will crash after that time.
So I'm guessing the reason it's happening to Filezilla is that it somehow asks for some sleep disabling or whatever after the password prompt.
I don't think it's related, but in the rest of the system, I have changed /etc/UPower/UPower.conf to use IgnoreLid=true (to ignore the state of lid, so I can close it without sleep etc). I do not want to use any sleep modes.
Offline
#4 2025-12-11 18:48:41
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 12,383
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
I don't see this option. I have Settings > Power Manager, I don't see it there, and don't see Settings > Interface. Alphabetically, I have Settngs > Display before and Settings > Keyboard after where it should be.
Are you looking in Filezilla Settings?
wxD-Bus: CPowerManagementInhibitor: Requesting busy
I think its related to the inhibit processes on your system. If you are using systemd, can you try to inhibit filezilla like:
systemd-inhibit --what="idle" --who="Me" --why="Test" filezillaDoes that work or error out?
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#5 2025-12-12 09:27:05
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Are you looking in Filezilla Settings?
Oh, my bad. Yes, that "Prevent system from entering idle sleep ..." option works! Filezilla doesn't crash and X11 stays alive.
I think its related to the inhibit processes on your system. If you are using systemd, can you try to inhibit filezilla like:
systemd-inhibit --what="idle" --who="Me" --why="Test" filezillaDoes that work or error out?
I didn't test it yet, will do it later also.
Meanwhile, I can say that Filezilla didn't crash in Fvwm or Windowmaker, only crashes in Xfce with power manager on.
Last edited by jaan513 (2025-12-12 09:29:16)
Offline
#6 2025-12-12 10:51:16
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 12,383
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Does it create a coredump?
coredumpctl listIf so:
coredumpctl info PID...where PID is the number in the PID column of the result above for the last filezilla coredump.
Meanwhile, I can say that Filezilla didn't crash in Fvwm or Windowmaker, only crashes in Xfce with power manager on.
Neither of those DEs have a compatible power manager. Could you try with Mate to see if the problem replicates?
Last edited by ToZ (2025-12-12 13:15:52)
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#7 2025-12-12 17:44:09
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
After installing systemd-coredump:
The command "coredumpctl list" showed 1 process, then "coredumpctl info 2057" showed that coredump was not generated:
PID: 2057 (Xorg)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Fri 2025-12-12 18:53:40 EET (22min ago)
Command Line: /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Executable: /usr/lib/xorg/Xorg
Control Group: /system.slice/lightdm.service
Unit: lightdm.service
Slice: system.slice
Boot ID: 6ebe521381c54a888a23db6bd339217d
Machine ID: 396dec7b6e1d41bea961e1121e30d5d8
Hostname: thinkpadx60j
Storage: none
Message: Process 2057 (Xorg) of user 0 terminated abnormally without generating a coredump.Now, after systemd-coredump is installed, journalctl shows this during the crash:
Dec 12 18:53:40 thinkpadx60j systemd-coredump[3183]: Process 2057 (Xorg) of user 0 terminated abnormally with signal 11/SEG>
Dec 12 18:53:40 thinkpadx60j systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
Dec 12 18:53:40 thinkpadx60j systemd[1]: Started systemd-coredump@0-3183-0.service - Process Core Dump (PID 3183/UID 0).
Dec 12 18:53:40 thinkpadx60j systemd-coredump[3184]: Resource limits disable core dumping for process 2057 (Xorg).
Dec 12 18:53:40 thinkpadx60j systemd-coredump[3184]: [🡕] Process 2057 (Xorg) of user 0 terminated abnormally without genera>
Dec 12 18:53:40 thinkpadx60j systemd[1]: systemd-coredump@0-3183-0.service: Deactivated successfully.
Dec 12 18:53:41 thinkpadx60j at-spi-bus-launcher[2201]: X connection to :0 broken (explicit kill or server shutdown).
Dec 12 18:53:40 thinkpadx60j polkitd[666]: Unregistered Authentication Agent for unix-session:6 (system bus name :1.96, obj>
Dec 12 18:53:40 thinkpadx60j pulseaudio[1028]: X11 I/O error handler called
Dec 12 18:53:41 thinkpadx60j lightdm[2137]: Failed to write utmpx: No such file or directory
Dec 12 18:53:40 thinkpadx60j pulseaudio[1028]: X11 I/O error exit handler called, preparing to tear down X11 modules
...Filezilla in Mate does not crash:
Reading locale option from /home/jaan/.config/filezilla/filezilla.xml
wxD-Bus: Signal from /org/freedesktop/DBus, member NameAcquired
wxD-Bus: Reply with serial 3
wxD-Bus: Reply to RegisterClient, our object path is /org/gnome/SessionManager/Client12
wxD-Bus: CPowerManagementInhibitor: Requesting busy
wxD-Bus: Reply with serial 4
wxD-Bus: Reply: Error: The name org.freedesktop.PowerManagement was not provided by any .service files
wxD-Bus: Falling back to org.gnome.SessionManager
wxD-Bus: CPowerManagementInhibitor: Requesting busy
wxD-Bus: Reply with serial 5
wxD-Bus: CPowerManagementInhibitor: Request successful, cookie is 1383296795
wxD-Bus: CPowerManagementInhibitor: Requesting idle
wxD-Bus: Reply with serial 6
wxD-Bus: CPowerManagementInhibitor: Request successful
wxD-Bus: UnregisteredThe systemd-inhibit still causes a crash in Xfce (with Settings > Interface option "Prevent ... idle sleep ..." checked):
systemd-inhibit --what="idle" --who="Me" --why="Test" filezilla
# crashed after entering the password to log in to a Filezilla siteI also tested replacing lightdm with lxdm, no difference.
To sum it up, this is what has been tested on my Lenovo Thinkpad X60s:
Here's what's causing X11 to crash to login screen:
* Filezilla in XFCE with xfce4-power-manager turned on and "Prevent system from entering idle sleep..." in Filezilla Settings > Interface checked, systemd-inhibit having no effect
* Not related to Filezilla: Unchecking XFCE Power Manager "Display power management" or using sleep timer for display
* Not related to Filezilla: Using sleep timer for display in MATE
Here's when Filezilla doesn't crash:
* Filezilla in MATE, Windowmaker, Fvwm3
* Filezilla in XFCE when xfce4-power-manager is turned off (-q option)
* Filezilla in XFCE when Filezilla Settings > Interface has "Prevent system from entering idle sleep..." unchecked
I don't know if it's possible to dig deeper, however I'm happy that I have a few workarounds to use Filezilla.
Last edited by jaan513 (2025-12-12 18:00:39)
Offline
#8 2025-12-13 01:07:33
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 12,383
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Filezilla in Mate does not crash:
If you wish to pursue this further, I would recommend creating a bug report against xfce4-power-manager. Feel free to link to this thread for background info.
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#9 2025-12-13 09:46:06
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Filezilla in Mate does not crash:
If you wish to pursue this further, I would recommend creating a bug report against xfce4-power-manager. Feel free to link to this thread for background info.
Before I do that, I still try to figure out if it's actually a bug of xfce4-power-manager, or something else.
I found out now that running "startx" in /dev/tty2 (Crtl+Alt+F2) does allow Filezilla to run in XFCE, and the Power Manager won't crash with any settings. Maybe I should reset my X11 system-wide settings or something. Continuing to debug.
Last edited by jaan513 (2025-12-13 09:46:26)
Offline
#10 2025-12-13 11:17:23
- Misko_2083
- Member
- Registered: 2015-10-13
- Posts: 232
- Website
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
From the logs in your first post it isbasically XFCE starting in a half-broken X11 environment and tripping over missing components + bad state.
Big problem:
xfsettingsd-WARNING: Stored Xfconf properties disable all outputs, aborting.XFCE stored a monitor config where all displays are off. That's why xfsettingsd refuses to apply it, leading to no power manager, no display logic.
This should fix it
rm -f ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xmllog out and back in.
Fix displays and power manager returns.
Broken polkit agent:
Unable to launch polkit-gnome-authentication-agent-1
No such file or directoryThis is a serious issue. XFCE is trying to start GNOME’s polkit agent, but it’s not installed.
Yet later in the log:
(polkit-mate-authentication-agent-1): GLib-CRITICALSo you have mate-polkit installed, but XFCE autostart still points to GNOME.
Pick ONE polkit agent.
Either install policykit-1-gnome or switch XFCE to mate-poolkit.
Make sure only one power manager runs. Check with:
ps aux | egrep 'power|upower|mate|gnome'Do you want to exit the Circus?
https://www.youtube.com/watch?v=ZJwQicZHp_c
Offline
#11 2025-12-13 20:57:33
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
From the logs in your first post it isbasically XFCE starting in a half-broken X11 environment and tripping over missing components + bad state.
Hello! Thank you for trying to help!
I don't know. It was a clean XFCE from Debian 12 Bookworm, upgraded to Debian 13 Trixie (because no direct i386 installer for Debian 13), without any other desktop environment installed before I started experimenting with this Filezilla stuff.
Big problem:
xfsettingsd-WARNING: Stored Xfconf properties disable all outputs, aborting.XFCE stored a monitor config where all displays are off. That's why xfsettingsd refuses to apply it, leading to no power manager, no display logic.
This should fix itrm -f ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xmllog out and back in.
Fix displays and power manager returns.
Removed displays.xml. Other than the .xsession-errors log not mentioning this line, no difference.
Broken polkit agent:
Unable to launch polkit-gnome-authentication-agent-1 No such file or directoryThis is a serious issue. XFCE is trying to start GNOME’s polkit agent, but it’s not installed.
Yet later in the log:(polkit-mate-authentication-agent-1): GLib-CRITICALSo you have mate-polkit installed, but XFCE autostart still points to GNOME.
Pick ONE polkit agent.
Either install policykit-1-gnome or switch XFCE to mate-poolkit.
I didn't do anything with the polkits, both gnome and mate polkit .desktop files were already in the autostart folder (/etc/xdg/autostart)... Probably Debian installed only the mate one by default. Anyway, I moved the gnome desktop file away from there.
Again, other than the warning disappearing from .xsession-errors, no difference.
Make sure only one power manager runs. Check with:
ps aux | egrep 'power|upower|mate|gnome'
root 151 0.0 0.0 0 0 ? I 21:30 0:00 [kworker/0:3-events_power_efficient]
root 593 0.1 0.3 61364 9356 ? Ssl 21:31 0:01 /usr/libexec/upowerd
jaan 1149 0.0 0.3 56504 9368 ? SLsl 21:32 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
jaan 2679 0.0 0.2 40936 7496 ? Sl 21:37 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
jaan 2725 0.0 0.6 78168 19768 ? Sl 21:37 0:00 xfce4-power-manager --restart --sm-client-id 29564b38d-4aba-48ec-a926-d159eba1e35b
jaan 2728 0.1 1.0 92432 32688 ? Sl 21:37 0:01 /usr/lib/i386-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/i386-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so 9 16777230 power-manager-plugin Power Manager Plugin Display the battery levels of your devices and control the brightness of your display
jaan 2786 0.0 0.4 65904 15240 ? Sl 21:37 0:00 /usr/libexec/polkit-mate-authentication-agent-1
jaan 3546 0.0 0.0 8420 2240 pts/0 S+ 21:47 0:00 grep -E power|upower|mate|gnomeTried to disable upower:
systemctl mask upower.serviceRebooted, upower not running. Now, xfce4-power-manager tab number 4 "Devices" is missing. Filezilla still crashing, so no difference. Enabled upower again with
systemctl unmask upower.serviceI also went over my X11 config in /etc/X11, moved that folder, then lightdm is not able to start any sessions any more. I may try to install Debian from scratch again, to see if it's some X11 config issue. Until then, moved /etc/X11 back where it was.
Again, thanks for trying to help!
Offline
#12 2025-12-13 21:56:55
- eriefisher
- Wanderer
- From: ON, Canada
- Registered: 2008-10-25
- Posts: 828
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Xfce now has it's own xfce-polkit. Policykit-gnome is no longer a thing. If it is installed it may work ok but the project has been abandon. Mate-polkit will work as well but only one can be active. Select one in autostart,
I AM CANADIAN!
Siduction
Debian Sid
Xfce 4.20 with Wayland/Labwc
Offline
#13 2025-12-14 17:23:29
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Did a fresh install of Debian on an SSD. Still on Thinkpad X60(s). So I had to install Debian 12 first (Bookworm) because I'm on i386 and that's the latest installer. No graphics. Then I upgraded to Debian 13 Trixie without installing any X packages. Then I installed xfce4 with xfce4-power-manager, systemd-coredump and filezilla. So the install should be quite clean. Still, polkit complains about missing gnome polkit or something.
.xsession-errors:
(polkit-mate-authentication-agent-1:1022): polkit-mate-1-WARNING **: 18:43:04.553: Failed to registe
r client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager w
as not provided by any .service filesAnyway, that's not the topic of this thread and I didn't find anything related to gnome polkit in /etc/xdg/autostart.
jaan@thinkpadx60j:/etc/xdg/autostart$ grep -R gnome
jaan@thinkpadx60j:/etc/xdg/autostart$ grep -R mate
polkit-mate-authentication-agent-1.desktop:Exec=/usr/libexec/polkit-mate-authentication-agent-1Filezilla fails as before, but now, the coredumps seem to be more informative:
jaan@thinkpadx60j:~$ sudo coredumpctl list
TIME PID UID GID SIG COREFILE EXE SIZE
Sun 2025-12-14 18:46:37 EET 713 0 0 SIGSEGV present /usr/lib/xorg/Xorg 2.9Mjaan@thinkpadx60j:~$ sudo coredumpctl info 713
PID: 713 (Xorg)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Sun 2025-12-14 18:46:35 EET (17min ago)
Command Line: /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Executable: /usr/lib/xorg/Xorg
Control Group: /system.slice/lightdm.service
Unit: lightdm.service
Slice: system.slice
Boot ID: ef4ab61792804e218fed7cb885d59a66
Machine ID: bb2cd901a0cb49dda457b9255e2ee6de
Hostname: thinkpadx60j
Storage: /var/lib/systemd/coredump/core.Xorg.0.ef4ab61792804e218fed7cb885d59a66.713.1765730795000000.zst (present)
Size on Disk: 2.9M
Message: Process 713 (Xorg) of user 0 dumped core.
Module libatomic.so.1 from deb gcc-14-14.2.0-19.i386
Module libstdc++.so.6 from deb gcc-14-14.2.0-19.i386
Module libzstd.so.1 from deb libzstd-1.5.7+dfsg-1.i386
Module libgcc_s.so.1 from deb gcc-14-14.2.0-19.i386
Module libsystemd.so.0 from deb systemd-257.9-1~deb13u1.i386
Module libudev.so.1 from deb systemd-257.9-1~deb13u1.i386
Stack trace of thread 713:
#0 0x00000000b7daeeb3 pci_device_vgaarb_set_target (libpciaccess.so.0 + 0x4eb3)
#1 0x00000000004ee98b n/a (/usr/lib/xorg/Xorg + 0xa898b)
#2 0x00000000004d3e83 ddxGiveUp (/usr/lib/xorg/Xorg + 0x8de83)
#3 0x000000000061e48f n/a (/usr/lib/xorg/Xorg + 0x1d848f)
#4 0x000000000061f024 FatalError (/usr/lib/xorg/Xorg + 0x1d9024)
#5 0x00000000006153a7 n/a (/usr/lib/xorg/Xorg + 0x1cf3a7)
#6 0x00000000b7f18570 __kernel_rt_sigreturn (linux-gate.so.1 + 0x570)
#7 0x00000000b7daeeb3 pci_device_vgaarb_set_target (libpciaccess.so.0 + 0x4eb3)
#8 0x00000000004ee98b n/a (/usr/lib/xorg/Xorg + 0xa898b)
#9 0x00000000004d0f49 n/a (/usr/lib/xorg/Xorg + 0x8af49)
#10 0x0000000000548e95 n/a (/usr/lib/xorg/Xorg + 0x102e95)
#11 0x0000000000549006 n/a (/usr/lib/xorg/Xorg + 0x103006)
#12 0x0000000000490290 n/a (/usr/lib/xorg/Xorg + 0x4a290)
#13 0x000000000049472c n/a (/usr/lib/xorg/Xorg + 0x4e72c)
#14 0x000000000047c3fa n/a (/usr/lib/xorg/Xorg + 0x363fa)
#15 0x00000000b780dcc3 n/a (libc.so.6 + 0x24cc3)
#16 0x00000000b780dd88 __libc_start_main (libc.so.6 + 0x24d88)
#17 0x000000000047c437 _start (/usr/lib/xorg/Xorg + 0x36437)
Stack trace of thread 726:
#0 0x00000000b788229b n/a (libc.so.6 + 0x9929b)
#1 0x00000000b7875949 n/a (libc.so.6 + 0x8c949)
#2 0x00000000b78760f5 n/a (libc.so.6 + 0x8d0f5)
#3 0x00000000b7878ed1 pthread_cond_wait (libc.so.6 + 0x8fed1)
#4 0x00000000b7109ee9 n/a (intel_drv.so + 0xa7ee9)
#5 0x00000000b7879781 n/a (libc.so.6 + 0x90781)
#6 0x00000000b790fe38 n/a (libc.so.6 + 0x126e38)
Stack trace of thread 732:
#0 0x00000000b788229b n/a (libc.so.6 + 0x9929b)
#1 0x00000000b7875949 n/a (libc.so.6 + 0x8c949)
#2 0x00000000b7875a00 n/a (libc.so.6 + 0x8ca00)
#3 0x00000000b79103a1 epoll_wait (libc.so.6 + 0x1273a1)
#4 0x0000000000615e87 n/a (/usr/lib/xorg/Xorg + 0x1cfe87)
#5 0x0000000000613158 n/a (/usr/lib/xorg/Xorg + 0x1cd158)
#6 0x00000000b7879781 n/a (libc.so.6 + 0x90781)
#7 0x00000000b790fe38 n/a (libc.so.6 + 0x126e38)
ELF object binary architecture: Intel 80386This doesn't tell me anything, but maybe someone else can see something here.
Also, as before, starting the X from another (non-graphical) tty with "startx" will run Xfce, and I can't crash Power Manager or X like that.
Added later 52 min 10 s:
It seems to be a DPMS problem.
This config for xfce4-power-manager.xml will crash X immediately and unable to log in via lightdm:
<property name="dpms-enabled" type="bool" value="false"/>(It is equivalent to unchecking "Display power management" in tab 3 "Display" of Xfce Power Manager)
However, startx from terminal still works, starts Xfce and doesn't crash X (and Filezilla works OK).
I got more logs from xfce4-power-manager. When Xfce is started with startx, and Filezilla is run, the logs read:
TRACE[xfpm-manager.c:618] name_appeared(): org.xfce.SessionManager started up, owned by :1.39
TRACE[xfpm-inhibit.c:390] xfpm_inhibit_inhibit(): Inhibit send application name=FileZilla reason=File transfer or remote operation in progress sender=:1.165
TRACE[xfpm-inhibit.c:89] xfpm_inhibit_has_inhibit_changed(): Inhibit added
TRACE[xfpm-power.c:865] xfpm_power_inhibit_changed_cb(): inhibited TRUE, presentation_mode FALSE
TRACE[xfpm-power.c:1323] xfpm_power_toggle_screensaver(): Disabling screensaver, timeout stored: 300
TRACE[xfpm-dpms.c:193] xfpm_dpms_set_inhibited(): DPMS inhibited: TRUE
TRACE[xfpm-inhibit.c:405] xfpm_inhibit_un_inhibit(): Uninhibit message received
TRACE[xfpm-inhibit.c:83] xfpm_inhibit_has_inhibit_changed(): Inhibit removed
TRACE[xfpm-power.c:865] xfpm_power_inhibit_changed_cb(): inhibited FALSE, presentation_mode FALSE
TRACE[xfpm-power.c:1329] xfpm_power_toggle_screensaver(): Enabling screensaver, timeout restored: 300
TRACE[xfpm-dpms.c:193] xfpm_dpms_set_inhibited(): DPMS inhibited: FALSE
TRACE[xfpm-main.c:53] xfpm_quit_signal(): sig 2
TRACE[xfpm-manager.c:1018] xfpm_manager_quit(): Exiting
TRACE[xfpm-brightness-polkit.c:201] xfpm_brightness_polkit_set_switch(): Failed to set brightness switch value: Failed to execute child process “pkexec” (No such file or directory)
TRACE[xfpm-backlight.c:556] xfpm_backlight_finalize(): Unable to restore the kernel brightness switch parameter to its original value, still resetting the saved value.So this was a log when everything worked.
Now I exited, went back to lightdm, logged in, started:
xfce4-power-manager -q
xfce4-power-manager --no-daemon --debug > /dev/tty2 2>&1Thinking I missed something last time, because I logged into a file (and files are not synced, crash happens too fast killing all X11 processes).
And I saw more than last time, when I ran Filezilla:
TRACE[xfpm-manager.c:618] name_appeared(): org.xfce.SessionManager started up, owned by :1.9
TRACE[xfpm-polkit.c:378] xfpm_polkit_changed_cb(): Auth changed
TRACE[xfpm-polkit.c:378] xfpm_polkit_changed_cb(): Auth changed
TRACE[xfpm-inhibit.c:390] xfpm_inhibit_inhibit(): Inhibit send application name=FileZilla reason=File transfer or remote operation in progress sender=:1.44
TRACE[xfpm-inhibit.c:89] xfpm_inhibit_has_inhibit_changed(): Inhibit added
TRACE[xfpm-power.c:865] xfpm_power_inhibit_changed_cb(): inhibited TRUE, presentation_mode FALSE
TRACE[xfpm-power.c:1323] xfpm_power_toggle_screensaver(): Disabling screensaver, timeout stored: 600
TRACE[xfpm-dpms.c:193] xfpm_dpms_set_inhibited(): DPMS inhibited: TRUEAnd that was the last message before X11 crashed. So the last message is DPMS related. Which is actually the same reason why Xfce4-power-manager crashes from its own menu also.
There were also different polkit messages in the crash log compared to a normal log (maybe Misko_2083 is right?), but the logs don't help me. I removed all .desktop files from /etc/xdg/autostart, rebooted and logged in via lightdm again. No difference.
I don't know yet how to debug DPMS related stuff.
Last edited by jaan513 (2025-12-14 18:19:54)
Offline
#14 2025-12-15 00:39:44
- Misko_2083
- Member
- Registered: 2015-10-13
- Posts: 232
- Website
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
The crash occurs in pci_device_vgaarb_set_target() from libpciaccess.so.0.
This function handles VGA arbitration, managing legacy VGA resource decoding on PCI devices.
This is very old hardware, and modern Linux distributions (like your apparent Debian 13/Trixie setup,
based on package versions like systemd 257) increasingly deprecate or cause issues with legacy Intel graphics from pre 2008 eras.
Switch to the generic modesetting driver
sudo apt install xserver-xorg-video-modesetting
sudo apt purge xserver-xorg-video-intel # Removes the legacy intel driverReboot. This uses the kernel's i915 modesetting more directly, bypassing some legacy Xorg paths including problematic VGA arbiter calls.
-------
This is a harmless warning:
(polkit-mate-authentication-agent-1:1022): polkit-mate-1-WARNING **: 18:43:04.553: Failed to registe
r client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager w
as not provided by any .service filesThe mate polkit authentication agent is forked from the original gnome version.
It still contains some legacy code that attempts to connect to the Gnome Session Manager on the D-Bus.
This is just a warning, not an error that breaks functionality.
Last edited by Misko_2083 (2025-12-15 00:53:52)
Do you want to exit the Circus?
https://www.youtube.com/watch?v=ZJwQicZHp_c
Offline
#15 2025-12-15 07:32:08
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Switch to the generic modesetting driver
sudo apt install xserver-xorg-video-modesetting sudo apt purge xserver-xorg-video-intel # Removes the legacy intel driverReboot. This uses the kernel's i915 modesetting more directly, bypassing some legacy Xorg paths including problematic VGA arbiter calls.
xserver-xorg-video-modesetting was already installed. Purged the intel package.
At first, X refused to start. Added nomodeset to kernel boot parameters, X started now.
Multi-monitor setup no longer works (works with 1 monitor at a time).
But, no crashes in Power Manager, no crashes in Filezilla. That's great!
I can't quite understand why DPMS seems to work (not crash) in Xfce with startx from /dev/tty2 for example, even with the intel driver installed.
As I use a multi-monitor setup, I will still have to use the intel driver, together with the workaround from Filezilla Settings > Interface menu (uncheck "Prevent system from entering idle sleep ...").
Offline
#16 Yesterday 20:07:12
- jaan513
- Member
- Registered: 2025-12-10
- Posts: 9
Re: Filezilla and xfce4-power-manager cause X to crash to login screen
Things are starting to get interesting again.
Whether or not I remove xserver-xorg-video-intel, the behaviour with nomodeset is the same. It doesn't crash, but multi-monitor is not supported. So I installed it back.
I installed Gnome:
apt install gnomeIt's now using gdm3 to log in.
The XFCE Power Manager is not crashing any more?!
Switched back to lightdm, manage to crash Filezilla and Power Manager again.
I used other lightweight login managers before, they didn't help, but gdm3 does something differently?!
Maybe my solution is using gdm3+xfce4. Will do some more testing.
Last edited by jaan513 (Yesterday 20:08:34)
Offline
- Registered users online in this topic: 0, guests: 3
- [Bot] DuckAssistBot,
- [Bot] PerplexityBot,
- [Bot] ClaudeBot
[ Generated in 0.014 seconds, 8 queries executed - Memory usage: 881.63 KiB (Peak: 962.47 KiB) ]