LottaNZB does not start after finishing configuration

Bug #213509 reported by Sander Tuit
2
Affects Status Importance Assigned to Milestone
LottaNZB
Fix Released
Low
LottaNZB Development Team

Bug Description

Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/lottanzb/firstrun.py", line 101, in handlePageChange
    serverInfo.id = _("Default Server")
AttributeError: 'dict' object has no attribute 'id'
INFO The preferences were correctly written.
INFO Closed the configuration assistant.
INFO The first-run configuration hasn't been completed. Shutting down LottaNZB.

Affects 0.2 and trunk

Severin H (severinh)
Changed in lottanzb:
assignee: nobody → lantash
importance: Undecided → Low
milestone: none → 0.2.1
status: New → Fix Committed
Revision history for this message
Andrew Williams (nikdoof) wrote :

Following diff is a start to fixing this, but it seems to be a more underlying issue with how the Hella configuration is saved.

=== modified file 'lottanzb/firstrun.py'
--- lottanzb/firstrun.py 2008-04-07 07:57:48 +0000
+++ lottanzb/firstrun.py 2008-04-07 21:32:11 +0000
@@ -98,7 +98,7 @@
                     server = Prefs.hella.servers[0]
                     server.setFromDict(serverInfo)
                 else:
- serverInfo.id = _("Default Server")
+ serverInfo["id"] = _("Default Server")
                     Prefs.hella.addServer(serverInfo)

                 if not Prefs.hella.loaded:

=== modified file 'lottanzb/prefs.py'
--- lottanzb/prefs.py 2008-04-07 21:03:46 +0000
+++ lottanzb/prefs.py 2008-04-07 21:36:43 +0000
@@ -92,6 +92,8 @@
                 if property in self:
                     value = self[property]

+ if value is None:
+ value = ""
                     if "transform" in args:
                         value = args["transform"](value)

Severin H (severinh)
Changed in lottanzb:
assignee: lantash → lottanzb
status: Fix Committed → In Progress
Changed in lottanzb:
status: In Progress → Fix Committed
Severin H (severinh)
Changed in lottanzb:
milestone: 0.2.1 → 0.3
Revision history for this message
VuDu (vudu-curse) wrote :

I have the same problem using lottanzb as a stand-alone client, using it as a front-end works ok.

 $ lottanzb
INFO Starting LottaNZB 0.2 using Python 2.5.2.
INFO The LottaNZB configuration could not be loaded. Starting configuration assistant.
INFO Created the LottaNZB directory /home/vudu/.lottanzb/.

*** clicking "Forward" on the "Server Information" window ***

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/lottanzb-0.2-py2.5.egg/lottanzb/firstrun.py", line 101, in handlePageChange
    serverInfo.id = _("Default Server")
AttributeError: 'dict' object has no attribute 'id'

*** clicking "Apply" on the "Complete!" window ***

INFO The preferences were correctly written.
INFO Closed the configuration assistant.
INFO The first-run configuration hasn't been completed. Shutting down LottaNZB.

Revision history for this message
VuDu (vudu-curse) wrote :

I forgot to say that if I run lottanzb again it will show the config window, so there's no way to use it as a stand-alone client.

I'm using arch linux with:

 $ hellanzb.py
hellanzb v0.13 (config = /home/vudu/.config/hellanzb.conf)

and

$ lottanzb
INFO Starting LottaNZB 0.2 using Python 2.5.2.

Revision history for this message
Severin H (severinh) wrote :

Hi VuDu,

as you can see at the top of the page, we already triaged and fixed this bug, but we haven't released a new version of LottaNZB containing the fix so far. LottaNZB 0.3 is (hopefully) going to be released in a few days. If you don't feel like waiting and can't live without the stand-alone mode, you might want to get the latest code and install it.

bzr branch lp:lottanzb

Please uninstall older LottaNZB versions first (most probably in /usr/lib/python2.5/site-packages/lottanzb*). Don't hesitate to report bugs if you encounter any. We definitely need people to test the new code and provide feedback before we release this new major version.

Thanks in advance!

Severin H (severinh)
Changed in lottanzb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.