Confirmed and construtively communicated to upstream.
** Package changed: autodock-vina (Ubuntu) => autodocktools (Ubuntu)
** Changed in: autodocktools (Ubuntu)
Status: New => In Progress
** Changed in: autodocktools (Ubuntu)
Assignee: (unassigned) => Steffen Möller (moell
Hello, please kindly try again once the just uploaded 2014-April version hits
Ubuntu. Do you get the same report when starting runAdt from the autodocktools
package?
The change of directory should not be required to runPmv.
Best,
Steffen
--
You received this bug notification because you are a
Hello, I just checked in the recently uploaded version
1.5.7~rc1+cvs.20140424 and that particular line is commented out
upstream already, as it seems. SM
** Changed in: mgltools-viewerframework (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a
It is in by now. Many thanks!
** Changed in: autodocksuite (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131211
Title:
Please sync autodocksuite to
Public bug reported:
Hello,
we have recently updated autodock in Debian. Because of the freeze we
hid it in experimental, just please find and forward the package to
Ubuntu.
Many thanks and regards,
Steffen
** Affects: autodocksuite (Ubuntu)
Importance: Undecided
Status: New
--
The original md5 error reported in this thread I have just seen again
with 7.0.34. The error sems to be associated with tests for the amount
of disk space. I could well assume some concurrency issue to play a role
since both the original reporter and me seem to be running many cores in
parallel -
On 08/22/2012 04:51 PM, Jonathan Harker wrote:
Promise I won't make any more noise, but Locutus: I can happily report
that your PPA boinc-app-seti is now running fine on one of my 12.04
machines, but it needed a reboot to fix the app_info.xml file doesn't
have a usable version of SETI@home
Hello, after rereading about that SETI issue I have to admit that my
answer was wrong. Jonathan was right by pointing out that the SETI
scientific app seeks older symbolic libraries.
This what it should look like
$ ldd `dpkg -L boinc-app-seti | grep setiathome`
linux-vdso.so.1 =
@Jonathan with his SETI limitation - this is because SETI thinks that it
has sent you enough workunits for that day. That limit will go up once
the client works and workunits have been validated successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I suggest to change projects until locutus' PPA features boinc-app-seti
-3 from unstable.
Cheers,
Steffen
Sent with AquaMail for Android
http://www.aqua-mail.com
On August 21, 2012 3:19:24 PM Jonathan Harker
1009...@bugs.launchpad.net wrote:
It can't be just in proposed if I installed 12.04
Hi Jonathan,
On 08/20/2012 09:40 AM, Jonathan Harker wrote:
Hi there,
I am currently running a new installed 12.04 LTS, with the following packages:
dpkg -l|grep boinc
ii boinc 7.0.27+dfsg-5ubuntu0.12.04.1
metapackage for the BOINC client and
Please try again with the latest BALL (-4) in unstable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935038
Title:
ball version 1.4.1+20111206-3 FTBFS on armhf in precise
To manage notifications
On 08/14/2012 06:49 PM, LocutusOfBorg wrote:
I'm building right now the new boinc-app-seti rev-123 in my ppa [1]
this release should fix this bug and the computation error bug.
[1] https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
This version just also made it to Debian
On 07/08/2012 07:56 PM, Steffen Möller wrote:
On 07/08/2012 11:18 AM, Matt Dittloff wrote:
I'm using 12.04 Precise, BOINC version 7.0.24, and it does now seem to
stop computation. However, now I'm having the opposite problem. It
doesn't seem to detect that the computer is idle to be able
On 07/09/2012 01:49 PM, Ace Suares wrote:
I think boinc-manager may need some more graphic stuff, since it needs X, but
boinc-client is all commandline stuff.
Except for the idle detection, for which the boinc-client needs a particular X
library - xss, if I am not erroneous. This was the
This is hilarious, indeed. No idea what is going on at the moment. What is it
like when you run
apt-get install --no-install-recommends boinc-client ?
And what does
apt-get install --no-install-recommends boinc-manager
say?
Anyway, I do not see any link to ntfsprogs or odbcinst either way. What
On 07/08/2012 11:18 AM, Matt Dittloff wrote:
I'm using 12.04 Precise, BOINC version 7.0.24, and it does now seem to
stop computation. However, now I'm having the opposite problem. It
doesn't seem to detect that the computer is idle to be able to resume
computation.
I have while computer
Hello,
On 06/04/2012 10:58 AM, LAZA wrote:
Public bug reported:
First: I crunch for over four years with BOINC and did not change the
project resources since months.
Nice to hear.
I did a fresh installation of Precise from alternate CD and added BOINC per
Synaptic.
Version 7.0.25
On 05/29/2012 07:00 PM, LocutusOfBorg wrote:
Hi everybody, based on Daniel's hint I created a boinc-app-seti project and
packaged it in my ppa [1]
This is almost based on boinc-app-seti directly taken from debian's git [2]
and boinc taken from debian (just two or three modification to make
On 05/27/2012 07:13 PM, Daniel Hahler wrote:
According to Steffen this is assumed to be fixed in version 6.12 of the
package, which is available in Ubuntu Quantal (development release).
** Changed in: boinc-app-seti (Ubuntu)
Status: Incomplete = Fix Released
6.12 is working fine
Hi Daniel,
On 05/27/2012 07:08 PM, Daniel Hahler wrote:
I am uploading backports for Precise, Oneiric and Lucid to the testing PPA at
https://launchpad.net/~pkg-boinc/+archive/testing .
Once I get positive feedback I might upload/copy it to the normal PPA, too.
About getting it fixed in
On 05/26/2012 08:17 AM, LocutusOfBorg wrote:
** Changed in: boinc-app-seti (Ubuntu)
Status: New = Confirmed
Hello, it builds all fine, and runs all fine on my machine, but Guo Yixuan has
found it all to segfault for him. This needs some
further investigation ... Any other early
On 05/22/2012 03:05 PM, LeForgeron wrote:
Others are working fine too (ABC Collatz). No regression on Einstein
(GPU only), milkyway(GPU only) nor sudoku(CPU).
Fine for me.
I experienced that once, too. It was with WorldCommunityGrid, if I am not
erroneous. And it is a lllooong time ago.
Original-Nachricht
Datum: Mon, 21 May 2012 17:18:56 -
Von: LocutusOfBorg costamagnagianfra...@yahoo.it
An: steffen_moel...@gmx.de
Betreff: [Bug 941483] Re: Missing libraries or wrong linkage
A new version is going to be released in debian soon (6.12).
Please take it
-Nachricht
Datum: Mon, 21 May 2012 17:36:26 -
Von: Steffen Möller steffen_moel...@gmx.de
An: steffen_moel...@gmx.de
Betreff: Re: [Bug 941483] Re: Missing libraries or wrong linkage
Original-Nachricht
Datum: Mon, 21 May 2012 17:18:56 -
Von: LocutusOfBorg
On 05/20/2012 02:11 AM, LocutusOfBorg wrote:
Hi sorry for the delay, do you still have this problem?
Since 6.12 will soon hit the archives, I suggest to close this report.
Cheers,
Steffen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Original-Nachricht
Datum: Sat, 19 May 2012 10:53:57 -
Von: LAZA 1001...@bugs.launchpad.net
An: steffen_moel...@gmx.de
Betreff: [Bug 1001168] Re: crashes when trying to add projects
@LocutusOfBorg:
Yeah, you right!
After a reboot today it works... - but the problem
On 05/18/2012 02:48 PM, LocutusOfBorg wrote:
I'm experiencing the same problem, so this is not fixed afaics, I'm
looking for a clean upstream version to look if the problem is due to a
bad patch in ubuntu/debian system.
Something is wrong in that add project. That much we know.
Amazingly, the
Hello,
Original-Nachricht
Datum: Sun, 13 May 2012 16:54:19 -
Von: Thomas Ward tew...@trekweb.org
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
I confirmed with MOTUs and the archives that the version from Debian is
imported already.
Ah! I need to invest the github repository, I presume. Locutus checks
out from there and apparently some adjustment of mine with the latest
updates of BOINC has not made it back into the remote git
repositoryor something like it. What has found entry to the Debian
archive comes from my local
Hello, yes, and I had one report from Debian in the meantime, too, who
had already confirmed this version to be fine with him (and SETI).
Cheers, Steffen
debian/changelog for the version being synced to quantal (notice where
it closes this bug, which is number 991179):
boinc (7.0.27+dfsg-3)
On 05/10/2012 06:48 AM, Rocky37 wrote:
Just checked for updates and was surprised to find 7.0.27
Many thanks to you all for this wonderful fix -- Hugs to all
Hey, great! Nice to see you happy. Thanks also from my side to
Lotus, Dave and the folks behind the PPA build demons.
Is it
On 05/10/2012 06:19 AM, Thomas Ward wrote:
7.0.26 isn't in Debian, so I'd have to poke around with the MOTUs to get
that into Quantal, if not take the source and repackage it for quantal-
proposed.
Once Locutus can confirm whether or not 7.0.27 builds in Quantal, I'll
go poke the MOTUs. I
Hello,
On 05/10/2012 04:05 PM, Thomas Ward wrote:
New Updates:
It may be prudent to deal with the Quantal side first.
The issue on Quantal is that 7.0.27 has an issue of FTBFS (Fails to
build from Source). It may be prudent to talk to the MOTUs and see
whether they'd support a sync to
On 05/10/2012 04:49 PM, Ben Giacalone wrote:
Just tried to run your 7.27 on Dell 630 laptop which had no problem
before 12.04 upgrade and I get computation error on all work units for
Seti@home.
Hi Ben,
somewhere in this thread there is hidden a pointer to
Hello,
On 05/10/2012 05:16 PM, Ben Giacalone wrote:
I just installed 7.0.27+dfsg-0~827~precise1 onto a Dell 630 laptop which
had been running fine until 12.04 LTS upgrade. I am still getting
computation error on (9) work units that just downloaded.
This is unexpected. I presume this is the
On 05/08/2012 07:12 PM, Dave wrote:
Seti@home is down for its Tuesdsay maintenance. Should be up in a few
hours.
If your next build goes through Locutus I'll test it as soon as the
project comes online.
Good luck.
Docking@Home was also affected.
Cheers,
Steffen
--
You received this bug
On 05/09/2012 03:12 AM, Dave wrote:
Indeed. The am64 also has the bug. So that patch is definitely still an
issue with 7.0.27, at least with Ubuntu.
This is not expected. Have many thanks for identifying that.
Steffen
--
You received this bug notification because you are a member of Ubuntu
On 05/08/2012 11:56 PM, Dave wrote:
So I don't wanna push anyone here, but can't we just put a 7.0.24
without the bad patch into the Ubuntu repository while we play with
the 7.0.27?
7.0.24 is bad for many reasons, especially for an incompatibility with
decent NVidia cards, no, please jump to
On 05/07/2012 05:24 PM, Dave wrote:
MoreInformativeAppStartFailure.patch is the culprit of the computation
error issue. :-)
I'm relieved that that one worked. .
Please update to 7.0.27. I have the client working and that patch is in.
Steffen
--
You received this bug notification
On 05/08/2012 10:30 AM, LocutusOfBorg wrote:
Unfortunately sometimes I have to sleep :)
I'm building right now 7.0.27 with the patch parse_issues.patch disabled,
since it doesn't build with it included (and as far as I can tell the patch
has no problem), I have already filled a bug against
On 05/08/2012 11:02 AM, LocutusOfBorg wrote:
According to this [1] which is based on your git [2] the patch isn't
included, I see a
#convinceDavid# MoreInformativeAppStartFailure.patch
which is clearly commented.
Right. I had not pushed. Sorry for that.
I thought this patch was included
On 05/07/2012 04:03 PM, LocutusOfBorg wrote:
So based on your last information seems to be
MoreInformativeAppStartFailure.patch that causes this problem.
This is weird. I have just compiled my 7.0.27 version with that patch in
and this works nicely from what I see. Anyway. Jump over to 7.0.27
And I just read Dave's reply that this would be just fine, indeed.
If it is not the order of lines, then my hunch is that it is the size of the
buffer that I had increased, which may create larger (too large) files for the
client to read.
I will split that patch in two halves - buffer and
Original-Nachricht
Datum: Sun, 06 May 2012 16:03:30 -
Von: Dave xclusive...@gmail.com
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
@ Locutus
If this ppa has the patch Steffen thought was breaking it, we made need
to re-think
Original-Nachricht
Datum: Sun, 06 May 2012 20:21:37 -
Von: LocutusOfBorg costamagnagianfra...@yahoo.it
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
Hi to all, unfortunately I cannot build the .27 from steffen git in
launchpad.
Hello,
Have many thanks for all your energies going into it. The patches are listed in
http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=blob;f=debian/patches/series
and of those my personal hunch is the have a second look at the
app_ipc_uninitialised.patch, where I had improved (so I
Hello,
Original-Nachricht
Datum: Fri, 04 May 2012 17:22:10 -
Von: Dave xclusive...@gmail.com
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
and interesting, in the changelog for 7.0.27 I read compile fix...
Don't really know what
Hello,
I can confirm this problem. I have only a hunch what may be wrong, most
likely the boinc-client now produces lines in its communication with the
scientific app that are complete - but too long. But I have to prove
that, still. The problem occurred while I was excluding potential issues
Hello,
Original-Nachricht
Datum: Thu, 03 May 2012 16:11:35 -
Von: Dave xclusive...@gmail.com
An: steffen_moel...@gmx.de
Betreff: [Bug 991179] Re: 7.0.24 computation error bug
@Locutus. Will do, happily! It's just gonna take about 12 hours til some
AP units finish up,
On 03/29/2012 11:23 PM, LocutusOfBorg wrote:
** Changed in: boinc (Ubuntu)
Status: New = Confirmed
7.0.23 has this fixed from what I observe.
Coming.
Cheers,
Steffen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 03/29/2012 11:25 PM, LocutusOfBorg wrote:
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
I'm building 7.0.23 in my persona archive, and it will be available in a few
hours.
Please try this never version, from latest upstream 7.0.23 and few
patches from Steffen (and a
On 03/14/2012 11:04 PM, Launchpad Bug Tracker wrote:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: boinc (Ubuntu)
Status: New = Confirmed
I have no idea how to fix it. The problem does not appear when the client
cannot connect to the server. It
On 02/16/2012 07:19 PM, LocutusOfBorg wrote:
(no problem, just a suggestion: I built this boinc version for oneiric
too)
I admit not to have addressed that issue. It can be circumvented by setting the
PYPATH environment variable, just like shown on
the ServerGuide page on the wiki ... at least
** Changed in: boinc (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/49249
Title:
Long project names result in clipped buttons
To manage notifications
The dependency on X is intentional. There is no CUDA / OpenCL without X.
And GPGPUs make up easily for those not installing the package any more
because of X. And there were complaints about the boinc-client not
detecting mouse movements, which only the X libraries detect. We could
have - in very
On 01/14/2012 10:23 PM, Leon Blakey wrote:
So then if X is so needed then why is there no X dependencies in the 32
bit version? Thats more of what I'm asking
For mere computation, the boinc-client package does not need X. For sensing
user interaction when X is running, it does. And there was a
Hello,
On 12/24/2011 05:18 AM, Launchpad Bug Tracker wrote:
[Expired for boinc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: boinc (Ubuntu)
Status: Incomplete = Expired
expiring bugs are not what you should see, but frankly, there is little point
in
On 12/26/2011 01:07 AM, LocutusOfBorg wrote:
@Steffen I agree with you but I have to say that I've personally
experienced this bug in the older 6.10 releases and the bug were already
reported by me before the opening of this one! (I were not experiencing
anymore this bug because ubuntu lacks
Hallo,
Is it necessary for the x64 version of the *client* to depend on
programs and libraries that provide X functionality? And if it does, why
does the x86 version not depend on them?
The dependencies for the 64bit version I presume to be auto-added by
the dh_shlibdeps program. Maybe this
Hm. Maybe. I thought that this way it would be even easier for someone
to know what to pick. I would rather add another boinc-nvidia-opencl
package at the very moment. And: for anyone with a working set of
dependencies the regular boinc package is already sufficient.
I admit not to have
Hello,
On 12/05/2011 09:07 PM, Daniel Hahler wrote:
The dependencies are not satisfied in Ubuntu (different packages for the
binary drivers).
See https://bugs.launchpad.net/608917 for the request to get Provides
for the nvidia ones.
That ones says not to be existing. Could you please just
On 12/03/2011 07:43 PM, Jérôme wrote:
Maybe we could add the below lines to the file /etc/init/boinc-client.conf on
oneiric version :
---
description BOINC core Client
start on (runlevel [45] and filesystem and login-session-start)
stop on (desktop-shutdown or runlevel [!45])
...
---
I
On 12/02/2011 04:09 PM, Daniel Hahler wrote:
libcuda.so is shipped with nvidia-current / nvidia-current-updates in
Ubuntu.
I don't know if just installing them is enough, when using the nouveau
driver (instead of nvidia) for display though.
The just released (to Debian unstable) version
Those run levels are interpreted differently across distributions as it
seems. I have further changed above dependencies to
### BEGIN INIT INFO
# Provides: boinc
# Required-Start:$all
# Required-Stop: $local_fs $remote_fs
# Should-Start: x11-common, network-manager, gdm,
There was some work on string copy functions why may have contributed to
something.
Reopen the bug if you find this to happen past 6.13.12.
** Changed in: boinc (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just tagged it as Fix released. Later versions don't show this, so I
presume to be kind of ok to say.
** Changed in: boinc (Ubuntu)
Status: Incomplete = New
** Changed in: boinc (Ubuntu)
Status: New = Incomplete
** Changed in: boinc (Ubuntu)
Status: Incomplete = Fix
There is now 6.13.12 in unstable. Daniel - would you volunteer to adopt it for
the PPA?
I was experimenting a bit with the runlevels. An update is likely to happen any
time soon,
depending on all your feedback.
Best,
Steffen
--
You received this bug notification because you are a member of
On 11/12/2011 07:01 PM, Jérôme wrote:
It seems that the boinc client still be launched at early steps :
--
j@lu64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric
j@lu64:~$ ls
6.13.10 has issues, too - just very different ones. Let's wait for
6.13.11 and then backport when this turns out to be stable.
Anybody feeling like providing a package for 6.12.34?
Steffen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 11/10/2011 10:17 PM, LocutusOfBorg wrote:
correction, after a look on the checkin_notes I see the changes between
33 and 34 are affecting only windows and mac users
Hm. I recall there was _something_ for us, too.
Leaky brain. Anyway, I was not overly enthused back
then and am fairly
On 11/01/2011 07:16 PM, Daniel Hahler wrote:
With X on about every machine, I could live with that change.
Servers usually do not have X installed, but I would be glad to give a
test-build a spin.
Apart from that, it may make sense to have a package for servers and
another one for GUI/X
On 11/01/2011 11:14 PM, Papamatti wrote:
The libraries libcuda.so and libOpenCL.so are in /usr/lib/nvidia-current.
Boinc should see this:
NVIDIA GPU 0: GeForce GTX 260 (driver version unknown, CUDA version
4000, compute capability 1.3, 896MB, 608 GFLOPS peak)
I'm just looking for new
On 10/25/2011 01:51 PM, LocutusOfBorg wrote:
I don't understand why do you need this library.
Doesn't boinc download automatically it when needed?
There is a separate package for it but BOINC does not
(and should not IMHO) depend on it. I happily accept
patches that help the detection of any
On 04/20/2011 12:08 AM, Christian Lins wrote:
Please note that the latest upstream patch for this issue requires special
buildparameters (--with-xss or something) which links the binary agains
libxss (X screen saver idle detection).
AFAIK this is not done in Debian because they don't want a
Hello,
On 10/09/2011 01:14 AM, northa wrote:
The bug still exists. in 6.12.33 in 11.10. When doing $sudo /etc/init.d
/boinc-client restart the GPUs will be found so its a workaround.
In the meantime I have managed to confirm this behaviour on a machine
at work - yes. Mighty annoying. I just
No idea what you might possibly mean here.
** Changed in: boinc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845509
Title:
error 403 forbidden al
Hello, could you please investigate again with mgltools-
pmv_1.5.6~rc1+cvs.20110617-2? I have just uploaded that to unstable and
it should solved the issue you are refering to. If there is a larger
crowd wishing to work with the MGLtools on Lucid, then we (or someone
from that crowd) should go
2.6.x of mgltools-pmv no longer crashes, please give it a try. It wil
lnot be available for 9.10, though, unless when you contribute it to the
Debian Med PPA, to which you are wholeheartedly invited.
** Changed in: mgltools-pmv (Ubuntu)
Status: New = Fix Released
--
You received this bug
I had meant 1.5.6~rc1+cvs.20110617-2 .. sorry. SM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484295
Title:
pmv crashes when loading
To manage notifications about this bug go to:
Try again with 1.4.0 that is now in unstable and the Debian Med PPA.
** Changed in: ball (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/590280
Title:
*** This bug is a duplicate of bug 630125 ***
https://bugs.launchpad.net/bugs/630125
** This bug has been marked a duplicate of bug 630125
package torque-client (not installed) failed to install/upgrade: trying to
overwrite '/usr/bin/qalter', which is also in package gridengine-client
The two are in conflict, indeed. The debian package I found to
explicitly mention the conflict at least since 2.4.9. Most groups will
only have a single queueing system, but, hey, at least during a
transition period the installation of both is not unlikely. So, this
conflict is truly unfortunate.
** Changed in: torque (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/441063
Title:
torque-gui: /usr/lib/xpbs/tclIndex and /usr/lib/xpbsmon/tclIndex point
Hello, 1.3.x is history. The Debian Med PPA has 1.4.0 for Lucid and Natty at
https://launchpad.net/~debian-med/+archive/ppa
Some more exotic platforms on Debian fail, but for a very different
reason. It should all be just fine for the next transfer from unstable
to Oneiric.
** Changed in: ball
We are currently rebuilding it all for Debian. A version that apparently
works for me is currently in unstable. What flavour of Ubuntu are you
using? There might be a volunteer to fast-track the mgltools-* packages
to the Debian Med PPA. This bug should then be of the past.
** Changed in:
** Changed in: mgltools-dejavu (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/500453
Title:
crashes upon launch; ClippingPlane index out of range
To manage
The answer is to add the architecture name in braces. 6.12.32+ shall
bring it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/560143
Title:
BOINC for amd64 should depend on the libc6-i386 or
After reading through http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=366741, which expresses a fierce opposition to a
dependency on the ia32 libs, I have now changed my mind and will leave
it with the recommends.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Could someone please help me with a patch that would keep the package
functional on non Intel|AMD machines?
One can recommend about everything, but to truly depend on it ... donno.
Today, the setting is
Package: boinc-client
Depends: ${shlibs:Depends}, ${misc:Depends}, python (= 2.3), adduser,
On 05/15/2011 09:41 AM, LocutusOfBorg wrote:
this bug seems to be fixed here.
http://boinc.berkeley.edu/trac/changeset/23529
Confirmed. I'll upload a new version as soon as
I see it announced on the download site.
Steffen
--
You received this bug notification because you are a member of
Hi Swen,
have many thanks for your report!
On 05/14/2011 04:21 AM, Swen Kühnlein wrote:
Public bug reported:
Binary package hint: boinc
Boinc crashes a few seconds after starting with the following last lines
on stdout:
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: boinc-client
Hi Swen, have many thanks for rerunning with symbols.
@David: It's two bugs, confirmed on both 6.12.18 and
6.12.59 with Ubuntu.
It is apparently caused by a circular path below /sys
leading to an exceeded length of some internal path
representation. The first bug is that the recursion was
not
Hello, Skip had sent me a pointer to his summary on the BOINC forums on
the matter and I have followed your all's instructions. So, when
6.12.23+ comes out, this should also auto-detect your graphics card.
Many thanks to you all.
Steffen
--
You received this bug notification because you are a
** Changed in: boinc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/587426
Title:
No GPU found
--
ubuntu-bugs mailing list
Done, I tend to think. Closing this with 6.12.23+.
** Changed in: boinc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/525241
Title:
Move to upstart
It does not work any longer with the introduction of auto-detected
dependencies. Version 6.12.23+ will have this fixed.
** Changed in: boinc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is any of these packages packages here
libcuda1-ia32 - NVIDIA CUDA runtime library (32-bit)
libcuda1 - NVIDIA CUDA runtime library
libnvcuvid1 - NVIDIA CUDA nvcuvid runtime library
libnvidia-compiler-ia32 - NVIDIA runtime compiler library (32-bit)
libnvidia-compiler - NVIDIA runtime compiler
Is this bug still reproducible with 6.12.22? I would otherwise tend to
just close it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/362079
Title:
boincmgr crashed with SIGSEGV in
Hello,
Debian and Ubuntu are working together for BOINC (and elsewhere). The
bug was fixed by upstream recently.
Please investigate 6.10.59 (when you see it) and 6.12.18 may have it
already, too.
For Ubuntu check out
https://launchpad.net/~pkg-boinc/+archive/ppa
For Debian it is in unstable
1 - 100 of 154 matches
Mail list logo
