We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Visibility changed to: Private
--
ardour-2.2 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/191751
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
in 8.10
Il giorno sab, 29/11/2008 alle 03.37 +, Daniel T Chen ha scritto:
> Is this symptom still reproducible in 8.10 or 9.04?
>
> ** Changed in: ardour (Ubuntu)
>Status: New => Incomplete
>
--
ardour-2.2 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/191751
You received this
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: ardour (Ubuntu)
Status: New => Incomplete
--
ardour-2.2 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/191751
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
** Visibility changed to: Public
--
ardour-2.2 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/191751
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/