Comment 5 for bug 616508

Did some more testing, found out that it makes a difference whether or not I delete the ~/.sabnzbd dir prior to launching lotta.

Starting without sab running, and without a pre-existing lotta config:

====

* with the usual ~/.sabnzbd in place: SessionNotSpecifiedError traceback appears twice, lotta never displays the session selection dialog and always behaves as seen in the screenshot attached to this bug.

* continuing from the above, setting "active = local" and trying to start lotta again the SessionNotSpecifiedError is gone, the traceback known from bug #608209 appears (twice!) and the app window is in the same zombie condition as before.

====

* now when I remove ~/.sabnzbd and ~/.config/lottanzb/* to clean up, and start lotta again a session selection window ("Start Downloading") appears in front of the zombie window and the app appears functional. The command line shows the SessionNotSpecifiedError traceback - but this time only once. In case I cancel that dialog the app exits cleanly but it has about a 50/50 chance of crashing with 'lottanzb: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.' the next time it's started.

* continuing from the above, If I insert "active = local" and start lotta again it appears to work, starts a sab instance; the gui is responsive and warns in bright orange that a server is needed.

====

Quite puzzling how having the sab dir in place influences the process and makes tracebacks appear twice, especially since I guess that lotta didn't try reading the ini yet (since that would have caused a traceback of its own with my normal sab config)...

The SessionNotSpecifiedError traceback is probably best to hide away, same for the one that appears if no server is defined in sab yet.