We shouldn't close bugs without explaining why. So here's the
explanation: the original bug report here was fixed in an upstream
commit that was part of csound 6.10.0, which is in Ubuntu 18.04.
(Ubuntu 17.10 is end of life, so the supported way to get this fix is to
upgrade to 18.04.)
Now, there
** Changed in: csound (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to csound in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1754944
Title:
It looks like the upstream fix was just a matter of deleting one line.
We should try cherry-picking just that change first. It was part of a
commit with some other changes upstream, but here's a link to the
relevant part of the patch:
** Changed in: csound (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to csound in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1754944
Title:
[Impact]
* Currently, this is the number one bug affecting Ardour users of Ubuntu
(including Ubuntu Studio).
* Please see https://discourse.ardour.org/t/ubuntu-studio-17-10-problem/88933
, https://discourse.ardour.org/t/process-error-ardour-wont-launch/99829 ,
Fixed in upstream Debian, needs SRU.
** Changed in: csound (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to csound in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
** Changed in: ardour
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to csound in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1754944
Title:
Crash in
7 matches
Mail list logo