[SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

anark10n · 2022-09-27 18:39:15

Hey there

I'm using openbox/lxsession with tint2 panel, and lxsession causes tint2 display on a taskbar desktop 1 whenever lxsession is started, whether before or after tint2 (and whether I start with the autostart file, or i start lxsession manually). The other desktops are still present, as I can scroll through them, but the taskbar only displays desktop 1 content regardless. Tint2 only displays the correct number of taskbars for each desktop after running obconf and either increasing/decreasing the number of desktops. All i have in my autostart for lxsession is "lxsession &". Am i missing something here?

Last edited by anark10n (2022-10-07 18:09:33)

Lone_Wolf · 2022-09-27 19:00:22

Depends ... lxde & lxqt use their own copies of configuration files and not those of standalone openbox.

Check ~/.config/openbox/lxde-rc.xml , <desktops> section .

anark10n · 2022-09-27 22:40:15

No such file in that directory. There's only the following files:

├── autostart
├── bookmarks.sh
├── environment
├── menu.xml
├── rc.xml
└── recentlyopened.sh

Lone_Wolf · 2022-09-28 10:44:49

Do you use startx / xinit to start openbox or are you using openbox as WM for a Desktop Environment ?
(post ~/.xinitrc if the former)

anark10n · 2022-09-29 07:43:53

I'm using openbox as my desktop environment, not as a WM. I use lightdm to start openbox so I don't have xinitrc file in my home directory. I do, however, have an ~/.xsessio-errors file with the following entries for tint2:

tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes
tint2: xRandr: Found crtc's: 4
[1;34mtint2: xRandr: Linking output HDMI-0 with crtc 0, resolution 1920x1080, DPI 81[0m
tint2: xRandr: crtc 1 seems disabled
tint2: xRandr: crtc 2 seems disabled
tint2: xRandr: crtc 3 seems disabled
tint2: Loading config file: /home/anark10n/.config/tint2/tint2rc
tint2: real transparency on... depth: 32
tint2: panel items: TSC
tint2: Systray composited rendering on
tint2: nb monitors 1, nb monitors used 1, nb desktops 1
[1;34mtint2: panel 1 uses scale 1 [0m
tint2: Kernel uevent interface initialized...
tint2: systray window 41943053
[1;32mtint2: systray started[0m
[1;32madd_icon: 12582983 (parcellite), pid 1902, visual 0x55aa62b4e700, colormap 12582982, depth 32, width 48, height 48[0m
[1;32madd_icon: 29360140 (Ethernet network connection “Wired Connection” active), pid 1925, visual 0x55aa62b4e700, colormap 29360139, depth 32, width 1, height 1[0m
[1;32madd_icon: 14680076 (volumeicon), pid 1898, visual 0x55aa62b4e700, colormap 14680075, depth 32, width 1, height 1[0m
[1;32madd_icon: 20971530 (), pid 1900, visual 0x55aa62b4e700, colormap 20971529, depth 32, width 22, height 22[0m

Lone_Wolf · 2022-09-29 09:20:19

I'm using openbox as my desktop environment, not as a WM.

I'm pretty sure openbox devs & lots of its users wouldn't like that statement. All DEs for X require a WM, but WMs don't require DEs.
You're using openbox as WM and don't use a DE (which is perfectly fine).

The xsession-errros file doesn't give clues, but I do have a hunch what might be wrong.

Since you are using lightdm you are probably using /usr/share/xsessions/openbox.desktop to start openbox.
Please post the contents of that file.

peterklarc · 2022-09-29 18:57:09

Did you check ~/.config/tint2/tint2rc the taskbar part: taskbar_mode = single_desktop or taskbar_mode = multi_desktop

anark10n · 2022-10-02 05:36:07

Lone_Wolf wrote:

I'm pretty sure openbox devs & lots of its users wouldn't like that statement. All DEs for X require a WM, but WMs don't require DEs.
You're using openbox as WM and don't use a DE (which is perfectly fine).

My bad

Contents of /usr/share/xsessions/openbox.desktop:

[Desktop Entry]
Name=Openbox
Comment=Log in using the Openbox window manager (without a session manager)
Exec=/usr/bin/openbox-session
TryExec=/usr/bin/openbox-session
Icon=openbox
Type=Application

peterklarc wrote:

Did you check ~/.config/tint2/tint2rc the taskbar part: taskbar_mode = single_desktop or taskbar_mode = multi_desktop

It has taskbar_mode = multi_desktop, even on startup.

Last edited by anark10n (2022-10-02 05:39:08)

Lone_Wolf · 2022-10-02 10:06:53

The openbox.desktop is what I expected and hasn't been changed from the default.

For clarity :
When you start openbox without lxsession does the tint2 taskbar show the expected number of desktops ?

If yes,

The openbox.desktop file contains Exec=/usr/bin/openbox-session .
Why do you want to start another session ?

anark10n · 2022-10-03 10:14:22

Lone_Wolf wrote:

The openbox.desktop is what I expected and hasn't been changed from the default.
For clarity :
When you start openbox without lxsession does the tint2 taskbar show the expected number of desktops ?
If yes,
The openbox.desktop file contains Exec=/usr/bin/openbox-session .
Why do you want to start another session ?

Yes, the correct number of desktops are displayed when i start openbox without lxsession. and also, starting lxsession manually causes tint2 to display a taskbar for only one desktop.

As to why I want to start another session, i'm not too sure what you're asking here. Is my current configuration starting 2 sessions of openbox? or does lxsession start another openbox-session?

Last edited by anark10n (2022-10-03 10:15:29)

Lone_Wolf · 2022-10-06 10:47:18

lxsession is a X session manager, but openbox-session already started a X session for you.

You are running a X session inside a X session now, each with their own settings.
It's possible you are also running 2 instances of openbox now, but I'm not sure .
(ps -aux | grep openbox should help to determine that)

rephrasing the question :
What do you hope to achieve by running lxsession inside the existing openbox X session ?

Last edited by Lone_Wolf (2022-10-06 10:48:23)

anark10n · 2022-10-07 05:44:17

output of ps -aux | grep openbox:

username     745  0.3  0.1 220460 23024 ?        Ss   07:27   0:00 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
username     771  0.0  0.0   7396  1584 ?        S    07:27   0:00 sh /home/username/.config/openbox/autostart
username     772  0.0  0.0   7396  1584 ?        S    07:27   0:00 sh /home/username/.config/openbox/autostart
username    1401  0.0  0.0   6568  2460 pts/0    S+   07:29   0:00 grep openbox

Lone_Wolf wrote:

rephrasing the question :
What do you hope to achieve by running lxsession inside the existing openbox X session ?

It's required for an internal drive of mine to mount when I click on it. With lxsession, I get a password input request to mount the drive; without it, it just throws a Not authorized to perform operation dialogue box.

Lone_Wolf · 2022-10-07 09:59:37

Now the picture is getting clear.

Those permissions are applied through polkit and polkit requires users to register with them, typically through an authentication agent .
Lightdm & openbox don't support polkit so don't come with a polkit authentication agent.

You're not using lxsession as a X session manager, but as polkit authentication agent.

What bites you and causes the lxsession / tint2 number of desktops conflict is :
lxde / lxqt are designed to work with openbox in a very specific way which interferes with openbox own settings .

To keep settings synchronized with openbox they use lxappearance-obconf / lxappearance-obconf-gtk3 as plugins to their configuration applets
lxappearance / lxappearance-gtk3 .

The simplest solution for your issue is to choose a different polkit authentication method .

There are (atleast) 2 possible sources for that :
- another polkit authentication agent , see https://wiki.archlinux.org/title/Polkit … ion_agents
- systemd-logind can communicate with polkit (through pam I think ?) without needing a separate polkit authentication agent.
Some display managers support that, SDDM is one of them.

Last edited by Lone_Wolf (2022-10-07 10:01:09)

anark10n · 2022-10-07 18:08:17

Lone_Wolf wrote:

The simplest solution for your issue is to choose a different polkit authentication method .
There are (atleast) 2 possible sources for that :
- another polkit authentication agent , see https://wiki.archlinux.org/title/Polkit … ion_agents
- systemd-logind can communicate with polkit (through pam I think ?) without needing a separate polkit authentication agent.
Some display managers support that, SDDM is one of them.

Like a boss. I went for another polkit authentication agent (polkit-gnome) and now I have the correct number of taskbars on startup, and the authentication when mounting my drive. Thank you, sir. All of the blessings to you and yours for sticking with me through all this.

Arch Linux

#1 2022-09-27 18:39:15

[SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#2 2022-09-27 19:00:22

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#3 2022-09-27 22:40:15

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#4 2022-09-28 10:44:49

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#5 2022-09-29 07:43:53

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#6 2022-09-29 09:20:19

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#7 2022-09-29 18:57:09

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#8 2022-10-02 05:36:07

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#9 2022-10-02 10:06:53

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#10 2022-10-03 10:14:22

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#11 2022-10-06 10:47:18

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#12 2022-10-07 05:44:17

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#13 2022-10-07 09:59:37

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

#14 2022-10-07 18:08:17

Re: [SOLVED] Lxsession causing tint2 to display the wrong no. of desktops

Board footer