Your message dated Tue, 22 Dec 2009 11:55:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#473065: iceweasel: Missing URL's showing as "visited" 
but not in history menus
has caused the Debian Bug report #473065,
regarding iceweasel: lost history on 2.0.0.12-1 to 2.0.0.13-1 upgrade
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.)


-- 
473065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473065
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iceweasel
Version: 2.0.0.13-1
Severity: normal


On upgrade of Iceweasel from 2.0.0.12-1 to 2.0.0.13-1 all previous 
history was lost.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-rc6 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages iceweasel depends on:
ii  debianutils            2.28.4            Miscellaneous utilities specific t
ii  fontconfig             2.5.0-2           generic font configuration library
ii  libatk1.0-0            1.22.0-1          The ATK accessibility toolkit
ii  libc6                  2.7-9             GNU C Library: Shared libraries
ii  libcairo2              1.4.14-1          The Cairo 2D vector graphics libra
ii  libfontconfig1         2.5.0-2           generic font configuration library
ii  libfreetype6           2.3.5-1+b1        FreeType 2 font engine, shared lib
ii  libgcc1                1:4.3.0-2         GCC support library
ii  libglib2.0-0           2.16.1-2          The GLib library of C routines
ii  libgtk2.0-0            2.12.9-2          The GTK+ graphical user interface 
ii  libhunspell-1.1-0      1.1.9-1           spell checker and morphological an
ii  libjpeg62              6b-14             The Independent JPEG Group's JPEG 
ii  libnspr4-0d            4.7.0-2           NetScape Portable Runtime Library
ii  libnss3-1d             3.12.0~beta2-1    Network Security Service libraries
ii  libpango1.0-0          1.20.0-1          Layout and rendering of internatio
ii  libpng12-0             1.2.15~beta5-3    PNG library - runtime
ii  libstdc++6             4.3.0-2           The GNU Standard C++ Library v3
ii  libx11-6               2:1.0.3-7         X11 client-side library
ii  libxft2                2.1.12-2          FreeType-based font drawing librar
ii  libxinerama1           2:1.0.3-1         X11 Xinerama extension library
ii  libxp6                 1:1.0.0.xsf1-1    X Printing Extension (Xprint) clie
ii  libxrender1            1:0.9.4-1         X Rendering Extension client libra
ii  libxt6                 1:1.0.5-3         X11 toolkit intrinsics library
ii  procps                 1:3.2.7-6         /proc file system utilities
ii  psmisc                 22.6-1            Utilities that use the proc filesy
ii  zlib1g                 1:1.2.3.3.dfsg-11 compression library - runtime

iceweasel recommends no packages.

-- debconf-show failed



--- End Message ---
--- Begin Message ---
On Fri, Mar 28, 2008 at 04:54:25PM +1030, Arthur Marsh wrote:
> Package: iceweasel
> Version: 2.0.0.13-1
> Followup-For: Bug #473065
> 
> 
> I went to a web page which had links to the pages that I had had open 
> but had not shown in the history menu, and the links that I had had open 
> in iceweasel 2.0.0.12-1 were shown in a different colour showing that 
> they had been visited.
> 
> I was unable to reproduce the problem on another machine running Debian 
> unstable going through the upgrade process.
> 
> So it appears that sessionstore.js on the first machine was lost for 
> unknown reasons.

That could have been file access rights, and the upgrade process /could/
have been a trigger, in some particular situations, though I'm not quite
sure.

Anyways, the upgrade process has been safe since at least version 3.0
and the hypothetical particular situations I'm referring to above
definitely can't happen with these newer versions.

I'll therefore close this bug.

Thanks for your report.

Cheers,

Mike


--- End Message ---

Reply via email to