Bug 462019 - Saving files (downloads) and browsing for upload locations is painfully slow (firefox 3.0.1-1)
Saving files (downloads) and browsing for upload locations is painfully slow ...
Product: Fedora
Classification: Fedora
Component: libbeagle (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-09-11 19:04 EDT by Peter Blomgren
Modified: 2009-07-14 10:28 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 10:28:54 EDT
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 Peter Blomgren 2008-09-11 19:04:21 EDT
Description of problem:
Saving files (downloads) and browsing for upload locations is painfully slow.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
a-1. Log in to gmail, find a message with attachment.
a-2. Download -> Save to file -> OK
a-3. WAIT for 2-3 minutes for file selection box to open.
a-4. Save.

b-1. Log in to gmail, compose new message
b-2. Click "Attach a file"  -> Browse 
b-3. WAIT for 2-3 minutes for file selection box to open.
b-4. Select file for upload...
Actual results:
It works, but waiting for 2-3 minutes for the dialog box to put up is "somewhat" annoying.

Expected results:
Shorter wait?

Additional info:
Problem not specific to gmail, but it's a good test site...
Comment 1 Peter Blomgren 2008-09-15 17:03:51 EDT
I ran an strace and found a thousands of these:

connect(69, {sa_family=AF_FILE, path="/home/user/.beagle/socket"}, 110) = -1 EAGAIN (Resource temporarily unavailable)
nanosleep({0, 200000000}, NULL)         = 0

I uninstalled all the beagle packages (beagle-gnome, beagle, and libbeagle; beagle-firefox was not installed) and the problem went away, so it's not a firefox bug...
Comment 2 Bug Zapper 2009-06-09 22:41:45 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-07-14 10:28:54 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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