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 412532 - crash in Help: Clicking the back button
crash in Help: Clicking the back button
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-02-27 05:13 UTC by dominator1
Modified: 2007-03-15 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dominator1 2007-02-27 05:13:24 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Clicking the back button


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

Memory status: size: 134733824 vsize: 0 resident: 134733824 share: 0 rss: 51175424 rss_rlim: 0
CPU usage: start_time: 1172553023 rtime: 0 utime: 2230 stime: 0 cutime:2052 cstime: 0 timeout: 178 it_real_value: 0 frequency: 90

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 -1227401552 (LWP 4566)]
[New Thread -1303393376 (LWP 4584)]
[New Thread -1278215264 (LWP 4581)]
[New Thread -1269560416 (LWP 4573)]
[New Thread -1247073376 (LWP 4570)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 114246

Thread 1 (Thread -1227401552 (LWP 4566))

  • #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 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Claudio Saavedra





          2007-03-15 22:38:43 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 ***