tag 358652 - fixed-upstream thanks On Fri, Mar 24, 2006 at 02:08:31AM -0800, Elladan wrote: > On Thu, Mar 23, 2006 at 01:55:42PM -0500, Justin Pryzby wrote: > > tag 358652 upstream > > forwarded 358652 https://bugzilla.mozilla.org/show_bug.cgi?id=331490 > > thanks > > > > On Thu, Mar 23, 2006 at 10:19:57AM -0800, Elladan wrote: > > > Package: mozilla-firefox > > > Version: 1.0.7-1 > > > Severity: important > > > > > > > > > When I go to www.weatherunderground.com and enter zip code 98112, > > > firefox crashes. > > Not for me; what extensions do you have installed? Would you consider > > installing the sid firefox 1.5 package and retesting? You'll want to > > either use apt pinning, or remove the sid sources immediately after > > upgrading (and only update firefox and its dependencies). > > I upgraded to 1.5, and found it still crashed. Did you upgrade anything else?
> When I tried to run with debugger, I got: > > [EMAIL PROTECTED]:~$ firefox --debugger=gdb > > (Gecko:1568): GLib-GObject-WARNING **: gsignal.c:1017: unable to lookup > signal "activate" of unloaded type `MaiAtkObject' > > (Gecko:1568): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion > `signal_id > 0' failed > The program 'Gecko' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAlloc (insufficient resources for operation)'. > (Details: serial 62143 error_code 11 request_code 53 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) Did you try this --sync? I don't expect it will actually help though. Are you running any plugins (flash-nonfree perchance)? This is WRT bug #358379. What if you run firefox as: G_SLICE=always-malloc firefox? (after closing all running firefox processes) This is WRT bug #358071. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
