Bug 183519 - Konqueror and others extremely slow on eTrade.com
Konqueror and others extremely slow on eTrade.com
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2006-03-01 12:58 EST by Kim Lux
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-01 13:22:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kim Lux 2006-03-01 12:58:45 EST
Description of problem: 
Konqueror and Firefox are both extremely slow (compared to IE on Windows) when 
first logging in.  
Version-Release number of selected component (if applicable): 
konqueror -v 
Qt: 3.3.5 
KDE: 3.5.1-2.3.fc4.kde 
Konqueror: 3.5.1-4.2.fc4.kde 
How reproducible: 
It has been a problem back to FC3. 
Steps to Reproduce: 
1. Open konqueror (or FireFox).  www.etrade.com 
2. Wait.  It will take minutes for the login screen to appear.  
3. Login.  It will take minutes for the client screen to appear.  
4. Everything will work normally once logged in.  
Actual results: 
Getting the actual screen and logging in takes forever.  
Expected results: 
In IE it is almost instantaneous.  No significant wait.   
Additional info: 
This has been a problem since FC3.  I am not sure if the issue is in konqueror 
and firefox or in something within the OS underneath it.
Comment 1 Ngo Than 2006-03-01 13:22:12 EST
Hmm, konqueror only takes few seconds for the login screen to appear on my test
machine on FC4 with updates. I saw the version-release number of your kdebase.
It seems you have installed 3rd-party KDE RPM packages on your system!

The current version of kde from FC4-update are:

You should please install the KDE packages from FC4.

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