Philip Chee wrote:
On Thu, 31 Dec 2009 11:29:10 -0800, Rufus wrote:
Other odd thing was that the SM Crash Reporter came up in a different
Space than SM was opened into - SM assigned to Space 2; SM Crash
Reporter came up in Space 1. I entered a description in the Crash
reporter and relaunched SM and it launched/ran normally.
You didn't tell us the crash ID so we can't help you there. Go to
about:crashes . Your crash should be the most recent listed. Copy and
paste the URL here in this thread.
The Crash Reporter is a separate process (and process name). You could
try pinning the crash reporter to the same workspace as SeaMonkey itself.
Phil
Ok - that makes sense...new to this...
<http://crash-stats.mozilla.com/report/index/bp-fb88e14c-5fe7-49a6-957a-7da662091230>
Looks like I've actually had two crashes since install - here's the
other one:
<http://crash-stats.mozilla.com/report/index/bp-81c77584-38b1-4480-9beb-3afa72091221>
Something else strange is that even though I've fixed the "window not in
front at launch" problem I was having, SM 2.x.x does the "hokey-pokey"
with Spaces when I launch it - i.e.; when I launch SM (assigned to Space
2) the app returns to Space 1, displays the SM Menu bar, then moves to
Space 2 and opens the window.
Because I had solved the previous issue by rebuilding Launch Services, I
had assumed this was an OS X issue and not a SM issue - now I'm not so
sure...SM 1.1.18 doesn't do this.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
