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 371007 - 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
: 371186 416310 416430 421600 423446 423674 428703 434395 452011 452040 453100 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-05 12:51 UTC by barthelemy
Modified: 2007-08-08 20:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description barthelemy 2006-11-05 12:51:20 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 37494784 vsize: 0 resident: 37494784 share: 0 rss: 13148160 rss_rlim: 0
CPU usage: start_time: 1162731029 rtime: 0 utime: 25 stime: 0 cutime:22 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229027632 (LWP 6419)]
[New Thread -1233343584 (LWP 6459)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 83181

Thread 1 (Thread -1229027632 (LWP 6419))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/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/libc.so.6
  • #6 abort
    from /lib/i686/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 gnome_ice_init
    from /usr/lib/libgnomeui-2.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_override_class_closure
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/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 /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
  • #25 __libc_start_main
    from /lib/i686/libc.so.6
  • #26 ?? 






Comment 1


Don Scorgie





          2006-11-05 20:00:31 UTC
        



*** Bug 371186 has been marked as a duplicate of this bug. ***






Comment 2


Don Scorgie





          2006-11-05 20:02:28 UTC
        



Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Unfortunately, that stack trace is also 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. Thanks in advance!







Comment 3


André Klapper





          2006-12-04 23:09:19 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!







Comment 4


palfrey





          2007-04-29 22:16:26 UTC
        



*** Bug 434395 has been marked as a duplicate of this bug. ***






Comment 5


palfrey





          2007-04-30 15:02:07 UTC
        



*** Bug 416310 has been marked as a duplicate of this bug. ***






Comment 6


palfrey





          2007-04-30 15:02:10 UTC
        



*** Bug 416430 has been marked as a duplicate of this bug. ***






Comment 7


palfrey





          2007-04-30 15:09:50 UTC
        



*** Bug 421600 has been marked as a duplicate of this bug. ***






Comment 8


palfrey





          2007-04-30 15:10:48 UTC
        



*** Bug 423446 has been marked as a duplicate of this bug. ***






Comment 9


palfrey





          2007-04-30 15:12:02 UTC
        



*** Bug 423674 has been marked as a duplicate of this bug. ***






Comment 10


palfrey





          2007-04-30 15:16:40 UTC
        



*** Bug 428703 has been marked as a duplicate of this bug. ***






Comment 11


palfrey





          2007-06-29 11:56:07 UTC
        



*** Bug 452011 has been marked as a duplicate of this bug. ***






Comment 12


palfrey





          2007-06-29 11:56:09 UTC
        



*** Bug 452040 has been marked as a duplicate of this bug. ***






Comment 13


Christian Kirbach





          2007-07-02 20:57:53 UTC
        



piles of duplicates .. Tom why did you not reopen?? This also caused the addresses of the dups not to be CCed here. *rustle*








Comment 14


Christian Kirbach





          2007-07-02 20:59:55 UTC
        



*** Bug 453100 has been marked as a duplicate of this bug. ***






Comment 15


Christian Kirbach





          2007-07-02 21:01:33 UTC
        



a more complete trace here:






+
Trace
    145341






    

  • 
#3
<signal handler called>

    • 

  • 
#4
__kernel_vsyscall

    • 

  • 
#5
raise

    
                from
                /lib/libc.so.6

    

    • 

  • 
#6
abort

    
                from
                /lib/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

    

    • 













Comment 16


Christian Kirbach





          2007-07-02 21:01:44 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 17


Don Scorgie





          2007-08-08 20:09:07 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 ***