Ubuntu
pitivi package

pitivi crashed with IOError in save(): [Errno 2] Нет такого файла или каталога: '/home/teddy/.local/share/pitivi/audio_presets'

Bug #846250 reported by Кузнецов Юрий on 2011-09-10

This bug report is a duplicate of: Bug #812671: pitivi crashed with IOError in save(): [Errno 2] Arquivo ou diretório não encontrado: '/home/jorge/.local/share/pitivi/audio_presets'. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	pitivi (Ubuntu)	New	Undecided	Unassigned

Bug Description

Ubuntu 11.10 beta1 under VirtualBox when i tried to create a new project and add new video preset

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pitivi 0.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Sat Sep 10 10:23:18 2011
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/pitivi']
SourcePackage: pitivi
Title: pitivi crashed with IOError in save(): [Errno 2] Нет такого файла или каталога: '/home/teddy/.local/share/pitivi/audio_presets'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Кузнецов Юрий (teddypickerfromul) wrote on 2011-09-10:

Traceback.txt Edit (389 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-10: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #812671, so 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. Please continue to report any other bugs you may find.