Thanks alot for your in-depth explanation of the issue. It allowed me to
reproduce it and track it down.
The duplicate SessionNotSpecifiedError actually indicates that a
SessionNotSpecifiedError has been raised (which is perfectly fine), but
there was an unhandled exception in one of the handlers dealing with
this error (e.g. responsible for opening the 'Start Downloading'
dialog). For some reason, the SessionNotSpecifiedError was displayed a
second time instead of the actual error, making it impossible to know
what actually went wrong. This has been fixed in the latest code. As
soon as new daily builds have been released, such errors will be
displayed properly on the console, allowing us to fix the bug for good.
As for the unresponsive window occurring after having connected
successfully to SABnzbd: Even though I haven't experienced it for some
time, it will still require some investigation.
** Changed in: lottanzb
Status: Confirmed => In Progress
--
Main window insensitive upon startup
https://bugs.launchpad.net/bugs/616508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
