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 396254 - crash in Help: Bij het opzetten van (vo...
crash in Help: Bij het opzetten van (vo...
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-01-13 22:14 UTC by Eduard de Leeuw
Modified: 2007-02-07 23:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Eduard de Leeuw 2007-01-13 22:14:39 UTC
Version: 2.16.1

What were you doing when the application crashed?
Bij het opzetten van (voor mij nieuw) Ubuntu, was ik bezig met randapparatuur. 
Bij crash van Help zocht ik hulpinformatie voor installatieproblemen bij installeren van driver voor Canon BLC4200 printer.
Printer werd herkend in de lijst, maar stopte na ongeveer 10 lijnen van de testpagina.
In de hulpfunctie bovenaan het scherm typte ik ´printer´ in.

Even daarvoor liep bij het configureren van de geluidsindstellingen het venster vast. (systeem->voorkeuren->geluid->geluidsopname testen->sluiten->´wilt u geforceerd afsluiten?´)


Met vriendelijke groeten, Eduard de Leeuw


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

Memory status: size: 171208704 vsize: 0 resident: 171208704 share: 0 rss: 69271552 rss_rlim: 0
CPU usage: start_time: 1168725829 rtime: 0 utime: 1624 stime: 0 cutime:1542 cstime: 0 timeout: 82 it_real_value: 0 frequency: 29

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 -1227647312 (LWP 6016)]
[New Thread -1322161248 (LWP 6036)]
[New Thread -1313768544 (LWP 6035)]
[New Thread -1305375840 (LWP 6034)]
[New Thread -1296983136 (LWP 6033)]
[New Thread -1288311904 (LWP 6024)]
[New Thread -1247519840 (LWP 6018)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227647312 (LWP 6016))

  • #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 Christian Kirbach 2007-01-29 21:27:30 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 Marc-Andre Lureau 2007-02-07 23:51:12 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 ***