Bug 86309 - taskbar applet cannot be made to occupy all available space
Summary: taskbar applet cannot be made to occupy all available space
Status: CLOSED DUPLICATE of bug 75637
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase   
(Show other bugs)
Version: 8.0
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-19 11:43 UTC by Alexey Neyman
Modified: 2007-03-27 04:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:14 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)
Taskbar look before its extension. (30.11 KB, image/png)
2003-03-19 11:47 UTC, Alexey Neyman 		no flags Details
Taskbar look afterwards: note its size (30.05 KB, image/png)
2003-03-19 11:49 UTC, Alexey Neyman 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Alexey Neyman 2003-03-19 11:43:49 UTC 
Description of problem: 
Taskbar applet cannot be made to occupy all available free space 
in the kicker's panel. See the screenshots. 
 
Version-Release number of selected component (if applicable): 
kdebase-3.0.3-13 (RedHat Linux 8.0) 
 
How reproducible: 
When the task bar does not occupy all available space, try to 
drag it in order to extend. After the mouse button is released, 
the task bar will shrink to a rather small size.
Comment 1 Alexey Neyman 2003-03-19 11:47:53 UTC 
Created attachment 90659 [details]
Taskbar look before its extension.
Comment 2 Alexey Neyman 2003-03-19 11:49:31 UTC 
Created attachment 90660 [details]
Taskbar look afterwards: note its size
Comment 3 Alexey Neyman 2003-03-19 14:22:10 UTC 

*** This bug has been marked as a duplicate of 75637 ***
Comment 4 Red Hat Bugzilla 2006-02-21 18:52:14 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.