Just open from menu emacs, the cmd line is /usr/bin/emacs23 %F
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: emacs23 23.3+1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Wed Jun 29 22:44:33 2011
ExecutablePath: /usr/bin/emacs23-x
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcCmdline: /usr/bin/emacs23
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LC_MESSAGES=en_US.utf8
LANG=es_CL.utf8
LANGUAGE=en_US:en
SegvAnalysis:
Segfault happened at: 0x8fa416 <__kernel_vsyscall+2>: ret
PC (0x008fa416) ok
destination "(%esp)" (0xbfa44de8) ok
SP (0xbfa44de8) ok
Reason could not be automatically determined. (Unhandled exception in kernel code?)
Signal: 11
SourcePackage: emacs23
StacktraceTop:
os_pager_hide (pager=0x0) at /build/buildd/overlay-scrollbar-0.2.1/./os/os-pager.c:378
os_scrollbar_unrealize (widget=0xa31a160) at /build/buildd/overlay-scrollbar-0.2.1/./os/os-scrollbar.c:2494
g_cclosure_marshal_VOID__VOID (closure=0x84f93e8, return_value=0x0, n_param_values=1, param_values=0xa110f98, invocation_hint=0xbfa45710, marshal_data=0x7f6b130) at /build/buildd/glib2.0-2.29.8/./gobject/gmarshal.c:79
g_type_class_meta_marshal (closure=0x84f93e8, return_value=0x0, n_param_values=1, param_values=0xa110f98, invocation_hint=0xbfa45710, marshal_data=0x78) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:882
g_closure_invoke (closure=0x84f93e8, return_value=0x0, n_param_values=1, param_values=0xa110f98, invocation_hint=0xbfa45710) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771
Title: emacs23-x crashed with SIGSEGV in os_pager_hide()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 800387, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.