LottaNZB

Remote front-end mode is not saved

Bug #290449 reported by Tim Düllmann
2
Affects Status Importance Assigned to Milestone
LottaNZB
Fix Released
Medium
LottaNZB Development Team
LottaNZB 0.4

Bug Description

Concerning the question I had last week (https://answers.launchpad.net/lottanzb/+question/48809), here is the bug report for this little bug:

I want to use LottaNzb in remote front-end mode by default. But every time I open it, it assumes I would like to use local front-end mode and asks me for the missing HellaNZB config file. After manually choosing remote connection, everything works the right way.

The problem seems to have something to do with saving preferences. Here is my config file after closing from remote front-end mode:

<lottaprefs><xmlrpc_port>8760</xmlrpc_port><remote>False</remote><window_height>350</window_height><xmlrpc_address>****</xmlrpc_address><window_width>700</window_width><sleep_time>1.0</sleep_time><prefs_revision>1</prefs_revision><frontend_mode>True</frontend_mode><hellanzb_launcher>/usr/bin/hellanzb.py</hellanzb_launcher><start_minimized>False</start_minimized><xmlrpc_password>****</xmlrpc_password></lottaprefs>

The connection details for remote mode are saved perfectly. I tried to change "<remote>False</remote>" into "<remote>True</remote>", which led to the intended way of operation, as LottaNZB went directly into remote front-end mode. Nontheless, after closing, the config file is saved wrong again, with "remote" set to "False".

Here is my logging output without manual changes to the config file:

INFO Starting LottaNZB 0.3.1 using Python 2.5.2.
ERROR Could not enter usage mode 'Local front-end mode'.
ERROR The specified HellaNZB configuration file doesn't exist.
INFO Connected to the HellaNZB daemon at ****:8760.
INFO Set usage mode to 'Remote front-end mode'.
INFO Left usage mode 'Remote front-end mode'.

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

Hi Tim,

thanks for filing the bug report. Thanks to your detailed description of the problem I could quickly locate the bug in LottaNZB's source code. It's an obvious mistake actually. The method that saves the remote connection settings contains the following lines of code:

        prefs.lotta.update({
            "remote" : False,
            "xmlrpc_address" : args[0],
            "xmlrpc_port" : args[1],
            "xmlrpc_password" : args[2]
        })

Obviously, "False" should be "True" here. The whole related code has been rewritten during the past months so that this bug shouldn't exist anymore in the upcoming 0.4 version of LottaNZB. I'm not sure if this bug is worth to be fixed in a separate 0.3.2 version though.

If you're feeling adventurous (since you're running a Gentoo machine, this is most probably the case ;-)), you can manually fix this bug by editing the file /usr/lib/python2.5/site-packages/lottanzb/modes.py.

Regards,
Severin

Changed in lottanzb:
assignee: nobody → lottanzb
importance: Undecided → Medium
milestone: none → 0.4
status: New → Triaged
status: Triaged → Fix Committed
Revision history for this message
Tim Düllmann (tim-duellmann) wrote :

Works great now, thanks! :)

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.
Subscribing...

Other bug subscribers

Remote bug watches

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