Your message dated Wed, 23 Dec 2009 12:15:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#524926: iceweasel: "Error launching browser window:no
XBL binding for browser" on startup
has caused the Debian Bug report #524926,
regarding iceweasel: "Error launching browser window:no XBL binding for
browser" on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
524926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524926
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iceweasel
Version: 3.0.6-1
Severity: normal
Since today, each time starting Iceweasel I get a dialog box with title
"[JavaScript Application]" and content "Error launching browser window:no XBL
binding for browser".
After that, the Iceweasel window shows up (without window contents, transparent)
for a fraction of a second and then silently disappears.
I do not remember changing anything since I last used iceweasel.
The log of a gdb session running
$ HOME=/tmp MOZILLA_DISABLE_PLUGINS=1 iceweasel -safe-mode -g
is attached. I hit ^C and generated a backtrace while the described dialog box
was showing. Note that gdb behaves strangely (look for "Cannot detect new
threads").
Don't hesitate to ask me for more information.
Kind regards,
Patrik Fimml
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages iceweasel depends on:
ii debianutils 2.30 Miscellaneous utilities specific t
ii fontconfig 2.6.0-3 generic font configuration library
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libglib2.0-0 2.16.6-1+lenny1 The GLib library of C routines
ii libgtk2.0-0 2.12.12-1~lenny1 The GTK+ graphical user interface
ii libnspr4-0d 4.7.1-4 NetScape Portable Runtime Library
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii procps 1:3.2.7-11 /proc file system utilities
ii psmisc 22.6-1 Utilities that use the proc filesy
ii xulrunner-1.9 1.9.0.7-0lenny2 XUL + XPCOM application runner
iceweasel recommends no packages.
Versions of packages iceweasel suggests:
ii latex-xft-fonts 0.1-8 Xft-compatible versions of some La
ii libkrb53 1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
pn mozplugger <none> (no description available)
pn ttf-mathematica <none> (no description available)
pn xfonts-mathml <none> (no description available)
pn xprint <none> (no description available)
ii xulrunner-1.9-g 1.9.0.7-0lenny2 Support for GNOME in xulrunner app
-- no debconf information
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi,
On Wed, Apr 22, 2009 at 08:24:39PM +0200, Mike Hommey wrote:
> On Wed, Apr 22, 2009 at 03:28:04PM +0200, Patrik Fimml wrote:
> > On Mon, Apr 20, 2009 at 10:53:51PM +0200, Mike Hommey wrote:
> > > Attachment is missing ;)
> > >
> > > > Don't hesitate to ask me for more information.
> > >
> > > Can you try to apt-get install --reinstall xulrunner-1.9 iceweasel?
> > > Does it get any better?
> > > What about downgrading one of both?
> >
> > Gah. I cannot reproduce the error myself any more after a clean reboot.
> > It happened after resuming from hibernation. Might have to do something
> > with files iceweasel keeps in /tmp or something...
> >
> > Unfortunately, I also deleted the not-attached gdb log already. Sorry...
>
> Did you happen to have upgraded either xulrunner-1.9 or iceweasel while
> iceweasel was running?
I'll just assume that there was still an iceweasel running after an
upgrade, and that rebooting made sure there was no stale process.
Cheers,
Mike
--- End Message ---
