Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

2019-08-15 Thread Arnaldo Pirrone
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)
Foreign Architectures: i386

Kernel: Linux 5.2.0-8.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swami depends on:
ii  libc6   2.28-10
ii  libfftw3-single33.3.8-2
ii  libfluidsynth1  1.1.11-4
ii  libglib2.0-02.60.6-1
ii  libgnomecanvas2-0   2.30.3-4
ii  libgtk2.0-0 2.24.32-3
ii  libinstpatch-1.0-0  1.0.0-7
ii  libswami0   2.0.0+svn389-5+b11

Versions of packages swami recommends:
ii  jackd  5+nmu1

swami suggests no packages.

-- no debconf information



Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

2018-10-02 Thread Simon Budig
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. Sorry, I don't have 
swami debug symbols.

(gdb) run
Starting program: /usr/bin/swami 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
libswami-Message: 01:09:24.220: Loading plugins from /usr/lib/swami
libswami-Message: 01:09:24.322: Loaded 4 plugins

Program received signal SIGSEGV, Segmentation fault.
0x775d6b7d in g_type_fundamental () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(gdb) bt
#0  0x775d6b7d in g_type_fundamental () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1  0x775ba851 in g_object_new_with_properties () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2  0x775bb581 in g_object_new () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x77d4e9cc in  () at /usr/lib/x86_64-linux-gnu/libswamigui.so.0
#4  0x775d6677 in g_type_create_instance () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x775b9398 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x775bab15 in g_object_new_with_properties () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x775bb581 in g_object_new () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x77d4ff6a in swamigui_root_new () at 
/usr/lib/x86_64-linux-gnu/libswamigui.so.0
#9  0x5445 in main ()

Interestingly the segfault does not happen when swami is running within
valgrind. valgrind also does not show any warnings that might explain the
segfault.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages swami depends on:
ii  libc6   2.27-6
ii  libfftw3-single33.3.8-2
ii  libfluidsynth1  1.1.11-1
ii  libglib2.0-02.58.1-2
ii  libgnomecanvas2-0   2.30.3-4
ii  libgtk2.0-0 2.24.32-3
ii  libinstpatch-1.0-0  1.0.0-7
ii  libswami0   2.0.0+svn389-5

Versions of packages swami recommends:
ii  jackd  5

swami suggests no packages.

-- debconf-show failed



Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

2018-02-09 Thread Michael Hatzold
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)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

"Speicherzugriffsfehler" which I think ist german for Segfault, but not sure.


dmesg shows on consecutive attempts to open it:

[ 3965.728274] swami[25701]: segfault at 315adf34 ip 7fdf11874d64 sp
7ffd3b177e68 error 4 in libgobject-2.0.so.0.5400.3[7fdf1184+52000]
[ 5635.507587] swami[5610]: segfault at 51b66034 ip 7f58c369dd64 sp
7ffc1ae92038 error 4 in libgobject-2.0.so.0.5400.3[7f58c3669000+52000]
[ 5664.362004] swami[6051]: segfault at fb09fa14 ip 7fda2546dd64 sp
7ffe427aac18 error 5 in libgobject-2.0.so.0.5400.3[7fda25439000+52000]
[ 5688.961412] swami[6316]: segfault at 1708d04 ip 7f96c8682d64 sp
7ffc6f135878 error 4 in libgobject-2.0.so.0.5400.3[7f96c864e000+52000]
[11559.981128] swami[14138]: segfault at 83b40d04 ip 7f4159ca2d64
sp 7ffc11195d88 error 5 in libgobject-2.0.so.0.5400.3[7f4159c6e000+52000]



*** End of the template - remove these template lines ***



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.1-towo.2-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swami depends on:
ii  libc6   2.26-6
ii  libfftw3-single33.3.7-1
ii  libfluidsynth1  1.1.9-1
ii  libglib2.0-02.54.3-2
ii  libgnomecanvas2-0   2.30.3-3
ii  libgtk2.0-0 2.24.32-1
ii  libinstpatch-1.0-0  1.0.0-6
ii  libswami0   2.0.0+svn389-5

Versions of packages swami recommends:
ii  jackd  5

swami suggests no packages.

-- no debconf information



Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

2017-09-02 Thread paul ulrich niggli
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 outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swami depends on:
ii  libart-2.0-2 2.3.21-2+b2
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo21.14.10-1
ii  libfftw3-single3 3.3.6p2-1
ii  libfluidsynth1   1.1.6-4
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglade2-0  1:2.6.4-2+b1
ii  libglib2.0-0 2.53.4-3
ii  libgnomecanvas2-02.30.3-3
ii  libgtk2.0-0  2.24.31-2
ii  libinstpatch-1.0-0   1.0.0-6
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpangoft2-1.0-01.40.6-1
ii  librsvg2-2   2.40.18-1
ii  libsndfile1  1.0.28-4
ii  libswami02.0.0+svn389-3
ii  libxml2  2.9.4+dfsg1-3.1

Versions of packages swami recommends:
ii  jackd  5

swami suggests no packages.

-- no debconf information