[SOLVED] Post-Install Script location

thomas29needles · 2026-05-05 13:37:23

I decided to give the Carbon version a shot, but I feel like something is missing from my installation. When I first booted into a fresh system it greeted me with a terminal window with BunsenLabs specific text and prompt that some questions will be asked to fine tune the installation. However, my system decided that this is the best time to freeze and I had to do a hard reset. On next boot, the post-install script is no longer running automatically. How to run it manually, i.e., where to look for it?

WolfeN · 2026-05-05 13:44:49

You should be able to just type "bl-welcome" in terminal and it will run the welcome script.

thomas29needles · 2026-05-05 14:55:22

WolfeN wrote:

You should be able to just type "bl-welcome" in terminal and it will run the welcome script.

TYSM, running smoothly.

hhh · 2026-05-06 06:18:56

The file 'bl-welcome' is in the hidden ~/.config/bunsen folder in your home folder (Ctrl+h in Thunar to show/hide hidden files, or from Thunar's main menu under "View"). When ran and completed it also creates bl-welcome-understood. bl-setup can be run to recreate the default BL configs, IIRC. Running 'bl-welcome' in a terminal is described in the first paragraph... 'If you do not want to run this script now, you can run it at a later date with the command "bl-welcome".'

Marking this thread [SOLVED]. Thanks for being a forum member!

johnraff · 2026-05-06 08:11:23

hhh wrote:

The file 'bl-welcome' is in the hidden ~/.config/bunsen folder in your home folder (Ctrl+h in Thunar to show/hide hidden files, or from Thunar's main menu under "View"). When ran and completed it also creates bl-welcome-understood.

Slight correction here:
~/.config/bunsen/bl-welcome is created the first time bl-welcome is auto-run (even if exited part-way through), so the auto-run only happens once.
~/.config/bunsen/bl-welcome-understood is created when $user responds "OK" to the Awful Warning about non-Debian repos etc so the message doesn't get repeated every time.

hhh · 2026-05-06 08:46:38

@johnraff, more than a slight correction!

To answer the original thread title then, and correct me if I'm wrong, the file location for the "Hello!" script is /usr/bin/bl-welcome

johnraff · 2026-05-07 01:27:27

^correct!

@thomas you can find the location of any command with one of these:
type <command>
command -v <command>
which <command>

("which" is the traditional choice, but depending on the system, it can be wrong.)

hhh · 2026-05-07 15:59:37

^ lol, I didn't know this, I used catfish! Great post.

johnraff · 2026-05-08 06:00:05

^Most of the time it turns out to be /usr/bin/<command> but the above methods find it anywhere in your $PATH.

marens · 2026-05-09 18:18:20

johnraff wrote:

^correct!
@thomas you can find the location of any command with one of these:
type <command>
command -v <command>
which <command>
("which" is the traditional choice, but depending on the system, it can be wrong.)

Thanks.
Everything works here.

$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

$ type sacad
sacad is /usr/local/bin/sacad

$ command -v sacad
/usr/local/bin/sacad

$ which sacad
/usr/local/bin/sacad

I mainly use whereis:

$ whereis sacad
sacad: /usr/local/bin/sacad

marens · 2026-05-09 18:20:21

hhh wrote:

... I used catfish! ...

A very useful tool.
I always have catfish installed.

I've seen your screenshots and I know you sometimes have the Nautilus file manager.
This is a custom action in ~/.local/share/nautilus/scripts:

Catfish Search Here

#!/bin/bash

# Set IFS so that it won't consider spaces as entry separators.  Without this, spaces in file/folder names can make the loop go wacky.
IFS=$'\n'

# See if the Nautilus environment variable is empty
if [ -z $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS ]; then
    # If it's blank, set it equal to $1
    NAUTILUS_SCRIPT_SELECTED_FILE_PATHS=$1
fi

# Loop through the list (from either Nautilus or the command line)
for ARCHIVE_FULLPATH in $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS; do
    NEWDIRNAME=${ARCHIVE_FULLPATH%.*}
    FILENAME=${ARCHIVE_FULLPATH##*/}
    NAME=${ARCHIVE_FULLPATH##*/.*}

    /usr/bin/catfish --path="$ARCHIVE_FULLPATH"
done

Just right click on the folder you are browsing > Scripts > Catfish Search Here.

hhh · 2026-05-09 20:58:49

^ Thanks for the tip!

#1 2026-05-05 13:37:23

[SOLVED] Post-Install Script location

#2 2026-05-05 13:44:49

Re: [SOLVED] Post-Install Script location

#3 2026-05-05 14:55:22

Re: [SOLVED] Post-Install Script location

#4 2026-05-06 06:18:56

Re: [SOLVED] Post-Install Script location

#5 2026-05-06 08:11:23

Re: [SOLVED] Post-Install Script location

#6 2026-05-06 08:46:38

Re: [SOLVED] Post-Install Script location

#7 2026-05-07 01:27:27

Re: [SOLVED] Post-Install Script location

#8 2026-05-07 15:59:37

Re: [SOLVED] Post-Install Script location

#9 2026-05-08 06:00:05

Re: [SOLVED] Post-Install Script location

#10 2026-05-09 18:18:20

Re: [SOLVED] Post-Install Script location

#11 2026-05-09 18:20:21

Re: [SOLVED] Post-Install Script location

#12 2026-05-09 20:58:49

Re: [SOLVED] Post-Install Script location

Board footer