On Fri, Sep 09, 2005 at 04:34:36PM -0700, Alex Roitman wrote:
> James, should we close this one since it's not gramps' problem?
Since part of gramps will be broken until this is fixed, it is usual
to keep the bug open until the problem is fixed.
--
James Treacy
[EMAIL PROTECTED]
--
To UNSUBSC
Quoting Alex Roitman <[EMAIL PROTECTED]>:
[ snip ]
>
> Please go ahead and file the new one. The import statement causing
> segfault is really the only thing they will need to know to fix it. The
> gramps baggage is irrelevant to them.
>
> James, should we close this one since it's not gramps' pro
Quoting Alex Roitman <[EMAIL PROTECTED]>:
> Larry,
>
> On Fri, 2005-09-09 at 16:19 -0700, Larry McCarthy wrote:
> > rio:/home/lmm# apt-get remove python2.3-gnome2-extras
> [snip]
> > And gramps comes up fine.
>
> Thanks for confirming. Now, if you could come up with a simple
> testcase showing gtk
On Fri, 2005-09-09 at 16:31 -0700, Larry McCarthy wrote:
> [EMAIL PROTECTED]:~$ python
> Python 2.3.5 (#2, Aug 31 2005, 03:10:40)
> [GCC 4.0.2 20050821 (prerelease) (Debian 4.0.1-6)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import gtkspell
> Segmentat
Larry,
On Fri, 2005-09-09 at 16:19 -0700, Larry McCarthy wrote:
> rio:/home/lmm# apt-get remove python2.3-gnome2-extras
[snip]
> And gramps comes up fine.
Thanks for confirming. Now, if you could come up with a simple
testcase showing gtkspell problem it would be great. What if
you install python
Quoting Alex Roitman <[EMAIL PROTECTED]>:
[ -snip- ]
>
> Looks like gtkspell's problem. Removing python-gnome2-extras (actually,
> python2.3-gnome2-extras) should help in this case, at the cost of no
> spell checking in the notes.
>
> If you can confirm this, I think we can re-assign the bug to
>
On Fri, 2005-09-09 at 15:19 -0700, Larry McCarthy wrote:
> (gdb) backtrace
> #0 0x2b0d69d0 in strlen () from /lib/libc.so.6
> #1 0x0043c6ab in PyString_FromString ()
> #2 0x004368fe in PyDict_GetItemString ()
> #3 0x0044a749 in PyType_Ready ()
> #4 0x2aaab22
Quoting "James A. Treacy" <[EMAIL PROTECTED]>:
> It would be useful if you could run gramps under gdb:
> $ cd /usr/share/gramps
> $ gdb /usr/bin/python
> (gdb) run gramps.py
> after it segfaults then type
> (gdb) backtrace
>
> Please send the results of the backtrace as a reply. This should he
It would be useful if you could run gramps under gdb:
$ cd /usr/share/gramps
$ gdb /usr/bin/python
(gdb) run gramps.py
after it segfaults then type
(gdb) backtrace
Please send the results of the backtrace as a reply. This should help
us identify which library has the bug and refile the bug aga
se for a segfault, only a python traceback.
> This crash is caused by a bug in one of the python packages that gramps
> uses.
>
> Do other python applications work fine? For example: meld or pygtk-demo
>
>
> Cheers, Martin.
>
>
>
> > Betreff: Bug#327297: gramps
.
> Betreff: Bug#327297: gramps 2.0.8-1 segfaults on startup on AMD64
>
> >>From terminal window:
>
> $ gramps
> Segmentation fault
> $
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
--
To U
Hmmm.. this is a segfault. GRAMPS is written in 100% python and can never be
the cause for a segfault, only a python traceback.
This crash is caused by a bug in one of the python packages that gramps
uses.
Do other python applications work fine? For example: meld or pygtk-demo
Cheers, Martin.
Package: gramps
Version: 2.0.8-1
Severity: grave
Justification: renders package unusable
Start gramps from (KDE) menu - never starts
>From terminal window:
$ gramps
Segmentation fault
$
/var/log/syslog says:
Sep 8 21:03:34 localhost kernel: python[5235]: segfault at
0005 rip
13 matches
Mail list logo
