boinc-client bad signature for URL

Bug #585547 reported by Robert Sander
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)
Medium
Unassigned
Nominated for Lucid by Robert Sander
Nominated for Maverick by Robert Sander

Bug Description

Binary package hint: boinc

Installed a new lucid amd64 host. After that not being able to attach to projects via boincmgr and BAM account manager.

http://boincstats.com/forum/forum_thread.php?id=5198 is pointing to a new upstream version of boinc-client.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: boinc-client 6.10.17+dfsg-3ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32.11-epi+drm33.2 x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue May 25 22:00:16 2010
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: boinc

Revision history for this message
Robert Sander (gurubert) wrote :
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

This is a big problem and I'm going to request a packaging for boinc 5.10.56 (since it has been released yesterday or today)

Revision history for this message
Saenger (uwe-herzke) wrote :

I'm currently running Koala 64bit with BOINC 6.10.17 manually installed on my machine. It has no problems with either BOINC, the projects or BAM!.

I installed Lynx 64bit on the machine of my parents, and got the same error messages described in the above mentioned thread at BOINCstats.

So obviously the fault is not with 6.10.17 but with the Lynx, although the manual installation of 6.10.56 seems to help as well.

Revision history for this message
Skip Guenter (skip) wrote :

Same problem after upgrade of Xubuntu from v8.04LTS to V10.04LTS (64b). Moved v6.10.56 binaries to /usr/bin and resolved.

Revision history for this message
dinwath (dinwath) wrote :

i confirm that upgrading to v 6.10.56 (via package found at https://launchpad.net/~turl/+archive/ppa) worked for me

Revision history for this message
Robert Sander (gurubert) wrote :

The manual upgrade works generally. The only thing that seems not to be working is detecting user interaction and pausing computation.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

@Robert please see this bug and the upstream related one https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/128357

Revision history for this message
Skip Guenter (skip) wrote :

Upgraded to v6.10.58 (via PPA http://ppa.launchpad.net/pkg-boinc/ppa/ubuntu lucid main) on my v10.04 Xubuntu machine and the problem seems to have returned. However I have v6.10.58 from the PPA installed on other versions of Ubuntu and don't have the issue. Am I thinking this correctly that this tells me it's the combo of v10.04 AND the Ubuntu/Debian Boincmgr to create this problem? If ya'll think it'll add definition I could try moving the v6.10.58 x64 binaries from Berkeley onto my v10.04 machine and see if the problem goes away??

Revision history for this message
Skip Guenter (skip) wrote :

@ comment #8 (mine)

Revision history for this message
Skip Guenter (skip) wrote :

@ comment #8 (mine)
Update: I saw no change in behavior with the Berkeley v6.10.56 BUT I failed to detach/re-attach from BAM :-(
Upon re-installing v6.10.58 from the PPA AND detaching/re-attaching from/to BAM the error went away again.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I am closing this bug. It appears to be fixed in the current upstream version, which will be available in Maverick.
You can add the following PPA to always get the latest upstream version: https://launchpad.net/~pkg-boinc/+archive/ppa
A stable release update is unlikely, or somebody else would have to go through the "paperwork".

Changed in boinc (Ubuntu):
status: New → Fix Released
importance: Undecided → Medium
Revision history for this message
Elbarbudo (patricearnal) wrote :

Apparently, the bug is still present :
Ubuntu 10.04 LTS 64 bits
BOINC 6.10.17 from Ubuntu repository

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers