Well I fixed this quirk and it didn’t break anything, so...

We get it. You don’t take criticism well. It’s really ok. No reason to get upset, or even take it as a personal attack, that someone fixed something that had an issue.

---

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

How many versions of Linux have you tried your version of the Manager? The one in the AIO has been the SAME since BOINC 14.2, it has worked in many different versions of Linux. It has been thoroughly tested. You compiled your version last night... or this morning? Yet you are trying to push this on people. Rightttt...

I know due to the dependency on GLIBC that it will not work on anything earlier than Ubuntu 18.04. I very clearly mentioned this, no one should download my boincmgr executable expecting it to work with anything else. I tested it on both Ubuntu 18.04 and 20.04, and verified the expected behavior.

I gave people the information to decide for themselves. They are free to use whichever they like. If they want to use your package in its entirety and can deal with the startup lag, that’s their decision. But if they are comfortable copy/pasting a single executable to solve an annoying issue, then I provided the means to do so.

You’ll note that my first response was exactly to point Rick to YOUR latest package for him to try.

---

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

Try this....
Launch GKrellM, then select the Configuration option and count how long it takes to launch the window. Then try it in older OS versions.
There are undoubtedly others as well.
It will probably be fixed in some future update.... as usual.

Well I already fixed it so there’s really no point talking about unrelated software.

GKrellm is trash anyway, I had lag issues with that app too when using a lot of GPUs, even on Ubuntu 18, it’s a resource hog. Psensor is much better, and much more light weight. But again, that has nothing to do with the issue at hand. Stop deflecting.

---

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

Sounds to me you're repeating the WoW fiasco. I'd suggest you Stop trying to degrade other peoples work. The thing works fine.

maybe you should install the official release and see for yourself? maybe you think Keith is in on this conspiracy? I'm only reporting my observations, and took the initiative to try to fix it.

"works fine" is subjective. it "works", yes.

don't be so sensitive, it's not a personal attack.

Yes, I tested your TBar official BOINC.7z 7.16.5 AIO package on my new 20.04 LTS release. I thought something was broken it took so long for the Manager to appear. I timed it at 16 seconds versus Ian's 25 seconds because I have a faster cpu/memory host than he does.

On 18.04 LTS, the Manager opens instantaneously. It may take a while to list all the Einstein GW cpu tasks and populate the window, but no way needing 16 seconds to appear after clicking on the file or using the .desktop file.

So know something right away not kosher with the Manager application in Ubuntu 20.04 LTS.

---

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

A proud member of the OFA (Old Farts Association)

Try this....
Launch GKrellM, then select the Configuration option and count how long it takes to launch the window. Then try it in older OS versions.
There are undoubtedly others as well.
It will probably be fixed in some future update.... as usual.

The lag in the GKrellm configuration window opening is not new to 20.04. It had lag back in 19.10 too. The same amount it has in 20.04. So yes, there are issues with slow opening apps in the latest releases. Probably do to some of the security mitigations in the latest kernel and the GNOME environment.

I was running the very same 5.3. kernel in both 18.04 and 19.10 and yet the GKrellm config window appeared instantly when right-clicked in 18.04 but took over ten seconds to appear in 19.10.
Difference was the Gnome 3.28 version in 18.04 and the 3.34 GNOME version in 19.10. So I put the blame on GNOME for slow opening applications.

---

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

A proud member of the OFA (Old Farts Association)

I found the most likely reason that Tbar's boincmgr has slow startup. because he most likely compiled it with the now depreciated GTK2. I built mine with newer GTK3.

you can solve the slow startup in 20.04, while keeping Tbar's original file, by installing the GtkMenuShell D-Bus exporter for GTK+2.

https://launchpad.net/ubuntu/bionic/+package/appmenu-gtk2-module

sudo apt install appmenu-gtk2-module

then reboot. now his will start with no delay.

might be a good idea to either make this a footnote in the readme for the AIO, or recompile your software with more modern packages.

---

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

I gave it a try to see it it would help GKrellm. It does not. Still takes 20+ seconds for the configuration panel window to appear.

---

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

A proud member of the OFA (Old Farts Association)

Yeah, probably won’t help with everything. As the reasons for slow startup are likely different. But it helps in this specific case.

---

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

That still doesn't explain why it starts immediately when run as Root. Only one thing explains that.
No, adding that module didn't speed it up that much for me. If you read the readme it says;

4) The Default 7.16.5 version Will work with Ubuntu 18.04, but will need Dependencies to work with Ubuntu 20.04.
As of this release you will need to add libgtk2.0-dev to 20.04 for the Manager to work.
sudo apt install libgtk2.0-dev

That doesn't speed it up either, although back then it would allow it to work. It seems they partially fixed it since I wrote the readme, they just need something more.

When enough people complain about Apps starting slowly, they will fix it. There are already a few Apps named at Ask Ubuntu, there will be more.
Here, https://askubuntu.com/questions/1231105/apps-started-slowly-once-when-i-started-them-as-a-user

I have one strange issue... It's heppening to me from ubuntu 19.10, and now It's same with 20.04. It's related for next two apps: * WPS office * cisco anyconnect
Both apps is started very slowly once when I started them, but this heppening only when I started them as a normal user. If I started them as a sudo user... They are started very quickly. Do you have any suggestion what can be and how to check what can be. I tested kubuntu as well... and in kubuntu I don't have any issue.
asked 21 hours ago

Hmmmm, OK, after the reboot it now starts immediately. So, hopefully Ubuntu will fix it in the Release soon.
Even the GKrell Configuration starts immediately now, but, I did install both packages...

Hmmmm, OK, after the reboot it now starts immediately. So, hopefully Ubuntu will fix it in the Release soon.

I did say that you needed a reboot after adding that module. It does solve the problem. It’s repeatable too. Purge that module (and everything that it added) reboot, and its back to lagging.

Being compiled with the depreciated GTK+2 looks like the culprit.

---

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

That comes with compiling the App in Ubuntu 15.04. My Manager will work with Ubuntu 15.04 and above. It's boinc that has problems prior to 18.04, earlier versions require OpenSSL 1.0, above 18.04 requires OpenSSL 1.1.

Just a curiosity. Why you compile with Ubuntu 15.04 if you run hosts with 18.04 ?

---

Because I make software for EVERYONE, not just a handful of select users..
Real developers make Software for the largest number of the User-base. Something I kept trying to explain about the CUDA Special App...

Look at Einstein.... They have closed off the GW App to GPUs with 4GB of vram and above, now they can't find enough users to issue Wingmen. Right after the CUDA Special App was closed off to SETI Beta, SETI went into Hibernation...

Look at Einstein.... They have closed off the GW App to GPUs with 4GB of vram and above, now they can't find enough users to issue Wingmen.

I was unaware of that, long time out of E@H. I was imagine the problem was the low credit the paid (2000) compared with the GR (3,465) who runs faster.
I know is all not about credit, but if you use similar resources you expect receive the same credit, that was one of the big problems of CreditScrew.
Anyway thanks for the clarification about why you choose to compile with 15.04. If was me, and i know how, i sure do the same.
But you know i had a bad time even learning how to compile with 18.04. My Linux knowledge is almost zero. LOL

---

Well, from my perspective the problem with the GW App, besides the vram issue, is it was supposed to be much faster. Hence the lower Credit reward. Look at the time estimates, the estimates indicate they expected the GW App to be around three times as fast as the Gamma App. But, it's close to the same on anything older than a couple of years. In My tests the GW App is about 25% faster on a 2 year old machine than it is on a 10 year old machine using the same GPU. From the time estimates, they expected it to be even faster.

Because I make software for EVERYONE, not just a handful of select users..

what about people using distributions older than 15.04? that's certainly not everyone. maybe you should go back to 14.04 and recompile for those folks? or maybe 12? or.... your logic falls on it's face as even you recognize that you have to draw the line somewhere. there's nothing wrong with that, but dont try to claim you made something for everyone when you've clearly created a cutoff.

and seti hibernation had NOTHING to do with the Special app, that's the second time you've proposed that ridiculous conspiracy theory. nor does anything about Einstein and their apps have anything to do with what's being discussed in this thread. Please try to stay on topic.

---

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

I did say that you needed a reboot after adding that module. It does solve the problem. It’s repeatable too. Purge that module (and everything that it added) reboot, and its back to lagging.

I missed that part of the post. Now that I have rebooted, the config menu for GKrellm Monitor appears immediately. Thanks for sleuthing that out for us, Ian.

---

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

A proud member of the OFA (Old Farts Association)

If you look in the Docs folder of the All-In-One there are BOINC Apps that work all the way back to Ubuntu 12.04. That is most people out there...
I'm just answering questions here, you appear to be the one making accusations about software.

Oh, and none of this explains why you don't need to install anything if you launch as Root...