0

I tried this answer, but it broke my Gnome Terminal, with this error message:

There was a problem with the command for this terminal
Text was empty (or contained only whitespace)

I tried reinstalling it and uninstalling/reinstalling it to no avail. Anyone have any ideas how I can fix this? I really need my terminal ;-)

EDIT - I should clarify... Before the terminal broke, I could spawn a new terminal with the command:

gnome-terminal --geometry 120x30

It broke after I placed the same command but with an "=" in the config settings and saved it. It just so happens that I had a working terminal open when all this happened and it is still functioning fine, indicating that the terminal works OK, but the launcher is corrupted.

Community
  • 1
nicorellius
  • 6,815

1 Answers1

1

I fixed this by un-checking the box by an option, under Profiles > Title and Command, called "Run as a custom command instead of my shell." This was checked when I altered the custom option under System > Preferences > Preferred Applications, System tab. I still haven't figured out how to make the custom configuration stick, but I at least found a way to fix my terminal when I experiment with tweaking it.

EDIT - Also, the reason the original error said Text was empty (or contained only whitespace) was because when the checkbox was checked, the command was missing (under Profiles > Title and Command). So, thinking I could simply add the command and actually use the "Run as a custom command instead of my shell" I entered gnome-terminal --geometry 120x30 and clicked close. Then when I opened the terminal, it started to freak out and it appeared like the terminal was being launched repeatedly, very quickly. @quack, if you happen to try this as well, maybe you could explain this odd behavior?

What fixed the problem and serves as this answer:

I edited the /usr/share/applications/gnome-terminal.desktop file with the Exec=gnome-terminal --geometry=120x30 line and this finally gave me what I wanted...

nicorellius
  • 6,815