Summary: | Run Command Interface Fatal Error signal 11 (SIGSEGV) | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Chris <novashadow> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED REMIND | ||
Severity: | crash | CC: | christophe, dominik.tritscher, dyapason, finex, icarolearningtofly, martyfelker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Chris
2008-12-22 21:02:19 UTC
Hi, could you explain better how to reproduce the crash? If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks! No useful backtrace was provided for this bug report (see comment #1). Changing its status. same problem, but some different codes: .. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb07ffb90 (LWP 4128)] [New Thread 0xb11fdb90 (LWP 3568)] [New Thread 0xb19feb90 (LWP 3567)] [New Thread 0xb21ffb90 (LWP 3566)] [New Thread 0xb2b32b90 (LWP 3565)] (no debugging symbols found) .. Same version of KDE, same OS and (almost) identical code of error. No hints for the solution? Without a proper backtrace it is nearly impossible to guess what went wrong here. Please see the techbase article following the link finex posted in comment #1 for detailed instructions on how to provide a usefull backtrace. As there is still no usable backtrace available, I close this bug for now. We will of course reopen it, if the needed information becomes available. |