istanbul not working properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
istanbul (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: istanbul
I'm on Hardy , /var/cache/
Somes bugs :
* When I select Window record, it not work properly and it appear work like area record !!!!! I don't understand.
* When video capture is finish, istanbul be freeze on save capture mode, i must kill it.
* when I select Area record it produce an error :
$istanbul
window behind the pointer: <gtk.gdk.Window object at 0x118b460 (GdkWindow at 0x1649010)>
(759, 467) - (1094, 82)
DEBUG: final pipeline: oggmux name=mux ! filesink location=
Traceback (most recent call last):
File "/var/lib/
self.
File "/var/lib/
self._pipeline = gst.parse_
gobject.GError: impossible de connecter videoscale0 à theoraenc0
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/
report_file = open(pr_filename, 'wt')
IOError: [Errno 13] Permission non accordée: '/var/crash/
Original exception was:
Traceback (most recent call last):
File "/var/lib/
self.
File "/var/lib/
self._pipeline = gst.parse_
gobject.GError: impossible de connecter videoscale0 à theoraenc0
Traceback (most recent call last):
File "/var/lib/
self.
File "/var/lib/
self.
AttributeError: Screencast instance has no attribute '_vsource'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/
report_file = open(pr_filename, 'wt')
IOError: [Errno 13] Permission non accordée: '/var/crash/
Original exception was:
Traceback (most recent call last):
File "/var/lib/
self.
File "/var/lib/
self.
AttributeError: Screencast instance has no attribute '_vsource'
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #132130, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.