pitivi crashed with AttributeError in _responseCb()

Bug #326928 reported by Uphaar Agrawalla
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
pitivi (Ubuntu)
Fix Released
Medium
Luis de Bethencourt Guimerá

Bug Description

Binary package hint: pitivi

Crashed when clicking on the OK button in Project Settings dialog.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pitivi
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: ath_hal nvidia
Package: pitivi 0.11.1-0ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/pitivi']
SourcePackage: pitivi
Title: pitivi crashed with AttributeError in _responseCb()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pitivi/python/pitivi/ui/projectsettings.py", line 58, in _responseCb
     self.hide()
 AttributeError: 'ProjectSettingsDialog' object has no attribute 'hide'
Uname: Linux 2.6.27-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Uphaar Agrawalla (uphaar) wrote :
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, however you're using an old version of Pitivi, please file a new bug with apport if you get the same issue with pitivi 0.13.3 ; Thanks in advance.

Changed in pitivi (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
jimlovell777 (jimlovell777-yahoo-deactivatedaccount-deactivatedaccount) wrote :

I'm running 0.13.3 and got the same error.

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Please see if this still happens with 0.13.4.

Revision history for this message
Matt (mathphreak) wrote :

It does still happen with 0.13.4.

Jeff Fortin Tam (kiddo)
Changed in pitivi (Ubuntu):
status: Invalid → New
Revision history for this message
Edward Hervey (bilboed) (bilboed-deactivatedaccount) wrote :

Need a 0.13.4 backtrace report in order to investigate this further.

Revision history for this message
Edward Hervey (bilboed) (bilboed-deactivatedaccount) wrote :

and by backtrace I meant like in the initial report, but for the new version.

Changed in pitivi (Ubuntu):
status: New → Incomplete
Changed in pitivi (Ubuntu):
status: Incomplete → Fix Committed
Changed in pitivi (Ubuntu):
assignee: nobody → Luis de Bethencourt Guimerá (luisbg)
Changed in pitivi (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
NoahY (noahy) wrote :

Still a problem in 0.13.5... what version was the fix released in?

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

It was thought to be fixed in 0.13.5.

Please provide precise steps to trigger the bug in 0.13.5, as well as the traceback that you get.

You can also create debug logs by running pitivi like this:
PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1
(Then compress and attach the log file to this bug report.)

Changed in pitivi (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Old bug is old. 0.93 is now available in Ubuntu 14.04's proposed updates.

Changed in pitivi (Ubuntu):
status: Incomplete → Fix Released
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.