Re: Gramps freezing
Ron Johnson <ron.l.johnson <at> cox.net>
2014-07-25 01:38:38 GMT
That sounds like a Gtk problem. Sadly, I can't replicate it with Xubuntu
13.10 even when I shrink the gramps window enough to require scrolling.
$ gramps -v
python : 2.7.5
gramps : 4.0.4-1
gtk++ : 3.8.6
pygobject : 3.10.0
pango : 1.32.5
Not using bsddb3
bsddb : 5.3.0
bsddb.db : 5.1.29
cairo : 1.12.16
pycairo : 1.8.8
osmgpsmap : not found
GExiv2 : 0.4
ICU : 126.96.36.199
PyICU : 1.5
o.s. : linux2
kernel : 3.11.0-24-generic
LANG : en_US.UTF-8
LANGUAGE : en
GRAMPSI18N: not set
GRAMPSHOME: not set
GRAMPSDIR : not set
Graphviz : 2.26
Ghostscr. : 9.10
System PATH env variable:
On 07/24/2014 08:19 PM, Chris Bagley wrote:
> Hi Paul
> Well, I now know a little more about permissions. Did I mention I have
> even less experience with Linux than a newbie?
> Anyway, moving right along, I copied data.gramps.gz to a gramps folder
> in my home area and then extracted data.gramps, which as you say is an
> xml file. I then opened gramps, set up a new family tree and imported
> data.gramps. It opened fine and has, as you say, 60 people. I then tried
> the fan-graph option. The fan graph opened, and I moved it about a bit,
> and then it froze. I would like to attach pdfs showing the messages but
> I get bounced because I exceed the 40kb message limit. As a side issue,
> do you know if there is a way around this?
> In then meantime I have been working up a mini-family tree from scratch.
> At this stage I am only up to 12 people, but fan graph works fine.
> However, there are not enough people to make the graph big enough to
> require a slider bar, and I think that the freeze occurs when I use the
> slide bar. Let me try again using data.gramps ... yes, as I thought, I
> can swirl the graph around but when I try the slider bar I get the big
> freeze. As part of that I get a message box "This window might be busy
> and ..." which provides the opportunity to exit from Gramps.
> I will continue to enlarge the tree I am establishing and report further
> when I get enough to require the slider bar.
> Incidentally, when I use "Import" I get an error message saying
> "Django.conf could not be found. Django Addons require Django 1.3 or
> greater". Is this relevant?
> And incidentally again, Import does not recognise .gz. It is not
> included in the list of recognised file types, and when I attempt to
> load using automatic recognition it tells me it does not recognise .gz.
> On 24/07/14 23:35, Paul Franklin wrote:
>> On 7/24/14, Paul Franklin <pf.98052 <at> gmail.com> wrote:
>>> On 7/24/14, Chris Bagley <chrisbagley1 <at> bigpond.com> wrote:
>>>> Hi Paul
>>>> Thanks for the advice. I found a data.gramps as data.gramps.gz in
>>>> /usr/share/doc/gramps/example/gramps/, as well as an example.gramps.gz,
>>>> but I was refused permission to open them. I can't see a password
>>>> provision in gzip. Should I open them from the root? Or am I looking in
>>>> the wrong directory. There are no files in the Gramps directory under
>>>> the home directory, either hidden or unhidden.
>>>> On 24/07/14 13:18, Paul Franklin wrote:
>>>>> "4) Create a new and "sparse" tree with some junk names, and see if it
>>>>> still freezes."
>>>>> If you don't want to do that, use the "data.gramps" database
>>>>> (=family tree) which is included with every gramps. "Import"
>>>>> it into an empty tree. Does it them still happen?
>>>>> I wonder if you have a loop in your data? A begat B who
>>>>> begat C who adopted A, or something?
>>> Well, I guess every linux distribution packages up things
>>> slightly differently, but the files you found should be the
>>> ones I was thinking of.
>>> It's not clear to me what you mean when you said you were
>>> "refused permission to open them" since you didn't give any
>>> details. Did you try to run gunzip right there, as opposed to
>>> making a copy of that file in your own directory?
>>> But much more importantly, you shouldn't need to gunzip
>>> them at all, yourself. Gramps expects them to be compressed
>>> and will do the gunzip itself. (But if you did gunzip one, it is
>>> then an XML text file which gramps will also happily open, too.)
>>> Make a "new" family tree. It will then be empty. Go to the
>>> menu in the upper-left corner and choose File==>Import. In
>>> the resulting dialog either navigate your way to that file or type
>>> in its full pathname. Then hit accept or OK or whatever the
>>> button is down in the lower-right corner. That should allow
>>> gramps to read it in and populate your new family tree with the
>>> already-prepared data. (I suggested data.gramps since it
>>> has only sixty people, and so loads in a shorter time than the
>>> other one, which has over two thousand.)
>>> Then you can compare its behavior with your own data's one.
>> p.s. I'm not sure if gramps will "automatically" recognize the
>> "format" of either file (since it ends in ".gz" for you, I guess).
>> You might have to tell it the format, by manually choosing the
>> "gramps" format in the choice list down at the bottom-left of
>> the file=>import dialog.
My word, man! Don't you know your quantum statistics?
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.