Bug 329216 - KPatience crash
Summary: KPatience crash
Status: RESOLVED WORKSFORME
Alias: None
Product: Oxygen
Classification: Plasma
Component: style (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords: drkonqi
: 307512 329602 329926 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-12-25 11:18 UTC by Markus
Modified: 2018-11-30 03:56 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus 2013-12-25 11:18:34 UTC
Application: kpat (3.6)
KDE Platform Version: 4.11.4
Qt Version: 4.8.5
Operating System: Linux 3.10.0-sabayon x86_64
Distribution: "Sabayon Linux amd64 14.01"

-- Information about the crash:
- What I was doing when the application crashed:
Starting new game. KPatinece sometimes crahes at the start, sometimes during the game and sometimes it dosen't at all.

- Custom settings of the application:
Green background and classic cards.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KPatience (kpat), signal: Aborted
[KCrash Handler]
#5  0x00007f0755d5c5c5 in raise () from /lib64/libc.so.6
#6  0x00007f0755d5da48 in abort () from /lib64/libc.so.6
#7  0x00007f0755d9cb45 in ?? () from /lib64/libc.so.6
#8  0x00007f0755da2826 in ?? () from /lib64/libc.so.6
#9  0x00007f0755da35d3 in ?? () from /lib64/libc.so.6
#10 0x00007f0756985855 in QImageData::~QImageData() () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007f07569858e3 in QImage::~QImage() () from /usr/lib64/qt4/libQtGui.so.4
#12 0x00007f07569af628 in QRasterPixmapData::~QRasterPixmapData() () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00007f07569af669 in QRasterPixmapData::~QRasterPixmapData() () from /usr/lib64/qt4/libQtGui.so.4
#14 0x00007f07569a089d in QPixmap::operator=(QPixmap const&) () from /usr/lib64/qt4/libQtGui.so.4
#15 0x00007f074995d9e7 in ?? () from /usr/lib64/kde4/plugins/styles/oxygen.so
#16 0x00007f075753e7dc in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f07568d10ec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#18 0x00007f07568d3a5b in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#19 0x00007f0758020466 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#20 0x00007f07575250be in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#21 0x00007f0757556052 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007f0757552d74 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#23 0x00007f0757552d91 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007f07517b6b55 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f07517b6e98 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f07517b6f54 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f0757553506 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007f07569715ae in ?? () from /usr/lib64/qt4/libQtGui.so.4
#29 0x00007f0757523d6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#30 0x00007f0757523ff8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#31 0x00007f0757529238 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#32 0x000000000041a61a in main ()

Possible duplicates by query: bug 307512, bug 299736.

Reported using DrKonqi
Comment 1 Jekyll Wu 2014-01-04 17:09:20 UTC
*** Bug 329602 has been marked as a duplicate of this bug. ***
Comment 2 Hugo Pereira Da Costa 2014-01-04 19:06:44 UTC
Would need debug symbols for oxygen.
Also, this really seems a Qt bug. 
Can you try running with 
kpat -graphicssystem native
and see if the bug still happens ?
Comment 3 Hugo Pereira Da Costa 2014-01-04 19:08:33 UTC
*** Bug 307512 has been marked as a duplicate of this bug. ***
Comment 4 Markus 2014-01-04 21:47:08 UTC
I can try. Is there a good way to slam -graphicssystem native on the GUI shortcut? Also, i reinstalled kpat with debug symbols enabled, so if it crashes again, should i just re-report it?
Comment 5 Hugo Pereira Da Costa 2014-01-05 13:41:33 UTC
@Markus
"Is there a good way to slam -graphicssystem native on the GUI shortcut"
Don't know :(

"so if it crashes again, should i just re-report it?"
yes, if it is using the "native" graphicssystem.
and report if it does not crash anymore after (a couple of days use).
That would definitly help deciding whether it is Qt or Oxygen's bug.

Hugo
Comment 6 Markus 2014-01-07 20:55:36 UTC
Set the -graphicssystem native on today. Seems ok so far, but on my ucer account it slows down quite a lot (amazingly it dosen't do it on other user accounts). I could mention here that my KDE-sabayon desktop after update didn't change to blue either and that dark green kpat background dosen't work and displays grey.

On the other hand, it didn't crash yet, so i am hopeful.
Also, to set parameters for app run, you must edit .desktop file.
Comment 7 Jekyll Wu 2014-01-14 02:04:00 UTC
*** Bug 329926 has been marked as a duplicate of this bug. ***
Comment 8 Andrew Crouthamel 2018-10-31 04:07:01 UTC
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!
Comment 9 Bug Janitor Service 2018-11-15 10:43:40 UTC
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!
Comment 10 Bug Janitor Service 2018-11-30 03:56:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!