Ubuntu
alacarte package

alacarte crashed with IOError in copyItem()

Bug #511757 reported by jwichman@gmail.com on 2010-01-24

This bug report is a duplicate of: Bug #205463: alacarte crashed with IOError in copyItem() (when copying item with / in name). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: alacarte

I had been draggin gand drooping items tyo re-arrange the menu, but I (believe( that alacarte was in the backgroud when it crashed.

Description: Ubuntu 9.10
Release: 9.10

alacarte:
  Installed: 0.12.4-0ubuntu2
  Candidate: 0.12.4-0ubuntu2
  Version table:
*** 0.12.4-0ubuntu2 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Sat Jan 23 18:04:14 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu-Server 9.10 "Karmic Koala" - Release i386 (20091027.2)
Package: alacarte 0.12.4-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcEnviron: SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Title: alacarte crashed with IOError in copyItem()
Uname: Linux 2.6.31-17-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse jj lpadmin netdev plugdev sambashare sudo video

Tags:

Revision history for this message

jwichman@gmail.com (jwichman) wrote on 2010-01-24:

Traceback.txt Edit (434 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-01-24: 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 #205463, 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.