Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Martin Javorek <martin@ja...> - 2010-06-28 20:48:12
last days was bad for my Gramps app. "Nothing changed", but something must changed (I don't believe in computer ghosts). I didn't update Gramps recently, nothing new in my Python or OS (still W7), but suddenly I cannot enter data into Gramps.
After adding several new people or new info (like events, sources, ...) app hangs. It looks like hanging while saving into database (hangs when pressing OK button in a popup win). I must kill the app then, break the database tree lock and fill the info again. Today morning it didn't start after break as it finds database broken. I tried database recovery and - lost about 5 days of work (I know now why, it was the latest successfully backuped tree - and as the app is misbehaving about five days and I must kill it every day several times, it is possible that the last successfull backup was five days ago).
OK. My fault, I should better backup into gpkg/gramps files. But I want to know, what's bad in my app. Nothing visible in command line window I'm running Gramps from (in Windows 7). No errors, no warnings. I tried to study something about debug mode/logging (http://www.gramps-project.org/wiki/index.php?title=Logging_system), but cannot figure out, how turn logging into file on (if it is possible).
Can anybody help me a little bit with the bug investigation?
Thanks a lot.
From: Jakim Friant <jmodule@fr...> - 2010-06-29 14:27:51
On 06/28/2010 04:47 PM, Martin Javorek wrote:
> After adding several new people or new info (like events, sources,
> ...) app hangs. It looks like hanging while saving into database
> (hangs when pressing OK button in a popup win). I must kill the app
> then, break the database tree lock and fill the info again.
I've recently experienced something similar, but with gramplets. When I
had a bunch open that did semi-intensive operations I would get the same
type of lock-up when adding new information to a person.
I could trace it as far as a database update signal, but couldn't pin it
down to anything. The temporary solution was to remove all the
gramplets I had open and then add them back one by one. At the moment
I'm running Calendar, Top Surnames, and What Next. Census and Last
Change are two that give me trouble.
Our problems might not be related, but you could give it a try and see
> I tried to study something about debug mode/logging
> but cannot figure out, how turn logging into file on (if it is
> Can anybody help me a little bit with the bug investigation?
You should be able to turn on all debug messages by running gramps from
the command line:
They'll show up in the command window and you can copy them from there.
TCP: Why the Internet is full of SYN