Bug 538625 - GNOME Panel launchers won't go next to each other
Summary: GNOME Panel launchers won't go next to each other
Keywords:
Status: CLOSED DUPLICATE of bug 529614
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 23:28 UTC by Richard Schwarting
Modified: 2009-11-19 15:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-19 15:07:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard Schwarting 2009-11-18 23:28:04 UTC
Description of problem:
I have a number of convenient, handy launchers on my panel.  In Fedora 11, they sat next to each other, where I put them.  However, since preupgrading to Fedora 12 final, gaps have appeared between most of them and I can't seem to move them next to each other.  I can still rearrange them, but there's a weird gap between them that's wasting my panel space.

Having a 1024x768 fixed resolution, I can of need all the space I can get, as right now my window list is just really tightly bunched together.

Version-Release number of selected component (if applicable):
gnome-panel-2.28.0-13.fc12

How reproducible:
Always

Steps to Reproduce:
1. log into Fedora 12
2. try putting launchers next to other
3.
  
Actual results:
They refuse to, with a weird gap separating them.  (Perhaps they think they're larger than they are?) 

Expected results:
They should go where I've moved them, preferably where I had them in Fedora 10, 11, etc.

Additional info:

Comment 1 Ray Strode [halfline] 2009-11-19 15:07:20 UTC
Hi,

This is configurable in gconf.

1) run gconf-editor
2) navigate to /apps/panel/toplevels
3) double-click the padding item and move it from 8 to 0.

*** This bug has been marked as a duplicate of bug 529614 ***


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