From: Emrys W. <emr...@ev...> - 2009-04-29 06:16:12
|
I think that, no matter how broken gramps was, it shouldn't be able to "freeze" an entire linux system. If the keyboard stops working, then the internals of linux are in a mess, and no user program, no matter how bizarre, should be able to do that. It implies either a bug in the linux kernel, which happens to be exercised by some sequence of gramps operations, or a fault in your hardware which linux isn't hardened against, again exercised by gramps operations. Tedious, but not really gramps's problem. The fact that the gramps check-and-repair tool doesn't detect upsets in the database which later cause errors elsewhere in gramps is more relevant. This happened to me, too, although I have no idea if it was the same bug. I deleted the records of the people from the database and re-entered them by hand, and the errors went away. Emrys Williams 2009/4/28 doug <dro...@al...> > Hi, > > I originally filed a bug report on what I thought was a bug in NavWeb. > On further testing it's obviously not that; but I'm not sure what to do > next. > I'm hoping you Gramps-users can give me some advice. There seem to be a > couple of problems: > > I'm using 3.1.1 on Mandriva Linux 2008.1 64-bit. > > I've twice had gramps freeze the entire system on me - with two > different databases during different editing processes. When this > happened I couldn't kill the program, the X-server, Ctrl-Alt-Del, etc.; > the screen, keyboard and mouse were frozen. I could only get out by > pulling the power supply. > > In these circumstances there were no error messages. > So the first problem: > (1) How can I follow this up? > > My filesystem is ReiserFS. After each deliberate crash I got back to the > state before the freeze: the databases seemed perfectly OK. > Except that when I now attempted to create a NavWeb Report from those > databases, the Report would not work with the option 'include persons > marked private' disabled. (It worked perfectly with other databases). It > crashed, the error dump indicating that for some record or other the > Privacy attribute was unset or missing. > This wasn't apparent in gramps itself: I was able to filter on persons > marked private or not marked private without errors. > Moreover the Check and Repair Tool indicated there were no internal > errors in the databases. > So the second problem: > (2) Check and Repair did not pick up errors in the Privacy attributes of > one or more of the records. Could something be done about this? > > I've put the details of the crashes in bug report 0002942 > > Doug > > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > > |