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 445360 - crash in Help:
crash in Help:
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-08 03:13 UTC by rgclay
Modified: 2007-08-08 20:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rgclay 2007-06-08 03:13:22 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.fc6xen #1 SMP Sat Feb 10 16:09:50 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (6 sec old) ---------------------
Failed to connect to socket /tmp/fam-rgclay-
** (bug-buddy:15723): WARNING **: Failed to connect to the FAM server: Connection failure
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  155
  Minor opcode:  6
  Resource id:  0x45
kdeinit: Got EXT_EXEC 'knotify' from launcher.
DCOP: register 'knotify' -> number of clients is now 9
DCOP: register 'anonymous-15766' -> number of clients is now 10
DCOP: new daemon knotify
DCOP: unregister 'anonymous-15766'
kdeinit: PID 15766 terminated.
** (bug-buddy:15723): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 61652992 vsize: 0 resident: 61652992 share: 0 rss: 15667200 rss_rlim: 0
CPU usage: start_time: 1181272125 rtime: 0 utime: 178 stime: 0 cutime:146 cstime: 0 timeout: 32 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208817408 (LWP 15550)]
[New Thread -1210918000 (LWP 15627)]
(no debugging symbols found)
0x003f5402 in __kernel_vsyscall ()

+ Trace 139261

Thread 1 (Thread -1208817408 (LWP 15550))

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






Comment 1


Don Scorgie





          2007-08-08 20:01:11 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 ***