Eddie Desktop edition 2.24.6 released

[per23 0]

On 1/30/2025 at 5:31 PM, tranquivox69 said:

Same situation on Mint 22. Together with seriously laggy performance in the Servers tab. Selecting and unselecting "Show All" takes like 10 seconds before the view us updated.

I see similar behavior, the list of servers very slow to be populated (Fedora 40) with latest stable Eddie version.

The pings of nearest, geographically, servers are showing > ~20/30ms, which seems to vary, from down as low as ~8ms with other recent previous Eddie versions.

[ss11 22]

Nice work, how is IPv6 over IPv4 handled? Via a 6tunnel , is there any third party / provider included in the process?

[cla 4]

On 2/2/2025 at 2:09 PM, cla said:

 

on Mac 3.2 GHz 6-Core Intel Core i7, MacOs Sequoia Version 15.3
the hang over the speed and conecction time report on the main window
is still there, occurred after 26:07:13 hrs of service,
as before VPN is still up an running.
Seem an hard bug to be fixed...

the only way to fix it is to to restart the Mac.

 

no fix around ??

[noah1shadow 2]

Why is there no problem with the 2.21.8 version booting? I cannot boot into the menu with the 2.24.6 version and an error message is given

 

[Zoya 0]

Eddie keeps crashing constantly for me 😭

[win8 7]

 2.24.6 appimage not working ... simply disappears from download location after 1st start under mint and lmde6 .... previous versions never had such behavor....

[OpenSourcerer 1468]

On 3/19/2025 at 2:22 AM, win8 said:

 2.24.6 appimage not working ... simply disappears from download location after 1st start under mint and lmde6 .... previous versions never had such behavor....

It does work, but for some reason if you launch it via GUI (observed with Dolphin), the script in the AppImage copies the container into a /tmp directory, executes it – then deletes the original. Upon exit the /tmp directory is then cleared, with the AppImage removed completely, necessitating a redownload. It doesn't occur if you launch it via terminal.
And check the link, too; the first user reporting this worked around it by wrapping the launch in a script.