[Bug 1142877] New: Cadence ALSA MIDI bridge and PulseAudio bridge to Jack broken in Tumbleweed
http://bugzilla.opensuse.org/show_bug.cgi?id=1142877 Bug ID: 1142877 Summary: Cadence ALSA MIDI bridge and PulseAudio bridge to Jack broken in Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: sb56637@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 811629 --> http://bugzilla.opensuse.org/attachment.cgi?id=811629&action=edit logs Hi, I'm running Tumbleweed on a Thinkpad T570 laptop with integrated Intel audio. For about a year I've been using Cadence on Tumbleweed to configure the ALSA MIDI bridge and to bridge PulseAudio through Jack. I haven't had any problems until recently. I don't update to every single TW release, only approximately every month or so. On Tuesday, 23/July of this week I updated to the latest Tumbleweed release, and that is when the problems started. Now, the ALSA MIDI bridge will not start, nor will the PulseAudio to Jack bridge start. I am attaching logs. I thought maybe it was a problem with the new 0.9 version of Cadence. But I did a fresh install of Leap 15.1 on the same laptop and added the same version 0.9 of Cadence from the Multimedia repo and it worked perfectly. Then, I upgraded that Leap installation to Tumbleweed again, and it immediately broke the new system. So I don't know if this is a kernel regression or an ALSA regression or a Jack regression or what. Thanks for the help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142877 http://bugzilla.opensuse.org/show_bug.cgi?id=1142877#c1 --- Comment #1 from S. B. <sb56637@gmail.com> --- Created attachment 811644 --> http://bugzilla.opensuse.org/attachment.cgi?id=811644&action=edit And here's the A2J (from Packman) segfault I'm getting. LTO related perhaps? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com