| Summary: | Programma: KMahjongg (kmahjongg), signaal SIGABRT [Current thread is 1 (Thread 0xb6017920 (LWP 31991))] Thread 1 (Thread 0xb6017920 (LWP 31991)): [KCrash Handler] #6 0xffffe430 in __kernel_vsyscall () #7 0xb642b990 in raise () from /lib/libc.so.6 #8 0 | ||
|---|---|---|---|
| Product: | [Applications] kmahjongg | Reporter: | louppen |
| Component: | general | Assignee: | Mauricio Piacentini <piacentini> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | crash | CC: | andresbajotierra, kde-games-bugs-null, schwarzer |
| Priority: | NOR | ||
| Version First Reported In: | 0.8 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
louppen
2009-05-11 14:47:06 UTC
What were you doing when the application crashed? 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 "kdegames4-debuginfo" package Thanks Marking as NEEDSINFO Is this bug still reproducable for you? I will close this as WOTFIX, since we cannot fix an issue with insufficient info given and the report is very old and KMahjongg has changed quite a bit since then. Feel free to reopen if the problem still occurs and more info can be provided. |