Double click on a .nzb file won't add it into the list if LottaNZB is started

Bug #719483 reported by Antoine Dessaigne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LottaNZB
Confirmed
High
Severin H

Bug Description

Hi,

When LottaNZB is running, double-clicking on a .NZB file won't add it into the list.

Step to reproduce:
- Launch LottaNZB
- Double-click on a .NZB file

Result:
- Nothing happen

Expected Result:
- The NZB is added to the queue.

Regards,

OS: Ubuntu 10.10
LottaNZB: 0.6 (PPA version)

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

Thanks for taking the time to report this bug. On my Ubuntu 10.10 machine, it works as expected. So it would be great to figure out what is different on your machine.

I assume that the NZB files are properly associated with LottaNZB on your machine, i.e. they have an icon with a green arrow and default to be opened with "LottaNZB Usenet Downloader". Next, it would be interesting to know what happens when you add such an NZB file to the already running LottaNZB using the terminal, i.e. by running "lottanzb some_file.nzb". Also, you might want to check if there's anything unusual in Help -> Message Log after you've unsuccessfully attempted to add an NZB file. Note that by default, duplicates are not added to the download queue. If the NZB file you clicked on has been previously added to LottaNZB, nothing will happen when clicking on it again.

Changed in lottanzb:
status: New → Incomplete
Revision history for this message
Antoine Dessaigne (antoine-dessaigne) wrote :

So yes it's associated with LottaNZB. Also it's 2 different .NZB files

When using the command line I have the following error message in the console (translated by me):
The request "addlocalfile" to localhost:8080 failed: the file does not exist.

This message also appears in the Message Log.

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

Sorry for not getting back to you earlier. The error message means that LottaNZB actually transmitted the name of the NZB file to be added to SABnzbd, but according to SABnzbd, the file doesn't exist.

I noticed that SABnzbd doesn't seem to provide any helpful error message (like the file name that actually arrived) and no problems seem to be caused by characters like 'é' and '&' in the file name. Thus, I currently don't know any solution to this problem.

Revision history for this message
Antoine Dessaigne (antoine-dessaigne) wrote :

I've look and whilst my file name doesn't contain any special character, the path contains 2 'é'. You've probably right.

I think there are 2 options:
- either the file name with special chars aren't provided the way SABnzbd expects it, therefore it's a bug from the LottaNZB side
- either SABnzbd doesn't handle path with special chars therefore maybe it is possible to forward this bug to them.

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

Finally! The problem doesn't have anything to do with what kind of name the NZB file has or in what folder it is located. Instead, adding a download by clicking on the NZB file or using the command line *always* fails when LottaNZB is already running at that time. So there must be something wrong with the way how the short-lived LottaNZB instance talks to the already-running LottaNZB instance (which is done using DBus).

Thanks alot again for reporting this bug. It's definitely something that will be need to fixed in the next version of LottaNZB.

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

I should have read your problem description more carefully. :-) You explicitly stated that the problem occurs "if LottaNZB is started". This could have saved us from a lot of trouble. Sorry.

Changed in lottanzb:
status: Incomplete → Confirmed
importance: Undecided → High
milestone: none → 0.6.1
assignee: nobody → Severin Heiniger (lantash)
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.