saving the video results in a crash

Bug #56982 reported by Sebastian Heinlein
6
Affects Status Importance Assigned to Milestone
Istanbul
Fix Released
Critical
istanbul (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

DEBUG: final pipeline: istximagesrc name=videosource ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=1280,height=1024,framerate=10/1 ! theoraenc ! oggmux name=mux ! filesink location=/tmp/tmpe6j5WA
Traceback (most recent call last):
  File "/var/lib/python-support/python2.4/istanbul/main/tray_icon.py", line 56, in _trayicon_clicked
    self.current_screencast.start_recording()
  File "/var/lib/python-support/python2.4/istanbul/main/screencast.py", line 109, in start_recording
    self._pipeline = gst.parse_launch(final_pipeline)
gobject.GError: Konnte videorate0 nicht mit ffmpegcsp0 verbinden
[TRANSLATION: Could not connect videorate0 to ffmpegcsp0]
Traceback (most recent call last):
  File "/usr/bin/istanbul", line 40, in ?
    sys.exit(main.main(sys.argv))
  File "/var/lib/python-support/python2.4/istanbul/main/main.py", line 86, in main
    gtk.main()
KeyboardInterrupt

Changed in istanbul:
status: Unknown → Unconfirmed
Changed in istanbul:
status: Unconfirmed → Fix Released
Revision history for this message
Tangui (tangui-le-pense) wrote :

Also crash with me when clicking a second time on the tray icon to save :

tangui@deus:~$ istanbul
DEBUG: final pipeline: istximagesrc name=videosource ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=1024,height=768,framerate=10/1 ! theoraenc ! oggmux name=mux ! filesink location=/tmp/tmpgjmPBQ
SaveWindow with file: /tmp/tmpgjmPBQ
The program 'istanbul' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 45 error_code 11 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Revision history for this message
Florian Boucault (fboucault) wrote :

This second issue is referenced in bug #69825.

Revision history for this message
William Grant (wgrant) wrote :

Fixed in Feisty.

Changed in istanbul:
status: Unconfirmed → Fix Released
Changed in istanbul:
importance: Unknown → Critical
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.