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 377227 - crash in Terminal: just changed a gtk theme...
crash in Terminal: just changed a gtk theme...
Status: RESOLVED DUPLICATE of bug 353498
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: 2006-11-20 00:37 UTC by lifeless_
Modified: 2006-11-21 17:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lifeless_ 2006-11-20 00:37:14 UTC 
Version: 2.16.1

What were you doing when the application crashed?
just changed a gtk theme, the gtk theme was amora, and it's reperible here: http://www.capc-online.net/?p=41,
The console was running mp32ogg on a shared folder so maybe it's alla cause to a acces violation ? i dunnow, hope this is helpfull


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

Memory status: size: 136974336 vsize: 136974336 resident: 18280448 share: 10321920 rss: 18280448 rss_rlim: -1
CPU usage: start_time: 1163979857 rtime: 162 utime: 142 stime: 20 cutime:1598 cstime: 57 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47875926972080 (LWP 4986)]
[New Thread 1082132816 (LWP 4990)]
(no debugging symbols found)
0x00002b8af773beef in waitpid () from /lib/libpthread.so.0

+ Trace 87852

Thread 1 (Thread 47875926972080 (LWP 4986))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_style_get_valist
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 gtk_widget_style_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 gtk_widget_style_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 gtk_widget_style_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 gtk_widget_style_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 gtk_widget_style_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 gtk_widget_queue_resize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 gtk_widget_set_usize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 gtk_widget_set_usize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_notebook_popup_enable
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_box_pack_start_defaults
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_rc_get_module_dir
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 gtk_rc_reparse_all_for_settings
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 gtk_rc_reparse_all
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #21 g_object_class_override_property
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_object_notify
    from /usr/lib64/libgobject-2.0.so.0
  • #23 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 _gdk_events_init
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 ??
  • #30 __libc_start_main
    from /lib/libc.so.6
  • #31 ??
  • #32 ??
  • #33 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Mariano Suárez-Alvarez





          2006-11-21 17:12:04 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 353498 ***