I Broke Openbox - Doesn't Start on Login

[KenD]

Debian 11 (updated) with Openbox

I edited ~/.config/openbox/rc.xml to add a key binding and apparently made an error. Now my system starts and logs in correctly but I get an error message saying that I forgot to add "</" somewhere. Openbox does not start.

How do I get to a terminal so that I can use nano to try to find my error and fix it?

[Aki]

Hello,

Debian 11 (updated) with Openbox

I edited ~/.config/openbox/rc.xml to add a key binding and apparently made an error. Now my system starts and logs in correctly but I get an error message saying that I forgot to add "</" somewhere. Openbox does not start.

How do I get to a terminal so that I can use nano to try to find my error and fix it?

You can start Debian selecting from grub "Advanced options for Debian GNU/Linux" and the select the entry with the "recovery mode" label. It will start Debian in single user mode. At the prompt, typing the root password, a terminal console will be opened for user root. Your home directory will be in /home/yourusername (where yourusername is your user name).

[KenD]

Thank you. I did that as you directed but it took me back to my usual login screen where I was asked for my user name and password as usual. Upon entering them I was back at the same place as before - i.e. logged into my system but Openbox has not started.

[Bulkley]

On your keyboard push Ctrl + Alt + F3 at the same time.

[KenD]

SOLVED: At the grub menu hit "e". Find the line beginning with "linux" and add a space and "3" at the end. Hit enter, command prompt appears.

[kent_dorfman766]

As @Bulkley alluded to, there are other virtual consoles running, so <CTLR><ALT><F?> can give you a separate and distinct command line login session. It used to be that VT7 was reserved for X11 but I'm not sure if that policy still holds true because I always boot to command line mode, login, then manually start X11. You can check using systemctl | grep getty

[oswaldkelso]

The fix is easy. login to another tty Control+Alt+F3 then rename you broken openbox.rc

Code: Select all

 mv  ~/.config/openbox/rc.xml   ~/.config/openbox/rc-backup.xml 

You'll then be able to login with the system wide config.

Then fix the error in rc-backup.xml

The are xml validators on line that will show you where you made a cock up. Once fixed rename it back to the original.

https://www.xmlvalidation.com/
https://www.w3schools.com/xml/xml_validator.asp

[wizard10000]

Another thing that I think is worth mentioning is that almost every Linux text editor can be configured to make a backup of any file you edit. This has saved my bacon many times

[CwF]

make a backup of any file you edit

Better yet leave comments of edits within the file itself as to prior edits, what ifs, version or distro variations, etc

I use a 'probe' thunar custom action to cat any file into a gxmessage/xenity/notify-send dialog for review. For file that are mostly commented I use 'cliff' (think cliffsnotes) instead of 'probe' for a dialog condensed to actually active code;

Code: Select all

grep -Env '^\s*$|^\s*\#' %f | gxmessage -geometry 960x480 -name "%f" -buttons "cool:0" -file -

[wizard10000]

Better yet leave comments of edits within the file itself as to prior edits, what ifs, version or distro variations, etc

I do this also. I copy the entry I want to change, paste it below the original entry, make my edits and then comment out the original.