alacarte crashed with TypeError in on_menu_tree_cursor_changed()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alacarte (Ubuntu) |
New
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: alacarte
alacarte crashed with TypeError in on_menu_
^^ dont know what it means and i just used this whit dvd so its happened almost every ime i use just a cd to explore internet. same whit screensaver and also that
appot gtk furter info was sended.
im new for this and english is do:snt my best way to write so forgiveme that and also im losing my min whit recovering my kubuntu/
^^^last think is not bug or im bug its my hobby to crash abd try to repair but windows was easier to crash abd also install again... but its easy to not have any clue what i was just did that it ""works"" hhuh never again if someone nows there is like 20 programs that missing and i tryed to apt.get install missing updates and no use,,,
chiers Jani Haaparanta
ProblemType: Crash
Architecture: i386
Date: Sat Feb 20 03:48:37 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
Package: alacarte 0.12.4-0ubuntu2
PackageArchitec
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcEnviron:
LANG=fi_FI.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: alacarte
Title: alacarte crashed with TypeError in on_menu_
Traceback:
Traceback (most recent call last):
File "/usr/lib/
menu_path = menus.get_
TypeError: iter should be a GtkTreeIter
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
tags: | removed: need-duplicate-check |
Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace. wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
Please try to obtain a backtrace manually following the instructions at http://