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 382022 - 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: 2006-12-03 21:35 UTC by eshowman
Modified: 2006-12-05 01:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description eshowman 2006-12-03 21:35:26 UTC 
Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 51535872 vsize: 0 resident: 51535872 share: 0 rss: 17518592 rss_rlim: 0
CPU usage: start_time: 1165181693 rtime: 0 utime: 93 stime: 0 cutime:85 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227163984 (LWP 6345)]
[New Thread -1246774368 (LWP 6405)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 91370

Thread 1 (Thread -1227163984 (LWP 6345))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/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/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/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 _IO_stdin_used
  • #11 ??
  • #12 _IO_stdin_used
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-12-05 01:53:33 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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