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 492667 - crash in Appearance: selected preference/appe...
crash in Appearance: selected preference/appe...
Status: RESOLVED DUPLICATE of bug 501391
Product: gnome-control-center
Classification: Core
Component: [obsolete] Appearance
2.20.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 495381 497225 497226 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-11-02 11:45 UTC by mdemarco
Modified: 2007-12-14 14:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description mdemarco 2007-11-02 11:45:19 UTC 
Version: 2.20.0

What were you doing when the application crashed?
selected preference/appearance from main menu.


Distribution:                   Solaris Express Community Edition snv_75a X86
Gnome Release: 2.20.0 2007-09-24 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Default
Icon Theme: gnome

Memory status: size: 75812864 vsize: 75812864 resident: 14848000 share: 0 rss: 14848000 rss_rlim: 0
CPU usage: start_time: 0 rtime: 39 utime: 349363 stime: 44432 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-appearance-properties'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 174584

Thread 1 (LWP 1)

  • #0 _waitid
    from /usr/lib/libc.so.1
  • #1 _waitpid
    from /usr/lib/libc.so.1
  • #2 waitpid_cancel
    from /usr/lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 __sighndlr
    from /usr/lib/libc.so.1
  • #9 call_user_handler
    from /usr/lib/libc.so.1
  • #10 <signal handler called>
  • #11 countbytes
    from /usr/lib/libc.so.1
  • #12 _ndoprnt
    from /usr/lib/libc.so.1
  • #13 vsnprintf
    from /usr/lib/libc.so.1
  • #14 g_printf_string_upper_bound
    from /usr/lib/libglib-2.0.so.0
  • #15 g_vasprintf
    from /usr/lib/libglib-2.0.so.0
  • #16 g_strdup_vprintf
    from /usr/lib/libglib-2.0.so.0
  • #17 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #18 g_log
    from /usr/lib/libglib-2.0.so.0
  • #19 gtkrc_get_details
  • #20 gtk_theme_changed
  • #21 prepare_list
  • #22 style_init
  • #23 main 

Thread 1 (LWP    1        ):
#-1 0xfeef3355 in _waitid () from /usr/lib/libc.so.1
No symbol table info available.
#-1 0xfeef3355 in _waitid () from /usr/lib/libc.so.1
Comment 1 Jens Granseuer 2007-11-02 18:13:23 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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Jens Granseuer 2007-11-09 19:53:01 UTC 
*** Bug 495381 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-11-16 13:06:32 UTC 
*** Bug 497226 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-11-16 13:06:39 UTC 
*** Bug 497225 has been marked as a duplicate of this bug. ***
Comment 5 palfrey 2007-11-16 13:21:09 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 488564 ***
Comment 6 Jens Granseuer 2007-12-14 14:48:52 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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