Your message dated Thu, 13 Apr 2006 20:57:33 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#305490: firefox: that annoying bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mozilla-firefox
Version: 1.0.1-2
Severity: important
I've seen that many times at ogame.de (online-game). There's a navigation frame
and a main-content-frame. When I click a link in the navigation
frame, firefox sometimes shows the content in a new window "A" (without any
tool- status- or menubar, marked with an "X"-Symbol in the headline)
instead of loading it into the mainframe. This doesn't happen every time but
maybe every 4th or 5th try. When I close this new window "A", all
running instances crash. When I click the same link (in the navogation frame)
again, FF sometimes opens a new window "B" but sometimes it closes
window "A" and everything runs normal again. When I close the main window,
windows "A" and "B" are closed too and the other instances keep running.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1)
Versions of packages mozilla-firefox depends on:
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii fontconfig 2.3.1-2 generic font configuration library
ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.1-2 generic font configuration library
ii libfreetype6 2.1.7-2.3 FreeType 2 font engine, shared lib
ii libgcc1 1:3.4.3-12 GCC support library
ii libglib2.0-0 2.6.4-1 The GLib library of C routines
ii libgtk2.0-0 2.6.2-4 The GTK+ graphical user interface
ii libidl0 0.8.5-1 library for parsing CORBA IDL file
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libkrb53 1.3.6-2 MIT Kerberos runtime libraries
ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio
ii libpng12-0 1.2.8rel-1 PNG library - runtime
ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte
ii libxft2 2.1.7-1 FreeType-based font drawing librar
ii libxp6 4.3.0.dfsg.1-12.0.1 X Window System printing extension
ii libxt6 4.3.0.dfsg.1-12.0.1 X Toolkit Intrinsics
ii psmisc 21.5-1 Utilities that use the proc filesy
ii xlibs 4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu
ii zlib1g 1:1.2.2-3 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
I'm closing this for now, as it is either not a firefox bug, or is
fixed by recent versions. If it recurs, we can reopen it, or open a
new one.
On Thu, Apr 13, 2006 at 08:44:26PM -0400, Chris Davies wrote:
> well, I've given it a pretty good and thorough runthrough and I haven't
> had the problem.
>
> I reloaded multiple pages in multiple tabs that used to exhibit this
> problem (cnn.com, cnnfn.com, etc) -- mostly sites using iframes for
> their banner ads, and it appears to be working properly now.
>
> Thanks for the perserverence on this one.
>
> Justin Pryzby wrote:
> >On Tue, Apr 11, 2006 at 02:50:55AM -0400, Ove Kaaven wrote:
> >>Package: firefox
> >>Version: 1.5.dfsg+1.5.0.1-4
> >>Followup-For: Bug #305490
> >>
> >>Since I complained about this earlier, I should probably mention that I'm
> >>not
> >>seeing this issue anymore after an upgrade (libxul0d was among the
> >>upgraded
> >>packages, I think, don't remember any others)... don't know about the
> >>original
> >>submitter
> >Thomas and Chris, could you both update to recent library versions,
> >and report whether this bug still affects you?
--- End Message ---