Now then, with that oud of the way, what is your output when you do ldd boincmgr (that's el dee dee)?

you can easily just run ./run_client (without the added --daemon), to see the output in the terminal window.

I'm not remembering the whole thread (and it's way too early/late - depending on how you look at it - to go back through it).

Is there something that seems to trigger the crash? If there is, you could always run it under gdb. I've only done it once, and with help, so I'm not any use beyond the suggestion.

I'm not remembering the whole thread (and it's way too early/late - depending on how you look at it - to go back through it).

Is there something that seems to trigger the crash? If there is, you could always run it under gdb. I've only done it once, and with help, so I'm not any use beyond the suggestion.

...

It seems, but only seems, that it crashes after a hydrogen@home work unit has been downloaded. But I cannot believe downloading a work unit would do it. It seems, but only seems, that the hydrogen@home work unit does not get started. But this could be because it starts and causes the crash before the boinc client gets around to logging that it started. Many hydrogen@home work units complete, many of them successfully.

Well I have now run both machines for a little over a week with hydrogen@home getting no work units and the clients have not crashed. I will try for another week, but it is suggestive...

Hi,

not sure if someone else allready posted it but i do think 6.2.xx is broken like hell.

I've seen this on numberous project while beeing paired with some wingmen that use 6.2.xx
It's allways the same message...

<core_client_version>6.2.14</core_client_version>
<![CDATA[
<message>
Can't get shared memory segment name: shmget() failed
</message>
]]>

example:
http://genlife.is-a-geek.org/genlife/workunit.php?wuid=18194

seen some crashes on Milkyway and S@H too... always the same pattern/error message...

I just had the same issue on Centos.

The fix for me - believe it or not - was

> yum install libXcomposite

!

Changing the font is the wrong way to solve your problem. Adjust the width of the fields instead. You can adjust the width of the fields by grabbing the right side of the field box with the mouse. Slide the side left to shrink the field. Slide right to expand the field.

To grab the right side of the field box, carefully hover the mouse pointer over the right side of the field box. When the grabber (a small left-right arrow) appears, press and hold the mouse button (usually the left button). Hold the button down while sliding. When you release the button the grabber changes back to a normal pointer.

How new/old is CentOS 5? I know it's Red Hat based, but that's about it.

Couple things...

You don't need to unpack the .sh as root. You can do that with your regular user account.

It's possible that the Ubuntu build's manager won't work for you. You can try an older version. They are here, scroll down to the bottom and try 5.8.16 and see if that runs for you.

When running boincmgr in Red Hat Enterprise Linux 5 with a 1024(height) x 1280(width) monitor, the size of the type is too large to get the fields on the screen even when the window is the full width of the screen.

This was not the case with 5.10.45 or even 6.2.11. Of course those used an older version of boincmgr.

Can you either make the type size smaller, or provide a way for the user to control it?

I'm not remembering the whole thread (and it's way too early/late - depending on how you look at it - to go back through it).

Is there something that seems to trigger the crash? If there is, you could always run it under gdb. I've only done it once, and with help, so I'm not any use beyond the suggestion.

...

It seems, but only seems, that it crashes after a hydrogen@home work unit has been downloaded. But I cannot believe downloading a work unit would do it. It seems, but only seems, that the hydrogen@home work unit does not get started. But this could be because it starts and causes the crash before the boinc client gets around to logging that it started. Many hydrogen@home work units complete, many of them successfully.

I'm not remembering the whole thread (and it's way too early/late - depending on how you look at it - to go back through it).

Is there something that seems to trigger the crash? If there is, you could always run it under gdb. I've only done it once, and with help, so I'm not any use beyond the suggestion.

In the mean time, I've forwarded all information you've given to the developers. I am now waiting for one of them to tell me what to ask you, or him to dive into the thread all by himself. Whichever comes first. ;-)

Excuse my complete ignorance but what is trillian.error.log doing in a BOINC log? Googling this only ever shows up on Seti forum and now here.

Used to use an alternate msnmgr called Trillian, so is this something u use and would you mind running BOINC if so without this program active?