Ubuntu
lottanzb package

lottanzb won't start after upgrade from Ubuntu 9.10 to 10.4

Bug #577105 reported by Jim in Chicago
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LottaNZB
Fix Released
High
Severin H
LottaNZB 0.5.4
lottanzb (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: lottanzb

using lottanzb 0.5.3-1 on ubuntu 9.10 and all was well. After upgrading to 10.4, now it won't start. Tried re-installing it, but no joy. Python is 2.6.5-0ubuntu1, hellanzb is 0.13-6, unrar (nonfree) is 1:3.9.3-1, unrar-free is 1:0.0.1+cvs200711

When I start in terminal here's what I get:
11:50:06 lottanzb.core Starting LottaNZB 0.5.3...
Traceback (most recent call last):
  File "/usr/bin/lottanzb", line 7, in <module>
    app.run()
  File "/usr/lib/pymodules/python2.6/lottanzb/core.py", line 366, in run
    self.quit(self.main(sys.argv))
  File "/usr/lib/pymodules/python2.6/lottanzb/core.py", line 335, in main
    self.launch()
  File "/usr/lib/pymodules/python2.6/lottanzb/core.py", line 204, in launch
    self.mode_manager.load(on_failure=self.handle_mode_loading_error)
  File "/usr/lib/pymodules/python2.6/lottanzb/modes/__init__.py", line 133, in load
    mode = cls(self.config[self.config.active])
  File "/usr/lib/pymodules/python2.6/lottanzb/modes/standalone.py", line 72, in __init__
    self.hella_config.load()
  File "/usr/lib/pymodules/python2.6/lottanzb/hellaconfig.py", line 625, in load
    self.fix_common_problems()
  File "/usr/lib/pymodules/python2.6/lottanzb/hellaconfig.py", line 651, in fix_common_problems
    self._ensure_drop_unrar_free()
  File "/usr/lib/pymodules/python2.6/lottanzb/hellaconfig.py", line 679, in _ensure_drop_unrar_free
    nonfree_unrar_cmd = find_executable("unrar")
NameError: global name 'find_executable' is not defined

Anyone have an idea what's going on here? I'm lost.
Thanks,

Severin H (severinh)
Changed in lottanzb (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Severin Heiniger (lantash)
status: Fix Committed → Triaged
assignee: Severin Heiniger (lantash) → nobody
Changed in lottanzb:
status: New → Fix Committed
Changed in lottanzb (Ubuntu):
importance: High → Medium
Changed in lottanzb:
importance: Undecided → High
assignee: nobody → Severin Heiniger (lantash)
milestone: none → 0.5.4
Revision history for this message
Severin H (severinh) wrote :

Hi Jim,

thanks alot for reporting this bug! It has been fixed in latest development code of the LottaNZB 0.5 series and will be released as part of LottaNZB 0.5.4. However, I cannot provide you with a concrete date.

The problem happens in code that replaces "unrar-free" with "unrar" in the HellaNZB configuration file, because "unrar-free" is unable to handle a major part of the archives found on the Usenet. You should be able to work around the bug by manually making this replacement. I'm not exactly sure what HellaNZB configuration file triggers the error, so you should check the following files (if they exist):

~/.config/lottanzb/hellanzb.conf
~/.lottanzb/hellanzb.conf
/etc/hellanzb.conf (unlikely to have caused the problem)

Make the hidden directory in your home directory ~ visible using Alt-H. In such a file, replace

Hellanzb.UNRAR_CMD = "/usr/bin/unrar-free"
with
Hellanzb.UNRAR_CMD = "/usr/bin/unrar"

and launch LottaNZB again. Hope this helps.

Revision history for this message
Jim in Chicago (jbcady) wrote :

Thanks for the quick fix! <G>

It was in the ~/.config/lottanzb/hellanzb.conf file, and that did the trick.

Downloaded a test file and it's working like a champ. My /home/user/.lottanzb dir seems to have disappeared, but it doesn't seem to need it.

thanks again.

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

You're welcome! It's good to hear that you could solve the problem.
/home/user/.lottanzb was used in previous versions of LottaNZB and might still have existed.

Severin H (severinh)
Changed in lottanzb:
status: Fix Committed → Fix Released
Severin H (severinh)
Changed in lottanzb (Ubuntu):
status: Triaged → 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.