Saka randomly stops working and trashes settings on auto update

[ghost]

Saka Key mysteriously stopped working recently. (I don't know why. It's still an installation from 2018. Firefox wasn't updated recently. I didn't try to install a newer Saka release.) It was notable that the extensions was still displayed. The icon was present in the toolbar, but trying to use any of the hotkeys did nothing, and when clicking the Saka icon, most of the UI was empty.

I tried various things. I uninstalled the addon, and installed a newer release. This restored it, but all my settings are gone. I don't have the settings in an exported form either.

Anyway, I still have an older backup of the firefox profile. Opening it with the browser (under a different unix user), Saka works, but exporting the saka settings does not. (Persistent download error. I have no clue why this is implemented as download at all.) So apparently I can't restore the settings the normal way.

I tried copying browser-extension-data/{461... (should be the Saka UUID) from the old profile to the proper profile, but this did not appear to change anything.

What can I do to properly transplant the old settings?

[ghost]

I found storage/default/moz-... but after copying the Saka one, the Saka extension is broken again, as I described above. Nothing showing in options. Mysterious.

[ghost]

Well, now I can't get Saka Key in a working state anymore. Even removing and reinstalling it (whether it's the 2018 version of the most recent release) makes it show up broken. Also, websites do not load. Is it hanging due to running addon code? Everything is fucked now.

I'm considering getting a low level job as pig shit shoveler, so I never have to see a computer again. But I guess even they need to use computers these days.

[ghost]

Well, I "solved" my problem by deleting ~/.mozilla and restoring it from a more recent full backup. It works again now. Why? Why did it even break? I didn't do anything.

I still can't export the Saka settings asd json. The download fails (literally says "Failed", and the file is not present). The URL is blob:moz-extension://05e51f1d-4c8f-4dbe-b0f1-3132e112d9ad/38a18036-3a4f-43b3-bd44-cc35bc6bece1. Trying to put it into the firefox address bar shows an error page saying "Hmm. That address doesn’t look right." (what the hell does that mean? unknown URL schema?) If I remove the blob: part, it just says file not found.

I swear I'll switch to qutebrowser or something as soon as it supports ublock.

[ghost]

Now it broke again. Only thing I did was probably restarting the browser by closing the last opened window, and then opening a new one later again. What the fuck is going on?

[ghost]

OK I think I figured out what "causes" this: the add-on was auto-updated because you recently pushed a new release. The really confusing thing is that you can't install it on the mozilla add-on web page, but it'll still auto-update it.

The update from 1.25.5 to 1.26.3 apparently trashed the settings, and in an irrecoverable way. This is probably quite severe. You can't even reset the settings and get back to a working state. Anyway, I really don't want to lose my settings anyway, because they were hard to configure.

Uninstalling and reinstalling the new version seems to simply reset all settings. But sometimes, and for unknown reasons, often reinstalling the older and newer versions puts firefox in a completely broken state, where websites won't load even if the add-on gets uninstalled. I have no clue what went wrong, there's not even logging anywhere. Thank you, Mozilla, for completely hiding away any useful way to debug this. By which I mean I'll switch browsers sooner or later.

Sorry for the noisy issue.

So, as a user, I can provide the following workaround:

• disable auto-update of this by changing the radio box choice in Tool->Add-Ons
• if you already updated, rm -rf .mozilla and restore a backup (you do have a backup, right?)

[matheusfillipe]

I have the same issue and don't have a backup :P .... Im basically reinstalling saka keys and loading my configuration json file every time i use my browser.

To me sometimes just disabling it and enabling again works as well but is working like crap :(

[ghost]

Does that mean newer Saka releases somehow trash the config every time? From my experiences, I suspected it only had to do with updating. But since I don't have a backed up json config (only a backed up full profile), I effectively can't use the new version.

[matheusfillipe]

Oh yes the config page also doesn't show up to me and I think you might have the same so no way you can test unless if using a config. To me at least it stops working even when I suspend my computer with firefox open but I haven't tested enough. For sure every time I start firefox it is not working.

Seems like just loading the config file can bring it back to live. Here is my config in case you want to test this or/and you can use this as a model for creating your own I guess: saka_key_config.zip

[matheusfillipe]

I can confirm that to me, every time I close firefox I have to reload the config .json file and it works again. Also nothing displays under my options menu.

[j-cr]

Similar issue here. I updated the extension (why, jeez, oh why), it stopped working completely and the settings page is broken now. Importing the old config file from the backup does nothing, literally.

What's even better is that it seems the author removed all the older versions from the firefox addons page, so I can't downgrade to a working version. Sigh.

[joefiesta]

I have had problems with Saka-Key for the longest time, and have learned to never update. I run windows 7 32 bit and have Saka-key 1.25.5. Recently my shortcuts got screwed up and no longer start with the lowest number (I use "0123456789" for shortcuts). I just checked out the .JSON file @MATHEUFILLIPE provided (see above). I see it has no entries for the APPEARANCE section. I doubt it, but I wonder if having those is why I don't have the problems you others have. It it might help, here is my APPEARANCE section. Maybe saka-key works better with this section in the .JSON.

saka_key_config_20191004.json.txt

i've never attached a file before here. if it didn't work, lmk. And, you'll have to change my filetype, since I couldn't paste a .JSON file. And, oh, my appearance is GREATLY modified, but you might like it.