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 104877 - Gnome Themes crashes when trying to Open it
Gnome Themes crashes when trying to Open it
Status: RESOLVED DUPLICATE of bug 97883
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.1.x
Other other
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-31 02:10 UTC by GorskiLuke
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description GorskiLuke 2003-01-31 02:07:00 UTC 
Package: gnome-themes
Severity: normal
Version: 2.1.6
Synopsis: Gnome Themes crashes when trying to Open it
Bugzilla-Product: gnome-themes
Bugzilla-Component: General
BugBuddy-GnomeVersion: 2.0 (2.1.90)

Description:
Description of Problem:
When trying to open Gnome Theme the program responds with Errors.

Steps to reproduce the problem:
1. Select from menu prefferences Control Center.
2. From control center click on Gnome Themes.
3. 

Actual Results:
Error messagebox shows up with the bug submition dialogue

Expected Results:
Theme dialog to open

How often does this happen?
This is a first time I tried to go into Gnome Themes

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(no debugging symbols found)...[New Thread 1086376000 (LWP 4557)]
0xffffe002 in ?? ()

+ Trace 33340

Thread 1 (Thread 1086376000 (LWP 4557))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 gnome_theme_details_reread_themes_from_disk
  • #8 gnome_theme_details_update_from_gconf
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gnome_window_manager_settings_changed
    from /usr/lib/libgnome-window-settings.so.1
  • #15 _init
    from /usr/lib/window-manager-settings/libmetacity.so
  • #16 gconf_marshal_VOID__STRING_POINTER
    from /usr/lib/libgconf-2.so.4
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gconf_client_value_changed
    from /usr/lib/libgconf-2.so.4
  • #22 gconf_client_change_set_from_current
    from /usr/lib/libgconf-2.so.4
  • #23 gconf_client_change_set_from_current
    from /usr/lib/libgconf-2.so.4
  • #24 gconf_client_change_set_from_current
    from /usr/lib/libgconf-2.so.4
  • #25 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #26 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 main
  • #32 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-30 21:07 -------

The original reporter (GorskiLuke@cox.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, calum.benson@sun.com.
Comment 1 Calum Benson 2003-01-31 13:06:09 UTC 
Control-center bug, reassigning
Comment 2 Elijah Newren 2003-01-31 18:12:52 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Marking priority->high & severity->critical (it's
a crasher), adding GNOMEVER2.1 and bugsquad keywords, and marking as new.
Comment 3 Andrew Sobala 2003-01-31 18:37:04 UTC 
But very similar to the bug 97883 trace.

Please upgrade and see if the bug still occurs.

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