Hello, I changed my config in black box such that now it exits or crashes immediately on launch. I was trying to get it to start tmux on launch, but I must've done it wrong because now the window pops up for a fraction of second before disappearing. Is there a way to simply reset the config to default so I may try again?
#Reset Black Box config
prime moss
tranquil bear
Hello, I changed my config in black box such that now it exits or crashes immedi...
What config did you change?
prime moss
I don't remember the exact name, but it was the startup command. I appended && tmux after what was already there.
tranquil bear
I don't remember the exact name, but it was the startup command. I appended `&& ...
You can right click BlackBox and choose "Rescue Shell".
This is on the host, so some things might be restricted or different, but gsettings for example should still work.
prime moss
Hmm, that seems to do nothing, but I can (what looks like) a host shell by installing it from FlatHub 🤔
Also noticed it's a bit of a special case as it shows up in my list of isntalled apps in software, but when I click into the app details, it give me the option to install, but launching give me a host shell..
If I could blow away and start anew, that seems ideal, but idk if I borked it being that 😞
This is from the FH installed BB. The one that was installed by default had a custom command. I suspect this one is storing its config in .var/app like other flatpaks, but the installed default likely stored it elsewhere. Is it in gsettings? If so, do you/anyone know where those settings are? I can poke around from there.
tranquil bear
Hmm, that seems to do nothing, but I can (what looks like) a host shell by insta...
Ah yeah, that makes sense.
I mean you can also get dconf editor from the Store and use that to edit the standard command in BlackBox
prime moss
Yeah can do, just need to know where that config is.
tranquil bear
/com/raggesilver/BlackBox/
in dconf
key is "custom-shell-comand"
should be just "/usr/bin/vanilla-shell-detect"
tranquil bear
Yessssss tytytyty!!
Also, if you want to actually modify stuff that runs when the shell opens, it's more common to do that in ~/.bashrc
Though I would recommend checking if tmux exists before running it in .bashrc, because of the multiple environments in VanillaOS.
Changing /usr/bin/os-shell should also work, though that would be very difficult to fix if messed up.
prime moss
Hmm, I'll look into that. Just kind of assumed bashrc was more for config and stuff to run to set things up whereas tmux kind of wraps the shell. I had done this in Debian where I could just use it as a custom command, but I understand this is more like a shell in a container. I've confirmed tmux is indeed installed in the container, though I should probably add it to the host...?
tranquil bear
Hmm, I'll look into that. Just kind of assumed bashrc was more for config and st...
Hm, I don't think you need to add it to the host.
prime moss
Hm, I don't think you need to add it to the host.
Wouldn't I need to reinstall it every time I reset the container then?
tranquil bear
Wouldn't I need to reinstall it every time I reset the container then?
You wouldn't normally reset the container
prime moss
You wouldn't normally reset the container
Is there a way to automatically install it if it is reset? Like a script that runs on reset?