GNOME Bugzilla – Bug 333351
gnome-sound-recorder crashes if window closed while recording
Last modified: 2007-09-07 10:07:15 UTC
Distribution: Ubuntu 6.04 (dapper) Version: GNOME2.13.92 2.13.93 Gnome-Distributor: Ubuntu Description of the crash: gnome-sound-recorder crashes when I close a recording window and there is unsaved data. Steps to reproduce the crash: 1. click "New" 2. In the new window press "Record" 3. close the window while recording 4. Click "Don't save" Expected Results: Don't crash How often does this happen? Everytime Debugging Information: Backtrace was generated from '/usr/bin/gnome-sound-recorder' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1996487456 (LWP 21127)] [New Thread 1978166192 (LWP 21134)] [New Thread 1987091376 (LWP 21131)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 66678
Thread 1 (Thread 1996487456 (LWP 21127))
This still happens with version 2.14.0 ... I will raise this to major hoping that someone will see this and at least comment on it!
Still happens with 2.14.1
I can't reproduce this anymore seems to be fixed, closing the bug
Launchpad bug on GNOME 2.18.0: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/103139 "sound recorder closed unexpectedly Binary package hint: gnome-media accidentally had two recordings going at the same time. Stopped the first recording with the stop button and it closed both windows and sort of crashed out. Not a big deal and probably my fault..... Otherwise seemed like the program was running fine. S* ProblemType: Crash Architecture: i386 Date: Wed Apr 4 20:37:34 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-sound-recorder Package: gnome-media 2.18.0-0ubuntu1 ... .
+ Trace 125176
Thread 1 (process 6809)
2007-09-07 Bastien Nocera <hadess@hadess.net> * src/gsr-window.c: (record_start), (record_state_changed_cb): Remove the record timeout tick when we're done recording, so the timeout isn't called after we've destroyed the window (Closes: #333351)
*** Bug 420597 has been marked as a duplicate of this bug. ***