| Summary: | kpat crashes when slecting New Game | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Alan <alan> |
| Component: | kshareddatacache | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | andrew.crouthamel, kde-games-bugs-null, kdebug, kissisti, lorenzo.calabrese, mpyne |
| Priority: | NOR | ||
| Version First Reported In: | 4.8.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi attachment-22395-0.html |
||
|
Description
Alan
2012-11-22 10:54:13 UTC
Created attachment 85272 [details]
New crash information added by DrKonqi
kpat (3.6) on KDE Platform 4.12.2 using Qt 4.8.5
- What I was doing when the application crashed:
Clicked on Spider, changed my mind, clicked on new game in order to select Mod43, crash.
-- Backtrace (Reduced):
#5 0x00000033e5036dd1 in KSharedDataCache::insert(QString const&, QByteArray const&) () from /lib64/libkdecore.so.5
#6 0x00000033e56aea81 in KImageCache::insertImage(QString const&, QImage const&) () from /lib64/libkdeui.so.5
#7 0x00000033e76160dd in KAbstractCardDeckPrivate::requestPixmap (this=<optimized out>, id=<optimized out>, faceUp=<optimized out>) at /usr/src/debug/kpat-4.12.2/libkcardgame/kabstractcarddeck.cpp:211
#8 0x00000033e76161c0 in KAbstractCardDeck::cardPixmap (this=<optimized out>, id=<optimized out>, faceUp=<optimized out>) at /usr/src/debug/kpat-4.12.2/libkcardgame/kabstractcarddeck.cpp:506
#9 0x00000033e76195f2 in KCard::paint (this=0x1fe7740, painter=0x7fff8203d800, option=<optimized out>, widget=<optimized out>) at /usr/src/debug/kpat-4.12.2/libkcardgame/kcard.cpp:319
Created attachment 85565 [details]
New crash information added by DrKonqi
kpat (3.6) on KDE Platform 4.12.3 using Qt 4.8.5
- What I was doing when the application crashed:
changing game selection. I have had this happen on many occasions, the game selected has varied. It seem to be about every tenth or so game but not regularly. I have had it crash within less than ten changes.
I tend to play one game, change to another, cycling around my favourite five games: Forty & eight, Klondike, grandfather, spider and grandfather's clock.
Version of Kpatience as supplied by fedora 20 ( also happened on fedora 17 and 19)
-- Backtrace (Reduced):
#6 0x000000317803d861 in SharedMemory::defragment() () from /lib64/libkdecore.so.5
#7 0x000000317803e5b5 in SharedMemory::removeUsedPages(unsigned int) () from /lib64/libkdecore.so.5
#8 0x0000003178037d89 in KSharedDataCache::insert(QString const&, QByteArray const&) () from /lib64/libkdecore.so.5
#9 0x00000031786aece1 in KImageCache::insertImage(QString const&, QImage const&) () from /lib64/libkdeui.so.5
#10 0x000000317aa160dd in KAbstractCardDeckPrivate::requestPixmap(unsigned int, bool) () from /lib64/libkcardgame.so
*** Bug 333098 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Yes I can confirm the bug is still there. Currently, due the redhat bug 1515265 the report backtrace is not working and I am afraid that further information is not not possible. Could you Andrew wait the reporting tools resolve their own bug first ? Or could you suggest an alternative tracing procedure ? Cheers Thanks for the update! You can get a backtrace with 'gdb'. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Created attachment 134142 [details] attachment-22395-0.html I no longer use the application, so have no idea if the bug is fixed or not... Alan A Hart On 17/12/2020 05:37, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=310490 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|CONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #8 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and confirm > if this issue is still occurring or if this bug report can be marked as > resolved. > > I have set the bug status to "needsinfo" pending your response, please change > back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Crash was in kdelibs4 code, which is no longer maintained. |