Bug 126906 - Konqueror shivers
Summary: Konqueror shivers
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 2
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-28 22:28 UTC by Roland Wolters
Modified: 2007-11-30 22:10 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-07-04 09:13:59 UTC


Attachments (Terms of Use)

Description Roland Wolters 2004-06-28 22:28:09 UTC
Description of problem: 
konqueror shivers, trembles, however you would call it, when you try 
to change the position of the middle bar in the file management under 
special circumstances (see below). The bar jumps back and forth 
several times per second as long as you have the bar dragged with the 
mouse. At all, it jumps back to the first position, independent from 
the place where I try to drop it. 
Only if I try to drop it near the next border, then it jumps to the 
border... 
 
Version-Release number of selected component (if applicable): 
KDE 3.2.2 and 3.2.3 (tested with original RedHat packages and with 
the KDE-RedHat packages). 
 
How reproducible: 
Use tabbed backround browsing for links with the konqueror, and do 
not hide the tab when only one tab is opend. 
Now open the file-managment view, and try to change the position of 
the middle bar. 
   
Actual results: 
Do not now how to get more information - there is nothing in the 
konsole when I start it there. 
 
Expected results: 
No shivering, just changing position to the place where I move the 
bar. 
 
Additional info: 
As mentioned above, it hapens with both KDE Packages: with the 
packages from the KDE-Redhat project and with the original RedHat 
packages.

Comment 1 Andrea Santilli 2004-07-01 12:48:48 UTC
Here same happens...

Comment 2 Ngo Than 2004-07-04 09:13:59 UTC
it's fixed in KDE 3.3 Beta1. i don't see this problem in this version
anymore.


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