BOINC with Ubuntu 20.04
Message boards :
Number crunching :
BOINC with Ubuntu 20.04
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
| Author | Message |
|---|---|
 ML1 Send message Joined: 25 Nov 01 Posts: 21253 Credit: 7,508,002 RAC: 20 
 |
... it wasn't so much as a WAG, as it was an educated guess based on knowing... Hey! That was in reply to my WAG ("Wild Ass Guess")! :-P :-) Ok, so dbus interfacing isn't a network lookup but at least it is still an interface timeout :-P Good sleuthing and good fixing, good all round. Keep searchin', Martin See new freedom: Mageia Linux Take a look for yourself: Linux Format The Future is what We all make IT (GPLv3) |
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 
 |
The Real problem is with Gnome and DBUS, the GTK module is just a bandaid. Someone suggested simply changing from GDM to lightdm as the display manager. I might try that next. What really needs to happen is to have Ubuntu fix DBUS. |
Ian&Steve C.  Send message Joined: 28 Sep 99 Posts: 4267 Credit: 1,282,604,591 RAC: 6,640
|
Someone suggested simply changing from GDM to lightdm as the display manager. even if it works, its kind of using a cannon to kill a fly. and not the kind of change to expect your users to do to fix such a small problem. wouldn't it just be much simpler to just recompile the software so the user doesn't have to change anything? or do you not have the capability anymore? is that why you're so adverse to it? Seti@Home classic workunits: 29,492 CPU time: 134,419 hours  
|
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768
|
Because it doesn't fix the problem, and some people are still having trouble after using the module. The fact that running as Root avoids the real problem of DBUS timeout should be a major clue. |
|
Ian&Steve C. Send message Joined: 28 Sep 99 Posts: 4267 Credit: 1,282,604,591 RAC: 6,640
|
I made some more edits. mostly aesthetic this time. I played around with different versions of wxWidgets, but it doesn't really seem to matter much which one you use. this latest one just happens to be with the latest dev version 3.1.3. seems like any version >3.0.0 is good enough for BOINC. I have my manager that works with Ubuntu 14.04-20.04, but I noticed some oddities with how it looks in 20.04, vs how it looks in previous OS's. seems to come down to using GTK3 vs GTK2. The most egregious was the Compute Preferences window. All of the text somehow gets bolded and italicized when compiled with GTK3. So I dug into the various .cpp modules to see if I could find what is doing that. Found and Fixed :) just a small tweak to the code. I can't explain why this code doesn't get applied with GTK2 though, the code in the module is exactly the same regardless of toolkit used, so I dunno. Left = 20.04 - GTK3 w/o fix. Middle = 20.04 - GTK3 with fix Right = 20.04 - default look when compiled with GTK2  the second thing is the page tab labels. they also are bolded for some reason. and again seems to be caused by GTK3 being used. I haven't found the bit of code to change this one yet, it wasn't as obvious in the code as the previous fix. I can deal with this one though. I'd rather have some bolded tabs than 20+ seconds of startup time.  And in Ubuntu 18.04, it seems to only get the bold/italic issue, but it's tabs remain unchanged, when GTK3 is used.  Ubuntu 16 and 14 are not affected by this at all. weird stuff. Here's the link to the new version if anyone want's to use it: https://drive.google.com/open?id=1erjrEKCwxTr3QsL6tm4cIbTqRzLVxttA Seti@Home classic workunits: 29,492 CPU time: 134,419 hours
|
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768
|
Ha! I found a work around for those that have problems with the module for 20.04. I remembered a couple people saying they didn't have any Lag trouble when they did an in place network upgrade from a version prior to 19.10. It was only after they did a clean install of 19.10 when the Lag started. So..... How about doing an upgrade from 18.04 to 20.04? Short version, it works. I upgraded 18.04 by entering sudo do-release-upgrade -d and observed all the warnings about how long it would take, blah, I have a fast internet and an SSD. It took about 15-20 minutes and booted without the nVidia driver. But Gkrell worked normally, so, on to the driver. Install it by entering sudo apt install nvidia-driver-440. Then after a reboot I tested my BOINC 16.5, boom, starts up instantly. Nice. For this test I used an existing install that had the Home folder on a different partition from the system, don't know how it would work if the Home folder is on the same partition as the system. I really like having my Home folder on a different partition, that way you can install a different system in a flash while leaving your Home folder with BOINC in it untouched. It comes in real handy, all you have to do is select 'something else' in the installer, choose the Home partition as /Home without formatting, and then the system partition as / with formatting. I'll test it for a while, but right now everything seems to work normally. |
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768
|
After some testing I can report the problem with Startup Lag is actually fixed by running a Web based Upgrade of a System Prior to 19.10. I installed a fresh copy of 18.04.3 from my USB installer, updated it to 18.04.4, then ran the install command sudo do-release-upgrade -d. After about 15-20 minutes I had a Bug-free version of 20.04 which launched Apps as User the same way as when launched as Root, without adding any additional packages. A quick check with Synaptic shows there are not any appmenu packages installed. Why would you expect to have to add software to launch as User when you don't have to add software to launch as Root? I feel much better about 20.04 now.... After the Upgrade I noticed I had a Newer kernel than my other System which hasn't been changed since installing 20.04 on day one. There was 94mb of updates on the other machine, apparently released last night just before my 'Upgrade' of the other machine. I ran the update and unfortunately it doesn't fix the App Startup Lag problem on that machine. I guess I'll have to reinstall the OS on that machine to fix it anytime soon. It's the furthest one away from me and just sits there running Einstein 24/7. |
Keith Myers   Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
I have never been successful in doing the sudo do-release-upgrade -d upgrade from either 19.04 to 19.10, 19.10 to 20.04 or 18.04 to 20.04. Always blows up at around 90-95% complete in the finalization. Only a clean install has ever worked for me. So I would still have been affected by the bug. Seti@Home classic workunits:20,676 CPU time:74,226 hours   A proud member of the OFA (Old Farts Association) |
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768
|
Have you tried it with a Clean version of the Host OS, without any GPU drivers installed? The OS I Upgraded was completely Stock as I was fresh out of 18.04 systems on the test machine. Also, I had the Home and System on different partitions so only the OS partition was Upgraded. It worked very nicely and only asked about one gdm3 configuration file that it alleged had been changed from the Maintainers version. Strange since I had just installed a Clean version of the OS. Anyway, it worked fine on that system. |
|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
No, I had never started with a clean system. Just an operational one. Just trying the supposed "easy" path to an release upgrade. Great idea . . . . if it works. Never does for me. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
|
Ian&Steve C. Send message Joined: 28 Sep 99 Posts: 4267 Credit: 1,282,604,591 RAC: 6,640
|
Yeah some systems just never seem to upgrade properly. I know Keith has issues with that before. Neat workaround, for those who are able to get an upgrade done. But it’s a workaround to the problem, not a fix. Just like how installing that appmenu module is a workaround, or editing grub so auto-login works with Nvidia drivers. All workarounds. A fix means that the user doesn’t have to do anything special to make something work. Seti@Home classic workunits: 29,492 CPU time: 134,419 hours
|
|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768
|
Fortunately for Ubuntu a large number of their Users run Laptops, only use the LTS versions of the OS, and Upgrade their OS over the Internet. Apparently most of those people don't have any trouble with the Internet Upgrade, and will not experience the same trouble as those who install from the Downloaded image as a clean install. BTW, the Test machine I Upgraded has One Maxwell GPU, somewhat similar to a Laptop. The major question is what is different about a clean install which results in the App working normally when launched as Root, but results in a DBUS Timeout when run as a User. That shouldn't happen. |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
That was May, this is October! I updated to 20.04 LTS when prompted, and now boinc is dead. The manager runs but the service does not. I tried installing boinc again, got tons of chains of uninstalled prerequisites! dgp@dgp-p6803w:~ $ Downloads/boinc_7.4.22_x86_64-pc-linux-gnu.sh use /home/dgp/BOINC/run_manager to start BOINC dgp@dgp-p6803w:~ $ /home/dgp/BOINC/run_manager ./boincmgr: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory dgp@dgp-p6803w:~ $ How do I re-install boinc on 20.04 LTS? |
|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
The old deprecated BOINC from the website you are using to install does not work anymore. You should use the newest 7.16.6 provided on the BOINC download page. https://boinc.berkeley.edu/download_all.php Or use the AIO from the arkayn Crunchers Anonymous webstite. http://www.arkayn.us/lunatics/BOINC.7z Or use any of the packages listed in this thread. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
How to install? dgp@dgp-p6803w:~ $ mv BOINC BOINC-old dgp@dgp-p6803w:~ $ ^C dgp@dgp-p6803w:~ $ sudo apt-get autoremove boinc-client [sudo] password for dgp: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: boinc-client libboinc7 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 3,182 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 286138 files and directories currently installed.) Removing boinc-client (7.16.6+dfsg-1) ... Removing libboinc7:amd64 (7.16.6+dfsg-1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... dgp@dgp-p6803w:~ $ ^Cdo apt-get autoremove boinc-client dgp@dgp-p6803w:~ $ sudo apt-get remove boinc-client Reading package lists... Done Building dependency tree Reading state information... Done Package 'boinc-client' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. dgp@dgp-p6803w:~ $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. dgp@dgp-p6803w:~ $ Downloads/boinc_7.4.22_x86_64-pc-linux-gnu.sh use /home/dgp/BOINC/run_manager to start BOINC dgp@dgp-p6803w:~ $ new BOINC -rwxr-xr-x 1 dgp dgp 282296 Sep 16 2014 BOINC/boincscr -rw-rw-r-- 1 dgp dgp 3048 Sep 16 2014 BOINC/boincmgr.48x48.png -rw-rw-r-- 1 dgp dgp 1901 Sep 16 2014 BOINC/boincmgr.32x32.png -rw-rw-r-- 1 dgp dgp 827 Sep 16 2014 BOINC/boincmgr.16x16.png -rwxr-xr-x 1 dgp dgp 7003976 Sep 16 2014 BOINC/boincmgr -rwxr-xr-x 1 dgp dgp 277696 Sep 16 2014 BOINC/boinccmd -rwxr-xr-x 1 dgp dgp 983496 Sep 16 2014 BOINC/boinc -rw-rw-r-- 1 dgp dgp 219 Sep 16 2014 BOINC/binstall.sh -rwxrwxr-x 1 dgp dgp 43 Oct 3 14:07 BOINC/run_manager -rwxrwxr-x 1 dgp dgp 40 Oct 3 14:07 BOINC/run_client dgp@dgp-p6803w:~ $ /home/dgp/BOINC/run_client ./boinc: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dgp@dgp-p6803w:~ $ /home/dgp/BOINC/run_manager ./boincmgr: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory dgp@dgp-p6803w:~ $ |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
The first link gives me the file I am using: boinc_7.4.22_x86_64-pc-linux-gnu.sh BTW: Why does Ubuntu lag so many versions behind? Are version numbers independent by platform? |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
I tried http://www.arkayn.us/lunatics/BOINC.7z dgp@dgp-p6803w:~ $ new BOINC drwxr-xr-x 3 dgp dgp 4096 Aug 31 2018 BOINC/projects -rw-r--r-- 1 dgp dgp 41 Aug 31 2018 BOINC/run_client -rw-r--r-- 1 dgp dgp 44 Aug 31 2018 BOINC/run_manager -rw-r--r-- 1 dgp dgp 198 Aug 31 2018 BOINC/cc_config.xml -rwxr-xr-x 1 dgp dgp 60195392 Mar 19 2019 BOINC/boincmgr -rwxrwxr-x 1 dgp dgp 15375704 Feb 27 2020 BOINC/boinc -rwxrwxr-x 1 dgp dgp 998568 Feb 27 2020 BOINC/switcher -rwxrwxr-x 1 dgp dgp 3038808 Feb 27 2020 BOINC/boinccmd -rwxrwxr-x 1 dgp dgp 2917640 Feb 27 2020 BOINC/boincscr drwxr-xr-x 3 dgp dgp 4096 Mar 2 2020 BOINC/docs dgp@dgp-p6803w:~ $ BOINC/run_client -bash: BOINC/run_client: Permission denied dgp@dgp-p6803w:~ $ file BOINC/run_client BOINC/run_client: ASCII text dgp@dgp-p6803w:~ $ head BOINC/run_client cd "/home/user/BOINC" && exec ./boinc $@ dgp@dgp-p6803w:~ $ chmod u+x BOINC/run_client BOINC/run_manager dgp@dgp-p6803w:~ $ BOINC/run_client BOINC/run_client: line 1: cd: /home/user/BOINC: No such file or directory dgp@dgp-p6803w:~ $ |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
Anyone have an Ubuntu BOINC install process that works? |
|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
https://boinc.berkeley.edu/download_all.php gives me an exe file, but I am on Ubuntu. Do I install BOINC under wine? The 7.4.42 version will not work anymore. Did you look in the Linux x64 category for the 7.16.6 file download. It is most certainly NOT an .exe. https://boinc.berkeley.edu/dl/boinc_ubuntu_7.16.6_x86_64-pc-linux-gnu.sh Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
|
DGPickett Send message Joined: 20 May 99 Posts: 31 Credit: 347,636 RAC: 2
|
I modified that post once I saw the other platform files way down below. It took me back where I started. dgp@dgp-p6803w:~ $ rm -rf BOINC dgp@dgp-p6803w:~ $ sudo apt-get remove boinc-client Reading package lists... Done Building dependency tree Reading state information... Done Package 'boinc-client' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. dgp@dgp-p6803w:~ $ Downloads/boinc_7.4.22_x86_64-pc-linux-gnu.sh use /home/dgp/BOINC/run_manager to start BOINC dgp@dgp-p6803w:~ $ /home/dgp/BOINC/run_manager ./boincmgr: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory dgp@dgp-p6803w:~ $ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.