Your message dated Sun, 13 May 2007 10:04:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335029: mozilla forces removal of .mozilla on most upgrades
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
Version: 2:1.7.12-1
Severity: important
Sorry that I cannot be more specific, but today it happened again:
apt-get upgrade brought me a new version of mozilla, which was extremely
crash-prone (e.g. visiting http://www.alice-dsl.de crashes within seconds,
visiting imdb.com and entering and submitting a search form crashes etc.).
moving away .mozilla stops the crashes, but also voids all configuration.
The problem is that this happens on almost every upgrade: mozilla starts
to crash without _any_ error message or indication whatsoever whats
wrong, and the only workaround is to delete ones .mozilla and losing all
configuration (which can take an hour to edit and remember).
This is, I think, a highly suboptimal state of affairs, and at the very
least mozilla should indicate an error message, or, better yet, allow
upgrades withotu losing all configuration settings.
This happens on both my amd64 as well as my x86 machines.
I marked this as important, because this has a major effect on the
usability (IMHO), but this could easily be changed to wishlist (mozilla
doesn't seem to segfault or anything similar, it just exits) if it isn't
deemed important :)
My thanks to the debian maintainers (or better: condolences :) for
investing so much time and effort into such a difficult-to-maintain
package as mozilla!
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (700, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.11
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages mozilla depends on:
ii dpkg 1.13.11 package maintenance system for Deb
ii mozilla-browser 2:1.7.12-1 The Mozilla Internet application s
ii mozilla-mailnews 2:1.7.12-1 The Mozilla Internet application s
ii mozilla-psm 2:1.7.12-1 The Mozilla Internet application s
mozilla recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Oct 21, 2005 at 04:41:33PM +0200, Marc Lehmann <[EMAIL PROTECTED]>
wrote:
> Package: mozilla
> Version: 2:1.7.12-1
> Severity: important
>
> Sorry that I cannot be more specific, but today it happened again:
>
> apt-get upgrade brought me a new version of mozilla, which was extremely
> crash-prone (e.g. visiting http://www.alice-dsl.de crashes within seconds,
> visiting imdb.com and entering and submitting a search form crashes etc.).
>
> moving away .mozilla stops the crashes, but also voids all configuration.
>
> The problem is that this happens on almost every upgrade: mozilla starts
> to crash without _any_ error message or indication whatsoever whats
> wrong, and the only workaround is to delete ones .mozilla and losing all
> configuration (which can take an hour to edit and remember).
>
> This is, I think, a highly suboptimal state of affairs, and at the very
> least mozilla should indicate an error message, or, better yet, allow
> upgrades withotu losing all configuration settings.
>
> This happens on both my amd64 as well as my x86 machines.
>
> I marked this as important, because this has a major effect on the
> usability (IMHO), but this could easily be changed to wishlist (mozilla
> doesn't seem to segfault or anything similar, it just exits) if it isn't
> deemed important :)
>
> My thanks to the debian maintainers (or better: condolences :) for
> investing so much time and effort into such a difficult-to-maintain
> package as mozilla!
Upgrades from mozilla to iceape (which now replaces it), and from iceape
1.0.x to 1.1.y have been troubleless here. I'll assume this somehow got
better in the meanwhile and will close this bug.
If, however, you had to remove your .mozilla directory between two
releases of iceape, please feel free to reopen this bug.
Thanks
Mike
--- End Message ---
