Tiny Core Extensions > TCE Bugs

[Solved] OpenBox autostart not working when adding other programs

<< < (2/2)

WoodenStone:

--- Quote from: Rich on September 27, 2020, 04:44:34 PM ---Hi WoodenStone
The 32 bit version already contains the contents of  openbox-config.tcz.  For some reason the Tinycore scripts were
split off in x86_64.

Could you post the contents of your  ~/.config/openbox/autostart.sh  script please.

--- End quote ---
Here is my autostart.sh


--- Code: ---# This shell script is run before Openbox launches.
# Environment variables set here are passed to the Openbox session.

aterm &

# Set a background color
BG=""
if which hsetroot >/dev/null; then
    BG=hsetroot
else
    if which esetroot >/dev/null; then
BG=esetroot
    else
if which xsetroot >/dev/null; then
    BG=xsetroot
fi
    fi
fi
test -z $BG || $BG -solid "#4f5f82"

# D-bus
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
       eval `dbus-launch --sh-syntax --exit-with-session`
fi

# Make GTK apps look and behave how they were set up in the gnome config tools
if test -x /usr/libexec/gnome-settings-daemon >/dev/null; then
  /usr/libexec/gnome-settings-daemon &
elif which gnome-settings-daemon >/dev/null; then
  gnome-settings-daemon &
# Make GTK apps look and behave how they were set up in the XFCE config tools
elif which xfce-mcs-manager >/dev/null; then
  xfce-mcs-manager n &
fi

# Preload stuff for KDE apps
if which start_kdeinit >/dev/null; then
  LD_BIND_NOW=true start_kdeinit --new-startup +kcminit_startup &
fi

# Run XDG autostart things.  By default don't run anything desktop-specific
# See xdg-autostart --help more info
#DESKTOP_ENV=""
#if which /usr/local/lib/openbox/xdg-autostart >/dev/null; then
#  /usr/local/lib/openbox/xdg-autostart $DESKTOP_ENV
#fi
--- End code ---

    [EDIT]: Added code tags.  Rich

Rich:
Hi WoodenStone
Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:


--- Quote ---[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---

It will appear like this in your post:

--- Code: ---[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.

Rich:
Hi WoodenStone
The first line in that script says:

--- Quote from: WoodenStone on September 27, 2020, 06:11:04 PM --- ...
--- Code: ---# This shell script is run before Openbox launches.

 ----- Snip -----
--- End code ---

--- End quote ---
To me that says this is the wrong place to launch an application since the window manager is not running yet.

Try this:

--- Code: ---echo "exec aterm &" > ~/.X.d/Autostart
--- End code ---

Then restart X.

WoodenStone:

--- Quote from: Rich on September 27, 2020, 08:11:39 PM ---Hi WoodenStone
The first line in that script says:

--- Quote from: WoodenStone on September 27, 2020, 06:11:04 PM --- ...
--- Code: ---# This shell script is run before Openbox launches.

 ----- Snip -----
--- End code ---

--- End quote ---
To me that says this is the wrong place to launch an application since the window manager is not running yet.

Try this:

--- Code: ---echo "exec aterm &" > ~/.X.d/Autostart
--- End code ---

Then restart X.

--- End quote ---
Thanks it worked

Rich:
Hi WoodenStone

--- Quote from: WoodenStone on September 30, 2020, 08:26:15 PM ---Thanks it worked
--- End quote ---
Marked as solved.

Navigation

[0] Message Index

[*] Previous page