zim crashed with SIGSEGV in g_main_context_prepare()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zim (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: zim
just done an edit source to gedit when I got this error. Wannted to see the underlying syntax for the text files.
ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 14:09:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/zim
InterpreterPath: /usr/bin/perl
Package: zim 0.28-1
PackageArchitec
ProcCmdline: /usr/bin/perl /usr/bin/zim
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x2e2f3e <g_main_
PC (0x002e2f3e) ok
source "(%eax)" (0x00c47c00) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: zim
StacktraceTop:
g_main_
?? () from /lib/libglib-
g_main_loop_run () from /lib/libglib-
gtk_main () from /usr/lib/
XS_Gtk2_main () from /usr/lib/
Title: zim crashed with SIGSEGV in g_main_
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in zim (Ubuntu): | |
status: | New → Invalid |
Probably due to a glitch in either gtk itself or the gtk-perl bindings. A bug in the perl code in which the application is written should never result in a segfault.
Since zim 0.42 is a complete rewrite now using python-gtk bindings instead, and since gtk has seen new releases since this bug report I advise closing it.