Bug 74942 - Can't move items in (redhat) menu
Summary: Can't move items in (redhat) menu
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-panel   
(Show other bugs)
Version: 8.0
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Keywords:
: 75223 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-02 22:58 UTC by Samuel Flory
Modified: 2008-05-01 15:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-02 22:58:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Samuel Flory 2002-10-02 22:58:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
  In at least one prior beta you could modify the menu acessed via the redhat
icon. I've done the below operation, and also moved all of the open office stuff
otherthe word proccessor to extras, swap emacs and xemacs....  These changes
remain, but I can not make futher changes after upgrading to 8.0.  I've noted
this on my laptop, and on a coworkers system.  This occurs on a new created user.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Open 2 windows via the start here button:
2.Window #1 Start Here ->Applications -> Office
3.Window #2 Start Here ->Applications -> Extras -> Office
4.Drag abiword from Window #2 to Window #1.  

Additional info:

Comment 1 Havoc Pennington 2002-10-02 23:45:50 UTC
wasn't added in working form until gnome 2.0.2, we have 2.0.1. We will get
the feature on upgrade.

Comment 2 Havoc Pennington 2002-10-05 17:08:06 UTC
*** Bug 75223 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.