GNOME Bugzilla – Bug 339089
sound-juicer crashes on %as-%at-%tN-%tt file pattern
Last modified: 2014-03-24 16:38:36 UTC
X-Mailer: bug-buddy 2.14.0 Distribution: Ubuntu 6.06 (dapper) Package: sound-juicer Severity: Normal Version: GNOME2.14.1 2.14.3 Gnome-Distributor: Ubuntu Synopsis: sound-juicer crashes on file pattern %as-%at-%tN-%tt Bugzilla-Product: sound-juicer Bugzilla-Component: general Bugzilla-Version: 2.14.3 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: After setting the pattern in gconf-editor, sound-juicer crashes when Edit -> Preferences is clicked Steps to reproduce the crash: 1. Set %as-%at-%tN-%tt as file pattern in gconf-editor 2. Start sound-juicer 3. Choose Edit -> Preferences, watch it crash Expected Results: I can set the pattern since all codes are listed in the key documentation in gconf-editor How often does this happen? Always Debugging Information: Backtrace was generated from '/usr/bin/sound-juicer' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (...) [Thread debugging using libthread_db enabled] [New Thread -1225843808 (LWP 27701)] [New Thread -1240933456 (LWP 27703)] (no debugging symbols found) (...) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67739
Thread 1 (Thread -1225843808 (LWP 27701))
------- Bug created by bug-buddy at 2006-04-19 21:47 ------- Unknown version 2.14.3 in product sound-juicer. Setting version to "2.14.x".
this is actually gconf leading to a crash, reassigning cannot reproduce with Gnome 2.14.1cvs Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. please install the gconf and glib debugging packages
Hm, do you happen to know, which Debian/Ubuntu package contains the gconf dbg stuff? I can't find it http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=gconf&searchon=names&subword=1&version=dapper&release=all
gconf2-dbg ?
Nope: http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=gconf2-dbg&searchon=names&subword=1&version=dapper&release=all
*** Bug 339355 has been marked as a duplicate of this bug. ***
Installed libglib2.0-0-dbg, had to rebuild libgconf2-4 manually to get debugging symbols. Attached is the new backtrace. Please advise if additional debug packages are required. TIA! Backtrace was generated from '/usr/bin/sound-juicer' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225656640 (LWP 29523)] [New Thread -1244955728 (LWP 29526)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 67787
Thread 1 (Thread -1225656640 (LWP 29523))
I can see this as well with Ubuntu dapper seems to happen with any gconf string I am using UTF8 locale report opened here: https://launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/42602
Other Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/38300 Christian, why did you reassign to gconf? "#5 0xb75d36df in gconf_engine_set_string (conf=0x8108cc8, key=0x8060260 "/apps/sound-juicer/file_pattern", val=0x203e62 <Address 0x203e62 out of bounds>, err=0xbf9a9680) at gconf.c:3382
+ Trace 67987
it looks like than prefs_file_option_changed () from sound-juicer uses an incorrect "val" parameter, which is a sound-juicer issue. Could anybody run sound-juicer with valgrind (apt-get install valgrind && valgrind sound-juicer), it makes it slow but might give useful informations on what happens to the "val" parameter
Created attachment 64769 [details] Output of 'valgrind sound-juicer' Sound-juicer was launched without a CD in the drive. After the window appeared, Edit->Preferences was selected from the menu. Upon crashing, the "close" option was chosen.
Hm, I can't replicate this at all. :/ Can someone who can grab the source and start by printing the values of active and pattern in prefs_file_option_changed()?
not reproducable with pristine Gnome 2.16 cvs build
Can anyone replicate this with G2.16?
The Ubuntu bug submitter wrote he didn't have the issue for some time on dapper and there is no new duplicate for the bug, I closed the Ubuntu bug as fixed
Not reproducable any more with Gnome 2.16/Unbuntu Edgy Marking this FIXED.
It seems to be still an issue with sound-juicer 2.22: https://bugs.edge.launchpad.net/sound-juicer/+bug/198905 ; is there any other information we can provide? thanks in advance.
I think I just fixed this in svn, so it will be in 2.26. Sorry it took so long!
(In reply to comment #16) > Sorry it took so long! Many thanks!