You are not logged in.

#1 2022-09-03 21:35:53

warteeminus321
Member
Registered: 2022-09-03
Posts: 27

SOLVED: executible not autolaunching in openbox

"Lead" executible (hot corners functionality) used to auto launch fine from openbox' autostart. I switched to Xephyr and everything launches fine except lead.
What's weirder openbox' autostart won't launch xterm exec now.
What's even weirder lead won't launch from .xinitrc after openbox launch directive.

SOLUTION: it kind of started working - lead executible launches from .xinitrc' Xephyr invokation.

Last edited by warteeminus321 (2022-09-04 12:09:33)


Hitchhacker's Guide to the Galaxy: “Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.”
If you didn't know you are backdoored, you are backdoored.

Offline

#2 2022-09-03 21:57:57

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,223

Re: SOLVED: executible not autolaunching in openbox

"switched to Xephyr" from what?
Can you run "lead" from an interactive terminal?
Does openbox autostart start *anything*?

Please post your entire xinitrc.

Offline

#3 2022-09-04 05:12:09

warteeminus321
Member
Registered: 2022-09-03
Posts: 27

Re: SOLVED: executible not autolaunching in openbox

Switched to Xephyr from just a plain Xorg display.
That's the weirdest thing - I *can* run lead from an interactive terminal once the window manager loads, just not from openbox' autostart or .xinitrc.
xinitrc is the default xinitrc - just deleted default couple of lines at the end that launch things, and add instead

firejail --profile=/etc/firejail/Xephyr.profile `Xephyr :88 & DISPLAY :88 openbox --startup "sakura" & DISPLAY=:1 polybar`

openbox' autostart does not seem to start anything but then I can start polybar from .xinitrc but not the lead exec.


Hitchhacker's Guide to the Galaxy: “Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.”
If you didn't know you are backdoored, you are backdoored.

Offline

#4 2022-09-04 07:10:20

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,223

Re: SOLVED: executible not autolaunching in openbox

xinitrc is the default xinitrc…

https://bbs.archlinux.org/viewtopic.php?id=57855

However what immediately sticks out is that the DISPLAY is all over the place and also I'm not sure whether and how firejail will handle the subshell execution (the backticks) - did you copy that from somewhere?

Apparently your xinitrc is supposed to be run on starting a regular xorg server and then there start a firejail'd xephyr instance on :88 and then trying to run openbox on :88, but "DISPLAY :88" is nonsense and for sure doesn't get exported so everything will quite likely keep trying on :0 and you're also starting polybar on :1, but in the same firejail context… ??

=> Elaborate what you're trying to achieve and post the complete xinitrc, because there're obvious syntax errors already in that line you posted.

For a start I'd suggest to wrap your firejail session into a script and have eg ~/bin/xephyrjailbox start w/ something like

#!/bin/sh
Xephyr :88 &
export DISPLAY=:88
lead &
xterm &
openbox

and run that w/ firejail

Offline

#5 2022-09-04 07:31:52

warteeminus321
Member
Registered: 2022-09-03
Posts: 27

Re: SOLVED: executible not autolaunching in openbox

My bad, there's a syntax typo in the code I posted. The actual line is:

firejail --profile=/etc/firejail/Xephyr.profile `Xephyr :88 & DISPLAY=:88 openbox --startup "sakura" & DISPLAY=:88 polybar`

Hitchhacker's Guide to the Galaxy: “Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.”
If you didn't know you are backdoored, you are backdoored.

Offline

#6 2022-09-04 08:06:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,223

Re: SOLVED: executible not autolaunching in openbox

The DISPLAY still isn't exported and where does that start lead?

Offline

#7 2022-09-04 09:00:30

warteeminus321
Member
Registered: 2022-09-03
Posts: 27

Re: SOLVED: executible not autolaunching in openbox

If I export DISPLAY so:

firejail --profile=/etc/firejail/Xephyr.profile `Xephyr :88 & export DISPLAY=:88 & openbox --startup "sakura" & polybar`

printenv shows DISPLAY as :0


Hitchhacker's Guide to the Galaxy: “Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.”
If you didn't know you are backdoored, you are backdoored.

Offline

#8 2022-09-04 11:50:54

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,223

Re: SOLVED: executible not autolaunching in openbox

printenv shows that *where*?

Again: I'm not optimistic about the subshell invocation there, you still didn't explain what your actual plan is here and wtr I'll once more point out https://bbs.archlinux.org/viewtopic.php?id=57855
Read that thread, be more precise, elaborate and literal in your descriptions if you want this to go forward.

Offline

#9 2022-09-04 12:05:23

warteeminus321
Member
Registered: 2022-09-03
Posts: 27

Re: SOLVED: executible not autolaunching in openbox

It's working now. I don't know what I did but this works fine now:

firejail --profile=/etc/firejail/Xephyr.profile `Xephyr :88 & DISPLAY=:88 openbox --startup sakura & DISPLAY=:88 polybar & DISPLAY=:88 lead`

Thank you for your input and advice. Really helpful for people who don't know their way around here.


Hitchhacker's Guide to the Galaxy: “Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.”
If you didn't know you are backdoored, you are backdoored.

Offline

Board footer

Powered by FluxBB