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 461076 - crash in Help: using help file system.
crash in Help: using help file system.
Status: RESOLVED DUPLICATE of bug 364768
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-27 21:06 UTC by followme
Modified: 2007-07-27 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description followme 2007-07-27 21:06:58 UTC 
Version: 2.16.1

What were you doing when the application crashed?
using help file system.


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

Memory status: size: 99590144 vsize: 0 resident: 99590144 share: 0 rss: 33366016 rss_rlim: 0
CPU usage: start_time: 1185570342 rtime: 0 utime: 108 stime: 0 cutime:100 cstime: 0 timeout: 8 it_real_value: 0 frequency: 4

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 -1227536720 (LWP 5495)]
[New Thread -1286825056 (LWP 5504)]
[New Thread -1278432352 (LWP 5503)]
[New Thread -1269777504 (LWP 5498)]
[New Thread -1247290464 (LWP 5497)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 151049

Thread 1 (Thread -1227536720 (LWP 5495))

  • #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 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #0 __kernel_vsyscall 






Comment 1


Iestyn Pryce





          2007-07-27 21:18:50 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 364768 ***