Bug#577244: gnome-terminal: segmentation fault, crash on startup
Linus Lüssing
linus.luessing at web.de
Sat Apr 10 17:55:59 UTC 2010
Package: gnome-terminal
Version: 2.30.0-1
Severity: important
Tags: sid
I did an aptitude full-upgrade yesterday and since then I'm not able to
start gnome-terminal anymore, getting a segmentation fault instead.
2.28.2-1 worked fine before. Don't know if this is of any help, but
that's what I'm getting with valgrind for the Debian version:
----------------------------------------------------------
==6000== Memcheck, a memory error detector
==6000== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==6000== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info
==6000== Command: gnome-terminal
==6000==
Xlib: extension "RANDR" missing on display ":0.0".
==6000== Invalid read of size 4
==6000== at 0x7802C0B: cairo_xlib_surface_get_width (in /usr/lib/libcairo.so.2.10800.10)
==6000== by 0x6D70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D73853: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D67590: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x8069223: ??? (in /usr/bin/gnome-terminal)
==6000== by 0x73F4C9B: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73E57A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73E7141: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FCE99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FEBD3: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FF055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==6000==
==6000==
==6000== Process terminating with default action of signal 11 (SIGSEGV)
==6000== Access not within mapped region at address 0x0
==6000== at 0x7802C0B: cairo_xlib_surface_get_width (in /usr/lib/libcairo.so.2.10800.10)
==6000== by 0x6D70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D73853: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x6D67590: ??? (in /usr/lib/libvte.so.9.13.0)
==6000== by 0x8069223: ??? (in /usr/bin/gnome-terminal)
==6000== by 0x73F4C9B: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73E57A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73E7141: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FCE99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FEBD3: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== by 0x73FF055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000== If you believe this happened as a result of a stack
==6000== overflow in your program's main thread (unlikely but
==6000== possible), you can try to increase the size of the
==6000== main thread stack using the --main-stacksize= flag.
==6000== The main thread stack size used in this run was 8388608.
==6000==
==6000== HEAP SUMMARY:
==6000== in use at exit: 1,201,347 bytes in 14,389 blocks
==6000== total heap usage: 42,919 allocs, 28,530 frees, 4,175,181 bytes allocated
==6000==
==6000== LEAK SUMMARY:
==6000== definitely lost: 4,392 bytes in 15 blocks
==6000== indirectly lost: 14,460 bytes in 719 blocks
==6000== possibly lost: 790,896 bytes in 7,473 blocks
==6000== still reachable: 391,599 bytes in 6,182 blocks
==6000== suppressed: 0 bytes in 0 blocks
==6000== Rerun with --leak-check=full to see details of leaked memory
==6000==
==6000== For counts of detected and suppressed errors, rerun with: -v
==6000== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 156 from 11)
zsh: segmentation fault valgrind gnome-terminal
----------------------------------------------------------
Then I started to try compiling version 2.30.0 manually with a
"./configure && make". The "make" failed because of a missing
scrollkeeper-config. Installing rarian-compat then did the trick for
making the compiling procedure work (shouldn't the ./configure check for
the scrollkeeper-config script?).
Running this self-compiled version resulted in a similar error, but
valgrind giving some extra information for the failing function in
gnome-terminal now:
----------------------------------------------------------
==10519== Memcheck, a memory error detector
==10519== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==10519== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info
==10519== Command: ./gnome-terminal
==10519==
Xlib: extension "RANDR" missing on display ":0.0".
** (gnome-terminal:10519): WARNING **: Could not load desktop file '/usr/local/share/applications/gnome-terminal.desktop': No such file or directory
Failed to load UI: Failed to open file '/usr/local/share/gnome-terminal/terminal.xml': No such file or directory
(gnome-terminal:10519): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_WIDGET (child)' failed
(gnome-terminal:10519): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed
(gnome-terminal:10519): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `merge_id > 0' failed
(gnome-terminal:10519): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `merge_id > 0' failed
(gnome-terminal:10519): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `merge_id > 0' failed
(gnome-terminal:10519): Gtk-CRITICAL **: gtk_ui_manager_add_ui: assertion `merge_id > 0' failed
==10519== Invalid read of size 4
==10519== at 0x7425C0B: cairo_xlib_surface_get_width (in /usr/lib/libcairo.so.2.10800.10)
==10519== by 0x6E70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E73853: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E67590: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x8068AA3: terminal_screen_realize (terminal-screen.c:330)
==10519== by 0x76EBC9B: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76DC7A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76DE141: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F3E99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F5BD3: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F6055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==10519==
==10519==
==10519== Process terminating with default action of signal 11 (SIGSEGV)
==10519== Access not within mapped region at address 0x0
==10519== at 0x7425C0B: cairo_xlib_surface_get_width (in /usr/lib/libcairo.so.2.10800.10)
==10519== by 0x6E70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E73853: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x6E67590: ??? (in /usr/lib/libvte.so.9.13.0)
==10519== by 0x8068AA3: terminal_screen_realize (terminal-screen.c:330)
==10519== by 0x76EBC9B: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76DC7A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76DE141: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F3E99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F5BD3: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== by 0x76F6055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==10519== If you believe this happened as a result of a stack
==10519== overflow in your program's main thread (unlikely but
==10519== possible), you can try to increase the size of the
==10519== main thread stack using the --main-stacksize= flag.
==10519== The main thread stack size used in this run was 8388608.
==10519==
==10519== HEAP SUMMARY:
==10519== in use at exit: 1,025,634 bytes in 12,215 blocks
==10519== total heap usage: 37,102 allocs, 24,887 frees, 3,865,244 bytes allocated
==10519==
==10519== LEAK SUMMARY:
==10519== definitely lost: 2,344 bytes in 9 blocks
==10519== indirectly lost: 6,540 bytes in 327 blocks
==10519== possibly lost: 642,549 bytes in 6,172 blocks
==10519== still reachable: 374,201 bytes in 5,707 blocks
==10519== suppressed: 0 bytes in 0 blocks
==10519== Rerun with --leak-check=full to see details of leaked memory
==10519==
==10519== For counts of detected and suppressed errors, rerun with: -v
==10519== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 156 from 11)
zsh: segmentation fault valgrind ./gnome-terminal
----------------------------------------------------------
Hope this information helps, xterm just sucks :P.
Cheers, Linus
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnome-terminal depends on:
ii gnome-terminal-data 2.30.0-1 Data files for the GNOME terminal
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libdbus-glib-1-2 0.84-1 simple interprocess messaging syst
ii libgconf2-4 2.28.1-1 GNOME configuration database syste
ii libglib2.0-0 2.24.0-1 The GLib library of C routines
ii libgtk2.0-0 2.20.0-2 The GTK+ graphical user interface
ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library
ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio
ii libsm6 2:1.1.1-1 X11 Session Management library
ii libvte9 1:0.24.0-1 Terminal emulator widget for GTK+
ii libx11-6 2:1.3.3-2 X11 client-side library
Versions of packages gnome-terminal recommends:
ii gvfs 1.6.0-1 userspace virtual filesystem - ser
ii yelp 2.30.0+webkit-1 Help browser for GNOME
gnome-terminal suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list