** Bug watch removed: Debian Bug tracker #947376
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947376
** Also affects: pavucontrol (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958178
Importance: Unknown
Status: Unknown
** Changed in: pavucontrol (Ubuntu)
These are the relevant upstream bugs at Debian, probably all the same root
cause:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947376
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958178
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960741
** Bug watch added: Debian Bug
** Changed in: libffado (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libffado in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/649542
Title:
New
** Changed in: libffado (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libffado in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1097308
Title:
No refusal, just that I got this information meanwhile from FFADO
maintainer (before I got around reporting it at Debian) and it solved it
for me. So I shared that it here because perhaps it is not a bug at all.
I have also been relaying feedback from the FFADO maintainer on issues
reported at
After evaluating this bug, it would be impossible to upgrade the verison
of FFADO in Ubuntu 18.04 to a newer version, especially considering it's
in the Universe repository which is only supported for 3 years. Closing.
** Changed in: libffado (Ubuntu)
Status: New => Won't Fix
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Debian/Bugs.
** Changed in: libffado (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libffado in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/445823
Title:
** Changed in: libffado (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libffado in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1790707
Title:
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: libffado (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libffado in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/461628
Title:
Pander, I don't know why you refuse to report these bugs to Debian. It's
a Debain-imported package and no Ubuntu developer has touched it. The
way it works is that Ubuntu syncs packages from Debian during the
development cycle. Unless you see a "-xUbuntux" in the package name,
it's a Debian
Ffrom FFADO maintainer:
Bug: No output from Presonus Firebox
Suggestion:
This appears to be a request to make the Firebox work with
Pulseaudio as the OP didn't want to (or couldn't) use JACK.
This bug could be marked as "will not fix" since it is unlikely that
>From FFADO maintainer:
Bug: More xruns under new Firewire kernel stack compared to the old
stack.
Suggestion:
The final comment in this bug report suggests that an upgrade to
Ubuntu 11.04 resolved the problem. The bug should therefore be
closed.
--
You received
>From FFADO maintainer:
Bug: Jack crashes and consumes 100% CPU after resume from suspend
Suggestion:
FFADO was not set up to deal cleanly with suspend and resume, mainly
because the nature of Firewire interfaces makes this a very difficult
problem to solve. In
>From FFADO maintainer:
Bug: Echo Audiofire 12 not working on Ubuntu 12.10
Suggestion:
Follow up comments indicate that this was resolved in r2451 and
r2452. The bug should therefore be closed.
--
You received this bug notification because you are a member of Ubuntu
Studio
>From FFADO maintainer:
Bug: Installation error message for FFADO 2.1.0.
Suggestion:
This was a problem with the installation process overseen by the
Ubuntu package manager. It is not a FFADO problem and should
probably be closed appropriately.
--
You received this
>From FFADO maintainer:
Bug: Buzzing from MOTU 828 Mk2
Suggestion:
This was probably caused by the use of a generic kernel (neither
"lowlatency" or "rt"). No further information is available. Given
the age of the report the bug should probably just be closed.
--
>From FFADO maintainer:
Bug: ffado-mixer crashes immediately on invocation with ValueError
Suggestion:
This is a python error in ffado-mixer. An upgrade to FFADO 2.4.4
will almost certainly fix this. If not, the OP is encouraged to get
in touch through the
>From FFADO maintainer:
Bug: ffado-mixer crash in import_pyqt.py
(the PyQt5.QtCore and PyQt4.QtCore modules both wrap the QObject class)
Suggestion:
The root cause of the crash is the import of modules from both PyQt4
and PyQt4.
This has almost certainly been
>From FFADO maintainer:
Bug: Could not use Personus Firebox
Suggestion:
This bug report is over 10 years old. It should be closed unless
updated information is available. My understanding based on the
FFADO "configuration" file is that the Firebox is currently
>From FFADO maintainer:
Bug: "xdg-desktop-icon: command not found" reported during
installation.
Suggestion:
This is a problem associated with the Ubuntu package manager and the
installation process it was overseeing. It has nothing to do with
FFADO.
--
You received
>From FFADO maintainer:
Bug: segfault in "ffado-test Discover"
Suggestion:
The reporter acknowledges that prior to running ffado-test "there
already were problems with the Firewire connection". The crash is
associated with a bus reset. While bus resets should be
>From FFADO maintainer:
Bug: Segfault in ffado-test-streaming, seemingly while shutting down.
This may be due to the user stopping the program or an xrun. More
details about the scenario are required.
Suggestion:
Test using jackd rather than ffado-test-streaming.
>From FFADO maintainer:
Bug: Python error.
Suggestion:
Upgrade to FFADO 2.4.4 and retest.
The ffado-diag script saw significant changes in early 2018, between
FFADO 2.4.0 and 2.4.1.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which
As requested by a maintainer of FFADE, the output of the diagnose tool.
This is most likely to do with device rights for the user or group.
UPDATE: When I looked at the output of the diagnose tool, I see two
Firewire devices with different user/group rights. (The card in the
desktop has actually
26 matches
Mail list logo
