Bug 690796 - gnome-panel orientation inconsistent
Summary: gnome-panel orientation inconsistent
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-panel
Version: 6.0
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 11:58 UTC by Fred F
Modified: 2017-12-06 10:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 614724
Environment:
Last Closed: 2017-12-06 10:50:51 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Fred F 2011-03-25 11:58:55 UTC
Version: gnome-panel-2.30.2-5.el6
Issue: When "expand" is disabled for the panel at the bottom of the screen, the panel will appear at the top of the screen after loggin off and in again.

Very likely related to Bug #614724.


+++ This bug was initially created as a clone of Bug #614724 +++

Description of problem:
Panel does not follow "bottom" position setting if not in "expanded" mode

Version-Release number of selected component (if applicable):
gnome-panel-2.30.0-4.fc13.x86_64

How reproducible:
Default setup has panel at top of screen. If "expand" is unselected in properties and then "bottom" is selected for position of panel, panel remains at top. If "expand" is selected however, and then position "bottom" is selected, panel appears at bottom of screen.

Steps to Reproduce:
1. Using properties of panel gui, select "bottom" for position
2. 
3. 
  
Actual results:
Panel appears at top only - when "expand" is unselected.

Expected results:
Expect to see panel at bottom of screen

Additional info:
This also happens for i686 as well. I've tried modifying ~/.gconf/apps/panel/toplevels/top_panel/%gconf.xml manually at runlevel 3 by changing the "orientation" string value to bottom, but it keeps reverting to top and makes no difference if "expand" is set to false.

Comment 2 RHEL Program Management 2011-04-04 02:08:26 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Jan Kurik 2017-12-06 10:50:51 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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