On 2/8/20 5:25 PM, paul ulrich niggli wrote:
On Sun, 3 Sep 2017 13:57:46 +0200 paul ulrich niggli
wrote:
> Dear Maintainer,
today I updated swami and can confirm,
it works again.
many thanks
paul niggli
On Sun, 3 Sep 2017 13:57:46 +0200 paul ulrich niggli
wrote:
> Dear Maintainer,
still no luck with the new version.
first I had to copy /usr/share/swami to my
home as /share/swami.and when I restart fluidsynth I get
(swami:15991): libswami-CRITICAL **: 17:23:54.980: swami_wavetbl_close:
ass
Package: swami
Version: 2.0.0+svn389-5+b11
Followup-For: Bug #874051
Hi,
I can confirm the bug is still present.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
F
According to the Red Hat bug report for their Swami package, the Swami
segfault is caused by an invalid pointer cast (with GPOINTER_TO_INT) on
64-bit systems. Link here:
https://bugzilla.redhat.com/show_bug.cgi?id=1541394#c2
Package: swami
Version: 2.0.0+svn389-5
Followup-For: Bug #874051
Dear Maintainer,
The segfault seems to be related to the fluidsynth_plugin.so plugin. If I
rename this plugin the crash no longer happens (there are other warnings then).
Here is a stacktrace from gdb when the segfault happens
As mentioned above,
swami_2.0.0+svn389-3_amd64.deb and libswami0_2.0.0+svn389-3_amd64.deb
don't show this segfault. Thus this version can be used as a workaround.
Package: swami
Version: 2.0.0+svn389-5
Followup-For: Bug #874051
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Opening swami
* What exactly did you do (or not do) that was effective (or
ineffective
Dear Maintainer,
sorry for my noobish reportbug.
even novice was to complicated
for me.
I like to give you some more infos.
I do have 2 computers,1 laptop and
1 desktop.both amd64 and debian testing.
on my desktop i have swami -3 pinned,as it
works.on my laptop i do have always the latest
Package: swami
Version: 2.0.0+svn389-3
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outco
9 matches
Mail list logo
