Fixed it for me!!! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379568
Title:
Synaptic won't start, report Xapian::DatabaseCorruptError
--
ubuntu-bugs mailing list
More details in this thread. Looks like it's a corrupted .xml file
being sent from BOINC.
http://boincstats.com/forum/forum_thread.php?id=5198
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/629740
I've got Collatz GPUGrid running on a machine that has a GTX-275 and a
GTS-250 in it with Nvidia driver 260.19.21.
I don't have Prime Grid working (they error out in 9 ~ 49 seconds).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oh yea... v10.04LTS, x64, Boinc from PPA v6.10.58
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655139
Title:
Boinc GPU tasks all end with Computation Error after update to NVidia
260.19.06
I thought this was working this morning as after creating
/etc/gdm/custom.conf and rebooting (but not logging on) I was able to go
to another machine and remote gui in and saw GPU WUs running! Applied
the change to my other ATI machines (v9.10 V10.10 but all running
v6.10.58 boinc). All seemed
I ran across an issue after changing boint to run as my primary user and
connecting to the ATI card. I don't recall this behavior when I had it
running as root but will have to retest that to be sure.
IF you logout the GPU WU running will finish but all subsequent WUs
will get repeated errors
Public bug reported:
Binary package hint: boinc
Selected Sync with BAM Account Manager from GUI Tools menu:
Fri 03 Sep 2010 11:18:24 AM CDT Fetching configuration file from
http://bam.boincstats.com/get_project_config.php
Fri 03 Sep 2010 11:18:28 AM CDT Contacting account
Since I'm using the 'sleep' for my' boinc after gdm delay' I just added
the xhost + in front of that to get:
start()
{
log_begin_msg Starting $DESC: $NAME
if is_running; then
log_progress_msg already running
else
xhost +
sleep 5
/home/skip/setfan.sh
start-stop-daemon
A guy (gfarmerfr) on the DNETC project forums told me The user
launching boinc must have a Xorg session running. We were discussing
getting the ATI cards to work on that project. He took another route
(that I like better that what I did) in that he changed ownership of the
/var/lib/boinc-client
My understanding is that upstream doesn't want to force xserver as a
pre-req for running BOINC. OK, then we need something in the install to
ask if it's going to run on a server w/o a GUI (leave as is) or in a
normal desktop environment with gdm running (set the boinc user to be
the installing
Another approach:
sudo update-rc.d -f boinc-client remove
sudo update-rc.d boinc-client defaults 99
I got this from gfarmerfr an ATI/Ubuntu user on the DNETC forums but
haven't actually tried it. It worked for gfarmerfr.
--
BOINC should run later than gdm
Brian, I booted up the Inspiron 1100 and got the usual v10.04 black
screen.
I then did Ctrl-Alt-F1 and:
sudo add-apt-repository ppa:xorg-edgers
sudo add-apt-repository ppa:brian-rogers/intel-shadow
I then created the /etc/X11/xorg.conf via nano with only:
Section Device
Identifier GPU
Public bug reported:
Binary package hint: apt-cacher
Was finding that apt-cacher-cleanup.pl had been running (I think, based
on time in top) for days, maybe weeks. Found the pid and killed it.
Got back onto that server tonight and found it running again (and again
I think for days).
Did went
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 the user to root in:
# The BOINC core client
Also confirmed the problem is bypassed with desktop effects on remote
machine turned off, don't need them on my remote machines so this is no
longer an issue for me.
--
screen content is not updated
https://bugs.launchpad.net/bugs/475093
You received this bug notification because you are a
OK, I'm using the drivers off of the AMD/ATI sight with same results so
it's good to know it's across both driver installs.
--
No GPU found
https://bugs.launchpad.net/bugs/587426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OK, another day and no major progress on finding what the issue is but
for sure:
1) The general problem of boinc getting started to soon can be confirmed
by doing the terminal command sudo /etc/init.d/boinc-client restart.
IF the GPU is then found apply the sleep 5 to the startup script that
I've
I just did a fresh install of v10.04 and driver .run package from ATI
running the PPA BOINC v6.10.58 (all x64 stuff) and BOINC reports no
usable GPUs found (HD5830). Dang... guess I'll go try the berkeley
binaries but I'm thinking it's a driver issue.
--
No GPU found
moved the Berkeley v6.10.56 binaries to /usr/bin/ and no diff. @northa,
what driver r u using from where?
--
No GPU found
https://bugs.launchpad.net/bugs/587426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Yup controlling a freshly installed remote v10.04 x64 machine gets one
screen then no updates/control until I go turn of effects on the remote
machine (ATI fglrx from ATI, HD5830). Local machine's (v9.10 x64)
Compiz and Nvidia prop drivers on local desktop seem to make no
difference.
--
screen
I think this thread is suggesting that it's a permissions problem for
boinc?? Any thoughts on that?
http://boinc.berkeley.edu/dev/forum_thread.php?id=5936
--
No GPU found
https://bugs.launchpad.net/bugs/587426
You received this bug notification because you are a member of Ubuntu
Bugs, which is
WOW! Guys I just downloaded the Berkeley package and ran it's script
which installs into /home/skip/BOINC (skip being my user account).
from the default home/skip prompt I typed BOINC/run_client and then
BOINC/run_manager and it started each up in a terminal. In the
run_client window I saw that
As I recall, many moons ago it had a random gen'd password and it the
end users complained about it until it was removed. Been here, did
this.
--
boinc manager password is empty by default
https://bugs.launchpad.net/bugs/328477
You received this bug notification because you are a member of
@ comment #8 (mine)
--
boinc-client bad signature for URL
https://bugs.launchpad.net/bugs/585547
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@ 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.
--
boinc-client bad signature for URL
Manual restart must have left something running. Sure sounds like
just need to
sudo gedit /etc/init.d/boinc-client and add the sleep 5 command as
shown below:
.
start()
{
sleep 5
log_begin_msg Starting $DESC: $NAME
if is_running; then
.
PS: Use sleep 9 if
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
@ comment #18
Under Linux (at least for CPU apps, don't know about GPU) your BOINC
tasks take a lower niced priority and so will give up their CPU slices
to other things (you on the computer) by nature of how the thread
scheduling works... Unless you've set SCHEDULE=0 (manually, it comes
turned
Public bug reported:
Binary package hint: boinc
Priority Low(est).
s...@crunch35:~$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
s...@crunch35:~$ uname -a
Linux crunch35 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 02:41:03 UTC 2010
x86_64 GNU/Linux
s...@crunch35:~$
Sleep command in the start() function works fine. Only need a sleep
value of around 5 though.
start()
{
sleep 5
log_begin_msg Starting $DESC: $NAME
if is_running; then
--
BOINC should run later than gdm
https://bugs.launchpad.net/bugs/414244
You received this bug notification because
Same problem after upgrade of Xubuntu from v8.04LTS to V10.04LTS (64b).
Moved v6.10.56 binaries to /usr/bin and resolved.
--
boinc-client bad signature for URL
https://bugs.launchpad.net/bugs/585547
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
getdeb provides BOINC v6.4.5 which works with CUDA once restarted to
pick up the nvidia driver. I assume the driver is attached either with
S20dkms-autoinstaller from this entry in /etc/X11/xorg.conf
Section Module
Loadglx
EndSection
Why was this marked as Invalid?
What Sxx level
[quote]By the way, where I mean VNC performance is Xvnc, not x11vnc.
They are 2 different programs. The performance of Xvnc is fine in Feisty
or Gutsy, but not in Hardy. The performance of x11vnc won't be as good
as Xvnc in theory, since it's started for the existing DISPLAY and need
to track the
33 matches
Mail list logo