Sidewise panel won't show up when I click its lightbulb icon.

[Wizek]

It wasn't showing up for some time now (1-2 days) but I wasn't thinking much of it: maybe a Chrome restart would solve it. It didn't. Also tried to disable and re-enable Sidewise to no avail.

Inspecting the background page revealed these uncaught exceptions:

Error in event handler for 'windows.onFocusChanged': Cannot call method 'isDetecting' of undefined TypeError: Cannot call method 'isDetecting' of undefined
    at onWindowFocusChanged (chrome-extension://biiammgklaefagjclmnlialkmaemifgo/js/bg/events/window-events.js:7:50)
    at chrome.Event.dispatchToListener (event_bindings:387:21)
    at chrome.Event.dispatch_ (event_bindings:373:27)
    at dispatchArgs (event_bindings:249:22)
    at Object.chromeHidden.Event.dispatchEvent (event_bindings:257:7) logging.js:3
Error in event handler for 'windows.onFocusChanged': Cannot call method 'isDetecting' of undefined TypeError: Cannot call method 'isDetecting' of undefined
    at onWindowFocusChanged (chrome-extension://biiammgklaefagjclmnlialkmaemifgo/js/bg/events/window-events.js:7:50)
    at chrome.Event.dispatchToListener (event_bindings:387:21)
    at chrome.Event.dispatch_ (event_bindings:373:27)
    at dispatchArgs (event_bindings:249:22)
    at Object.chromeHidden.Event.dispatchEvent (event_bindings:257:7) logging.js:3

The referenced source code appeared to be minified, so I didn't look deeper than that.

Versions:

• Sidewise 2013.1.11.0
• Chrome 24.0.1312.52
• Ubuntu 12.10

Any ideas as to what might have went wrong?

[joelpt]

I usually see that kind of debug when there is a syntax error in one of the background Javascript files, suggesting that the background page essentially failed to load correctly in its entirety.

Try reinstalling Sidewise - does that fix it? If so, it's possible that the files somehow got corrupted on your system.

[Wizek]

Reinstalling made the panel shows up, but it seems the session was corrupt, not the source files.

Two clues that lead me to believe this:

1. I did a diff on the source folder (biiammgklaefagjclmnlialkmaemifgo/2013.1.11.0_0) of the one I removed and the one I reinstalled and Meld tells me they are identical.
2. I exported my session data before reinstalling, but sw won't import it back properly despite saying the operation was successful and restarting itself. Sw settings seem to come back as I left them, but the tree data lacks all (500+) of my hibernated tabs.

The export is 930KB of size, so it seems the data is in there somewhere.

So, my next question is: How do I find+correct corrupt (as in syntactically corrupt, or structurally corrupt (e.g. there is a "tree_data" key whereas sw looks for a "treedata" key)) parts of that ~1MB json file?

[joelpt]

Can you ship me that export to [email protected]?

[Wizek]

Well, if there is another way, I'd rather not as it might contain some personal information. I hope you understand.

Could you tell me what checks or operations you would perform so that I may execute them based on your instructions?

[Wizek]

It is happening again.

The last thing I remember doing that might have caused it: I closed sw's window by right-clicking the it's unity launcher icon (the second chrome icon (also, it's a simple chrome icon, and not a light-bulb one)) and selected quit. It seems to be the exact same issue: nothing happens when I click the light-bulb, restarting chrome or (dis|en)abling the extension doesn't help, and the background page spews exceptions similar to the one I posted above.