Eagle ask for license file - not available freeware anymore

[Germán Pablo Gentile]

Binary package hint: eagle

After update eagle to latest package available in karmic repositories, it refuse to start asking to select a license key.
Theres not anymore a run as freeware button available.
What is wrong?

[Scott Howard (showard314)]

Thanks for your report and helping make ubuntu better. This may be a duplicate of bug 475891 (different symptom but same bug)

Could you try the following and see if it works:

cp /usr/lib/eagle/bin/eagle ~/.eagle/bin/

Thanks.

[Germán Pablo Gentile (germanpablogentile)]

Thanks Scott, already do, not helped.

[Magnus (koma-lysator)]

I reinstalled Karmic, keeping my /home.
I too get this problem.

When I installed eagle through Synaptic I was not asked for a freeware version.

And now when I launch eagle I get the popup asking for a license key.

[Magnus (koma-lysator)]

I think I found a workaround: I simply selected the file ~/.eagle/bin/freeware.key and did not enter anything else.
It seem to be accepted by eagle, and it now starts.

[Germán Pablo Gentile (germanpablogentile)]

Magnus,

  Your workaround work here also. Thanks.

  But the bugs is still present, btw.

[Magnus (koma-lysator)]

Agreed: there is still some kind of regression.

Did you also reuse an old /home after a reinstall?
Or did you just upgrade to Karmic?

[Germán Pablo Gentile (germanpablogentile)]

I reuse my home directory, always do. So yes, i don't know if the freeware license is there or was put for a previous package version. :(

[Scott Howard (showard314)]

I know that in previous versions, it required you to accept a freeware license (by running debconf), but the newer versions are "smarter" and don't require to run debconf, but they do require the license key location to be input. When you install for the first time with a "clean" /home, it will ask you if you would like a freeware license. However, when reusing /home, as seen in this bug, it will ask you for your license location.

Thanks for debugging this and finding the work around! The bug remains, but am I'm marking as triaged and "low" importance since a work around exists (per Ubuntu bug importance policy).

[Gianfranco Costamagna (costamagnagianfranco)]

This bug seems to have been fixed so far.

Closing.