Dragging an item in the left panel of mozo corrupts menu

Bug #1768975 reported by Michael von Glasow
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu MATE
Expired
Undecided
Unassigned
mozo (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. Right-click Applications (behavior with Menu may be the same)
2. Click “Edit Menus”.
3. Click “New menu” and add a new menu.
4. Try to drag the menu (in the left pane) to a different location with the mouse.

Expected behavior:

Either the menu being moved to wherever I drop it, or nothing happens.

Actual behavior:

Both content areas of the menu editor go blank. When I click the Applications menu, I get an empty menu. This persists across a logout/login cycle. When I try to bring up mozo again, it crashes right away.

Software Environment:

Ubuntu MATE 18.04 LTS, upgraded today from 16.04

Additional Information:

Upon closer examination of ~/.config/menus/mate-applications.menu, I noticed an entire tree of <Menu> items (one for each letter of the name of the item I tried to move), with a <Move> item at the bottom of the hierarchy. Deleting these items from the file restored my menu to its previous state.

Tags: bionic
summary: - Dragging an item in the left panel of alacarte corrupts menu
+ Dragging an item in the left panel of mozo corrupts menu
description: updated
Norbert (nrbrtx)
tags: added: bionic
Norbert (nrbrtx)
Changed in ubuntu-mate:
status: New → Incomplete
Changed in mozo (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mozo (Ubuntu) because there has been no activity for 60 days.]

Changed in mozo (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu MATE because there has been no activity for 60 days.]

Changed in ubuntu-mate:
status: Incomplete → Expired
Revision history for this message
Michael von Glasow (michael-vonglasow) wrote :

Any news on this? I don’t really feel like trying this again on a production machine and corrupting my menu again. However, if it got fixed, you guys would probably know – either this issue was addressed and fixed, or it went away as a side effect of the faulty code having been rewritten for some other reason.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.