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 444876 - crash in Yelp: restart
crash in Yelp: restart
Status: RESOLVED DUPLICATE of bug 364790
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-06 20:24 UTC by yattongwu
Modified: 2007-08-08 20:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description yattongwu 2007-06-06 20:24:06 UTC
Version: 2.16.1

What were you doing when the application crashed?
restart


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

Memory status: size: 407126016 vsize: 407126016 resident: 75931648 share: 29253632 rss: 105185280 rss_rlim: -771239936
CPU usage: start_time: 1181160982 rtime: 246 utime: 235 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47226855634720 (LWP 8735)]
[New Thread 1090525504 (LWP 8737)]
[New Thread 1082132800 (LWP 8736)]
(no debugging symbols found)
0x00002af3d8601c5f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47226855634720 (LWP 8735))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #7 nsIPrefService::GetIID
  • #8 gnome_ice_init
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #9 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #13 gnome_client_set_clone_command
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #14 _SmcProcessMessage
    from /usr/lib64/libSM.so.6
  • #15 IceProcessMessages
    from /usr/lib64/libICE.so.6
  • #16 gnome_ice_init
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #17 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #18 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #20 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #21 nsIPrefService::GetIID
  • #22 __libc_start_main
    from /lib64/libc.so.6
  • #23 g_cclosure_marshal_VOID__VOID
  • #24 ??
  • #25 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Don Scorgie 2007-08-08 20:04:49 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 364790 ***