kmenuedit does not save changes.

I wonder if this is related to some of my other bugs. 88429 and 88431. 88431 at least uses Python aswell?

Assigning this to kdebase.

Also I can't reproduce this bug. I want to make sure that you didn't run sudo kmenuedit instead. Also can you make sure your system is completely up to date and then update this bug.

Thanks,

Jonathan

Hi Jonathan,

I have all of the latest updates, and I have retried this. It is still the
same as before. It would be really useful to edit the menu, as at the moment,
I have got a folder on my desktop with my extra shortcuts in!

PS - I have other maybe similar bugs about not being able to see the Monitor &
Display thing in System Settings and the kscreensaver not actually loading a
screen saver when it comes on automatically. I don't know how it all works
though so maybe they aren't similar.

Hope you can sort it!

Bestest,

Tom

On Wednesday 21 March 2007 01:44:51 Jonathan Jesse wrote:
> Assigning this to kdebase.
>
> Also I can't reproduce this bug. I want to make sure that you didn't
> run sudo kmenuedit instead. Also can you make sure your system is
> completely up to date and then update this bug.
>
> Thanks,
>
> Jonathan
>
> ** Changed in: kdebase (Ubuntu)
> Sourcepackagename: None => kdebase
> Status: Unconfirmed => Needs Info

I have tried this again with the latest updates, and there don't seem to be any error messages in the konsole when I start it up with 'kmenuedit', however it still does not save any changes made to the actual shortcuts. Is there any other information that I can capture for you guys? It would be funky to have this sorted in time for Feisty's release, as I know some other folk who are having the same problem.

kmenuedit
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
tominglis@Achilles:~$ X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x2c0046c

Unless maybe the last thing is an error with it? The first two I think are just my mouse, and seem to come with most everything.

I have had the same issue and it is very annoying because I have shrotcut icons all over my desktop because I can't put them in the start menu.

Hi Guys,

This bug is still present in the latest build on my machine - it would be good to nail it before release? Is there any more info I can provide?

Bestest,

Tom

Hi
I am a new kubuntu user and have the exactly the same issue. Using 7.04 Feisty build with nvidia-glx.

I cannot edit the Kmenu in exactly the way this bug describes. Frustrating is an understatement. Here's hoping for a fix soon. I'm sure thousands of others have run into the same problem but aren't the bug reporting type.

For me the problem is the NTFS Config tool that can be installed. The menu command for it is "gksu ntfs-config" it should be "kdesu ntfs-config", since I can't edit the menu to correct it, I have to put it into run dialog every time and manually edit in order to launch the app. I also have new items I cannot create links in the menu too and others whose descriptions I would like to change.

Can anyone tell me if there is a file I could manually edit to make the simpler changes to the kmenu actually stick?

Thanks.

Matt

I should add that the system was a clean install and completely up to date.

The status of this bug is 'Needs info'. what information can I collect to help that hasn't been posted here already? How can we get this bug's status changed so it is looked at?

Regards,
Matt

Confirming htis bug on feisty as lots of people have made comments they are having issues w/ this bug.

We are experiencing this bug on all our Kubuntu Feisty Fawn machines.

Our temporary fix is using desktop shortcuts but we eagerly await a fix. The importance of this bug is fairly high for us as it is effecting the productivity of day-to-day tasks.

I have made the following observations:

- Folders are saved but items are not.
- After a name is specified for a new item, it is immediately lost.
- Running kmenuedit as root (via sudo) appears to save the items for the root user.

Does kmenuedit read the name from the newly-created .desktop item? If so it probably suggests that the .desktop item isn't being created at all for non-root users. Could this be a permission problem?

I few more observations:

- I can re-order menu items and save the new order successfully - such as dragging 'System Settings' above 'Help'.
- If I copy and paste an existing menu item, such as 'Help', the pasted item appears, but is not saved.

I am happy to announce that I have managed to fix this bug! ;)

Problem: kmenuedit does not save newly created desktop menu items.

Cause: The directory which holds the user .desktop files (~/.local/share/applications) is owned by the root user and group after a fresh installation of Kubuntu Feisty Fawn Final. This directory should be owned by the user, not root.

Solution (Fix): The temporary fix is the following command in a console: "sudo chown -R <USERNAME>: ~/.local/share/applications"
<USERNAME> should be replaced with the system usern/group name of the current system user and also note the colon trailing immediately afterwards. If your system user/group name is Mart (as in my case), the command would be: sudo chown -R mart: ~/.local/share/applications
The command sets both the user and group ownership of the ~/.local/share/applications directory to your system user and group respectively. This command must be ran as root so triple-check the command is correct before executing it!

The permanent fix is to have the ~/.local/share/applications directory user and group ownership set to the system user and group respectively on a fresh installation of Kubuntu Feisty Fawn.

Notes: ~/.local/share/mime is also owned by root. Although this doesn't effect this bug, it might be causing other problems. Should the mime directory also be owned by the system user/group?

It appears this bug does not affect the x64 distribution.

Thank you all for reporting and confirming this bug. I can reproduce the bug and Mart's solution has also worked. I'll set the importance to Low since there is an existing workaround.

is there any legitimate reason for ~/.local/ to be owned by root at all, ever?

If not, it's just a case of where would be a good place to chown it back.

(as a workaround, while hopefully someone figures out what's changing ~/.local/ ownership to root - as i didnt think that was normal for a fresh kde install.)

I wonder if this is fixed, with the sudo fixing patch dropped.

Please shout if you still see this on current gutsy.

No similar issues on Gutsy.

i got issues with kmenuedit on gutsy (a fresh installation of the daily image of 28/8/07)

i wanted to add kmail to the menu. the menu editor doesnt allow me to save changes in /home/michael/.config/menus/applications-kmenuedit.menu

kmail appears in the obsolete applications section, whatever this is called..

works for me now too

I had the same problem as mikkael. It turned out that ~/.config/ was set as owned by root, too. Dunno if this was default or after I installed a package or something. The subfolders for compiz and SpeedCrunch were also owned by root, as well as a file called Trolltech.conf.

Also, I had to create a ~/.config/menus/ folder manually before kmenuedit would save.

Should this be a different bug report?

I'm using the latest updated Gutsy and have exactly the same problem, so the bug still exists.
~/.config/ is owned by root, and only contains Trolltech.conf file.

Still an issue in Hardy/Intrepid?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.