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.
bug 240166 sounds related
Created attachment 145843 [details] [diff] [review] patch Don't send an xremote command if no -remote argument was given.
Assignee: blizzard → bryner
Status: NEW → ASSIGNED
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?
(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
I never specify -P, since there is only one profile involved.
Comment on attachment 145843 [details] [diff] [review] patch good catch. should include this as part of 1.7, too.
Attachment #145843 - Flags: approval1.7? → approval1.7+
checked in on trunk (will check in on 1.7 branch once it is open)
Status: ASSIGNED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
*** Bug 240399 has been marked as a duplicate of this bug. ***
*** Bug 200194 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.