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 372112 - crash in Help: Mein Programm ist nicht ...
crash in Help: Mein Programm ist nicht ...
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: 2006-11-07 18:21 UTC by hamika
Modified: 2006-11-21 19:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description hamika 2006-11-07 18:21:57 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Mein Programm ist nicht abgestürzt.
Mein 3d-treiber scheint nicht zu funktionieren.


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

Memory status: size: 149327872 vsize: 0 resident: 149327872 share: 0 rss: 48287744 rss_rlim: 0
CPU usage: start_time: 1162923360 rtime: 0 utime: 311 stime: 0 cutime:279 cstime: 0 timeout: 32 it_real_value: 0 frequency: 6

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 -1228003664 (LWP 5724)]
[New Thread -1288377440 (LWP 5727)]
[New Thread -1247851616 (LWP 5726)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84064

Thread 1 (Thread -1228003664 (LWP 5724))

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


André Klapper





          2006-11-08 16:10:29 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


Don Scorgie





          2006-11-21 19:17:44 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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