** Changed in: boinc
Importance: Undecided => Unknown
** Changed in: boinc
Status: New => Unknown
** Changed in: boinc
Remote watch: None => github.com/BOINC/boinc/issues #1177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It turns out there was already a bug reported for that. I added the new
info to https://github.com/BOINC/boinc/issues/1177
I don't know if I can spare the time to investigate but maybe someone on
github picks up on this.
** Bug watch added: github.com/BOINC/boinc/issues #1177
I could reproduce this with an upstream dev build. It seems something is
going wrong when calling execv() which is not reported back internally,
thus the lack of error messages. I'm filing an upstream bug report on
github.
--
You received this bug notification because you are a member of Ubuntu
The underlying problem here is not with BOINC but with the way the
driver initializes the GPU. It seems that for newer AMD/ATI GPU's you
need an active x-session (aka logged in user). Usually BOINC is started
via init-script at boot time but there is no user logged in. What you
can do is to
For the record: a fix to this was introduced in upstream today. This
issue can be closed with the next package release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140560
Title:
Manual (man)
We should continue this via mail (either personal or through a list). I
just spend some time trying to find the problem for the freeze if there
are images in notices which I could debug locally finding the bug for
this GPU not initialized will be even trickier.
--
You received this bug
I found the place in the code. In my opinion its best to just suppress
the message display function in client/current_version.cpp line 85:
show_newer_version_msg() and comment out the msg_printf_notice() call.
This will not prevent the client from talking to boinc.berkeley.edu from
time to time
This is only the check at client startup that checks the client state
file.
The actual communication is done in
client/current_version.cpp: 30
GET_CURRENT_VERSION_OP::do_rpc()
this is called only once in the same file at line 138. Commenting this
line should prevent communication and never
Yes, that would disable the new version notice at all. This will also
work for clients that already have a newer version in the state file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140597
I don't think there would be any side effects by commenting the printf
as this would prevent creation of the notice and changes to the sequence
number. But as always it's better to tackle the problem at the root,
which is what you did.
P.S.: I'm already contributing with updated man pages and
This option is already available. Just add the --no_info_fetch option to
the package init script of the BOINC client. I see if I can provide a
diff (for debian at least).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I already updated the pages. Whoever is interested in proof-reading can
drop me a message. I will send them to upstream in the next days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140560
Title:
** Patch added: patch for debian init script to supress version messages
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+attachment/3560724/+files/no_info_fetch_patch.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Your correct, I will see if I can pinpoint the version fetch in the
code.
** Patch removed: patch for debian init script to supress version messages
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+attachment/3560724/+files/no_info_fetch_patch.diff
--
You received this bug
14 matches
Mail list logo
