GNOME Bugzilla – Bug 418841
Can't stop, when recording sound
Last modified: 2008-04-15 09:18:01 UTC
Please describe the problem: After clicking the tray icon to start recording, the icon becomes insensitive. Clicking on it does nothing. Right-clicking on it does nothing. Starting another instance turns the icon blank (the space is there, but there's nothing in it). The only way out is to kill the program. Steps to reproduce: 1. Start Istanbul 2. start recording 3. try to stop recording. Actual results: See above. Expected results: I'd expect a save dialog or something. Does this happen every time? Yes Other information: According to the about dialog, I'm actually using version 0.2.1, but bugzilla doesn't offer that version as a choice. I'm running Ubuntu Edgy, and I'm using edgy's istanbul package. Also, it might be worth mentioning that I'm running Beryl, too.
Hello Scott! Can you try latest svn version please to see if this bug still happens ? Thanks a lot :)
Are you recording sound also?
It happened to me too, but I was recording sound also. At the end I just pressed CRTL+C Something else, when I try to stop to record, the icon change to a hard disk icon, and that's it. After that the only solution is press CRTL+C mario@mario:~$ istanbul --gst-debug-level=2 /var/lib/python-support/python2.5/istanbul/main/tray_icon.py:26: DeprecationWarning: the module egg.trayicon is deprecated; equivalent functionality can now be found in pygtk 2.10 import egg.trayicon DEBUG: final pipeline: oggmux name=mux ! filesink location=/tmp/tmpfBZCBj istximagesrc name=videosource show-pointer=false ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=640,height=512,framerate=10/1 ! theoraenc ! queue ! mux. gconfaudiosrc name=audiosource ! audioconvert ! vorbisenc ! queue ! mux. 0:00:03.299911000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.300113000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.300249000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.301501000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.306298000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.313878000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.353709000 17000 0xbd27e0 WARN istximagesrc gstximagesrc.c:890:gst_istximage_src_get_caps: User put in bogus co-ordinates, setting to full screen 0:00:03.359774000 17000 0xf6c3c0 WARN videorate gstvideorate.c:539:gst_video_rate_event:<videorate0> Got segment but doesn't have GST_FORMAT_TIME value xxxxx Here, there isn't any respond from istanbul xxxxxxxxxx Traceback (most recent call last):
+ Trace 136703
sys.exit(main.main(sys.argv))
gtk.main() KeyboardInterrupt
Sorry it took me so long to respond. I'll gladly try the latest SVN version if someone cal walk me through the process. Every time I've tried to figure out svn, I've been unsuccessful.
It's the same here with 0.2.2 under Fedora Core 8.
I get the same on Ubuntu 7.10 (64 bit) using 0.2.2-1 (gutsy). It appears to be an audio recording problem. If I uncheck the "Record Sound" menu option then the recording works fine. Note that the video still gets recorded in the /tmp/tmp* file but that the recording doesn't ever finish being saved to the disk. HTH.
I have the same problem: When I click the Stop button, the icon changes into the "saving to harddisk" button, but it stays like that forever. When I switch off sound recording, it works normally. System: Ubuntu 7.10 32-bit, installed Istanbul from Ubuntu repository, package version 0.2.2-1
*** Bug 517080 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 430151 ***