sound-juicer crashed with SIGSEGV in free()

Bug #259362 reported by Jonh Wendell
14
Affects Status Importance Assigned to Milestone
sound-juicer (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: sound-juicer

I just opened and then closed it...

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/sound-juicer
Package: sound-juicer 2.23.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: sound-juicer
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: sound-juicer
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 IA__g_free (mem=0x83e58955)
 IA__g_option_group_free (group=0xb7d58c20)
 IA__g_list_foreach (list=0x8425ab0,
 IA__g_option_context_free (context=0x82c55a8)
Title: sound-juicer crashed with SIGSEGV in free()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev pulse pulse-access pulse-rt sambashare

Revision history for this message
Jonh Wendell (wendell) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in sound-juicer:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Mihai Chivu (mihai.chivu) wrote :

Me too having this bug when I tried to close the application from menu Disc -> Quit. The bug can be replicated.

Revision history for this message
Pedro Fragoso (ember) wrote :

Yes it's known upstream, and it's fixed on 2.23.3 check Bug #267753

Changed in sound-juicer:
status: Incomplete → Fix Committed
Changed in sound-juicer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.