LXDE LXDE Logout

balanga · Sunday at 3:05 PM

With LXDE the Logout option sometimes shows a full list of options but often only allows me to select 'Lock Screen', 'Logout' or 'Cancel'.

Anyone know what launches these options?

It may well be related to this error which pops up when starting X

drr · Sunday at 3:47 PM

Is your LXDE started from a display manager that starts consolekit as well?

If manually starting it with startx, could you please try "exec dbus-launch --exit-with-x11 ck-launch-session startlxde" in your ~/.xinitrc to see if that works?

balanga · Sunday at 5:42 PM

drr said:
Is your LXDE started from a display manager that starts consolekit as well?

If manually starting it with startx, could you please try "exec dbus-launch --exit-with-x11 ck-launch-session startlxde" in your ~/.xinitrc to see if that works?

I use startx, but your suggestion makes no difference.

It looks like I have screwed up something in LXDE as I suddenly get Openbox sessions starting up when pressing UP in ee.

Maybe time to reinstall LXDE....

drr · Sunday at 10:42 PM

balanga said:
It looks like I have screwed up something in LXDE as I suddenly get Openbox sessions starting up when pressing UP in ee.

I have come across similar keybinding issues with the LXQT terminal, when I briefly tried it some time ago. Unfortunately, I did not do any research back then to resolve it, so I am unable to offer any further help.

balanga · Monday at 9:40 AM

After making numerous changes to .xinitc I get this variation which reports that an error has occurred but without giving any specifics. Has anyone come across this? My suspicion is that it has something to do with consolekit.

balanga · Monday at 10:20 AM

balanga said:
After making numerous changes to .xinitc I get this variation which reports that an error has occurred but without giving any specifics. Has anyone come across this? My suspicion is that it has something to do with consolekit.

View attachment 27622

This error occurred on a different laptop I am checking, I just found that this particular error occurs if dbus is not running, Once dbus is enabled this error disappears and I get a full menu when selecting logout. Unfortunately I can't get this working on my other laptop.

USerID · Monday at 12:24 PM

balanga said:
Unfortunately I can't get this working on my other laptop.

D-Bus always works for me. It’s strange that you’re having the issue on a different laptop. How is D-Bus linked to the hardware? Does FreeBSD have UPower? If so, perhaps the problem stems from a different implementation on the second laptop? This might be off-topic, but here is how it all ties together in Alpine Linux + LXQt.
~ $ pstree | grep dbus

Bash:

     |          |-{gdbus}
     |-at-spi-bus-laun-+-dbus-daemon
     |                 |-{gdbus}
     |-at-spi2-registr-+-{gdbus}
     |-2*[dbus-daemon]
     |-dbus-launch
     |-gvfs-mtp-volume-+-{gdbus}
     |                 |-{gdbus}
     |       |             |-{gdbus}
     |       |-{gdbus}
     |-supervise-daemo---polkitd-+-{gdbus}
     |                        |                            |         |-{gdbus}
     |                        |                            |                 |-{gdbus}
     |                        |                            |            |-{gdbus}
     |                        |                            |            |                 |-{gdbus}
     |                        |                            |             |-{gdbus}
     |         |-{gdbus}
     `-upowerd-+-{gdbus}

Check this out:
~ $ env | grep dbus

Code:

DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-BTPTnjAzuF,guid=c710ea2fe8d79192d753fba86acca4a4

USerID · Monday at 1:31 PM

FreeBSD15.1+ Desktop Environment: LXQt 2.4.0

$ pstree | grep dbus

Code:

 |--= 02039 messagebus /usr/local/bin/dbus-daemon --system
 |--= 02223 hkuser /usr/local/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
 |           |   \--- 02567 hkuser grep dbus
 |--- 02222 hkuser dbus-launch --exit-with-x11 ck-launch-session startlxqt

What if you disable watcher for the battery and laptop lid?

balanga · 2026-10-13T22:18:17+0100

USerID said:
D-Bus always works for me. It’s strange that you’re having the issue on a different laptop. How is D-Bus linked to the hardware? Does FreeBSD have UPower? If so, perhaps the problem stems from a different implementation on the second laptop? This might be off-topic, but here is how it all ties together in Alpine Linux + LXQt.
~ $ pstree | grep dbus

Bash:

| |-{gdbus} |-at-spi-bus-laun-+-dbus-daemon | |-{gdbus} |-at-spi2-registr-+-{gdbus} |-2*[dbus-daemon] |-dbus-launch |-gvfs-mtp-volume-+-{gdbus} | |-{gdbus} | | |-{gdbus} | |-{gdbus} |-supervise-daemo---polkitd-+-{gdbus} | | | |-{gdbus} | | | |-{gdbus} | | | |-{gdbus} | | | | |-{gdbus} | | | |-{gdbus} | |-{gdbus} `-upowerd-+-{gdbus}

Check this out:
~ $ env | grep dbus

Code:

DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-BTPTnjAzuF,guid=c710ea2fe8d79192d753fba86acca4a4

`

USerID said:
D-Bus always works for me. It’s strange that you’re having the issue on a different laptop. How is D-Bus linked to the hardware? Does FreeBSD have UPower? If so, perhaps the problem stems from a different implementation on the second laptop? This might be off-topic, but here is how it all ties together in Alpine Linux + LXQt.
~ $ pstree | grep dbus

Bash:

| |-{gdbus} |-at-spi-bus-laun-+-dbus-daemon | |-{gdbus} |-at-spi2-registr-+-{gdbus} |-2*[dbus-daemon] |-dbus-launch |-gvfs-mtp-volume-+-{gdbus} | |-{gdbus} | | |-{gdbus} | |-{gdbus} |-supervise-daemo---polkitd-+-{gdbus} | | | |-{gdbus} | | | |-{gdbus} | | | |-{gdbus} | | | | |-{gdbus} | | | |-{gdbus} | |-{gdbus} `-upowerd-+-{gdbus}

Check this out:
~ $ env | grep dbus

Code:

DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-BTPTnjAzuF,guid=c710ea2fe8d79192d753fba86acca4a4

DBUS_SESSION_BUS_ADDRESS=unix

ath=/tmp/dbus-S8VfSA801X,guid=dab5370ebf2d4605c31f89b46acd3697

balanga · 2026-10-13T22:33:37+0100

My struggle with getting a full menu when selecting Logout on LXDE is just causing more problems when trying various fixes.

My latest problem which has just surfaced and which makes my normal work system unusable is the sudden appearance of an error which is triggered by the up arrow key in a terminal application.

When I press up arrow in a terminal application I get an Openbox error:-

Failed to execute child process "gnome-screenshot".

AI solutions provide no clue as to what might be the cause of this. I am not aware of trying to do anthing with Openbox settings for a long time.

I have reinstalled LXDE to see if that might sort out the problem but it doesn't.

Every time I press UP arrow a new Openbox error session starts up making it impossible to use my main system.

Can anyone give me a hint as to where to look?

balanga · 2026-10-13T22:55:38+0100

Can anyone tell me if the action of pressing UP arrow whilst in a terminal under LXDE is defined by

/root/.config/openbox/lxde-rc.xml

T-Aoki · 2026-10-13T23:37:19+0100

I'm using Mate, and experience alike when upower or mate-power-manager is/are upgraded or crashed.
Isn't something equivalent happening?

balanga · 2026-10-13T23:52:24+0100

Does Openbox underpin Mate?

My system was working fine previously until I tried to find out why I got the initial freedesktop error.

It sounds like a pkg update must have caused my problem, but it is difficult to pinpoint what happened,

T-Aoki · 2026-10-14T00:04:40+0100

balanga said:
Does Openbox underpin Mate?

My system was working fine previously until I tried to find out why I got the initial freedesktop error.

It sounds like a pkg update must have caused my problem, but it is difficult to pinpoint what happened,

Don't know. If I recall correctly, I've never tried Openbox.
But if shutdown button exists, possibly some kind of power management feature would exist, and if it somehow crashes or become incompatible as of upgrades, the menu codes cannot connect to the feature and could drop shutdown button.

shepper · 2026-10-14T01:55:35+0100

There is a FreeBSD wiki on LXDE
You do need consolekit and to be a member, iirc, the wheel group. Dbus needs to be running system wide.

USerID · 2026-10-14T09:26:31+0100

balanga said:
Can anyone tell me if the action of pressing UP arrow whilst in a terminal under LXDE is defined by

I fixed this problem simply. Yes, when you launch a terminal in X, pressing the up arrow key triggers a screengrab.

drr · 2026-10-14T10:22:13+0100

balanga said:
Can anyone tell me if the action of pressing UP arrow whilst in a terminal under LXDE is defined by

/root/.config/openbox/lxde-rc.xml

An online post elsewhere suggests setting 'emulation' in the terminal setting to 'default'. Maybe something similar in your LXDE terminal?

balanga · 2026-10-14T13:33:14+0100

USerID said:
I fixed this problem simply. Yes, when you launch a terminal in X, pressing the up arrow key triggers a screengrab.

Thanks, but I'm not exactly sure what you have shown me a picture of.

balanga · 2026-10-14T13:36:23+0100

shepper said:
There is a FreeBSD wiki on LXDE
You do need consolekit and to be a member, iirc, the wheel group. Dbus needs to be running system wide.

I have been using LXDE for many years and install it on all my systems.

It works OK on some but have problems on others, I can't work out specifically what the differences are.

USerID · 2026-10-14T14:30:36+0100

balanga said:
Thanks, but I'm not exactly sure what you have shown me a picture of.

LXQt Settings -> Shortcut Keys.

LXDE LXDE Logout

balanga

drr

balanga

drr

balanga

balanga

USerID

USerID

Attachments

balanga

balanga

balanga

T-Aoki

balanga

T-Aoki

shepper

USerID

Attachments

drr

balanga

balanga

USerID