Public bug reported:
Couldn't convince Gimp to separate layers. It just crashed.
ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gimp-plugin-registry 9.20200927build1
ProcVersionSignature: Ubuntu 5.19.0-1003.3-lowlatency 5.19.0
Uname: Linux 5.19.0-1003-lowlatency x86_64
ApportVersion:
Public bug reported:
Crashes on startup
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: ffado-mixer-qt4 2.4.1-0.1
ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17
Uname: Linux 4.17.0-9-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: XFCE
Public bug reported:
Trying to insert the plugin.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: ardour 1:5.12.0-3
ProcVersionSignature: Ubuntu 4.17.0-6.7-lowlatency 4.17.9
Uname: Linux 4.17.0-6-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CrashCounter: 1
Public bug reported:
Probably happened in connection with shotcut crashing while being
connected to Jackd.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: jackd2 1.9.12~dfsg-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
Uname: Linux 4.15.0-10-lowlatency x86_64
Since a crash is a pretty bad kind of problem, wouldn't that warrant a
backport?
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to aeolus in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1708027
>From the Linux audio users list:
From: Fons Adriaensen
Subject: Re: [LAU] Trying to start Aeous gives me seg faults
Newsgroups: gmane.linux.audio.users
To: linux-audio-user-cunTk1MwBs/cejeg2xfrv2d2fqjk+...@public.gmane.org
Date: Mon, 18 Sep 2017
#6 also would be consistent with me seeing this problem only after
converting my system to 64 bits: it is perfectly conceivable that this
would increase the stack size requirements.
When I started computing, 128kB would have been double the total address
space (let alone local variables). Sigh.
Public bug reported:
When running ffado-test Discover (admittedly after there already were
problems with the Firewire connection) I got the following console
output:
---
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Public bug reported:
Just called ffado-test-streaming on the current setup (one builtin Ricoh
Firewire controller without attached hardware, one Expresscard with TI
chipset and an Alesis io|14 attached) and it crashed after some test
duration, apparently before wanting to exit.
ProblemType:
Public bug reported:
No idea what this is about. Ffado seems very unstable recently. C++
API change or something?
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: ffado-tools 2.3.0-2
ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5
Uname: Linux 4.12.0-11-lowlatency x86_64
Only a single device connected, the connection might have been
unreliable while I plugged a headphone. dmesg says:
[ 566.417496] firewire_core :15:00.1: created device fw1: GUID
0005950400400fc2, S400
[ 567.712261] firewire_core :15:00.1: BM lock failed (timeout), making
local node
*** This bug is a duplicate of bug 1708027 ***
https://bugs.launchpad.net/bugs/1708027
Public bug reported:
Happened when switching registers.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: aeolus 0.9.0-2
ProcVersionSignature: Ubuntu 4.11.0-13.19-lowlatency 4.11.12
Uname: Linux
Public bug reported:
Updated to ubuntustudio on amd64. Crash also occurs with user-level
config files/directories renamed, so is not dependent on them.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: aeolus 0.9.0-2
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname: Linux
Public bug reported:
Just calling
ffado-diag --help
is sufficient for triggering the bug.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: ffado-tools 2.3.0-2
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname: Linux 4.11.0-10-lowlatency i686
ApportVersion:
Public bug reported:
Started jackd (version 2) with
jackd -d firewire -r 96000
and had a Mackie Onyx 1620 (with Firewire extension card) and an Alesis
iO|14 connected in series.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
I think that the problem is likely in
/usr/include/sound/asound.h:625
struct snd_rawmidi_params {
int stream;
size_t buffer_size; /* queue size in bytes */
size_t avail_min; /* minimum avail bytes for wakeup */
unsigned int
Public bug reported:
This may or may not be an artifact of me running a 32-bit userland on a
64-bit kernel (for debugging and testing purposes).
However, preceding the command line with "setarch i386" does not help.
The exact command line used was
jackd -d alsa -X raw -d hw:0
To trigger
Public bug reported:
Just tried starting it from the command line with a midi file. Jack
available but not running at the time I tried this.
I cannot vouch whether this was started with or without pasuspender: I
tried both since without pasuspender fluidsynth (or jack) complained
about
Public bug reported:
Happened when pressing play.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: openshot 1.4.3-1.2
ProcVersionSignature: Ubuntu 4.10.0-9.11-lowlatency 4.10.0
Uname: Linux 4.10.0-9-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: i386
CurrentDesktop: MATE
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jack-audio-connection-kit in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: jackd1
https://bugs.launchpad.net/bugs/1665743
Title:
** Also affects: jack
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jack-audio-connection-kit in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: jackd1
This is an upstream bug. I read in a source repository (mirror?)
https://github.com/jackaudio/example-clients/blob/master/server_control.c#L151-L154
struct option long_options[] = {
{"driver", 1, 0, 'd'},
{"client", 1, 0, 'c'},
};
This is missing
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jack-audio-connection-kit in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: jackd1
https://bugs.launchpad.net/bugs/1665979
Title:
23 matches
Mail list logo