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 430770 - crash in Help: logging in
crash in Help: logging in
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: 2007-04-17 19:39 UTC by rpiyer
Modified: 2007-04-18 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rpiyer 2007-04-17 19:39:57 UTC 
Version: 2.16.1

What were you doing when the application crashed?
logging in					


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

Memory status: size: 51527680 vsize: 0 resident: 51527680 share: 0 rss: 17944576 rss_rlim: 0
CPU usage: start_time: 1176838740 rtime: 0 utime: 72 stime: 0 cutime:60 cstime: 0 timeout: 12 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 -1228097872 (LWP 4668)]
[New Thread -1247745120 (LWP 4692)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128594

Thread 1 (Thread -1228097872 (LWP 4668))

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






Comment 1


Pedro Villavicencio





          2007-04-18 00:27:10 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 364790 ***