240174 - Starting mozilla prints "No running window found" every time

Status: RESOLVED FIXED

(Core Graveyard :: X-remote, defect)

Description

[Boris Zbarsky [:bzbarsky]]

BUILD:  2004-04-10 CVS build

STEPS TO REPRODUCE:  Type "./mozilla" in dist/bin

ACTUAL RESULTS:
1)  Prints "No running window found"
2)  Starts the browser

EXPECTED RESULTS: Just start the browser, without printing garbage to the
console (printing an error message when there is no error, expecially in a
release build, is bad).

This looks like a regression from bug 237283.  At a guess, the mozilla startup
scripts need to redirect the error message from their non-forced attempt at
xremote to /dev/null.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

bug 240166 sounds related

Comment 2

[Brian Ryner (not reading)]

Attachment: patch

Don't send an xremote command if no -remote argument was given.

Comment 3

[Boris Zbarsky [:bzbarsky]]

I'm also getting "Error: Failed to send command: No response included." a lot
(coming at startup, right after 2-3 seconds of doing nothing).  Also this bug,
or should I file a separate one?

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #3)
> I'm also getting "Error: Failed to send command: No response included." a lot

I have also seen it, but only when I didn't specify a -P option on startup

Comment 5

[Boris Zbarsky [:bzbarsky]]

I never specify -P, since there is only one profile involved.

Comment 6

[Christopher Blizzard (:blizzard)]

Comment on attachment 145843 [details] [diff] [review]
patch

good catch.  should include this as part of 1.7, too.

Comment 7

[Brian Ryner (not reading)]

checked in on trunk (will check in on 1.7 branch once it is open)

Comment 8

[R.K.Aa.]

*** Bug 240399 has been marked as a duplicate of this bug. ***

Comment 9

[Marco Perez [:mpk]]

*** Bug 200194 has been marked as a duplicate of this bug. ***