[Jiaz]

@userx-bx
java -jar JDownloader.jar (when you are inside the JD folder)
or
java -jar /pathToJD/JDownloader.jar

You mean a 3rd button close after downloads?

[raztoki]

go to the jd path or provide full path when you give the -jar parameter
so java -Xmx512m -jar JDownloader.jar
or java -Xmx512m -jar /user/username/.jd/JDownloader.jar ?

[Super JD]

Originally Posted by Jiaz

Do you close JD normally or use shutdown of Windows? and let it kill JD?
Waiting for the dialogs, thanks for the feedback

I always close JD by clicking on the "Exit" icon on my toolbar. (The only exception to this may be if there is a Windows crash and JD is running. Such a crash hasn't happened to me in a very, very long time, and JD may not have been running when it did happen.) I can't recall if the "Exit" icon is on the toolbar by default, or whether I added it via Toolbar Manager. Either way, I believe that closing JD in this way is the same as > File > Exit.

[Jiaz]

Then JD should not show up any dialog as it installs Updates on shutdown by default. Did you reset all your updater settings in advanced settings (maybe you customized them?)

[Super JD]

Originally Posted by Jiaz

Then JD should not show up any dialog as it installs Updates on shutdown by default. Did you reset all your updater settings in advanced settings (maybe you customized them?)

I haven't reset my updater settings.

Please refer to the the first page of this thread (and my exchanges with you and with coalado) to see what my update preferences and settings have been, with the aim to not be prompted by updater dialogs. I began this thread in the first place because updates were not working as I prefer/as imagined, given my settings.

Please refer in particular to post #23 for a look at my most recent settings:

https://board.jdownloader.org/showpo...1&postcount=23

Please also take note of post #47, where I previously alerted to the very same updater dialog which I have been receiving in the last two days:

https://board.jdownloader.org/showpo...4&postcount=47

The problem has clearly returned.

The only changes of any kind that I've made to JD are detailed in my other recent thread:

https://board.jdownloader.org/showthread.php?t=63700

Thanks.

[Jiaz]

Please reset the settings, because we found many bugs and fixed them and by default JDownloader does not show any dialog/ask...it will install on shutdown. I ask you to reset because we fixed many bugs and I want to know if it works fine with default settings. Then you can customize them and see if it still fails
The Problem -> we did not change things in update for long long time. So please reset and see if it works. I can also offer Teamviewer for faster solution/help

Please provide a screenshot of your updater settings (in advanced settings, search for update). Maybe I can reproduce by setting the same settings as you have

[Super JD]

Here is the requested screenshot:









I hope this is helpful in avoiding a reset of the update settings, especially if any of the defaults (re)enable any update notificatons/dialogs. I continue to seek JD to be as silent as possible while still updating automatically in the background.

I'll await your thoughts on my settings, above, before I proceed with a reset.

Many thanks, as always.

[Super JD]

I continue to await a comment on the requested screenshot, as provided, above.

I likewise continue to receive update dialogs on startup of JD, including the aforementioned "You already have the latest version" dialog.

I began this thread over 2 months ago, seeking help with getting rid of the myriad update dialogs I receive when using JD.

You have provided guidance on what I should check and uncheck in Advanced Settings, and I believe I have followed those instructions, and yet these dialogs and prompts continue.

I have reverted to previous backups of JD and that also hasn't helped.

Again, you have my advanced settings to see, above. Is there anything there that I have set incorrectly? Is there anything in my settings that is causing these dialogs? If not, what is causing it and why is it taking more than 2 months to solve this, please?

As I've noted in this thread, the problem seems to be addressed, at times, upon some changes from your side, however the annoying behaviour has now returned several times.

The only changes I've made are ones you've suggested.

Again, I like JD, but my workflow requires it to be a silent partner. In the last two months it is seeking far too much of my attention and my patience with its dialog-demands is wearing thin...

[Jiaz]

Waiting for coalado to return from his holidays. I've create a ticket

[oEFLKQzikCqw]

Auch hier führte JD nach dem Start ein Update durch um dann zu melden, dass bereits die aktuelle Version benutzt wird.

15.05.15 09.46.55to08.05.15 21.40.48 jdlog://7763709980341/

[Jiaz]

Coalado wird sich das anschauen

[Super JD]

Originally Posted by Jiaz

Coalado wird sich das anschauen

Danke.

[coalado]

Bin wieder da. Jetzt gehts los. Sorry fürs Warten.

[coalado]

I cannot reproduce the problem :( Can you reproduce it, and show it to me via teamviewer?

[Super JD]

Originally Posted by coalado

Bin wieder da. Jetzt gehts los. Sorry fürs Warten.

Macht nichts! Ich hoffe der Urlaub war gut.

Originally Posted by coalado

I cannot reproduce the problem :( Can you reproduce it, and show it to me via teamviewer?

Unfortunately I cannot reproduce the problem - at least not at will / on-demand. You see the problem isn't consistent from day-to-day. One day it occurs, the next it doesn't. For a while it was happening on a once-per-day basis, and always the first time I launched JD.

On 19th May the "you already have the latest version" dialog opened; today, the 20th of May, it did not.

It may be helpful to know if this is currently a daily event for the other user who recently remarked the same problem, or if it is likewise sporadic.

That user, I should note, seems to be experiencing this problem in a similar manner to mine. Previously, it appears, the problem went away and returned along with JD updates. I lack your insight and access, yet it would seem that it is possible that something in your updates is indirectly causing this, as much as it is also - at times - removing it.

I have posted a screenshot of the dialog in this thread (Post #47); sadly this is the closest to reproducing the problem that I can muster.

Many thanks for looking at this upon your return from time off.

[coalado]

Super JD: Maybe you can post the logs of the dates when the problem occurred?
I only have the log of oEFLKQzikCqw, which does not show the dialog :/

[Super JD]

I don't have any logs. Will it work to create a log immediately after the dialog appears next?

[coalado]

Sure. JD usually writes the logs of the last few days.
Just use Menu->Create a log and choose the correct timeframe

[Super JD]

Thanks; I'll follow up.

[oEFLKQzikCqw]

Originally Posted by coalado

I only have the log of oEFLKQzikCqw, which does not show the dialog :/

Warum denn nicht? Das Log ist mit Sicherheit aus dem richtigen Zeitraum.

[Super JD]

I started JD moments ago and the dreaded update dialog launched again. Here is the requested log:

21.05.15 20.25.53to21.05.15 20.26.55 jdlog://0846909980341/

It is noteworthy that normally the update dialog occurs on the first JD start on a given day; in this case it was my second launch of JD today.

I hope my log helps to point to the problem.

Thank you.

[Jiaz]

Coalado is not in today (he is moving flat). Will forward him your log.

[Super JD]

Busy man, is coalado, as I'm sure are all of you at JD.

Some of JDownloader's quirky behaviour can be frustrating, and I've perhaps been lucky to not have had any reason to post here during the pre-JD2 days, yet JD2 still works remarkably well to the end that it's meant to serve. It remains, notably, a free utility, and the ongoing support from all of you isn't common. Larger players who serve people's search, webmail, and social media "needs" could learn from your support skills; whereas their users should demand more or move on.

Thanks again, Jiaz.

[Jiaz]

He is moving into a new place and because of that not in office today. Next week should be available again. And we will do our best to improve the user experience for JDownloader 2 as best as we can! It only needs some time because of forum/email latency and not always easy to reproduce/find/fix a bug/feature.
Thanks again for your understanding! and cooperation on this!

[Super JD]

You're welcome. I can't imagine how complicated it is, maintaining such a rapidly-changing landscape, as the one in which JD operates. That this utility is so customisable only complicates matters, I would think. Thanks again; we'll look at solutions next week.

[Jiaz]

Wish you a nice weekend

[Super JD]

Thank you; likewise.

Danke ebenfalls.

[oEFLKQzikCqw]

Originally Posted by oEFLKQzikCqw

Auch hier führte JD nach dem Start ein Update durch um dann zu melden, dass bereits die aktuelle Version benutzt wird.

15.05.15 09.46.55to08.05.15 21.40.48 jdlog://7763709980341/

Heute wieder das gleiche:

25.05.15 17.40.36to25.05.15 18.22.59 jdlog://1389019980341/

[Super JD]

Und auch bei mir.

Again, on my end too.

Here is another log:

26.05.15 14.43.49to26.05.15 14.45.15 jdlog://0852119980341/

Please also refer to my previous log, above.

The "you already have the latest version" dialog is always preceded by a window that indicates "extracting update package". Perhaps this helps.

Perhaps others who are having the same problem could post here. Are oEFLKQzikCqw and I the only ones?

Please help.

Thanks.

[Jiaz]

Coalado is back again and he will check/fix this asap

[Super JD]

... and again...

Here's the latest log:

27.05.15 13.03.34to27.05.15 13.04.43 jdlog://5565119980341/

Thanks.

[coalado]

Thanks for your logs.
I finally can reproduce the problem.

The JD Launcher tries to launch JDownloader. if this is not finished within 15 seconds JD thinks that there is a problem and tries to run an update. Since JDownloader is not launched, a fallback update controller does this job. It thinks that this is a kind of emergency and shows the dialog.

This happens for Super JD and oEFLKQzikCqw. However I do not know yet why the launching process takes more than 15 seconds for you (it's ~2-3 for me).

Anyway..I know the cause now, and will find a fix asap. Thanks for your patience.

[Super JD]

Good detective work, coalado.

I hope it isn't too difficult to reach a solution.

Thanks for your efforts.

[oEFLKQzikCqw]

JD2 liegt hier auf einer relativ lahmen 2,5"-USB3-Festplatte, die darüber hinaus auch noch verschlüsselt ist und häufig wird JD2 zusammen mit anderen Programmen gestartet.

[Jiaz]

Das Update von Coalado ist bereits live, sollte also jetzt keine Probleme mehr machen?!

[Super JD]

Originally Posted by Jiaz

Das Update von Coalado ist bereits live, sollte also jetzt keine Probleme mehr machen?!

Mal sehen... Ich sehe die Sache im Moment schon gut.

So far, so good. Up until now the update dialog didn't necessarily launch every time, and previously the problem was addressed/went away only to later return. For now, there was no update dialog on my first start of JD today.

I'm more optimistic this time since it seems that coalado has pinpointed a specific cause for the behaviour.

Unlike oEFLKQzikCqw, as noted here...

Originally Posted by oEFLKQzikCqw

Jhäufig wird JD2 zusammen mit anderen Programmen gestartet.

...I don't usually start JD simultaneously with other applications.

Thanks for the work, the update, and for keeping us posted. I'll return with feedback, one way or another.

[coalado]

didn't necessarily launch every time,

It happened only if the JDownloader Startup Process took more than 15 seconds.
Today, this timeframe is 90 seconds. As long as your JD does not take more than 90 seconds to start, everything will be fine.

[Super JD]

The update problem dialog hasn't returned since Jiaz's post from 28th May in which he notified of your update, coalado.

I am very pleased that this appears to be fixed and am hopeful that the problem won't return.

I am curious: Did your update address the length of JD startup time?

I am also wondering: Any idea about why my JD startup (apparently) took longer than intended? Again, I am not launching JD simlutaneously with other processes and am using it on a fast machine.

Many thanks for your help.

[raztoki]

From what I understand there was no addressing startup time since it seems to be a system specific issue. Only change was to increase the time before the failover controller takes over by 60 seconds.

[oEFLKQzikCqw]

Auch hier ist es bisher nicht wieder aufgetreten.