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 364105 - crash in Help: I was trying to read the...
crash in Help: I was trying to read the...
Status: RESOLVED DUPLICATE of bug 362797
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-22 08:10 UTC by gianpiero.ascenso
Modified: 2006-10-22 10:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gianpiero.ascenso 2006-10-22 08:10:20 UTC
Version: 2.16.1

What were you doing when the application crashed?
I was trying to read the emacs info from the Gnome Info center


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

Memory status: size: 124628992 vsize: 0 resident: 124628992 share: 0 rss: 42684416 rss_rlim: 0
CPU usage: start_time: 1161504424 rtime: 0 utime: 1249 stime: 0 cutime:1224 cstime: 0 timeout: 25 it_real_value: 0 frequency: 14

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 -1227245904 (LWP 5476)]
[New Thread -1302688864 (LWP 5489)]
[New Thread -1268851808 (LWP 5480)]
[New Thread -1247241312 (LWP 5479)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227245904 (LWP 5476))

  • #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 free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_free
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 _IO_stdin_used
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall

Comment 1 Fabio Bonelli 2006-10-22 10:58:00 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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