Version: 0.8 (using KDE 4.2.2) Installed from: Ubuntu Packages Questo backtrace sembra essere inutile. Probabilmente i pacchetti che stai utilizzando sono compilati in modo che non si possano creare dei backtrace corretti oppure lo stack frame è stato danneggiato seriamente durante il crash. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5f86700 (LWP 5158)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f68430 in __kernel_vsyscall () [Current thread is 0 (process 5158)] Thread 1 (Thread 0xb5f86700 (LWP 5158)): #0 0xb7f68430 in __kernel_vsyscall () #1 0xb65b7780 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb65b75be in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7b8e8b2 in ?? () from /usr/lib/libkdeui.so.5 #4 0xb7b8f274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #5 <signal handler called> #6 0xbfd83f18 in ?? () #7 0x0832b988 in ?? () #0 0xb7f68430 in __kernel_vsyscall ()
The crash information is not useful enought. If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdegames-dbg" package. Thanks :)
Also, please use English when writing a bug description. For example I didn't understand a thing from what you were saying :)
@Dmitry: the "description" is the italian translation of the message given by drkonqui. The reporter simply copied and pasted it from drkonqui to bugzilla. @Andres: we'll have to expect a lot of translated message of this kind...
Marking as NEEDSINFO
Closing as WONTFIX since we cannot fix what we don't know. Please feel free to reopen if you think you can add more info.