Closed
Bug 258016
Opened 20 years ago
Closed 13 years ago
mozilla-xremote-client 'ping()' doesn't return until browser-app gets an event (Linux)
Categories
(Core Graveyard :: X-remote, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ernstp, Assigned: blizzard)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040901 Firefox/1.0 PR (NOT FINAL)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040901 Firefox/1.0 PR (NOT FINAL)
this is probably not specific to some browser version,
tried with firefox nightly, mozilla 1.7 and firefox 0.9.3
I'm running unstable gtk+, version 2.5.2, and everything else from the latest
gnome rc.
Reproducible: Always
Steps to Reproduce:
1. start firefox or mozilla
2. mozilla-xremote-client -a any 'ping()'
3. don't move
Actual Results:
mozilla-xremote-client -a any 'ping()'
does not return, until the browser get's an event of some kind.
moving the mouse over the browser window, or clicking anywhere on the screen works.
Expected Results:
it should return immideately.
Gentoo Linux Portage 2.0.51_pre20 (gcc34-x86-2004.2, gcc-3.4.1,
glibc-2.3.4.20040808-r0, 2.6.8-gentoo-r2 i686 AMD Athlon(tm) 64 Processor 3200+)
Updated•20 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 1•20 years ago
|
||
Has anyone realized that these products (FF 1.0, Moz 1.8) will be released at
the same time as Gnome 2.8, so making them work with GTK+ 2.6 out of the box
could be a good thing?
Flags: blocking1.8a4?
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0?
Comment 2•20 years ago
|
||
Not blocking anything, we don't even have a diagnosis yet.
Flags: blocking1.8a4?
Flags: blocking1.8a4-
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0-
Reporter | ||
Comment 3•13 years ago
|
||
Old, can't see this problem now!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•