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 411579 - crash in Help: impossible de telecharge...
crash in Help: impossible de telecharge...
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-24 14:51 UTC by guy.dalmasso
Modified: 2007-02-25 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description guy.dalmasso 2007-02-24 14:51:07 UTC 
Version: 2.16.1

What were you doing when the application crashed?
impossible de telecharger les misese à jour


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

Memory status: size: 104583168 vsize: 0 resident: 104583168 share: 0 rss: 46370816 rss_rlim: 0
CPU usage: start_time: 1172332200 rtime: 0 utime: 132 stime: 0 cutime:122 cstime: 0 timeout: 10 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 -1227196752 (LWP 6789)]
[New Thread -1278518368 (LWP 6795)]
[New Thread -1269703776 (LWP 6792)]
[New Thread -1247069280 (LWP 6791)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113514

Thread 1 (Thread -1227196752 (LWP 6789))

  • #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


Susana





          2007-02-25 13:49:21 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 ***