https://bugzilla.novell.com/show_bug.cgi?id=736115 https://bugzilla.novell.com/show_bug.cgi?id=736115#c6 --- Comment #6 from Dave Plater <davejplater@gmail.com> 2011-12-15 12:49:59 UTC --- You need the matching libjack0. I've just checked and 12.1 x86_64 is published and the jack rpm requires libjack0-version-release so installing release 137 jack will pull in the correct libjack0. If you wanted the i586 derivative the 12.1 build server keeps hanging, I've just kicked it again. Use "zypper -v in --from <reponame> jack libjack-devel" and if the bug is still around in the non dbus jack also install jack-debugsource, jack-debuginfo, libjack0-debuginfo, ffado-debugsource, ffado-debuginfo and libffado2-debuginfo along with the binary rpms After refreshing the plater repo paste this as one line to the cli : zypper -v in --from platerreponame jack libjack-devel jack-debugsource jack-debuginfo libjack0-debuginfo ffado ffado-debugsource ffado-debuginfo libffado2-debuginfo Check that all of the version and release numbers match in the debugsource and info packages ie. all jack related rpms and debug rpms should be 1.9.7-137.1 and the ffado ones 2.0.1-74.1. The last digit of the release isn't that important, it's a rebuild without change counter but the major release counts the rebuilds triggered by source change. Release 136 has dbus and 137 hasn't. This is why usually require version-release if I can but it's not a common practise and it is even frowned upon due to triggering excessive package installation. Then if you can give me a good "gdb qjackctl" backtrace (don't use plater qjackctl, it's got no debug rpms) maybe I can track the problem myself. Note: If the bug goes away with non dbus jack don't install the debug rpms they're very difficult to get rid of and they don't always update with their packages, causing debugging headaches in the future. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.