Plugin Menu Items are an unordered list

Bug #276157 reported by Martin Owens
4
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Medium
Nautilus
Invalid
Undecided
Unassigned
gtk+2.0 (Ubuntu)
Fix Committed
Low
Ubuntu Desktop Bugs

Bug Description

Installing any number of plugins which as nautilus image plugin or bzr-gtk will quickly show that each right click menu has it's own and distinctive menu ordering for each of these plugins.

What is happening is that these plugins are being processed and their results are not being stored as a set list. This means that the menu location is unpredictable and the more plugins installed the worse it would get.

This is a bad behaviour and it will disrupt the design flow and constancy of nautilus. If this problem can be fixed in some way by the plugins themselves, I can't find it. So it seems to be a nautilus bug.

STR: Install a number of plugins including the image plugin, right click on an image, now right click an image and a sound file. The menu items are still there, but (at least on my machine) the resize and rotate options have switched places.

Nautilus: 2.22.3
Ubuntu: 8.04.1

Martin Owens (doctormo)
description: updated
Revision history for this message
Martin Owens (doctormo) wrote :

Most testing indicated that it shows up mostly when more than one kind of file is selected. Different files (and thus I suspect different plugin execution orders) produce different menus.

description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

that's an un upstream issue and should be opened on bugzilla.gnome.org directly

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still have interest in that? could you send the request to GNOME?

Revision history for this message
Martin Owens (doctormo) wrote :

Don't bugs flaw to gnome automatically?

Revision history for this message
Sebastien Bacher (seb128) wrote :

you are using launchpad why should they go to GNOME automatically, somebody needs to open the bug there

Revision history for this message
Martin Owens (doctormo) wrote :

My initial impression was that launchpad could be used for upstream reporting because it had some sophisticated way of making these bugs visible in various upstream projects.

I see now that was in err.

So, this bugs needs to go directly to gnome bug tracking.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=564864

Changed in nautilus:
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Upstream bug has been marked as duplicate of bug https://bugzilla.gnome.org/show_bug.cgi?id=603128 which is fixed upstream. The upstream bug is assigned to gtk so I am reassigning the Ubuntu package task.

affects: nautilus (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
status: Triaged → Fix Committed
Changed in nautilus:
importance: Unknown → Undecided
status: New → Invalid
Changed in gtk:
importance: Unknown → Medium
status: Unknown → Fix Released
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.