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 366150 - crash in Terminal: Changing gtk themes from...
crash in Terminal: Changing gtk themes from...
Status: RESOLVED DUPLICATE of bug 364396
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-10-28 08:03 UTC by ahornby
Modified: 2006-10-28 18:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ahornby 2006-10-28 08:03:49 UTC
Version: 2.16.1

What were you doing when the application crashed?
Changing gtk themes from QT to Raleigh. This is a duplicate of a previous bug report. A recent email from the developer asked for more crash reports with libglib gtk debug packages installed. Happy to oblige. Is reproducible every time the same way. Let me know if you need more. Regards Anthony. 


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

Memory status: size: 83677184 vsize: 0 resident: 83677184 share: 0 rss: 16232448 rss_rlim: 0
CPU usage: start_time: 1161988782 rtime: 0 utime: 368 stime: 0 cutime:326 cstime: 0 timeout: 42 it_real_value: 0 frequency: 5

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 -1225701712 (LWP 11850)]
[New Thread -1277793376 (LWP 11854)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225701712 (LWP 11850))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 ??
  • #5 gdk_event_apply_filters
    at gdkevents-x11.c line 345
  • #6 gdk_event_translate
    at gdkevents-x11.c line 894
  • #7 _gdk_events_queue
    at gdkevents-x11.c line 2254
  • #8 gdk_event_dispatch
    at gdkevents-x11.c line 2314
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 IA__gtk_main
    at gtkmain.c line 1024
  • #13 ??
  • #14 ??
  • #15 _IO_stdin_used
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-28 18:35:29 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 364396 ***