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 384263 - crash in Gnome Terminal: Using Theme Details to c...
crash in Gnome Terminal: Using Theme Details to c...
Status: RESOLVED INCOMPLETE
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-12-10 04:55 UTC by wbeebe
Modified: 2007-01-10 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description wbeebe 2006-12-10 04:55:13 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Using Theme Details to change the Controls look-and-feel. I switched from QtCurve to Chlorophyll.


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 86867968 vsize: 0 resident: 86867968 share: 0 rss: 9650176 rss_rlim: 0
CPU usage: start_time: 1165702742 rtime: 0 utime: 1339 stime: 0 cutime:1261 cstime: 0 timeout: 78 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/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 -1227176256 (LWP 4539)]
[New Thread -1232237680 (LWP 4545)]
(no debugging symbols found)
0xb7fa5410 in ?? ()

+ Trace 92954







Comment 1


André Klapper





          2006-12-10 23:13:13 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


Bruno Boaventura





          2007-01-10 16:47:13 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!