Package Details: jdownloader2 latest-10

Git Clone URL: https://aur.archlinux.org/jdownloader2.git (read-only)
Package Base: jdownloader2
Description: Download manager, written in Java, for one-click hosting sites like Rapidshare and Megaupload. Uses its own updater.
Upstream URL: http://jdownloader.org/
Keywords: download hoster internet jdownloader manager oneclick
Licenses: GPL
Conflicts: jdownloader
Replaces: jdownloader
Submitter: None
Maintainer: Holodoc
Last Packager: Holodoc
Votes: 286
Popularity: 9.082134
First Submitted: 2011-09-07 23:08
Last Updated: 2016-07-03 21:34

Latest Comments

X-Tornado commented on 2017-02-22 06:42

@Holodoc
Ok thanks! I will wait for the update.

Holodoc commented on 2017-02-21 23:42

@X-Tornado
Thanks for your reply. Its because of an internal switch not to restart the jdownloader automatically, becuase this should be done by systemd.

But I agree that this is very bad. I think I found a better solution in the last 2 days, but I have to test them a little bit more.
There will be an update soon (with this I mean during next week)

@raudi
Okay. I will try to reproduce your problem right after the issue from X-Tornado.

X-Tornado commented on 2017-02-15 09:49

I'm the only one getting an "update loop" when using the service?

It's not something new, I had this issue for a long time. Basically when there is an update for JDownloader that requires replacing the jar it gets stuck updating infinitely. Here is a video showing what happens:

https://www.youtube.com/watch?v=_7Rph6aitac

It's something related to the way the service works or something like that, because if I run it manually , using the jdownloader user, the update works.
Here a video of me updating manually and then starting the service again:

https://youtu.be/1JsQEY1YRCQ

So basically I have been fixing it manually from time to time but clearly that's not a solution.

raudi commented on 2017-02-06 20:41

@Holodoc
I am using it as a system service. I also ran it in the terminal to configure My Jdownloader.
But at least for me there were some permission issues.

Holodoc commented on 2016-11-08 23:52

@raudi:
Thanks for your note.
What did you meant with "headless-service"? The service itself runs as systemservice (but of cause as user "jdownloader") To be able to access via MyJDownloader it has to be configured. That's why during the installation it says: Please run JDownlaoderHeadless multiple times to configure it.

So right after you installed it with pacman there are two ways how to use it:
1) as system service: Please login as root and start JDownloaderHeadless. It will automatically switch to JDownloader user and start jdownlaoder. Please retry this command until you were abe to configre your login credentials for MyJdownloader. Afterwards you could abort the process and start the systemservice "systemctrl start jdownloader"

2) as user: Just open a terminal and start "JDownloaderHeadless". You don't have to be in JDownloader group. As in the method before: Rerun this command until it is started and configured. Please notice that the process is been killed if you request a restart over MyJdownloader (updating JDownloader).

If anything is unclear, feel free to ask

raudi commented on 2016-11-07 17:25

I was wondering why the headless service wouldn't work for me.
It seems as if I needed to add my user to the jdownloader group with

sudo gpasswd -a YourUserName jdownloader

and log in again before the first run. At least it is working for me right now.

Holodoc commented on 2016-10-24 23:20

@rpodgorny: i am not sure what's your proposal. Are you referencing baranators post?
Jdownloader download is now placed in another subscript..

rpodgorny commented on 2016-10-24 20:19

what's the purpose of the JDownloaderHeadless step? can't it be done during the build step? thanks...

DEUS commented on 2016-10-14 08:35

You may experience trouble after upgrading to Gnome 2.22, in my case it helped to disable the tray icon in settings. temporary use a different desktop and deactivate it or ssh with X from another machine with another or pre 2.22 desktop environment.
After some time and more trouble with other tools (xrandr and gparted), the issue is related to Wayland, which seems to be default for Gnome 2.22, so just change to XOrg on login and it is fine.

Holodoc commented on 2016-10-13 18:19

@RubenKelevra:
This seems to be related to your setup. I am not a developer for JDownloader. Please contact the guys from the JDownloader Team on their website. the package cannot get out of date, because it is always using the latest version

All comments