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 384248 - crash in Help: search entry for = "tote...
crash in Help: search entry for = "tote...
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-12-10 03:20 UTC by michelnguyen808
Modified: 2006-12-10 21:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description michelnguyen808 2006-12-10 03:20:00 UTC
Version: 2.16.1

What were you doing when the application crashed?
search entry for = "totem error message = coud not open resource for writing" - help for = no sound


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

Memory status: size: 136396800 vsize: 0 resident: 136396800 share: 0 rss: 52543488 rss_rlim: 0
CPU usage: start_time: 1165720450 rtime: 0 utime: 6212 stime: 0 cutime:5937 cstime: 0 timeout: 275 it_real_value: 0 frequency: 295

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 -1227512144 (LWP 7045)]
[New Thread -1269617760 (LWP 7052)]
[New Thread -1247138912 (LWP 7047)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227512144 (LWP 7045))

  • #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 2006-12-10 21:51:06 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 ***