How do I run the BOINC GUI on Linux?
30 Aug 2005 2:48:45 UTC
Topic 189791
(moderation:
I've installed Gentoo 2.6.12-r9 with X and Xfce4. I've gotten BOINC v4.72 installed from a terminal and the command line version seems to run ok. Now I'm interested in seeing at how the GUI version looks. (This is my main desktop system at home, so I might want to run it this way from time to time.)
When I try to run boincmgr from a terminal, the window is filled with the following text before exiting to the command prompt: "SIGABRT: abort called"
Ok Linux guru's, what do I need to do in order to get this working? Thanks for your assistance in advance.
How do I run the BOINC GUI on Linux?
)
I'm not a guru, but I've noticed that boincmgr basically only likes to work with GNOME. With me it acts kind of funny under both KDE and xfce.
Have a suspicion it's written with a cross platform toolkit (wxwindows?) whose libraries don't interplay well with all windows managers.
Short term solution might be to switch to GNOME. It has the best bells and whistles, anyway. It is a real memory hog, though.
It that does not work, maybe it would be a good idea to compile boinc from source.
Greetings, Mr. Ragnar Schroder
RE: I've installed Gentoo
)
Use version 4.43 of the boinc client, from http://boinc.berkeley.edu/download.php.
Greetings, Mr Ragnar Schroder
RE: Use version 4.43 of the
)
Thanks, I've downgraded to the standard 4.43 now.
I'm still having some problems though. When I start up Xfce4 and try to run boincmgr in a terminal, I get a couple messages and then a very distorted BOINC gui window opens up with everything blacked out and illegible.
Connection refused
execvp(/boinc) failed with error 2!
connect: Operation now in progress
init_poll: get_socket_error():111
init_poll: get_socket_error():111
already tried both ports, giving up
SIGPIPE: write on a pipe with no readersend: -1
send: Broken pipe
I have to close down the BOINC gui window since I can't read anything on it. :(
I'm pretty sure I'm usinng the right video drivers. I emerged the nvidia-kernel and nvidia-glx and installed them straight by the instructions on the gentoo online install documents.
The learning curve continues.
)
The learning curve continues. :)
I found I needed to add a DefaultDepth 24 statement into my xorg.conf in order to get the graphics to display properly. (My color bit depth was set too low before.) I was then able to get boincmgr to open up and display properly but it was giving me an odd connection failed message. It wasn't until I acidently started boinc in one window and then started boincmgr in another that BOINC opened up and started looking and acting like it does on WinXP. Is this the way it's intended to work? Run boinc first and then boincmgr? Rather a crazy way of doing things, and not explained anywhere that I've seen so far. Ah well...
Thanks for your help, Ragnar!
RE: giving me an odd
)
I get the "init_poll: get_socket_error():111" message too. Does not matter.
You should not have boincmgr running at all, since it seems to eat a significant number of CPU cycles. As long as the window is displayed, that is.
You can see that in GNOME by adding the "System monitor" utility to the panel. Have not found any similar "native" xfce app.
Greetings, Mr Ragnar Schroder
RE: You can see that in
)
Check out GKrellM for an excellent system monitoring tool that works under most if not all window managers.
Chuck