After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 394177 - crash in Terminal: Ich habe meinen Laptop a...
crash in Terminal: Ich habe meinen Laptop a...
Status: RESOLVED DUPLICATE of bug 357406
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-08 09:47 UTC by dark.ts
Modified: 2007-01-12 01:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dark.ts 2007-01-08 09:47:37 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Ich habe meinen Laptop aus dem Ruhezustand hochgefahren und etwas an meinen Themeneinstellungen geändert.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 43573248 vsize: 0 resident: 43573248 share: 0 rss: 16171008 rss_rlim: 0
CPU usage: start_time: 1168190785 rtime: 0 utime: 204 stime: 0 cutime:194 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226705232 (LWP 4665)]
[New Thread -1269056608 (LWP 4782)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 100391

Thread 1 (Thread -1226705232 (LWP 4665))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #6 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #7 g_quark_from_static_string
    from /usr/lib/libglib-2.0.so.0
  • #8 rsvg_error_quark
    from /usr/lib/librsvg-2.so.2
  • #9 rsvg_error_quark
    from /usr/lib/librsvg-2.so.2
  • #10 rsvg_handle_write
    from /usr/lib/librsvg-2.so.2
  • #11 theme_pixbuf_render
    from /usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
  • #12 g_cache_insert
    from /usr/lib/libglib-2.0.so.0
  • #13 theme_pixbuf_get_pixbuf
    from /usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
  • #14 theme_pixbuf_render
    from /usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
  • #15 rsvg_style_register_type
    from /usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
  • #16 rsvg_style_register_type
    from /usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
  • #17 gtk_paint_box
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_menu_bar_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gdk_window_is_viewable
    from /usr/lib/libgdk-x11-2.0.so.0
  • #28 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #29 gtk_container_check_resize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
  • #36 ??
  • #37 _IO_stdin_used
  • #38 ??
  • #39 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-01-12 01:20:54 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 357406 ***