On 06/02/2010 12:02 PM, Thierry Carrez wrote:
Which version of eucalyptus are you running ? Which logs do you find
those warnings in ?
1.6.2 is the version, sadly with some confusion now on my side if this
was from my initial attempt from the stable 1.6.2 release, the Debian sid one
or the
Public bug reported:
JAVA_HOME was set to /usr, just because
$ ls -l /usr/bin/java
lrwxrwxrwx 1 root root 22 May 26 17:01 /usr/bin/java - /etc/alternatives/java
and not directly to anything in
# ls -l /usr/lib/jvm
total 12
lrwxrwxrwx 1 root root 14 May 17 14:55 default-java - java-6-openjdk
The bug is in the error message, I tend to think. Daniel, please make
your magic words more prominent. Best, Steffen
--
Cannot upload bundle to Walrus
https://bugs.launchpad.net/bugs/429590
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
This is more of a comment than a bug report (well, the message could be
more informative and less missleading). It took me a while to get past
this one
ERROR: could not synchronize keys with cloud-server-derma!
The configuration will not have this node.
Hint: to setup
Public bug reported:
There is a series of these warnings appearing
WARNING: Handler
'com.eucalyptus.ws.handlers.WalrusRESTLoggerOutbound' does not have a
'ChannelPipelineCoverage' annotation with
The problem that I as a mere Debian user have is that there is no wxWidgets
2.8 in my distribution yet that is officially required for 5.10. Debian is at
2.6.0. However, 2.8 is apparently part of Ubuntu and you may hence not care
overly much, particularly since Frank is using Ubuntu, too :o)
I
I ran into this issue myself. apt-get install vim and then running vim
gives the error
vim: error while loading shared libraries: libgailutil.so.18: cannot
open shared object file: No such file or directory
I was not even interested in running anything else than the console
version so I now
Public bug reported:
Hello,
we had the protein modeling and -visualisation suite BALL in sid a
couple of days before the karmic freeze and because of an error report
very unrelated to the Ubuntu architectures the package was not moved to
testing in time. But it is in testing for a while now and
Hi,
James Westby wrote:
Where is the FFe for this?
sorry, this is a new acronym for me. Morten, can you jump in, please?
Google gave me
https://bugs.launchpad.net/ubuntu/+source/refpolicy-ubuntu/+bug/352801
and in analogy to it the following text:
I'd like to see uploaded the package BALL, a
Hello,
fcestrada wrote:
Boinc registers itselfs in the menu under Applications-Systemtools-Boinc
Manager (in german: Anwendungen-Systemwerkzeuge-Boinc Manager) which
seems to be quite inapropriate to me.
Boinc has nothing to do with my system, it's just using its resources
(like any
Hello,
dino99 wrote:
What i meant in my first question, is only about the job project (for
example: wgc) . I know about the difference in Jaunty karmic packages, but
what's about the download computed projects ? i continue to think that should
be done by any os if that work projects was
Hello, I have recently updated all the mgltools- packages. Could
someone please confirm this bug for 1.5.4.cvs.20090603-1 ? Many thanks,
Steffen.
--
autodocktools (runAdt) crashes with a TypeError
https://bugs.launchpad.net/bugs/371064
You received this bug notification because you are a member
Frank S. Thomas wrote:
On Wednesday 22 July 2009 07:37:24 dino99 wrote:
What i wish
is that apps path workunit can be costumized by user to use /home for the
reasons i've explained previously, that seem more logical cant see the
difficulties to do that.
You should read the fine
Hello,
I don't run a Xen kernel, planning for something solely working with
KVM. It is all on my Debian Sid laptop, as localhost, as Squeeze 64
binaries. The java process is started/stopped directly via /etc/init.d
/eucalyptus-cloud start/stop. There is no image on the system and
consequently no
I followed the advice to go from SYSTEM to MANAGED but then experienced
a far worse CPU usage towards 120% (dual core laptop).
The network controller apparently does not work for me since my machine
(running both as Eucalyptus server and client) is not prepared for Xen,
which is a prerequisite.
I have reconfigured eucalyptus.conf to have an empty nodes list, so
there should be no reason anymore to invoke anything like a network
controller on any execute host, right? My previous settings for the
MANUAL way were incomplete, I adapted these towards a 255.255.255.0
subnet and corrected the
chris grzegorczyk wrote:
If I am understanding correctly, this is an issue with the Cloud
Controller?
sudo /etc/init.d/eucalyptus-cloud stop
stops it.
cloud-controller is not /etc/init.d/eucalyptus-cc ? Stopping -cc has no
effect.
If so, the underlying problem has to do with the way that
please some confirm the original report.
** Changed in: autodocktools (Ubuntu)
Status: New = Incomplete
--
autodocktools (runAdt) crashes with a TypeError
https://bugs.launchpad.net/bugs/371064
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Have many thanks, Dino!
Steffen
** Changed in: boinc (Ubuntu)
Status: New = Invalid
--
boinc might use /home
https://bugs.launchpad.net/bugs/402082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Aaron Novstrup wrote:
Just had another crash, and this time there was nothing interesting in
the kernel log. Back to square one I guess
hello,
we have BOINC running smoothly on amd64, also with WCG. Are you trying
the latest kernels?
I had experienced problems in the past, but
robb1e wrote:
odd, I've been running in MANAGED all the time and I'm also seeing these
issues.
My hunch for my local CPU-burning (MANAGED better than SYSTEM but still bad
~30%) is that
the failing communication with the eucalyptus-nc provokes the eucalyptus-cloud
to
power-dump repetitive
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
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
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
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
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
** 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
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
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
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
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
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
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
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:
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
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 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
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
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
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,
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
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,
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
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
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
*** 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
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:
Hello,
On 11/06/2010 02:02 PM, Daniel Hahler wrote:
[..man-db crashed..]
+ ERROR during removal:
+ Removing boinc-client ...
+ [31m*[39;49m BOINC data directory '/var/lib/boinc-client' does not exist.
+ invoke-rc.d: initscript boinc-client, action stop failed.
+ dpkg: error processing
On 01/28/2011 09:55 PM, Crosshair wrote:
The only work around as of now is to insert any key stroke into the
terminal.
For me BOINC is always on, anyway, tough to test the bug ...
could someone please try 6.12.8 in Debian experimental in this respect?
Many greetings
Steffen
--
You received
Dear all,
my colleague, Andreas Recke, and I just ran into the same issue that was
reported just two weeks ago by Ralf Hildebrandt
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/714586 : The
boincmgr just crashes when attempting to attach to a project.
The crash was most reliably confirmed
Dear Rom,
On 03/07/2011 10:05 PM, Rom Walton wrote:
Okay, I think I've found and fixed this issue. The changes should be
committed to the 6.10 branch.
From what you wrote I understand that this issue is no longer relevant for
the 6.12.x versions, which are already in Debian unstable,
On 03/07/2011 11:48 AM, Martin Pitt wrote:
Declining for Natty; 6.10.58 is still the upstream recommended version.
** Changed in: boinc (Ubuntu)
Status: New = Won't Fix
There is now 6.10.59 with a single patch to 6.10.58 that we had asked for.
The problem (crash at attach project)
Hm. What project have you selected to have an account with? Or did it
crash even before that list appeared? Was it your very first
installation of BOINC? Daniel, how far is 6.12.15 from appearing with
Ubuntu so Ralf could also try that?
--
You received this bug notification because you are a
On 02/27/2011 01:45 PM, Daniel Hahler wrote:
Ubuntu is in feature freeze for Natty, but we could go through the Freeze
Exception process [1].
Steffen, do you think that it is unlikely to cause more problems than it
solves?
Well, no, we should not ship anything officially unstable. I just
Public bug reported:
Binary package hint: sensible-utils
Hello,
sensible-browser is apparently started from the boinc-manager and it truly
attempted to start iceweasel.
$ boincmgr
/usr/bin/sensible-browser: 27: /usr/bin/iceweasel: not found
None of the browsers in $BROWSER worked!
$
Dear all,
Dominique, Morten and Jordi have now completed working on a 2.4-based packaging
of Torque and this should hit the Ubuntu servers any time soon. For the time
speaking it is Debian unstable for the very last four days now.
To do so add
deb-src http://ftp2.de.debian.org/debian/
The torque 2.4 packages have arrived in Maverick. Please kindly
investigate if the bug is still valid.
--
torque-gui: /usr/lib/xpbs/tclIndex and /usr/lib/xpbsmon/tclIndex point to
non-existent files
https://bugs.launchpad.net/bugs/441063
You received this bug notification because you are a
The torque 2.4 packages have arrived in Maverick. Please kindly
investigate if the bug is still valid.
--
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
https://bugs.launchpad.net/bugs/360827
You received this bug notification because you are a member of Ubuntu
Bugs, which
Jordi said that he can send emails and he fixed something for it in the
Torque 2.4 packages that are now in Maverick. Please be so kind to
install those and report again/close this bug.
--
pbs_server does not email server events
https://bugs.launchpad.net/bugs/474727
You received this bug
Same here, out of the blue with maverick, otherwise always kept up to
date:
$ sudo apt-get -u dist-upgrade
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...
Traceback (most recent call last):
File /usr/sbin/update-python-modules, line
The funny thing is that until another apt-get install python-minimal
is performed, one cannot even report the bug with ubuntu-bug, since
this also requires the shutil module :)
--
python2.6 without shlib module gets unpacked/configured before required
python2.6-minimal
Hi Daniel,
On 07/13/2010 10:35 PM, Daniel Hahler wrote:
I'm updating the package for Maverick.
As said previously:
1. For existing releases, you'll need a StabeReleaseUpdate (paperwork), or
request a backport via e.g. lucid-backports
2. Please create a new bug for new upstream release
Public bug reported:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu
status new
importance wishlist
subscribe ubuntu-sponsors
done
Please sync gentle 1.9+cvs20100605+dfsg-2 (universe) from Debian
unstable (contrib)
All changelog entries:
gentle (1.9+cvs20100605+dfsg-2)
Public bug reported:
JAVA_HOME was set to /usr, just because
$ ls -l /usr/bin/java
lrwxrwxrwx 1 root root 22 May 26 17:01 /usr/bin/java - /etc/alternatives/java
and not directly to anything in
# ls -l /usr/lib/jvm
total 12
lrwxrwxrwx 1 root root 14 May 17 14:55 default-java - java-6-openjdk
On 07/21/2010 08:53 AM, KevinM wrote:
Public bug reported:
Binary package hint: boinc
This problem occurs occasionally (approximately once every 20 boots). I am
normally attached to at least 7 projects )including SETi, rosetta, malaria.
No projects start and none are displayed under the
Public bug reported:
Hello,
my GENtle package was recently accepted by Debian's ftpmasters and somehow it
is still not in maverick . Well, ok, I am not the most patient individual in
the world. Is there something I could do to accelerate this process?
Cheers,
Steffen
** Affects: ubuntu
Public bug reported:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu
status new
importance wishlist
subscribe ubuntu-sponsors
done
Please sync python-cogent 1.4.1-1 (universe) from Debian sid (non-free)
The license allows the use only for non-commercial projects, which
is
On 07/30/2010 09:42 AM, Daniel Holbach wrote:
This package fails to build.
he following NEW packages will be installed:
autoconf{a} automake{a} autotools-dev{a} bsdmainutils{a} cdbs{a}
debhelper{a} fdupes{a} file{a} gettext{a} gettext-base{a} groff-base{a}
html2text{a}
intltool{a}
Hello, there is something to it. Screen has always worked for me, but no
longer for some reason. Weird. There is no /var/run/screen existing on
my machine.
I am running 4.0.3-14ubuntu3 .
$ ls -la /var/run | head -2
total 64
drwxr-xr-x 19 root root720 2010-06-18 13:52 .
$ ls -la
On 06/02/2010 12:02 PM, Thierry Carrez wrote:
Which version of eucalyptus are you running ? Which logs do you find
those warnings in ?
1.6.2 is the version, sadly with some confusion now on my side if this
was from my initial attempt from the stable 1.6.2 release, the Debian sid one
or the
Public bug reported:
Binary package hint: pbuilder
Hello,
I had a fine install (at least pbuilder --execute -- /bin/echo huhu worked) of
squeeze on a Lucid system. Now I wanted to upgrade to sid and did
$ sudo pbuilder --update --override-config --distribution sid
I: Upgrading for
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48857710/Dependencies.txt
--
pbuilder --update fails with --distribution-sid
https://bugs.launchpad.net/bugs/583720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 08/22/2010 01:41 PM, Skip Guenter wrote:
OK, I got it working with the Debian package (actually used the PPA
v5.10.58 x64)... This is ugly but if nothing else it's another
confirmation that we've got a boinc user permissions problem with the
ATI driver.
In /etc/default/boinc-client I set
Thank you, Jonathan.
Steffen
--
Sync gentle 1.9+cvs20100605+dfsg-2 (universe) from Debian unstable (contrib)
https://bugs.launchpad.net/bugs/605402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello,
On 09/05/2010 01:18 AM, Kai Presler wrote:
Same issue for me as well.
we should then just test for the success of chrt and issue some warning
message.
Cheers,
Steffen
--
package boinc-client 6.10.58+dfsg-2 failed to install/upgrade: subprocess
installed post-installation script
The bug is in the error message, I tend to think. Daniel, please make
your magic words more prominent. Best, Steffen
--
Cannot upload bundle to Walrus
https://bugs.launchpad.net/bugs/429590
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 154 matches
Mail list logo
