Weird issues after logging out and logging back in via LXQt logout

Hi everyone,

I’m facing a strange issue on Lubuntu. Whenever I log out of the system and log back in, several things stop working properly. Specifically:

  • waybar, swaync, and copyq don’t start/work.
  • When I press the power button, the logout/shutdown menu that should pop up doesn’t appear.
  • A few other minor things are also broken.

Here’s the weird part — this issue only occurs when I log out using the LXQt logout button and then log back in. It does NOT happen in any of the following scenarios:

  1. If the system was fully shut down and I do a fresh boot — everything works fine.
  2. If I reboot the system — everything works fine.
  3. If I log out using the command pkill -u $USER instead of the LXQt logout button — everything works fine.

So I’m really confused as to why logging out via the LXQt logout button causes these problems, while logging out via pkill -u $USER does not.

Also, it’s worth mentioning that this issue only happens on Lubuntu. I have the exact same desktop environment and setup on Arch Linux, and I’ve never encountered this problem there at all.

Any help or insights would be greatly appreciated. Thanks!

Providing release details would help us to help you.

Software versions change over time, when we know your release, we have [easy] methods to look up version details for the defaults for that release.

You posted (if I recall correctly) recent screenshots of a Lubuntu system running labwc which included a screenshot of a fastfetch type details; but we don’t know if you’ve got only one machine, or like me have multiple (running different OS/versions).

1 Like

It sounds like some processes from your user session remain running after logout. Create another user, logout, login as another user and check if anything is still running.

Hi guiverc,

Thanks for your response. Here are the details:

  • I’m using Lubuntu 26.04 LTS
  • The issue only appears on this Lubuntu installation
  • I have only one machine

Hope this helps. Thanks!

Hi avb66,

I created a new user and tested as you suggested. Here’s what I did:

  1. Logged out from my original user (ali) via the LXQt logout button
  2. Logged in as the new user (linuxfixes)
  3. Ran the command ps aux | grep ali

Here are the results:

$ ps aux | grep ali
root           1  0.0  0.1  24916 15844 ?        Ss   19:20   0:03 /usr/lib/systemd/systemd --switched-root --system --deserialize=52 splash
avahi       1159  0.0  0.0   6696  4592 ?        Ss   19:21   0:00 avahi-daemon: running [ali-pc.local]
ali        23998  0.6  0.1  23120 13752 ?        Ss   21:33   0:00 /usr/lib/systemd/systemd --user
ali        24000  0.0  0.0  22924  4092 ?        S    21:33   0:00 (sd-pam)
ali        24041  0.4  0.0   9256  6096 ?        Ss   21:33   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
ali        24042  0.1  0.1 100496 11028 ?        S<sl 21:33   0:00 /usr/bin/pipewire
ali        24044  0.0  0.1 183236 10652 ?        SLsl 21:33   0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
ali        24047  0.0  0.0   7560  4064 ?        Ss   21:33   0:00 /usr/bin/mpris-proxy
ali        24049  0.6  0.2 482824 21132 ?        S<sl 21:33   0:00 /usr/bin/wireplumber
ali        24051  0.0  0.0  84812  5780 ?        Ssl  21:33   0:00 /usr/bin/pipewire -c filter-chain.conf
ali        24052  0.0  0.1 105776 11428 ?        S<sl 21:33   0:00 /usr/bin/pipewire-pulse
ali        24147  0.3  0.2 555596 20776 ?        Ssl  21:33   0:00 /usr/libexec/xdg-desktop-portal
ali        24157  0.0  0.0 307364  6772 ?        Ssl  21:33   0:00 /usr/libexec/xdg-permission-store
ali        24164  0.0  0.0 957432  7752 ?        Ssl  21:33   0:00 /usr/libexec/xdg-document-portal
ali        24228  0.0  0.0 380976  7796 ?        Ssl  21:33   0:00 /usr/libexec/at-spi-bus-launcher
ali        24236  0.0  0.0   8548  5144 ?        S    21:33   0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_1
ali        24238  0.0  0.1 312944  8856 ?        Ssl  21:33   0:00 /usr/libexec/gvfsd
ali        24245  0.0  0.0 324636  7832 ?        Sl   21:33   0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
ali        24282  0.0  0.0 168688  7664 ?        Sl   21:33   0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
ali        24291  0.0  0.1 534364  9756 ?        Sl   21:33   0:00 /usr/libexec/gvfsd-trash --spawner :1.30 /org/gtk/gvfs/exec_spaw/0
ali        24351  0.0  0.1 386788 11064 ?        Ssl  21:33   0:00 /usr/libexec/gvfs-udisks2-volume-monitor
ali        24356  0.0  0.0 168852  7204 ?        Ssl  21:33   0:00 /usr/libexec/gvfsd-metadata
ali        24369  0.0  0.0 308976  7904 ?        Ssl  21:33   0:00 /usr/libexec/gvfs-gphoto2-volume-monitor
ali        24375  0.0  0.0 308008  7420 ?        Ssl  21:33   0:00 /usr/libexec/gvfs-mtp-volume-monitor
ali        24383  0.0  0.1 389740  9420 ?        Ssl  21:33   0:00 /usr/libexec/gvfs-afc-volume-monitor
ali        24402  0.0  0.0 307832  7036 ?        Ssl  21:33   0:00 /usr/libexec/gvfs-goa-volume-monitor
ali        24442  0.0  0.2 380116 20816 ?        Ssl  21:33   0:00 /usr/libexec/bluetooth/obexd
ali        24455  0.0  0.0 304592  6404 ?        Sl   21:33   0:00 swaync-client -swb
linuxfi+   25650  0.0  0.0   6716  2592 pts/0    S+   21:34   0:00 grep ali
$ 

Do you have any suggestions to fix this issue?