Hello everyone,

Im getting errors when starting boinc-manager from the commandline.
So I cant launch boinc.
The error says :
boincmgr: xcb_xlib.c:42: xcb_xlib_lock: Controletest '!c->xlib.lock' faalt.
Afgebroken


Can someone give me a hint in solving this please ?
I use Suse10.3.

Many Thanx in advance !
Francis

Hi Francis,

Got the same problem and you're not the only one.
I'm running OpenSuSE 10.3 on an Athlon X2 3800+ (64-bit) and an Intel T2400 duocore (32-bit).

I tried 4 different BOINC-clients and they all don't work. It seems there is a problem trying to connect to the localhost.

In this massageboard there is also a message from dietyyli running a Fedora beta version with the same problem.

I tried running the windows version through BOINC. It worked but gave some funny results. Besides the architecture not being right (Intel instead of AMD) the CPU-time remained 0 (zero) and the claimed credit as well. Now I'm waiting to see what Leiden will do with these succesfull wu's with 0 claimed credits.

For the rest I'm waiting to see the problem fixed.

The best way to report this directly to the developers, is to register at BOINC Trac and make a new ticket about it.

Massageborden, he? Dat is een nieuwe. Waar kan ik me aanmelden voor een massage? :-)

---

Bedankt de heren, Thanx guy's,

I send a report to Robin, in Holland, I'll see what I get from there :-)
Older versions alway give me gtk-errors.
I'll see if I can get in the track list as menioned by Ageless :-)

Offrecord:
Als je een massage wenst, neem gerust contact op met mijn vrouw, das een massagetherapeute :-) PM mee :-) :-)

If need be, I'm willing to open a ticket & point to this thread.

---

Please do Ageless !

Many thanx !

I'm assuming this is with BOINC 5.10.8?
Has anyone tried BOINC 5.10.21?

32bit version
64bit version

I'll add that info to the ticket.
Ticket in the mean time is here: ticket #432

---

I'm assuming this is with BOINC 5.10.8?
Has anyone tried BOINC 5.10.21?

32bit version
64bit version

I'll add that info to the ticket.
Ticket in the mean time is here: ticket #432

Yes, I tried 5.4.11, 5.8.20 and 5.10.21 (Linux/X64).
With WINE I ran 5.10.20 (Win98+, Win2000+)
Only version 5.8.20 gave a GUI and running from a console gave the above mentioned error, the other Linux clients only ran from console but wouldn't start.

If running 5.8.20 (GUI) you get the message "disconnected from localhost". Trying to go o "Connect to computer.." freezes the GUI (In the Win-version it is possible to connect to the "Localhost".

The forumthread to the Fedora 8 beta version is: http://boinc.berkeley.edu/dev/forum_thread.php?id=2145


Berend

Thanks. Information added.

---

Thanks. Information added.

Forgot one other thing.

I don't know exactly which forum it was but it was suggested to install the 32-bit compatibility packages and the compat-package. So I did but that was also in vain.

Berend

I know if you run in consistent exit code 22 errors on all results that you have to add 32bit libs. See this FAQ for that.

But since neither of you can even start BOINC Manager, I don't think that is related. I could be wrong, though. Is Suse 10.3 a 32bit or 64bit OS?

---

DF,

I run the 32-bit version on an HP laptop (Intel duocore T2400) and the 64-bit version on a home-built AMD Athlon X2 3800+ (that's the one of course I put the compatibility packages on.

If you're interested in what Leiden is going to do with the wine-ran version:
http://boinc.gorlaeus.net/results.php?hostid=31813

The arch. is there an Intel instead of an AMD Athlon X2

Berend

I'm assuming this is with BOINC 5.10.8?
Has anyone tried BOINC 5.10.21?


I tried them both, it is the .21 that gave the xlib errors, the .18 gives me plenty gtk errors.
It is an 32 bit install of this OS, but yes, an AMD based-platform.

OK, but as ever, I don't see how the vendor of CPU could affect the executing of any program. It **is** possible to have differences in (comparable) run time of tasks/applications that run under BOINC as shown on Einstein and other projects, but not the incapability of running BOINC itself.

So Intel or AMD, it doesn't make a difference. Both should be perfectly able to start BOINC from a commandline.

---

DJ (Dear Jord - sounds nice)

Just some remarks annex a question.

I installed the PAN newsreader but not the one that came with the original OpenSuSE 10.3 distro (version 0.14.2-101). I liked the one that came with the 10.1 distro (version 0.132-33).
After installing it, it wouldn't run because it couldn't find the executable. So through YaST I found out that the executable was now situated in the /opt/gnome/bin directory. Unfortunately I didn't write down where it used to be installed but it wasn't in the /opt/gnome directory.

Because it's a Gnome program and I'm standard running KDE I thought that there might lay a clue.
I tried to run BOINC in KDE, Gnome and FVWM2. In vain.

Because of this PAN-issue I have a question. Could it be that the BOINC client is pointing the wrong directories?
Unfortunately I'm not quite good in the directory structure of Linux systems and am a zero in debugging programs.

Berend

I have a question. Could it be that the BOINC client is pointing the wrong directories? Unfortunately I'm not quite good in the directory structure of Linux systems and am a zero in debugging programs.

Don't look at me, I'm even more of a n00b in Linux. All the abbreviations you just threw at me... I don't know what they are.

I'm sure though that someone else will be along at one point in time, Nicolas perhaps, who can answer to those specifics.

As to where the BOINC client is pointing to, open up the run_manager or run_client script. But that's all the help I can give, until I change to my Mepis installation and go fiddle with things. (this weekend)

---

I got this xlib error, too.
It occurs on my dualcore linux machine with SUSE 10.3 64 Bit.
Any idea when this might be fixed?

I got this xlib error, too.
It occurs on my dualcore linux machine with SUSE 10.3 64 Bit.
Any idea when this might be fixed?

I'm on it but there is no solution so far. The amount of messages about this problem is growing.

The only solution now is to run the Windows BOINC client if you're in for the points. It's obvious you have to install WINE.
I tried this (see Message 12972 above) and it generates points althoug the CPU-time will remain zero as well as the claimed credits.
I ran this client (Win98+/200+) on the Leiden and Malaria projects because they have small wu's. In one case progression stopped and I had to kill the app. but when you restart it it restores itself perfectly.

Only one remark could be made at the beginning: "Can't connect to computer" But through the tab "Advanced" you can "Connect to computer" to localhost.

Berend

OK got the BOINC client running (5.10.8) in a console (./run_client).
I installed kboincspy, ran it and added the BOINC location (~/BOINC/client_state.xml) and allowed Leiden to get work.

It's crunching now, but actually I like to get the BOINC GUI back - so just keep on waiting a little.

Berend

I have asked one of the developers to come take a look. This may take a little while because he's over his ears in work on the new BOINC 6.0 version as well as trying to release the last (? we hope) 5.10 version.

---