Bug 366291 – crash in Terminal: Trying to change a theme...

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 366291 - crash in Terminal: Trying to change a theme...


Summary:	crash in Terminal: Trying to change a theme...


Status:	RESOLVED DUPLICATE of bug 352265

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-28 14:13 UTC by Raptor Ramjet
Modified:	2006-10-28 14:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Raptor Ramjet 2006-10-28 14:13:50 UTC

Version: 2.16.1

What were you doing when the application crashed?
Trying to change a theme using the "Theme Preferences" > "Theme Details" dialogue.  i.e. nothing special...


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

Memory status: size: 63148032 vsize: 0 resident: 63148032 share: 0 rss: 14843904 rss_rlim: 0
CPU usage: start_time: 1161975221 rtime: 0 utime: 160 stime: 0 cutime:148 cstime: 0 timeout: 12 it_real_value: 0 frequency: 12

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 -1226549584 (LWP 6787)]
[New Thread -1259070560 (LWP 6791)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79274

Thread 1 (Thread -1226549584 (LWP 6787))

#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 ??
#5 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#6 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#7 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#8 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
#15 _IO_stdin_used
#16 ??
#17 ??
#0 __kernel_vsyscall

Comment 1 Fabio Bonelli 2006-10-28 14:40:08 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 352265 ***