@ Juha,

I went back several posts to your suggestion of using Update Manager and installing PPAs. So, I followed the instructions verbatim to install the PPAs into Update Manager, told Update Manager to check for updates, it found the BOINC updates, BUT REFUSES TO INSTALL THEM; just like when I tried this for Wine...

"Requires installation of untrusted packages

The action would require the installation of packages from not authenticated sources"

What instructions did you follow? I wonder if you didn't install the signing key.

Here's how I did it:

Start Software Center.
Start Software Sources from Edit-menu.
Select Other Software -tab.
Click Add-button.
Type "ppa:costamagnagianfranco/boinc".
Click Add Source.
(I couldn't find a way to refresh the package list from SC so I had to do it from command line. I didn't know I had Update Manager available (running this from Live CD).)
Then I went back to SC and installed 7.2.33.

Looks like you can get to the Software Sources from Update Manager as well (Settings-button).

@ Juha and BobCat13,

I DEFINITELY want to keep BOINC Manager GUI operational. So; BobCat13, if I follow your instructions, will that happen??? Or, as Juha suggests, will I need more command line instructions?

I'd rather not try to answer this because I don't know for sure what happens.

I updated the PPAs through Update Manager, "Settings, Other Software, ADD+"... Then Update Manager, "Check for Updates"; it finds updates for BOINC and BOINC Manager, and more, clicked "Install", and it gave me the error message I posted here...

I did the same thing for Wine and got the exact same results. FAILURE!!!

I will try what you have just posted for Software Center; but, I won't hold my breath that it works...

[EDIT]

OK, the Sources information in Software Center is IDENTICAL to the Sources I updated through Update Manager, Settings... The PPA's are there from when I added them; however, they are now unchecked, so that I don't constantly get the error message that it WON'T INSTALL FROM NON TRUSTED SOURCES!!!

WHAT NOW???

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

[I updated the PPAs through Update Manager, "Settings, Other Software, ADD+"... Then Update Manager, "Check for Updates"; it finds updates for BOINC and BOINC Manager, and more, clicked "Install", and it gave me the error message I posted here...

I did the same thing for Wine and got the exact same results. FAILURE!!!

I will try what you have just posted for Software Center; but, I won't hold my breath that it works...

In Software Sources' Authentication-tab do you have entry for Launchpad costamagnagianfranco-ppa?

edit added: Software Sources Ubuntu Software -tab. Which sources do you have selected? In particular, is universe selected?

edit2 added: Ok, you are probably missing the key. Software Sources downloaded it for me, I don't know why it doesn't work for you. Run this command from command line (sorry):

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3c2a1859

You should get output like this:

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.8tt46E2SUE --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 3c2a1859
gpg: requesting key 3C2A1859 from hkp server keyserver.ubuntu.com
gpg: key 3C2A1859: public key "Launchpad costamagnagianfranco-ppa" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

OK, the Sources information in Software Center is IDENTICAL to the Sources I updated through Update Manager, Settings...

It's the same program...

@ Juha and BobCat13,

I DEFINITELY want to keep BOINC Manager GUI operational. So; BobCat13, if I follow your instructions, will that happen??? Or, as Juha suggests, will I need more command line instructions?

Many thanks to you both.

You don't have to change the Manager if you don't want to. It is entirely possible to have client ver 7.2.28 and Manager ver. 7.0.65 on your system and they will work together. The four steps I gave (stopping the client, renaming the old, copying the new, and starting the client again) will only update the client.

[I updated the PPAs through Update Manager, "Settings, Other Software, ADD+"... Then Update Manager, "Check for Updates"; it finds updates for BOINC and BOINC Manager, and more, clicked "Install", and it gave me the error message I posted here...

I did the same thing for Wine and got the exact same results. FAILURE!!!

I will try what you have just posted for Software Center; but, I won't hold my breath that it works...

In Software Sources' Authentication-tab do you have entry for Launchpad costamagnagianfranco-ppa?

edit added: Software Sources Ubuntu Software -tab. Which sources do you have selected? In particular, is universe selected?

edit2 added: Ok, you are probably missing the key. Software Sources downloaded it for me, I don't know why it doesn't work for you. Run this command from command line (sorry):

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3c2a1859

You should get output like this:

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.8tt46E2SUE --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 3c2a1859
gpg: requesting key 3C2A1859 from hkp server keyserver.ubuntu.com
gpg: key 3C2A1859: public key "Launchpad costamagnagianfranco-ppa" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

OK, the Sources information in Software Center is IDENTICAL to the Sources I updated through Update Manager, Settings...

It's the same program...

Because I'm a paranoid bastard, I stopped BOINC, exited the BOINC Manager, and then proceeded.

OK, the command line installing the Key did it. I reactivated the PPA lines in Update Manager, hit "Check" for updates, it found the BOINC updates; but, did NOT tell me the Version # of BOINC it was going install, and then I hit Install.

This time, the install process worked! :-) (Again, because I'm paranoid, I restarted the computer for good measure.) Next, I launched BOINC Manager, and went to "Help" --> "About BOINC", and it has now installed 7.2.33 (x86).

Why it skipped over 7.2.28, I don't know; and, I hope that 7.2.33 has been sufficiently tested; however, ALL seems to be working. NONE of my WU's were lost, and it is crunching away as normal.

So, apparently, I'm also missing the Key to Wine... However, that's minor. I successfully installed Wine 1.6 via Command Line, Update Manager just refuses to install a Library change to Wine, because I'm missing the Key.

Thank you both again, Juha, and BobCat13.

Now, I just need help installing the BOINC ScreenSaver. I've posted in the Linux Screensaver Thread, but no one has responded for days. Perhaps one of you can assist me with that, too?

It would be greatly appreciated.

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

One issue has arisen; when XScreenSaver activates, BOINC automatically states, "CPU is busy." When I "wake up" the computer, BOINC continues to state "CPU is busy." - and refuses to come out of that state.

I tried exiting BOINC, (on exit I check Stop BOINC Client), I wait 15 seconds, relaunch BOINC Manager and BOINC Manager is empty; nothing shows in any of the BOINC Manager Tabs... I restart the computer, re-login, re-launch BOINC and everything is restored to normal; until the next time XScreenSaver activates, and it all starts over again...

I was hoping to use XScreenSaver to utilize BOINC Screensaver; however, this will make that VERY difficult, if NOT impossible.

Is this a flaw in 7.2.33??? BOINC 7.0.65 did NOT have this issue with XScreenSaver; so, it MUST be a 7.2.33 thing...

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Glad you got it working. edit: Well, mostly...

but, did NOT tell me the Version # of BOINC it was going install, and then I hit Install.

Click Description of update.

Why it skipped over 7.2.28, I don't know; and, I hope that 7.2.33 has been sufficiently tested; however, ALL seems to be working.

7.2.33 got promoted to Recommended status a few hours ago.

I went through the PPA's list of builds. It has contained alpha releases and most likely will do so again in future. You may want to disable the PPA from Software Sources until a new Recommended version emerges.

So, apparently, I'm also missing the Key to Wine... However, that's minor. I successfully installed Wine 1.6 via Command Line, Update Manager just refuses to install a Library change to Wine, because I'm missing the Key.

I think the key you are missing is F9CB8DB0. Just replace the BOINC PPA key at the end of the apt-key command with that and you should get the Wine updates working.

Here's how you can figure it out yourself. Go to the PPA page, click Technical details and the key is here:

Signing key:
1024R/F9CB8DB0  (What is this?)

Key is after the slash.

Now, I just need help installing the BOINC ScreenSaver. I've posted in the Linux Screensaver Thread, but no one has responded for days. Perhaps one of you can assist me with that, too?

One problem at a time.

If nobody else volunteers I'll take a look at it but first I need to get some other stuff done. Some patience, please.

Glad you got it working. edit: Well, mostly...

but, did NOT tell me the Version # of BOINC it was going install, and then I hit Install.

Click Description of update.

Why it skipped over 7.2.28, I don't know; and, I hope that 7.2.33 has been sufficiently tested; however, ALL seems to be working.

7.2.33 got promoted to Recommended status a few hours ago.

I went through the PPA's list of builds. It has contained alpha releases and most likely will do so again in future. You may want to disable the PPA from Software Sources until a new Recommended version emerges.

So, apparently, I'm also missing the Key to Wine... However, that's minor. I successfully installed Wine 1.6 via Command Line, Update Manager just refuses to install a Library change to Wine, because I'm missing the Key.

I think the key you are missing is F9CB8DB0. Just replace the BOINC PPA key at the end of the apt-key command with that and you should get the Wine updates working.

Here's how you can figure it out yourself. Go to the PPA page, click Technical details and the key is here:

Signing key:
1024R/F9CB8DB0  (What is this?)

Key is after the slash.

Now, I just need help installing the BOINC ScreenSaver. I've posted in the Linux Screensaver Thread, but no one has responded for days. Perhaps one of you can assist me with that, too?

One problem at a time.

If nobody else volunteers I'll take a look at it but first I need to get some other stuff done. Some patience, please.

Thanks, Juha, that Wine Key worked great. I successfully updated and installed the Library file it wanted. (...and, one other file.)

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

One issue has arisen; when XScreenSaver activates, BOINC automatically states, "CPU is busy." When I "wake up" the computer, BOINC continues to state "CPU is busy." - and refuses to come out of that state.

What in use -preferences you have set? Open System Monitor and look which processes are using the most CPU time and how much.

I tried exiting BOINC, (on exit I check Stop BOINC Client), I wait 15 seconds, relaunch BOINC Manager and BOINC Manager is empty; nothing shows in any of the BOINC Manager Tabs... I restart the computer, re-login, re-launch BOINC and everything is restored to normal; until the next time XScreenSaver activates, and it all starts over again...

BOINC packages for various distros install the client as daemon=service. Manager can't restart that. Daemon management is so badly distro specific that there's no way Berkeley could support them.

You can start the client from command line with "sudo service boinc-client start" or from GUI program like BUM. There is also System Jobs=jobs-admin but that doesn't work at all for me. (Neither one is installed by default.)

Is this a flaw in 7.2.33??? BOINC 7.0.65 did NOT have this issue with XScreenSaver; so, it MUST be a 7.2.33 thing...

Hard to tell yet.

One issue has arisen; when XScreenSaver activates, BOINC automatically states, "CPU is busy." When I "wake up" the computer, BOINC continues to state "CPU is busy." - and refuses to come out of that state.

What in use -preferences you have set? Open System Monitor and look which processes are using the most CPU time and how much.

I tried exiting BOINC, (on exit I check Stop BOINC Client), I wait 15 seconds, relaunch BOINC Manager and BOINC Manager is empty; nothing shows in any of the BOINC Manager Tabs... I restart the computer, re-login, re-launch BOINC and everything is restored to normal; until the next time XScreenSaver activates, and it all starts over again...

BOINC packages for various distros install the client as daemon=service. Manager can't restart that. Daemon management is so badly distro specific that there's no way Berkeley could support them.

You can start the client from command line with "sudo service boinc-client start" or from GUI program like BUM. There is also System Jobs=jobs-admin but that doesn't work at all for me. (Neither one is installed by default.)

Is this a flaw in 7.2.33??? BOINC 7.0.65 did NOT have this issue with XScreenSaver; so, it MUST be a 7.2.33 thing...

Hard to tell yet.

OK in System Monitor, there are A LOT of processes; most are system specific, NOT anything I added, and are at 0% of CPU Usage. Of the processes I've added, Firefox alternates between 0% and 1% of CPU Usage, BOINC Manager goes between 1% and 5% Usage.

I've set XScreenSaver NOT to activate until 4 Hours has passed so that BOINC will do some work. However; that's counterintuitive to what I want XScreenSaver for... Namely to install BOINC Screensaver and have that run while BOINC crunches. With XScreenSaver set to NOT activate for 4 hours, its Usage is 0%.

Anything else I should be looking for???

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Juha,

With XScreenSaver set NOT to activate for 4 Hours; I stepped away from the computer, made lunch, watched some TV, and came back to the computer after two hours. I found BOINC locked up again, claiming "CPU is busy" and frozen in that state.

I relaunched System Monitor, and caught Firefox using 85% of the CPU!!! Why would that be??? I immediately shut down Firefox, went back to BOINC, and BOINC SETI restarted working on WU's.

So, perhaps the culprit isn't XScreenSaver; but, is Firefox!!!??? But, again, why would Firefox suddenly start using that much of the CPU - especially, when I've had no trouble until now???

I'm now going to experiment... I will reset XScreenSaver to activate in 10 Min of inactivity. I will let that run for an hour; with Firefox off, and see if BOINC still locks up.

I will post again after that.

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Juha,

Well, no change on XScreenSaver, it does interfere/prevent BOINC from crunching; however, once the computer is awakened, crunching resumes normally. The bigger culprit; however, is Firefox getting up to 85% of CPU Usage.

I have, again, set XScreenSaver NOT to activate until 4 Hours has passed so that BOINC SETI will crunch.

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Anything else I should be looking for???

What's your preference setting for

Suspend work when non-BOINC CPU usage is above   25 %
0 means no restriction
Enforced by version 6.10.30+

Did you try 100% (or 0, which has the same effect)?

Gruß
Gundolf

With XScreenSaver set NOT to activate for 4 Hours; I stepped away from the computer, made lunch, watched some TV, and came back to the computer after two hours. I found BOINC locked up again, claiming "CPU is busy" and frozen in that state.

I relaunched System Monitor, and caught Firefox using 85% of the CPU!!! Why would that be??? I immediately shut down Firefox, went back to BOINC, and BOINC SETI restarted working on WU's.

Ok, that's good to know. BOINC works properly.

So, perhaps the culprit isn't XScreenSaver; but, is Firefox!!!??? But, again, why would Firefox suddenly start using that much of the CPU - especially, when I've had no trouble until now???

I really don't know much about Firefox, I only use it to read email (Gmail and Opera don't work well together). If I had to guess, Flash?

Well, no change on XScreenSaver, it does interfere/prevent BOINC from crunching; however, once the computer is awakened, crunching resumes normally. The bigger culprit; however, is Firefox getting up to 85% of CPU Usage.

The screensaver you have selected may be using plenty of CPU power.

Suspend BOINC, launch System Monitor, adjust it's refresh rate if necessary so that it itself uses only minimal CPU time, then start screensaver.

Let the screensaver run for some time so that system monitor can collect statistics. After some time has passed exit screensaver and go back to system monitor. If the graph shows unreasonable CPU usage while the screensaver was running switch to less demanding screensaver.

Anything else I should be looking for???

What's your preference setting for

Suspend work when non-BOINC CPU usage is above   25 %
0 means no restriction
Enforced by version 6.10.30+

Did you try 100% (or 0, which has the same effect)?

Gruß
Gundolf

Thanks, Gundolf, I had that one set to 50%; now, it is set to 0%. I have now reset the XScreenSaver to activate after 10 min of idleness. Let's see what happens, now! :-)

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Well, no change on XScreenSaver, it does interfere/prevent BOINC from crunching; however, once the computer is awakened, crunching resumes normally. The bigger culprit; however, is Firefox getting up to 85% of CPU Usage.

The screensaver you have selected may be using plenty of CPU power.

Suspend BOINC, launch System Monitor, adjust it's refresh rate if necessary so that it itself uses only minimal CPU time, then start screensaver.

Let the screensaver run for some time so that system monitor can collect statistics. After some time has passed exit screensaver and go back to system monitor. If the graph shows unreasonable CPU usage while the screensaver was running switch to less demanding screensaver.

Juha,

Per Gundolf, I have changed a setting on BOINC that should help. If it does, then the last bit of help I need is to get BOINC Screensaver installed. (As previously stated, I posted in the Linux Screensaver Thread; still waiting for help there.)


Thanks, again everyone, you've all been great.

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

Per Gundolf, I have changed a setting on BOINC that should help. If it does, then the last bit of help I need is to get BOINC Screensaver installed.

Yes. However, if the screensaver you are using uses over 50% of CPU time, it will harm your computer's productivity greatly.

On my computer, thanks to [some component of the desktop stack that I have not yet identified], drawing anything to screen uses a considerable amount of CPU power. In addition, a screensaver may need to do a lot of computations before it knows what it wants to draw on the screen. So I imagine my computer could hit 100% CPU usage with some screensavers.

My 'screensaver experience' with 7.2.28 was as follows. Ran installer, noticed the screensaver box was ticked, so hit the advanced button and deselected [don't want the BOINC screensaver!]. Let the installation complete and made it to launch the BM, then walked away. Hours later noticed the adjacent room was rather bright and went to look. Display showing desktop. Went to look in the screensaver applet and found that the installer had kindly also disabled the 'blank' screensaver with password. Not big, but if running in a more public environment, less of an appreciable move.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Per Gundolf, I have changed a setting on BOINC that should help. If it does, then the last bit of help I need is to get BOINC Screensaver installed.

Yes. However, if the screensaver you are using uses over 50% of CPU time, it will harm your computer's productivity greatly.

On my computer, thanks to [some component of the desktop stack that I have not yet identified], drawing anything to screen uses a considerable amount of CPU power. In addition, a screensaver may need to do a lot of computations before it knows what it wants to draw on the screen. So I imagine my computer could hit 100% CPU usage with some screensavers.

Juha,

Well, after I posted here, I went and caught up on the SETI Boards; then, walked away from the computer and let XScreenSaver run. Keeping in mind that the computer waited an extra 10 min before activating, it ran for approx. 45 minutes. I woke the computer checked BOINC and BOINC continued to run, despite the screen saver running, too.

I understand the potential usage of the screen saver vs. BOINC; however, the whole point of getting XScreenSaver to run on my Ubuntu setup is to install the BOINC Screen Saver. What kind of usage does that run??? It works fine on Windows; I'd like to see what it does on Linux.

If it doesn't work, I'll uninstall XScreensaver, reinstall Gnome Screensaver, (which only blanks the screen), and be done with it...

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet

My 'screensaver experience' with 7.2.28 was as follows. Ran installer, noticed the screensaver box was ticked, so hit the advanced button and deselected [don't want the BOINC screensaver!]. Let the installation complete and made it to launch the BM, then walked away. Hours later noticed the adjacent room was rather bright and went to look. Display showing desktop. Went to look in the screensaver applet and found that the installer had kindly also disabled the 'blank' screensaver with password. Not big, but if running in a more public environment, less of an appreciable move.

SekeRob2,

Are you on Windows, or Linux??? This particular computer is on Ubuntu 12.0.4 32-Bit Linux, and DOESN"T install ANY Screen Saver stock... I had to force it to have Screen Savers by uninstalling the Gnome (Blanking) Screen Saver, and installing XScreenSaver, in preparation to install BOINC Screen Saver. A WHOLE LOTTA WORK!!! So, at this point, I really REALLY want to see what BOINC Screen Saver will do, (or won't do), on this Linux Box.

---

Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos
Pluto is still a planet