Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 185125 - "starting web browser" shows for a long time
Summary: "starting web browser" shows for a long time
Status: CLOSED DUPLICATE of bug 156710
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
Depends On:
Blocks: FC6Target
TreeView+ depends on / blocked
Reported: 2006-03-10 20:15 UTC by Ben Maurer
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-03-11 23:10:00 UTC

Attachments (Terms of Use)

Description Ben Maurer 2006-03-10 20:15:32 UTC
On the latest FC5, do the following:

1. Click the web browser button on the panel
2. Wait for ff to show up
3. Click again
4. Wait for ff to open a new window

after step 4, the "starting web browser" will still stay there until the button
times out. This should not happen, it should go away as soon as firefox launches.

Comment 1 Warren Togami 2006-03-10 21:17:39 UTC
This is not necessarily the fault of firefox, but this is a general problem with
the way application startup feedback works.  We need to figure out a general
solution to use across all software.

Assigning to Matthias so he can decide what we should do.

Comment 2 Ray Strode [halfline] 2006-03-10 22:02:21 UTC
No, this is probably a problem with firefox itself.  startup notification is a
known and solved problem; firefox just needs to implement it right if it's not.

Comment 3 Matthias Clasen 2006-03-11 14:31:49 UTC
Ray is right. gnome-terminal is similar in that it opens a new toplevel for
each button click, and it has correct startup notification. Firefox needs
to be fixed to do the right thing.

Comment 4 Christopher Aillon 2006-03-11 23:10:00 UTC
This is really bug 156710

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

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