LXDE LXDE Logout

B

balanga

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

1791731171944.png
 
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?
 
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?
Click to expand...
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....
 
  • Thanks
Reactions: drr
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.
Click to expand...

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.
 
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.

1791794368941.png
 
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
Click to expand...
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.
 
balanga said:
Unfortunately I can't get this working on my other laptop.
Click to expand...
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
 
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?
 

Attachments

  • 2026-10-12_15-28.png
    2026-10-12_15-28.png
    63.7 KB · Views: 40
  • 2026-10-12_15-40.png
    2026-10-12_15-40.png
    38.7 KB · Views: 35
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
Click to expand...
`
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
Click to expand...
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-S8VfSA801X,guid=dab5370ebf2d4605c31f89b46acd3697
 
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?
 
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
 
I'm using Mate, and experience alike when upower or mate-power-manager is/are upgraded or crashed.
Isn't something equivalent happening?
 
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,
 
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,
Click to expand...
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.
 
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.
 
balanga said:
Can anyone tell me if the action of pressing UP arrow whilst in a terminal under LXDE is defined by
Click to expand...
I fixed this problem simply. Yes, when you launch a terminal in X, pressing the up arrow key triggers a screengrab.
 

Attachments

  • 2026-10-14_11-24.png
    2026-10-14_11-24.png
    71.3 KB · Views: 37
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
Click to expand...

An online post elsewhere suggests setting 'emulation' in the terminal setting to 'default'. Maybe something similar in your LXDE terminal?
 
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.
Click to expand...
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 said:
LXQt Settings -> Shortcut Keys.
Click to expand...
With LXDE this is what I get from Preferences -> Set Up Hot Keys which explains that I am seeing a message about gnome-screenshot, but why it should be triggered by pressing the UP arrow key remains a mystery.
Every time I press UP a new task starts up displaying an error, which makes it impossible to use my laptop.

1792051406726.png
 
After running xev I discover that my keymapping for cursor keys is screwed up.

In my /etc/rc.conf I have keymap="uk.kbd" but it looks like this is not active in X. How do I display the value which is assigned when I'm in X?
 
balanga said:
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

View attachment 27612
Click to expand...
Following being sidetracked by other issues, I come back to the original post where the error above pops up when I start LXDE. This error occurs on one laptop but not on another even though I have made every effort to ensure I am using the same apps and the same configurations.

Does anyone understand what the error is complainimg about?

Where would I look for any debugging information?
 
balanga said:
Does anyone understand what the error is complainimg about?

Where would I look for any debugging information?
Click to expand...
Not much to debug, the error messages says clearly GDBus is not finding a service file. That org.freedesktop.ConsoleKit.service is provided by sysutils/consolekit2.

How to find? If you have a ports tree installed:
Rich (BB code): 
 % find /usr/ports -name pkg-plist -exec grep org.freedesktop.ConsoleKit {} +
/usr/ports/sysutils/consolekit2/pkg-plist:share/dbus-1/interfaces/org.freedesktop.ConsoleKit.Manager.xml
/usr/ports/sysutils/consolekit2/pkg-plist:share/dbus-1/interfaces/org.freedesktop.ConsoleKit.Seat.xml
/usr/ports/sysutils/consolekit2/pkg-plist:share/dbus-1/interfaces/org.freedesktop.ConsoleKit.Session.xml
/usr/ports/sysutils/consolekit2/pkg-plist:share/dbus-1/system-services/org.freedesktop.ConsoleKit.service

Otherwise, use a search engine: "org.freedesktop.ConsoleKit.service" site:www.freshports.org
 
You must log in or register to reply here.
Back
Top