GNOME Bugzilla – Bug 396254
crash in Help: Bij het opzetten van (vo...
Last modified: 2007-02-07 23:51:12 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 ()
+ Trace 101896
Thread 1 (Thread -1227647312 (LWP 6016))
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!
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 ***