Some time ago I upgraded 4.7.4 to 4.8, last weekend I did that again after a re-install of my OS and now the current version is 4.8.2
I use Mint 12 KDE in the 64 bits version.
The strange effect I have is this:
I use an index program to see what is available in newsgroups. When I see something I like I click a button on that page which opens my standard browser (Google Chrome) on the webpage from a search-engine. So far - so good.
When I click to download the corresponding NZB-file the screen starts to flicker and I am downloading 32 times the same NZB file. (An NZB file is a file which says which packages to download) After nr. 32 the downloading starts and nothing happens.
When I open the same webpage in Firefox and start downloading the same NZB file (it happens with all NZB files btw) things go well. The NZB file is automatically opened with sabnzbd+ and the download procedure starts.

With Chrome the same thing as in Firefox happened when I still used KDE 4.7.4, with 4.8.x it changed.
Now this can be because something is not programmed completely right in Chrome, it could also be something in 4.8.x

Does anybody know what could cause this strange behavior? I sure would like the program to behave again like it did.
Thanks.

Can you check file associations for NZB files?

einar wrote:Can you check file associations for NZB files?

I just did and the only association it has is sabnzbd+, just as I want to. In the lower panel I can see it starts this program, but somehow it wants to download the file not once but many times.

Is anything relevant output to the console if you run Chrome in a terminal when this happens?

This is what I get when I start Chrome for a terminal:

$ google-chrome
Gtk-Message: Failed to load module "canberra-gtk-module"
[12508:12508:6147314282:ERROR:browser_main_loop.cc(128)] GTK theme error: Theme directory scalable/animations/small/16x16 of theme Mint-KDE has no size field

[12508:12508:6147314391:ERROR:browser_main_loop.cc(128)] GTK theme error: Theme directory scalable/animations/small/22x22 of theme Mint-KDE has no size field

Gtk-Message: Failed to load module "canberra-gtk-module"
Moonlight: 3.99.0.3
Moonlight: Attempting to load libmoonloaderxpi


After trying the download, I see this added:

QFile::remove: Empty or null file name
QFile::remove: Empty or null file name

That's all. Does this help you in anyway? Sure hope so.
Thank you for your help.

Unfortunately that does not provide any detail linked to the cause of the problem. Does it occur under a new user account?

I made a new user, setup the programs I use for downloading with my accounts and the same happened. Exactly the same. Something has been changed between KDE 4.7.4 and 4.8.x
If only I knew what it was then I could change it again.
KDE 4.7.4 was perfect. Okay, I know what you are going to ask me now: why did I change to 4.8? Right?
No idea, probably just because it is there.

If it works in firefox and not in chrome, the latter is to blame. There seem to bee many problems with the combination of chrome and sabnzbd+.
My guess is you pulled in a new chrome version when updating to KDE SC 4.8 (note: I guess)

Can you try with an older version of chrome or is that not possible?

montfras wrote:If it works in firefox and not in chrome, the latter is to blame. There seem to bee many problems with the combination of chrome and sabnzbd+.
My guess is you pulled in a new chrome version when updating to KDE SC 4.8 (note: I guess)

Can you try with an older version of chrome or is that not possible?

I doubt if it is Chrome. I updated KDE before, some months ago and it was not good at that time. Afterwards I went back to KDE 4.7 and things were Okay again, with a newer version of Chrome. Now I updated KDE and things are not good. So my guess it is KDE.

Can you reproduce this behaviour with other file types such as ODT files?

bcooksley wrote:Can you reproduce this behaviour with other file types such as ODT files?

No, it is just with the nzb files which open sabnzbd+, which will open (when not yet done already) a new tab in Chrome to show me what it is doing.
The screen starts to flicker 32 times and in my download folder I see 32 times the same nzb file, only with different names because it makes copies of the original one.
Chrome is my default browser so it is Chrome which is opened by sabnzbd+. When I get the nzb file with Firefox and start it, sabnzbd+ is started and opens a tab in Chrome and things are fine.
Once again to make absolutely sure what I have done in the past already:
with KDE 4.7.4 and Chrome it worked fine. I have updated Chrome several times and it still worked.
with KDE 4.8 and Chrome it does not work the way I want it.
going back to KDE 4.7.4 but still with the latest version of Chrome it works.
Returning to KDE 4.8.2 it does not work.
Now I have installed Kubuntu 12.04 (with KDE 4.8.2) and it does not work.

Sorry for that very late response but I have been abroad for several days.

Any one who can help me?

I am mystified. It is almost as if some form of loop between Chrome and KDE occurs here. As I do not understand the exact process for using NZB files, it is a little hard for me to try to reproduce unfortunately.

One thing I would double check is that the associations and preferences inside Chrome, KDE and your NZB handling application are all correct.

New situation. It works, but in a different way.
It used to be that when downloading the nzb file Sabnzbd+ was automatically started. Sabnzbd+ then opens a tab in Chrome (default browser) to show its interface. At this moment opening an nzb file does not open Sabnzbd+ but instead downloads the file again.

I found that Sabnzbd+ can also work in a different way: the nzb file is downloaded into my Downloads folder. This folder is scanned by Sabnzbd+ to see if there are any new nzb files which need to taken care of.
I cleared the auto-opening settings in Chrome, download the nzb file into the Downloads folder and 1 second later Sabnzbd+ knows there is a new file and takes care of it. One little downside: since Sabnzbd+ is not automaically started now, I have to start it manually.

Thanks for all the help you gave me. It is still strange there is a difference between KDE 4.7.4 and 4.8.x.