nzb downloads in chromium are corrupt

nixIT · 2015-09-17 21:29:24

Hello all,

Did a fresh install of Arch64/Xfce over the weekend after a system upgrade. I am finally getting my system back up and running with all apps installed.

I installed Chromium and Midori (via same pacman -S command) as my browsers, set up nzbget as my nzb downloader and sonarr as my ... sonarr.

When I manually downloaded (in Chromium) a nzg file from an indexer, I tried multiple, when nzb tries to import that file from the watch folder I keep getting an error:

Could not add collection <filename>.nzb to queue
Error parsing nzb-file <filename>.nzb

I did a pacman -Syyu to update system, and retested, same thing.

At first I thought it was the permissions of my folders, since I was using the same data drive as my previous install, so I stopped nzbget, reset folder/file privs, and started the service. Same thing.

I then manually downloaded the same nzb file using Midori, into the same watch folder and viola, nzbget added the file and "bobs your uncle" it worked.

Is anyone else experiencing this? could it be a bug in Chromium, or is it a permissions issue?

Thanx in advance.

--nixIT

nixpunk · 2015-09-17 21:48:48

Have you actually compared an .nzb file from Chromium with one that works? I'm pretty sure that an .nzb file uses XML markup, so comparing one that works with one that doesn't might be useful in troubleshooting.

nixIT · 2015-09-17 22:04:12

good idea, didn't even think of that. I'll check it out and report back.

nixIT · 2015-09-17 23:12:41

performed a diff on the two files and there is no difference.

I then copied both the files into the watch folder. The file downloaded with chromium could not be added and the one from midori can.

any ideas?

thanx!

-nixIT

nixpunk · 2015-09-21 14:28:44

Did you try downloading a different file and/or clear the cache just to verify you are downloading a fresh copy of the same file? At this point I would consider creating a new issue on the Chromium bug tracker. Further, you can compute checksums and compare the files that way (.e.g. md5sum), or use something like cmp to compare them, bit-wise.

nixIT · 2015-09-21 14:39:27

@nixpunk

I did try different files, several in fact with the same results. I know it's a chromium issue only because sonarr and nzbget auto downloads them automatically and correctly, and Midori downloads the nzb's correctly too.

I'm going to try and test this some more this week and post on the chromium bug tracker.

Thanx.

-nixIT

R00KIE · 2015-09-21 16:22:54

I would check line terminations, the cr/lf stuff (dos vs unix line termination). The output of file should be enough to tell both formats apart.

Arch Linux

#1 2015-09-17 21:29:24

nzb downloads in chromium are corrupt

#2 2015-09-17 21:48:48

Re: nzb downloads in chromium are corrupt

#3 2015-09-17 22:04:12

Re: nzb downloads in chromium are corrupt

#4 2015-09-17 23:12:41

Re: nzb downloads in chromium are corrupt

#5 2015-09-21 14:28:44

Re: nzb downloads in chromium are corrupt

#6 2015-09-21 14:39:27

Re: nzb downloads in chromium are corrupt

#7 2015-09-21 16:22:54

Re: nzb downloads in chromium are corrupt

Board footer