Like two days ago on my laptop I keep getting this weird error. Something like "they keybinding chose for pulldown terminal is invavlid" it has something to do with Tilda settings that have somehow got CENSORED up. Can anyone help me solve this issue?
I have had this happen to me a couple of times. I just reset the shortcut back to f12 and it was happy again.
It also changed my full width view and height of the tilda panel to a quarter of the screen. so I had to reset them as well. I think ( but iām not sure) that the config for tilda has been reset after an update. Maybe one of the devs can confirm , or tell me iām talking crap. 
Yikesā¦language, please. If you havenāt searched on tilda on this site, there are a couple possible solutions there. Whatās worked for me is to just back-up and then delete the file in /home/yourusername/.config/tilda. It will either be recreated at the next login, or by starting Tilda from Applicationsā¦System Toolsā¦Tilda. You can then select a new keybinding if needed.
1 Like
sorry is āc r a pā offensive. I was just saying i was unsure if i was right and just tell me Iām wrong if i was
So I just delete the file, and when you say backup do you mean that file or the entire system? then reboot after itās deleted and it should remake it and everything will be fine?
I didnāt mean your comment, the one above yours. I donāt see where there has been an update to Tilda, but I guess it could be another update. Based on this though I am more convinced it is a bug in Tilda itself.
Just a backup of that config file.
I just checked and no reboot is necessary, recreate the config file by going to Applicationsā¦System Toolsā¦Tilda and click on the close button (after making any configuration changes you want). Keep in mind that you wonāt have any previously made/custom configurations. But you could in theory line up the old file with the new and copy/paste any configurations that you had, across.
Sorry I didnt see that the āfā word was used in the original post .
and yes the behaviour described in that linked bug report is exactly what i have seen. I t was the fact that it had only happened twice that led me to think it was linked with updates
Definitely a (long standing) bug. Author has pushed a commit a few days ago that should hopefully fix it. See here.
Now, until that arrives to the repositories ( likely not soon/to the current Ubuntu versions ), you can use this script Iāve written as a workaround. Served me well for more than a month now.
It checks conf files for size, and if some is found to be zero bytes itās restored from backup, after which Tilda is started.
Just place it in ~/.config/tilda and use it to first create backup config files.
Then edit Tilda autostart entry so that it starts the script instead of Tilda, and it should be good.
More info and download: https://github.com/cofi89/tilda-starter
Interesting, Iāve never had this happen to me personally but I have seen it happp others, particularly on Ubuntu MATE for Raspberry Pi 2.
I can incorporate this technique into the ubuntu-mate-settings-overlay script. @Filip is the test condition always a zero byte file?
Yes, since everytime Tilda trows the keybinding error, if you check the config file, it's always zero byte in size.
From what is known so far, it's getting nuked on shutdown/logout.
Certanly, but just as a suggestion, maybe it'd be better to wait a bit to see if the latest commit from the autor fixes the issue.
And if so, simply patch the existing Tilda ( v1.1 ) package, since it's pretty much a tiny change? 
I'm running a git version since yesterday, so we'll see how it pans out.
1 Like
Iāll update the settings overlay anyway, it is a one line modification 
Solution Worked for me. Got it after a fresh install of Mate.