Your message dated Tue, 1 May 2007 15:39:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#273291: mozilla-browser: running mozilla crashes after
upgrade
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-browser
Version: 2:1.7.3-2
Severity: normal
I just upgraded mozilla-browser and related packages fram 2:1.7.2-4 to
2:1.7.3-2 while several browser windows were open. When I went back to
these windows, I did a few operations successfully, but when I opened a
new window, it crashed. Although I did not repeat the experiment, I
expect this is because it looked for some file that was deleted with the
upgrade.
This may be a difficult issue, but I think we should try to avoid a
crash if at all possible. It would be ok if some functionality
disappeared, but the browser should basically keep working. (For
example, if you upgrade vim while it is running, you lose syntax
highlighting on new files and on-line help, but you can still edit files
just fine.)
I can try to reproduce and pinpoint the problem if anyone is willing to
help fix it.
Andrew
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages mozilla-browser depends on:
ii debconf 1.4.36 Debian configuration management sy
ii libatk1.0-0 1.6.1-3 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libfontconfig1 2.2.3-1 generic font configuration library
ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib
ii libgcc1 1:3.4.2-2 GCC support library
ii libglib2.0-0 2.4.6-2 The GLib library of C routines
ii libgtk2.0-0 2.4.10-1 The GTK+ graphical user interface
ii libnspr4 2:1.7.3-2 Netscape Portable Runtime Library
ii libpango1.0-0 1.4.1-2 Layout and rendering of internatio
ii libstdc++5 1:3.3.4-12 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-7 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-7 X Window System miscellaneous exte
ii libxft2 2.1.2-6 FreeType-based font drawing librar
ii libxp6 4.3.0.dfsg.1-7 X Window System printing extension
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii libxt6 4.3.0.dfsg.1-7 X Toolkit Intrinsics
ii psmisc 21.5-1 Utilities that use the proc filesy
ii xlibs 4.3.0.dfsg.1-7 X Window System client libraries m
ii zlib1g 1:1.2.1.2-1 compression library - runtime
-- debconf information:
* mozilla/dsp: none
mozilla/locale_auto: true
* mozilla/prefs_note:
--- End Message ---
--- Begin Message ---
Package: iceape-browser
Version: 1.0.7-3
On Fri, Sep 24, 2004 at 07:30:39PM -0700, Andrew Pimlott <[EMAIL PROTECTED]>
wrote:
> Package: mozilla-browser
> Version: 2:1.7.3-2
> Severity: normal
>
> I just upgraded mozilla-browser and related packages fram 2:1.7.2-4 to
> 2:1.7.3-2 while several browser windows were open. When I went back to
> these windows, I did a few operations successfully, but when I opened a
> new window, it crashed. Although I did not repeat the experiment, I
> expect this is because it looked for some file that was deleted with the
> upgrade.
>
> This may be a difficult issue, but I think we should try to avoid a
> crash if at all possible. It would be ok if some functionality
> disappeared, but the browser should basically keep working. (For
> example, if you upgrade vim while it is running, you lose syntax
> highlighting on new files and on-line help, but you can still edit files
> just fine.)
>
> I can try to reproduce and pinpoint the problem if anyone is willing to
> help fix it.
AFAIK, all versions of iceape would pretty much fail and display
garbage, eventually leading to XUL fast loading cache corruption (which
was fixed in 1.0.7-3), but never crashed due to an upgrade.
Closing this bug accordingly.
Mike
--- End Message ---
