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 413380 - 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-03-01 09:39 UTC by 09833
Modified: 2007-03-01 12:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description 09833 2007-03-01 09:39:22 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (14 sec old) ---------------------
Yelp-ERROR **: Cannot recieve window list - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
aborting...
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  156
  Minor opcode:  6
  Resource id:  0x4d
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  156
  Minor opcode:  6
  Resource id:  0x4d
** (bug-buddy:3496): WARNING **: Couldn't load icon for Open Folder
** (bug-buddy:3498): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 62144512 vsize: 0 resident: 62144512 share: 0 rss: 16093184 rss_rlim: 0
CPU usage: start_time: 1172741865 rtime: 0 utime: 227 stime: 0 cutime:199 cstime: 0 timeout: 28 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 -1209018656 (LWP 3416)]
[New Thread -1211118704 (LWP 3450)]
(no debugging symbols found)
0x00f72402 in __kernel_vsyscall ()

+ Trace 114859

Thread 1 (Thread -1209018656 (LWP 3416))

  • #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_chain_from_overridden
    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


Pedro Villavicencio





          2007-03-01 12:20:41 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 ***