...on GPU it require openCL as the client is
astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100

Yes, that's the same app that I'm running successfully on my 3 boxes with 7.2.42. No OpenCL detection problems here, so I would have to guess that there's some component missing that BOINC needs to call in order to find OpenCL. I don't know what that might be, though.

EDIT: BTW, I have driver 375.39 on one of my boxes and 375.66 on the other two.

Problem solved !
When using 7.2.47 fromTbar, both opencl is detected and 'boinccmd --get_cc_status' works ! :)
boinc v7.8.0 > /dev/null

PS: Driver is 375.82 and 375.66

---

The problem with 7.2.42 Not finding OpenCL has been discussed Numerous times previously. 7.2.42 is Only looking for the link named libOpenCL.so which some of the Repository drivers Don't create. I even walked Keith through creating a link to the OpenCL Library and naming it libOpenCL.so and then OpenCL was immediately found. It's the Driver that creates the link, NOT BOINC. That Bug was Repeatedly Named as being Fixed in the Rebuilt 7.2.47. If you don't want to use 7.2.42 because it isn't finding OpenCL with the Driver you are using, then use 7.2.47 as it has the Bug fixed;

Thanks Tbar ! :)
It's a pity boinc website still list 7.2.42 as the recommended version for linux.

---

The BOINC website also states If available, we recommend that you install a distribution-specific package instead. BOINC itself doesn't do Linux builds anymore, instead Linux package maintainers do BOINC builds. Or volunteers like TBar, MarkJ and others. The problem is that if you have problems with those versions, that you'll have to report it to them, not to BOINC.

---

The problem is that if you have problems with those versions, that you'll have to report it to them, not to BOINC.

Interesting, considering all 'them' do is compile the code supplied by BOINC.

It's easy enough to look them up here: https://github.com/BOINC/boinc/commits/client_release/7/7.8

I'd say you're missing https://github.com/BOINC/boinc/commit/709a04cebe50ff7ca47a3d2f6effc419ffb02a2c, which was certainly critical in the public release cycle.

That change doesn't seem to make much difference when using the standard system installed by the standard Linux installers. I think others have already said the major problems still exist with 7.8.2, I had the same results when compiled with both Ubuntu 12.04 and 16.04. I did run across some new errors when trying different compiles which leads me to think it's more of a scrolling problem than a RPC problem. After tracking down one error it was suggested to run sudo apt-get install libgl1-mesa-dev xorg-dev. That one line causes a Large number changes to the standard 12.04 install, so much you have to reinstall the nVidia driver. Afterwards the new wxWidgets and BOINC compile seems to be working a little better in 12.04. We'll see if it makes any difference in the other systems.

Is that a problem specific to Mageia? On my machines running 7.2.42 with Ubuntu 14.04, I haven't had any issues with AstroPulse.

No...I'm using also Ubuntu and there is openCL info in the coprocesseur :( Need to install 7.8 to get opencl
But boinccmd 7.8.0 doesn't seems to work ... :(
I only get "Authorization failure: -102" from "boinccmd --host <host> --passwd <password> --get_cc_status"
I will have to downgrade to 7.2.42 and forget about the AP....

Hmmm, that certainly seems odd, but I don't know enough about Linux to even have a clue. I didn't have to do anything special on my 3 Linux boxes to get the AstroPulse tasks to run just fine. They've simply worked okay right from the beginning with 7.2.42.

. . I am also running BOINC 7.2.42 with Ubuntu 14.04 and the APs I have received have all run pretty well, no sign of a problem.

Stephen

. .

TBar, do you have the problem with Network Activity in your BOINC 7.8.0? Is it fixed in BOINC 7.8.2? Maybe you didn't get my PM?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Nope, the Network Activity works perfectly fine in Ubuntu 12.04 & 14.04. Oh wait, you Do have to click it Twice in Ubuntu 16.04. There are a Few things that work perfectly fine in Some versions and not others. I suggest reporting the issue to the BOINC Developers since 'Them' are the ones that wrote the code.

I'm still picking up the pieces around here since having a Hurricane's eye pass over the house Sunday night, and there are a lot of pieces to pick up. Mostly pieces of trees and other foliage, and we are still having power outages.

The problem is that if you have problems with those versions, that you'll have to report it to them, not to BOINC.

Interesting, considering all 'them' do is compile the code supplied by BOINC.

We don't know which code you used. You don't say anywhere with your download which commits are included and whether that was from a branch or from master. As far as I could find, you don't provide the source code that you used to make the client and manager either, which you agreed to under the terms of the GNU Lesser General Public License that BOINC uses. This means that no one can check that you used just the source code from BOINC, or didn't also add something of yourself.

So yes, anyone having problems with the version you gave, should first go back to you, because you were the one compiling it.

---

I guess 7.8.0 is a little too obvious? Even I know 7.8.0 comes from the release branch as the master branch still says 7.7.0, https://github.com/BOINC/boinc/blob/master/version.h
So, I Now have 7.8.2 from here, https://github.com/BOINC/boinc/blob/client_release/7/7.8/version.h
What else do you wish to see besides what was in the docs folder for 7.8.0? You did look in the docs folder? So far this version of 7.8.2 seems to be working a little better, it will probably be an improvement over 7.8.0.

Let me make it simple.
You downloaded the source code on the 17th of November 2012 and upon compiling called it 7.8.0
We don't know. There is no source code. None of your files in \docs\ shows which commits got into 7.8.0

Now you bought a car from someone - no documentation or history on what was fixed with it. On the corner it broke down and the former owner points you to the car brand's dealer to complain there, because it's their brand. That's what you do.

You can compile BOINC all you want and use it for yourself without problems.
But as soon as you allow others out there to use your version, it becomes your responsibility.
Quoting from the COPYING document in your \docs\ folder:

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they
know their rights.

Are you willing to provide the source code to those that ask for it?

---

So far this version of 7.8.2 seems to be working a little better, it will probably be an improvement over 7.8.0.

If you look at the branch change list https://github.com/BOINC/boinc/commits/client_release/7/7.8, you'll find that precisely one code change affecting the operation of a Linux build was made between v7.8.0 and v7.8.2 - commit 709a04c: "Manager: don't crash if GUI RPC returns empty reply". All the others are for Mac only, concerning text translations, housekeeping (changing version numbers), and just one change for Windows disguised under a misleading title.

If by "working a little better" you mean "the Manager doesn't crash at startup", then I'd agree with you. But any change other than that is because of the way you've compiled the code, not because of the code itself.

If you read the wider discussion amongst the developers and outsiders like me, you'll find that new bugs are being reported, discussed, and worked on - on practically a daily basis.

I repeat my earlier advice: don't run v7.8.x on any platform unless you want to participate in the debugging process. If you were having GPU problems with an earlier versions, address those problems directly using the driver advice that's been provided in these threads. Don't clutch at straws you don't understand and which aren't fit for purpose yet.

Are you willing to provide the source code to those that ask for it?

The source code is here, https://github.com/BOINC/boinc/tree/client_release/7/7.8
At the time it was at 7.8.0, I believe you can download 7.8.0 from BOINC. Are you implying you can't download 7.8.0 from BOINC?
I was under the impression all you needed was a link which is in the Readme.md. Hey, if it's such a problem I'll just Stop All BOINC related activities. Much better than to be accused of wrongful acts.

So, I Now have 7.8.2 from here, https://github.com/BOINC/boinc/blob/client_release/7/7.8/version.h

That looks like you are building from the release branch. Depending on when you built your version and how the release management is done on BOINC side your build may be missing some commits that are in the official version or your version may have some commits that are not in the official version.

It would be better to build your versions from tags https://github.com/BOINC/boinc/tags. Tag is a snapshot of the tree at the time the tag was created and never changes. They are used to build the official versions.

TBar, sorry to have pestered you. Wasn't aware you were in the middle of the hurricane. I never tried double-clicking on the choice. Nope, that does nothing either. The radio button state never changes until you close the Activity window, re-open the Window and make your choice again, close the window and then re-open the window and your choice finally is reflected in the correct radio button position.

I guess developers have different a definition of what "release" means. In my past experience, "release" means the version of a software released to the general public and at the latest stable level of the software. If I was going to try and compile BOINC, I would have gone to a "release" branch logically. I would never had thought the stable and latest "release" would be in something called a tag directory.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Are you willing to provide the source code to those that ask for it?

The source code is here, https://github.com/BOINC/boinc/tree/client_release/7/7.8
At the time it was at 7.8.0, I believe you can download 7.8.0 from BOINC. Are you implying you can't download 7.8.0 from BOINC?
I was under the impression all you needed was a link which is in the Readme.md. Hey, if it's such a problem I'll just Stop All BOINC related activities. Much better than to be accused of wrongful acts.

Keep up the good work TBar ! At least, there is someone which provide an up -to-date boinc version for linux :)
Boinc developpers are mainly involved in the Windows/Mac port as most people use Windows. We definitely need someone for linux ;)
Adding 'tags' is a good idea so we could know which branch and when you get the source code, it will be easier to know if a bug/patch have been posted before or after.

A big number of volunteers work in computing area.
3% of the computers of the world are running linux but I think linux users are far more numerous in the seti quest....just my feeling.
Apologies for my poor english !

---

I just tried the BOINC Manager 7.8.2 that Christian Beer provided me from my GitHub post. It didn't work at first until I figured out how to check for dependencies. A bunch of stuff missing related to WxWidgets and GTK libraries missing. I think I remember that TBar version 7.8.0 only needed me to install the libwebkitgtk library which I guess is different.
Installed the following packages:
libwxbase3.0-0v5 (3.0.2+dfsg-1.3ubuntu0.1)
libwxgtk-media3.0-0v5 (3.0.2+dfsg-1.3ubuntu0.1)
libwxgtk-webview3.0-0v5 (3.0.2+dfsg-1.3ubuntu0.1)
libwxgtk3.0-0v5 (3.0.2+dfsg-1.3ubuntu0.1)

Now the BOINC Manager 7.8.2 runs but it has the same issue as my original 7.8.0 version of the Manager. So something else must be going on with my system since I have been told others don't have my problem.

Anyone want to offer some suggestion on what to try next?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

...I would never had thought the stable and latest "release" would be in something called a tag directory.

As Richard said, since 7.8.0 there has been One change that affects Linux, and that change was accompanied by a version change to 7.8.1. Since the version change to 7.8.2 there hasn't been any changes, so my 7.8.2 should be good. That one change back at 7.8.1 apparently isn't related to the problems people have posted here, I haven't heard of BOINC crashing at startup. So basically, there haven't been any Linux changes since 7.8.0 that would effect the problems posted on this board. I still have the Tasks page Scroll to the bottom and the Time tags still disappear/reappear in the Event Log. It just seems the Tasks page scrolls to the bottom much less in Ubuntu 16.04 with the new 7.8.2 build. I've also discovered the Time tags magically reappear if you Scroll the window up and then down again. I'm still trying to decipher what an 'undefined reference to non-virtual thunk' means. Apparently it has something to do with 'ScrollTarget'.

...At least, there is someone which provide an up -to-date boinc version for linux

I think this is pretty clear, ' BOINC itself doesn't do Linux builds anymore, instead Linux package maintainers do BOINC builds...." It would seem BOINC doesn't want to answer any questions about Linux anymore, they would rather just tell you to talk to someone else about it. That's probably why there hasn't been a new Linux release in 3 years. Of course, those someone elses can only shrug their shoulders and say it must be something in the code.

The new 7.8.2 build just needs libwebkitgtk-1.0-0, it still uses the static wxWidgets and other libraries.

The new 7.8.2 build just needs libwebkitgtk-1.0.so.0, it still uses the static wxWidgets libraries.

TBar, are you going to make this new 7.8.2 build available? Or are you still polishing it?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

There doesn't appear to be any polishing to be had, it is basically an Alpha build. All I can say is it works in Ubuntu 12.04, 14.04, and 16.04 without any horrendous problems. It probably won't be any different than 7.8.0 for most people. If all I have to do is add a link to the tag directory in the readme I suppose I could post it.

If you try to compile BOINC with wxWidgits Libs compiled in a different OS you get these errors;
CXXLD boincmgr
boincmgr-BOINCListCtrl.o:(.rodata._ZTV14CBOINCListCtrl[_ZTV14CBOINCListCtrl]+0x778): undefined reference to `non-virtual thunk to wxGenericListCtrl::GetSizeAvailableForScrollTarget(wxSize const&)'
boincmgr-DlgEventLogListCtrl.o:(.rodata._ZTV20CDlgEventLogListCtrl[_ZTV20CDlgEventLogListCtrl]+0x770): undefined reference to `non-virtual thunk to wxGenericListCtrl::GetSizeAvailableForScrollTarget(wxSize const&)'
....

Maybe it's just a coincidence there seems to be a Scrolling problem in BOINC Manager and Event Log, or maybe someone can suggest a possible course of action. You don't see the errors if you use the same OS to compile both wxWidgets and BOINC.