Claws-mail 2.9.1-2 doesn't start anymore
 

Hello. I just update to Claws-mail 2.9.1-2 version and now it won't start anymore. In Xterm this info is shown after trying to start application:

claws-mail: error while loading shared libraries: libetpan .so.11: cannot open shared object file: No such file or di rectory
~ $

What is going on, is there something wrong in
the update package?

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Same here.
Just updated and claws mail reports the same missing library.

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Looks like one of the libraries does not get upgraded automatically.

From an XTerm, I did apt-get install libetpan10 and Claws works fine.

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Yeah. Of course if works.
Thanks

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Yes sir, it is working again and thank you for advises.

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Due to an problem between oldest version of libetpan package and newest
version, I restored the old version of claws-mail repository and disable for this
moment the new version.

Sorry for these problems.

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

I couldnt seem to run the app either so I uninstalled it, but it wont allow me to reinstall it. I get message "Unable to download, Application package not found."

EDIT: Any of you have a direct link to the armel file?

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Anyone able to help?

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Add this catalog in the Application Manager:

www.claws-mail.org/maemo
bora
user

Then just install.

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Just installed it a second ago, the problem seems to have been in application manager ...

Re: Claws-mail 2.9.1-2 doesn't start anymore
 

Re: "Unable to download, Application package not found."

My guess is that the app. manager needed an update of the listing. If the name (version number) of the package was changed / moved on the repository then the app. manager would look for the wrong (non-existing) file. So, update the listing and try again if such things happens.

(The other possibility is that the repository Packages file is inconsistent with reality, but this is rare because it tends to be generated automatically by the repository management software)