Ubuntu
alacarte package

alacarte crashes when no permission to write ~/.config/menus/*

Bug #92272 reported by Higinio Raventós on 2007-03-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Alacarte Menu Editor	New	Critical	gnome-bugs #576799
	alacarte (Ubuntu)	Triaged	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: alacarte

I am using Feisty. This has been happening to me since Herd1. Everytime I right click on the menus and select "Edit the menus" I get this error.

I can open alacarte through the terminal without problems.

ProblemType: Crash
Architecture: i386
Date: Wed Mar 14 17:00:38 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.5
Package: alacarte 0.11.3-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcCwd: /home/higi
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=es_ES.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Uname: Linux HIGILINUX 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux

See original description

Revision history for this message

Higinio Raventós (higiraven) wrote on 2007-03-14:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (22.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (659 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (737 bytes, text/plain; charset="utf-8")

description:

updated

Revision history for this message

Travis Watkins (amaranth) wrote on 2007-03-15:

You've got broken permissions in your $HOME directory. You can fix them with chown -R higi:higi ~/.config/menus

Changed in alacarte:
status:	Unconfirmed → Rejected

Revision history for this message

montikiki (montikiki) wrote on 2007-04-06:

The Travis's way to solute the problem works for me

Revision history for this message

jyk (jykaminski) wrote on 2007-10-08:

The same solution worked for me on Gutsy.

More precisely I made the following command:

sudo chown -R jeremy:jeremy ~/.config/menus

Revision history for this message

kalvi (kalvi) wrote on 2008-03-23:

Yes, the following command solved the problem for me too (8.04). thx.
sudo chown -R username:username ~/.config/menus

Revision history for this message

Alexander S. Fomin (sashafl) wrote on 2008-04-16:

TanX, that works for me to.

Revision history for this message

Slucky31 (nicolas-dufaut) wrote on 2008-04-24:

It works for me too

Revision history for this message

axotolys (axotolys) wrote on 2008-05-13:

thanks, it's works for me
ubuntu 8.04

Revision history for this message

Nelson Head (jnhea) wrote on 2008-05-20:

This occurred when I tried to edit the Applications Menu. I tried the instruction suggested above, but I still get the same crash. It won't let me edit the Applications Menu. I wanted to add a program which I had just downloaded with the package manager to the applications menu.
Any suggestions?
jnh

Revision history for this message

map (mapicella-gmail) wrote on 2008-05-26:

#10

Perfect! Thank you!

8.04

Revision history for this message

Ryan (ubuntu-draziw) wrote on 2009-02-16:

#11

Just had this with a 8.10 -> 9.04 alpha system. Same issue of root:root ownership - but the question is how it got that way. I don't think this should be marked invalid.

Revision history for this message

Ryan (ubuntu-draziw) wrote on 2009-02-16:

#12

Had this happen on 9.04 too. Issue isn't invalid. Two issues IMHO.
1. How about failing with a message that says what the issue is vs triggering a crash?
2. What is causing the root:root menus ownership change?

Changed in alacarte:
status:	Invalid → Confirmed

Andreas Moog (ampelbein) on 2009-03-20

summary:

- [apport] alacarte crashed with IOError in save()
+ alacarte crashes when no permission to write ~/.config/menus/*

Revision history for this message

Andreas Moog (ampelbein) wrote on 2009-03-26:

#13

Reported the issue upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=576799

1. Yes, a message would be helpful, i've attached a patch to the upstream bugreport.
2. If you happen to run alacarte via sudo/gksudo this could happen.