Hi there.
I'm having the missing libnotify error.
I did have BOINC 6.10.58 that came with the Debian distribution.
(I had some problems with restarts after suspending work to let my antivirus run - so that is why I'm going to try the dev version.)

I detached the projects and used the debian aptitude function to uninstall the old version.
Next I went into /var and deleted the slots, project directories.

I went to the BOINC website and downloaded
boinc_7.0.20_i686-pc-linux-gnu.sh

I copied this into my home directory and installed as myself.

A message, for start up, said to use
/home/[your account]/BOINC/run_manager
to start boinc.

Then I got this message:
"./boincmgr: error while loading shared libraries: libnotify.so.4:
cannot open shared object file: No such file or directory."


OK... I *assumed* I may just need to add a link....

I went to / and, as root, did a
find . -name "libnotify*" -exec /bin/ls -al {} \; -print
to take a look.

Found:
/usr/lib/libnotify.so.1.2.3
and
/usr/lib/libnotify.so.1 -> /usr/lib/libnotify.so.1.2.3

I took a chance and made
/usr/lib/libnotify.so.4 -> /usr/lib/libnotify.so.1.2.3

This time,
~/BOINC/run_manager
kind of worked. The Boinc window started up - but...

Next a message that says libssl.so.1.0.0 is missing

I have /lib/libssl3.so..


But..
Now, I suspect that these libraries are supplied by BOINC and the
Dev install file did not have them.


How shall I procede?

Thanks!!
Jay

These libraries aren't supplied with boinc - run ldd to find which libraries you're missing

ldd ~/BOINC/boinc*

You're then faced with trying to find the correct debian packages to meet these dependencies, or compiling the boinc package yourself.

Randomly creating symlinks to versions of libraries you have is bad practice - do so at your own risk.

BTW, curious to know which antivirus you're running on your debian box.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Hi,
I'm having a similar problem on Fedora 16.
Installing 6.13.6 or.8 gets a similar problem. The boincmgr program is looking for older versions of the libnotify.so, libssl.so and libcrypto.so libraries than I have. 6.13.1 also can't find libboinc.so.6

libssl.so.0.9.8 => not found
libcrypto.so.0.9.8 => not found
libnotify.so.1 => not found

/usr/lib64/libssl.so -> libssl.so.1.0.0g
/usr/lib64/libssl.so.10 -> libssl.so.1.0.0g
/usr/lib64/libssl.so.1.0.0g

/lib64/libcrypto.so.10 -> libcrypto.so.1.0.0g
/lib64/libcrypto.so.1.0.0g

/usr/lib64/libnotify.so -> libnotify.so.4.0.0
/usr/lib64/libnotify.so.4 -> libnotify.so.4.0.0
/usr/lib64/libnotify.so.4.0.0


I've installed a 7. series, and don't get those errors any more, but I do get something I can't figure out:
$ sh ./Downloads/boinc_7.0.22_x86_64-pc-linux-gnu.sh
use /home/p/BOINC/run_manager to start BOINC
$ /home/p/BOINC/run_manager
./boincmgr: Symbol `_ZTV12wxBufferedDC' has different size in shared object, consider re-linking
./boincmgr: Symbol `_ZTV10wxClientDC' has different size in shared object, consider re-linking
./boincmgr: Symbol `_ZTV10wxMemoryDC' has different size in shared object, consider re-linking
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.4,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.6).
Aborted (core dumped)

No idea what's causing that! ldd boincmgr doesn't show any errors.
The core file it drops shows it getting a generated error in wx
#3 0x00000039f22a1f4c in wxLogFatalError(wchar_t const*, ...) () from /usr/lib64/libwx_baseu-2.8.so.0
#4 0x00000039f2266964 in wxAppConsole::CheckBuildOptions(char const*, char const*) () from /usr/lib64/libwx_baseu-2.8.so.0

I've partly answered my own question here.
It looks like the wxWidgets library on Fedora x64 (only!) has a compatibility flag for v-old programs, and that causes boinc to drop core.
I'll try to get a version installed that doesn't support that old version and report here what happened.

Until you sort this out you can still run the boinc client by itself

/home/p/BOINC/run_client 

should do it.

You'll still need a way to communicate and control the client though - you can use boinc_cmd, BAM, an older version of the boinc manager, or boinctasks (running on wine).

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Just to keep the progress going for any others who may want to know.
I downloaded and rebuilt the wxwidgets library and turned off the 2.4 compatibility in the spec file. That got it running, but then there were the issues with slightly different versions of libnotify, libcrypto and libssl.
Blatantly symlinking the required library names gets it running, but there is some other bug which breaks things.
Also, there is an rpm available anyway, so a lot of hacking around there for no real reason. I just yum installed boinc.
The fedora 16 rpm boincmgr still breaks - probably because I'm running gnome 3 - not sure.
The upshot of all of that is that I'm running the command line version of boinc and using boinccmd to get it processing, as you suggested!
So all the problems are in the gui boincmgr.
I'll have dabble every now and then to see if I can assist in resolving the GUI problems.