Tags Tags

Bug#664469: pianobooster: Segmentation fault

March 17th, 2012 - 06:50 pm ET by Carlo Stemberger | Report spam
Help Create a new topic
Package: pianobooster
Version: 0.6.4-3
Severity: grave
Justification: renders package unusable

When trying to run pianobooster, I immediately get a segmentation fault:

$ pianobooster
Errore di segmentazione

Regards,
Carlo

Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pianobooster depends on:
ii libasound2 1.0.24.1-4 shared library for ALSA applicatio
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.6.1-1 GCC support library
ii libgl1-mesa-glx [libgl1] 7.11-6 free implementation of the OpenGL
ii libqt4-opengl 4:4.7.3-5 Qt 4 OpenGL module
ii libqt4-xml 4:4.7.3-5 Qt 4 XML module
ii libqtcore4 4:4.7.3-5 Qt 4 core module
ii libqtgui4 4:4.7.3-5 Qt 4 GUI module
ii libstdc++6 4.6.1-1 GNU Standard C++ Library v3

pianobooster recommends no packages.

Versions of packages pianobooster suggests:
pn pianobooster-dbg <none> (no description available)




To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 Martin Erik Werner
March 17th, 2012 - 08:10 pm ET | Report spam

tags 664469 + unreproducible moreinfo
severity 664469 important

I am able to start pianobooster with no problem on my machine.
Hence the segfault might be hardware or driver-based?

I am decreasing the severity of the bug to 'important' since it does not
affect all users.

What sound and video card are you using? Along with which drivers?

Does
$ pianobooster -d
provide any additional info?

A backtrace of the crash might be useful:
If you install the packages 'pianobooster-dbg' and 'gdb' and then run
$ gdb pianobooster
Inside gdb:
(gdb) run
When it has crashed, still inside gdb, use:
(gdb) set logging file backtrace.log
(gdb) set logging on
(gdb) bt full
(gdb) set logging off
(gdb) quit
This will save the backtrace to the file 'backtrace.log' which might
contain something that could help figure out why the crash is happening.

Martin Erik Werner







To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics

Make your own search :