On Mon, 2005-04-04 at 12:21, Lo�c Minier wrote: > Hi, > > On Mon, Apr 04, 2005, Francois wrote: > > Sorry for not including the version. I used reportbug and did not check > > that there was a problem there as well (namely my > > /var/lib/dpkg/available seems to have got corrupted, so that i.e. dpkg > > -l does not work any more. I've filled a bug about it). > > Well, that looks like FS corruption to me: > - your /var/lib/dpkg/available is corrupted, > - your bookmarks disappear.
I did not think of it. I'll check this. > > I was using galeon_1.3.19-1 before > > The bookmarks file format has not changed between 1.3.19 and 1.3.20, > and I've downgraded and upgraded multiple times in the past, especially > from the buggy 1.3.19-1, so I don't see how Galeon might have fiddled > with your files from 1.3.19-1 until now, but for example they could > have been corrupted by an older version, and kept mysteriously intact > until now. If you've done it a lot in the past, then probably galeon is fine, and the culprit must be looked for somewhere else. > I suppose you would remember using a bookmarks import / export utility, > or maybe "galeon-config-tool" if that could have been the source of > your trouble. Simply overwriting bookmarks.xbel with bookmarks.xbel.3 (which, for some reason, contained a backup of my bookmarks) did the trick. > Since it's the only trail I may follow right now, I suggest you check > your hard disk and FS: > What FS type are you using? I got frequent corruptions with XFS for > example, random files get filled with zeroes, are truncated, or reset > to void. I'm using ext2 on a 6-month old Powerbook, but I might be unlucky and have a corrupt HD. > Are you confident with your hard disk? Are you using DMA? Does your > DMA driver print kernel warnings in your syslog? I've looked at my logs, but I've found no suspicious messages. I have tried to downgrade and upgrade galeon manually between 1.3.19 and 1.3.20 with dpkg -i and everything seems fine. I'll try to look around to see if it's something related to some problem on my machine, or if some other program messed around with my config file. In any case this does not seem to be related to galeon, so I would suggest closing this bug. Many thanks for the very quick support, and sorry for this false alarm. Kind regards Francois > Regards,
