Just was reading through the release notes for Disco Dingo, the new Ubuntu 19.04 distro release and saw this interesting tidbit.

Safe Graphics Mode. A new option is added to the Grub menu which will boot with "NOMODESET" on. This may help you resolve issues on certain graphics cards and allow you to boot and install any propriatary drivers needed by your system.

This will be very welcome as the lack of default nomodeset being used in installation always seems to trip up Linux newbies. I've always thought nomodeset should be the standard configuration.

. . Let's hope that it doesn't create any dependency (or other) issues with SETI software. OOPS! I spoke too late ...

Stephen

??

I guess I could install Disco Dingo on my development partition. Don't use it much other than for compiling the client. I do use it to test out the bug fixes that Richard and DA come up with for various issues. I could then see whether it has any roadblocks for installing or using BOINC. I don't see any issues so far with the Open SSL 1.1.1b platform which is the last beta of the default OpenSSL platform in Dingo. I had to download, compile and install it on my own since SSL 1.1.1 isn't part of any Ubuntu 18.XX repository. No issues as far as I can tell. The main thing the new SSL does is provide the TLS 1.3 security protocol which is the defacto world standard now.

---

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

A proud member of the OFA (Old Farts Association)

I guess I could install Disco Dingo on my development partition. Don't use it much other than for compiling the client. I do use it to test out the bug fixes that Richard and DA come up with for various issues. I could then see whether it has any roadblocks for installing or using BOINC. I don't see any issues so far with the Open SSL 1.1.1b platform which is the last beta of the default OpenSSL platform in Dingo. I had to download, compile and install it on my own since SSL 1.1.1 isn't part of any Ubuntu 18.XX repository. No issues as far as I can tell. The main thing the new SSL does is provide the TLS 1.3 security protocol which is the defacto world standard now.

. . That sounds like a worthwhile precaution. It's good that ppl like you are there to test out the bleeding edge stuff ...

Stephen

:)

Well, I just jumped into the test waters. Upgraded to Disco Dingo. No issues to speak of. Saw some ppas get disabled like the graphics-drivers ppa and the curl34 ppa which is not needed anyway. Will have to reinstall the graphics-drivers ppa again for Dingo if I want any newer drivers. The upgrade installation put in the latest 418.56 drivers so no issues there.

Now I have to find out if TBar's new BOINC package runs correctly and whether my compile environment still works or I have to reconfigure a bit. I'm sure I will because gcc went from 8 to 9.
Really can't tell much difference from 18.10 to 19.04. I think I saw maybe two icons change and of course the background image went from the cuttlefish to the dingo. Still have all my little utilities and such loaded. But I did pick up a new keith folder on the Desktop which is my home folder of course.

[Edit] TBar is correct. Showstopper with libssl and libcrypto for the client

ldd '/home/keith/Desktop/BOINC/boinc' 
	linux-vdso.so.1 (0x00007ffef8568000)
	libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007ffa2e6e8000)
	libssl.so.1.0.0 => not found
	libcrypto.so.1.0.0 => not found

Don't think you can ln to the old libssl.so.1.0.0 like I did in Ubuntu 18.04 with the new libssl 1.1.1 since the old libssl.so.1.0.0 isn't even there now.

Looks like I will have to compile the new client in the Disco distro to make a compatible client.

---

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

A proud member of the OFA (Old Farts Association)

[Edit] TBar is correct. Showstopper with libssl and libcrypto for the client

ldd '/home/keith/Desktop/BOINC/boinc' 
	linux-vdso.so.1 (0x00007ffef8568000)
	libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007ffa2e6e8000)
	libssl.so.1.0.0 => not found
	libcrypto.so.1.0.0 => not found

Don't think you can ln to the old libssl.so.1.0.0 like I did in Ubuntu 18.04 with the new libssl 1.1.1 since the old libssl.so.1.0.0 isn't even there now.
Looks like I will have to compile the new client in the Disco distro to make a compatible client.

. . OK, so that is a no go for ppl like myself then :(

Stephen

. . Thanks for the update.

ldd '/home/keith/Desktop/BOINC/boinc'

But what version of boinc were you testing?

---

I downloaded TBar's latest BOINC.7z package so the 7.14.2 client from that.

---

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

A proud member of the OFA (Old Farts Association)

So, you've found the 'issues' that concerned me? Actually, a Large number of people are going to be 'concerned' if the OS doesn't have some backward compatibility for OpenSSL 1.0.x. It's easy enough to fix, just install 1.1.1 and point the compiler at that when compiling BOINC. The problem is it removes any backward compatibility as that App will now require OpenSSL 1.1.1. Again, easy to fix, just install SSL1.1.1 in the OS that doesn't have it and all is well. They have also dropped LibWebKitGTK-1.0-0 from 19.04, so, the Manager will have to work around that as well. What you will end up with is an App that needs a Very recent OS to work.
I'd say anyone still running Ubuntu 14.04 needs to update to at least 16.04, and have a copy of openssl-1.1.1b installed to handle the next All-in-One Apps. Very soon now 14.04 is going to be retired.
It is possible to install the Downloaded nVidia driver in 16.04, it just takes 3 or 4 tries before it stops ending in the Log-in loop.

I don't remember seeing any dependency issues with boincmgr in 19.04 just with boinc. I'll have to reboot to that distro and check ldd again on boincmgr to be sure.

[Edit] BOINC Manager runs fine. Opens normally but doesn't do anything since there is no client to connect to.

@TBar, did you remove the libwebkitgtk-1.0 dependency from your latest BOINC.7z package?

[Edit 2] I see that you did in fact.

 ldd '/home/keith/Desktop/BOINC/boincmgr' 
	linux-vdso.so.1 (0x00007fffe7723000)
	libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007ffb2441f000)
	libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007ffb24414000)
	libnotify.so.4 => /usr/lib/x86_64-linux-gnu/libnotify.so.4 (0x00007ffb2440a000)
	liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007ffb243e3000)
	libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x00007ffb241d5000)
	libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007ffb240b5000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ffb240ad000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ffb24091000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007ffb23f57000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ffb23f36000)
	libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007ffb23aec000)
	libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007ffb23a35000)
	libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007ffb23a23000)
	libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007ffb23903000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007ffb238dd000)
	libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007ffb23892000)
	libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007ffb23836000)
	libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007ffb23715000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ffb23532000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffb233e4000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ffb233ca000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffb231df000)
	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007ffb22fcd000)
	libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007ffb22db2000)
	libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007ffb22da7000)
	libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007ffb22bde000)
	/lib64/ld-linux-x86-64.so.2 (0x00007ffb24640000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007ffb22bb5000)
	libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007ffb22baf000)
	libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007ffb229a9000)
	libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007ffb2297e000)
	libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007ffb22965000)
	libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007ffb2291f000)
	libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007ffb22715000)
	libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007ffb22710000)
	libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007ffb22500000)
	libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007ffb222f3000)
	libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007ffb222e8000)
	libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007ffb220e5000)
	libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007ffb21ee2000)
	libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007ffb21e27000)
	libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007ffb21d7f000)
	libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x00007ffb21d48000)
	libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007ffb21d43000)
	libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007ffb21d34000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ffb21d29000)
	libthai.so.0 => /usr/lib/x86_64-linux-gnu/libthai.so.0 (0x00007ffb21d1e000)
	libfribidi.so.0 => /usr/lib/x86_64-linux-gnu/libfribidi.so.0 (0x00007ffb21cff000)
	libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ffb21cf5000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ffb21c81000)
	libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 (0x00007ffb21c67000)
	libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007ffb21c0b000)
	libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007ffb21be1000)
	libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007ffb21bc4000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007ffb219c0000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007ffb217ba000)
	libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007ffb216c1000)
	libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007ffb21684000)
	libdatrie.so.1 => /usr/lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007ffb21679000)
	libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007ffb21624000)
	libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007ffb215f7000)
keith@Mal:~$

---

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

A proud member of the OFA (Old Farts Association)

I don't remember seeing any dependency issues with boincmgr in 19.04 just with boinc. I'll have to reboot to that distro and check ldd again on boincmgr to be sure.

[Edit] BOINC Manager runs fine. Opens normally but doesn't do anything since there is no client to connect to.

@TBar, did you remove the libwebkitgtk-1.0 dependency from your latest BOINC.7z package?

[Edit 2] I see that you did in fact.

Nope, I didn't remove or add anything. It's the people building the OS that are Removing and Adding things. If you were to build a version of BOINC in 16.04.6 you will see the Manager is Back to requiring libwebkitgtk-1.0-0. The work around is to use the Manager from 15.04 with the boinc from 16.04, 'cause libwebkitgtk-1.0-0 doesn't exist in 19.04. If you do that, you will end up with a working BOINC 7.14.2 in 19.04 such as this one, https://setiathome.berkeley.edu/show_host_detail.php?hostid=6906726

That version of boinc not only has the Non-Jumping Pages, it also has the Finish File present Too Long Fix. It also requires OpenSSL 1.1.1b.... which 16.04.6 doesn't have.
Hmmm, I thought I saw driver 410.x in the driver panel back when I installed the OS a few days ago. I don't see it now, just 418.56 and the older drivers.

That version of boinc not only has the Non-Jumping Pages, it also has the Finish File present Too Long Fix

Is the fix for Finish File present Too Long in the BOINC.7z package or just in that host on 19.04?

I wasn't even aware of the #PR3019 bug fix till Richard mentioned it in another thread.

---

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

A proud member of the OFA (Old Farts Association)

I just built it today. It hasn't escaped the compound as yet.
I figured it might work well on the Miner, for those times I do something unwise, such as try to add too many cards.
The first error is the Finish File Present Too Long, then followed by messages about can't use GPU, mixed with more Finish File messages.
Hopefully this will cut down on the Errors needing to be fixed. For some reason, when the GPU drops off-line, BOINC stops reporting, which leaves pages of Errors on the machine that haven't been reported.
Most of them are the Finish File Present Too Long variety, along with a few about 'out of memory'.
It's Not Wise to try too many GPUs, unless you are good at editing the state file...

So, you've found the 'issues' that concerned me? Actually, a Large number of people are going to be 'concerned' if the OS doesn't have some backward compatibility for OpenSSL 1.0.x. It's easy enough to fix, just install 1.1.1 and point the compiler at that when compiling BOINC. The problem is it removes any backward compatibility as that App will now require OpenSSL 1.1.1. Again, easy to fix, just install SSL1.1.1 in the OS that doesn't have it and all is well. They have also dropped LibWebKitGTK-1.0-0 from 19.04, so, the Manager will have to work around that as well. What you will end up with is an App that needs a Very recent OS to work.
I'd say anyone still running Ubuntu 14.04 needs to update to at least 16.04, and have a copy of openssl-1.1.1b installed to handle the next All-in-One Apps. Very soon now 14.04 is going to be retired.
It is possible to install the Downloaded nVidia driver in 16.04, it just takes 3 or 4 tries before it stops ending in the Log-in loop.

. . And this is why people stay with Windows ... M$ are #*&T^&^&U but their OS works without having to be a developer and re-write and recompile parts of the OS. Why does Linux have to be so frustrating?

Stephen

? ?

Stephen, we are not recompiling the OS, just the apps to be used in the new distro environment. Windows apps don't escape this fact either you know. If the Windows environment changes, the app developers have to compile a new version to be compatible with the latest Windows OS.

---

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

A proud member of the OFA (Old Farts Association)

Stephen, we are not recompiling the OS, just the apps to be used in the new distro environment. Windows apps don't escape this fact either you know. If the Windows environment changes, the app developers have to compile a new version to be compatible with the latest Windows OS.

. . OK, but from this end it is a whole lot less confusing ..

. . The scary thought is M$ changing to Linux for their new OS ........... [edit] though maybe then Special Sauce will work in Windows [/edit]

. . Might be time for me to give it away :(

Stephen

:(

Stephen, we are not recompiling the OS, just the apps to be used in the new distro environment. Windows apps don't escape this fact either you know. If the Windows environment changes, the app developers have to compile a new version to be compatible with the latest Windows OS.

. . OK, but from this end it is a whole lot less confusing ..

. . The scary thought is M$ changing to Linux for their new OS ........... [edit] though maybe then Special Sauce will work in Windows [/edit]

. . Might be time for me to give it away :(

Stephen

:(

You can already run a Linux file system and a copy of the Ubuntu OS from the Windows 10 store while also running Windows. I saw some benchmarking articles but didn't read closely enough to remember any results. I am not sure but I presume it is a guest OS.
I found out about the above from an article on how to setup a developers environment.

Tom

---

A proud member of the OFA (Old Farts Association).

On Windows 10 it is easy to run Linux. All you do is enable developer settings in the configuration and you get the WSL or Windows Subsystem for Linux and you can get a variant of Ubuntu 18.04 LTS from the Windows Store. Or you can install your own distro.

---

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

A proud member of the OFA (Old Farts Association)

On Windows 10 it is easy to run Linux. All you do is enable developer settings in the configuration and you get the WSL or Windows Subsystem for Linux and you can get a variant of Ubuntu 18.04 LTS from the Windows Store. Or you can install your own distro.

Oh...Keith used the M-word!!! run away...run away....

---

Oh...Keith used the M-word!!! run away...run away....

Darn . . . . now I will have to wash my mouth out with soap . . .ha hah ha.

---

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

A proud member of the OFA (Old Farts Association)

On Windows 10 it is easy to run Linux. All you do is enable developer settings in the configuration and you get the WSL or Windows Subsystem for Linux and you can get a variant of Ubuntu 18.04 LTS from the Windows Store. Or you can install your own distro.

But can you pass a GPU through to it? I’m guessing no.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours