Isn't that better if you guys upload a flatpak instead of a .deb version?

I just think that using a platform agnostic format could be a whole better just because everyone can install it, and it's easier than providing various package formats.

Hi, I noticed that FDM (latest stable version) is not optimized for multi-graphics cards notebook (MacBook Pro). The moment FDM launches, it forces the OS to select the high graphics cards which affect battery consumption. I hope the fix is simple and soon because I cannot and will not better download manager. Thank you.

6.3.0 build 1696 is released.

Hi ;
I'm using Ubuntu 19.03 and install FDM 6.3 Alpha .

Downloading from http sites very well but every https sites (e.g. github.com) "network error"

How to fix this problem ?

Thank you.

Alex wrote:6.3.0 build 1696 is released.

Thanks! Upgraded my Windows desktop and the 2 Sabayon Linux (Gentoo-based rolling release, ker 5.1) successfully.

lastottoman wrote:Hi ;
I'm using Ubuntu 19.03 and install FDM 6.3 Alpha .

Downloading from http sites very well but every https sites (e.g. github.com) "network error"

How to fix this problem ?

Thank you.

I just tried grabbing a file from GitHub, using Firefox Nightly (bin) v70.0a1 (2019-07-22) 64bit and FDM 6.3 Alpha build 1696, and I had 0 issues.
Sabayon Linux with kernel 5.1.16

The file I grabbed was this one: https://github.com/pal1000/Realtek-UAD- ... 6.0.8759.1

Hello Devs,

I wonder if it's planned to include functionality from previous FDM version to catch downloads only when ALT key is being pressed? This feature is still entirely missing from FDM 6.* and at least for me it's pretty essential one as I'm mainly using FDM to catch large downloads, where it makes most sense to benefit e.g. from FDM's multi-threading, server timestamp and file integrity checking.

ALT key related functionality is beneficial for sites where downloads trigger with delay and while there's possibly no direct link to start the download either via context menu.

Also, to address only of the downsides related to using ALT key is that you need to hold the key until the download even has been triggered. To improve the situation, I've sent a development idea in Ticket #616808 early 2018 and revising it a little here:

Allow user to define a key combination for following actions:
1. Toggle catching of download ON/OFF temporarily until toggled again
2. Toggle catching of the next download. After a download event has been caught, catching is turned OFF
If possible, these actions should be toggled per active browser instance. When the existing instance is closed / new instance is opened, it would retain the setting from FDM for if downloads should be caught or not by default.

This would improve usability and eliminate the need of holding ALT key and allow delayed sites to load on the background while continuing browsing. Thank you for listening!

-Kaedin-

lastottoman wrote:Hi ;
I'm using Ubuntu 19.03 and install FDM 6.3 Alpha .

Downloading from http sites very well but every https sites (e.g. github.com) "network error"

How to fix this problem ?

Thank you.

I'm running fdm from terminal and errors.

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: Incompatible version of OpenSSL

Ubuntu 19.04 openssl version is 1.1.1b default.

which version compatible to fdm ?

How to upgrade or downgrade to right version ?

lastottoman wrote:qt.network.ssl: Incompatible version of OpenSSL
Ubuntu 19.04 openssl version is 1.1.1b default.
which version compatible to fdm ?
How to upgrade or downgrade to right version ?

FDM 6.3 for Windows uses openssl 1.0.2 builds, so it looks like missing dependencies in Linux build. Version 1.02 is still supported, so try to install current openssl 1.0.2 libs and report how it works, please.

In Windows the problem is much more serious: FDM comes with old openssl 1.0.2k from 26 Jan 2017, so it should be updated to newest build as soon as possible. Note: Qt libs are dated on November 2018, and using much older SSL is just outrageous, IMHO.

Usher wrote:

lastottoman wrote:qt.network.ssl: Incompatible version of OpenSSL
Ubuntu 19.04 openssl version is 1.1.1b default.
which version compatible to fdm ?
How to upgrade or downgrade to right version ?

FDM 6.3 for Windows uses openssl 1.0.2 builds, so it looks like missing dependencies in Linux build. Version 1.02 is still supported, so try to install current openssl 1.0.2 libs and report how it works, please.

In Windows the problem is much more serious: FDM comes with old openssl 1.0.2k from 26 Jan 2017, so it should be updated to newest build as soon as possible. Note: Qt libs are dated on November 2018, and using much older SSL is just outrageous, IMHO.

Yes.It's worked now.

I'm installed only 1 package libssl1.0.0_1.0.2g-1ubuntu4.15_amd64.deb

https://launchpad.net/~ubuntu-security- ... _amd64.deb

Thank you for your efforts.

Kaedin wrote:Hello Devs,

I wonder if it's planned to include functionality from previous FDM version to catch downloads only when ALT key is being pressed? This feature is still entirely missing from FDM 6.* and at least for me it's pretty essential one as I'm mainly using FDM to catch large downloads, where it makes most sense to benefit e.g. from FDM's multi-threading, server timestamp and file integrity checking.

ALT key related functionality is beneficial for sites where downloads trigger with delay and while there's possibly no direct link to start the download either via context menu.

Also, to address only of the downsides related to using ALT key is that you need to hold the key until the download even has been triggered. To improve the situation, I've sent a development idea in Ticket #616808 early 2018 and revising it a little here:

Allow user to define a key combination for following actions:
1. Toggle catching of download ON/OFF temporarily until toggled again
2. Toggle catching of the next download. After a download event has been caught, catching is turned OFF
If possible, these actions should be toggled per active browser instance. When the existing instance is closed / new instance is opened, it would retain the setting from FDM for if downloads should be caught or not by default.

This would improve usability and eliminate the need of holding ALT key and allow delayed sites to load on the background while continuing browsing. Thank you for listening!

-Kaedin-

As for 1, if you enable the setting in the Browser Integration section titled Use browser if you cancel download via FDM, you can simply cancel the download and it passes back to the browser to be handled as if FDM were not even installed.

As for 2, I like the idea of being able to toggle in general, but it does overlap with the use browser setting I mention above.

Finally, wrt your stated objective for DLing only large files - you can easily set that up now to be automatic. In the same Browser Integration section, you have the ability to set the item titled Don't catch downloads smaller than X Mbytes, where X is a value determined by you. If you don't want to use FDM for downloads smaller than, say, 500 MB, enter 500 into that field for X and enable the setting.

That would make most of the reasons for modifying the ALT / Key combination less necessary to begin with, as you're only using FDM the way you intend to - to DL only large files.

HTH

Usher wrote:

lastottoman wrote:qt.network.ssl: Incompatible version of OpenSSL
Ubuntu 19.04 openssl version is 1.1.1b default.
which version compatible to fdm ?
How to upgrade or downgrade to right version ?

FDM 6.3 for Windows uses openssl 1.0.2 builds, so it looks like missing dependencies in Linux build. Version 1.02 is still supported, so try to install current openssl 1.0.2 libs and report how it works, please.

In Windows the problem is much more serious: FDM comes with old openssl 1.0.2k from 26 Jan 2017, so it should be updated to newest build as soon as possible. Note: Qt libs are dated on November 2018, and using much older SSL is just outrageous, IMHO.

Good point - Until I started looking at the *nix version of FDM I never paid attention to what gets installed with Windows version.

FDM v6.2.0 build 1533 for Windows x64 is NOT auto updating to v6.3.0 build 1696.

Hello, would you please build a Linux ARM (armhf, or aarch64) .deb package for Raspberry Pi?

When downloading a file from Jenkins that requires a login, FDM 6.x fails. Getting 403. But, it works fine with FDM 5.x.