** Changed in: boinc
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this b
This bug was fixed in the package boinc - 7.6.33+dfsg-10
---
boinc (7.6.33+dfsg-10) unstable; urgency=medium
* New upload changing the working dir during execve
-- Gianfranco Costamagna Wed, 15 Mar 2017
17:53:03 +0100
** Changed in: boinc (Ubuntu)
Status: Fix Committed =
** Changed in: boinc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notification
** Changed in: boinc (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about th
** Changed in: boinc
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go
** 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 Ubunt
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
https://github.co
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
B
seems that nobody is interested in boinc anymore, and I don't have time
to look at it :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To
I'm guessing that nobody is interested in this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go to
nope, I'll try to have a look soon (I hope)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go to:
ht
I don't suppose there's been any kind of response?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go
** Also affects: boinc
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications a
forwarded to boinc_alpha mail list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go to:
https://bug
The process for reporting a bug upstream to BOINC seems to be to send an
e-mail to a black hole, and then forget about it. The Trac system that
they have installed is broken so there's no way at all to record a bug
report!
http://boinc.berkeley.edu/trac/register
--
You received this bug notifica
** Changed in: boinc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: boinc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmg
no way, the patch wasn't working for some reasons, I need to further
investigate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage n
Was the patch accepted upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notifications about this bug go to:
https://bugs.
This still exists in saucy release 7.1.20+dfsg-1
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second instance
To manage notificatio
No problem I read it :-)
Anyway the problem is how the exec calls boincmgr, I think I patched it
yesterday night but only locally, before pushing anything to debian I
just want to be sure the patch works in any case...
In the meanwhile you can run another boinc manager instance with
boincmgr --m
Mail sent. Mailing list is private.
** Also affects: boinc (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launc
Hi Ken, I see the same behaviour in my machines, definitively a bug, but
I have this bug too with the official client build (from berkeley/dl
website).
So I suggest you to report it directly upstream, otherwise I'll have a
look at the source code, but this is an upstream bug, so is stupid to
fix i
Yep, all versions I've tried from the official build up to 7.0.47 from
the ppa have the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115607
Title:
boincmgr unable to launch a second
Are you saying you have the problem with the official build too?
Could you please try boinc 7.0.47 from ppa:costamagnagianfranco/boinc
ppa?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/111560
24 matches
Mail list logo
