This bug has been reported on Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/603242 mousepad crashed with SIGSEGV in g_path_get_basename() DistroRelease: Ubuntu 10.04 Package: mousepad 0.2.16-3ubuntu1 Uname: Linux 2.6.32-23-generic i686 Architecture: i386 ProcCmdline: mousepad /home/kng/Desktop/keyvalda.txt SegvAnalysis: Segfault happened at: 0x273022 <g_path_get_basename+34>: cmpb $0x0,(%eax) PC (0x00273022) ok source "$0x0" ok destination "(%eax)" (0x00000028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 StacktraceTop: IA__g_path_get_basename (file_name=0x28 <Address 0x28 out of bounds>) _gtk_text_btree_get_tags (iter=0xbfea6808, IA__gtk_text_iter_get_tags (iter=0x28) emit_event_on_tags (widget=0x28, gtk_text_view_event (widget=0x94e2808, event=0x947d638) Stacktrace available: http://launchpadlibrarian.net/51581876/Stacktrace.txt XsessionErrors.txt log file: http://launchpadlibrarian.net/51581437/XsessionErrors.txt
This bug seems fixed in version 0.3.0, even on launchpad it has been closed as 'fix released'. So I think this bug should be closed.
Closing as fixed since Ubuntu bug report confirms and the current versions is a complete re-write of the version this bug is reported against.