Well, I'm getting this fairly consistently from gdb:
Program received signal SIGSEGV, Segmentation fault.
0xb78b6630 in ?? () from /var/lib/python-support/python2.5/gtk-2.0/gtk/_gtk.so
but I can't seem to narrow it down. And pdb can't attach to an already
running process, so it gets lost by the t
Well, then -- it sounds like you know your stuff. Perhaps you can file
a report upstream, and see what they say?
One thought I have: if you could somehow kill Scribes, using Ctrl+C, via
a terminal, then you might see a Python stack trace... But,
unfortunately, I don't know of any way to make Scr
Ah bollocks. I always get turned around in Launchpad. I guess I didn't
file it under Gutsy :/.
I'm using Gutsy, resynced this morning, and the latest version of
Scribes from the repositories, which is 0.3.2.8. I have yet to try
purging all Scribes configuration, because I have done that in the
pas
Hi Henry. Which versions of Scribes and Ubuntu are you using?
--
Right click menu causes Scribes to crash
https://bugs.launchpad.net/bugs/137641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Public bug reported:
Binary package hint: scribes
To reproduce, right click on the main text box, and then click either on
the context menu or somewhere else. Scribes stops responding
indefinitely.
** Affects: scribes (Ubuntu)
Importance: Undecided
Status: New
--
Right click menu
