Bug 369385 - Kshisen just disappears
Summary: Kshisen just disappears
Status: RESOLVED WORKSFORME
Alias: None
Product: kshisen
Classification: Applications
Component: general (show other bugs)
Version: 1.8+ #13
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Frederik Schwarzer
URL:
Keywords: drkonqi
: 369533 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-26 17:52 UTC by Charles Coffee
Modified: 2018-12-02 03:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Coffee 2016-09-26 17:52:45 UTC
Application: kshisen (1.8+ #13)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.4.16 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed: Playing Kshisen (PID 6550). This application (amoug others) seems to constantly crash.  Will be playing a game and video just disappears from screen. Sometime get crash report, somethimes nothing.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Shisen-Sho (kshisen), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007ffa0a2843f8 in raise () at /lib64/libc.so.6
#7  0x00007ffa0a285ffa in abort () at /lib64/libc.so.6
#8  0x00007ffa0a2c66f9 in  () at /lib64/libc.so.6
#9  0x00007ffa0a2cef4a in _int_free () at /lib64/libc.so.6
#10 0x00007ffa0a2d2c1c in free () at /lib64/libc.so.6
#11 0x00007ffa0c244535 in QImageData::~QImageData() () at /usr/lib64/qt/lib/libQtGui.so.4
#12 0x00007ffa0c2445ab in QImage::~QImage() () at /usr/lib64/qt/lib/libQtGui.so.4
#13 0x00007ffa0c26d841 in QRasterPixmapData::~QRasterPixmapData() () at /usr/lib64/qt/lib/libQtGui.so.4
#14 0x00007ffa0c26d879 in QRasterPixmapData::~QRasterPixmapData() () at /usr/lib64/qt/lib/libQtGui.so.4
#15 0x00007ffa0c25fd5e in QPixmap::operator=(QPixmap const&) () at /usr/lib64/qt/lib/libQtGui.so.4
#16 0x00007ff9fc7f4973 in  () at /usr/lib64/kde4/plugins/styles/oxygen.so
#17 0x00007ffa0b2787f3 in QObject::event(QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4
#18 0x00007ffa0c18c48c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4
#19 0x00007ffa0c192f5c in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4
#20 0x00007ffa0ced88ea in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#21 0x00007ffa0b25fc0d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4
#22 0x00007ffa0b290368 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#23 0x00007ffa0b28d789 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#24 0x00007ffa06426787 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#25 0x00007ffa064269b8 in  () at /usr/lib64/libglib-2.0.so.0
#26 0x00007ffa06426a5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#27 0x00007ffa0b28e0ae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/qt/lib/libQtCore.so.4
#28 0x00007ffa0c22f9e6 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#29 0x00007ffa0b25e5d1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/qt/lib/libQtCore.so.4
#30 0x00007ffa0b25e8e5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/qt/lib/libQtCore.so.4
#31 0x00007ffa0b263ec9 in QCoreApplication::exec() () at /usr/lib64/qt/lib/libQtCore.so.4
#32 0x0000000000409aa0 in  ()
#33 0x00007ffa0a26f7d0 in __libc_start_main () at /lib64/libc.so.6
#34 0x0000000000409af9 in _start ()

Reported using DrKonqi
Comment 1 Frederik Schwarzer 2016-10-12 13:14:41 UTC
*** Bug 369533 has been marked as a duplicate of this bug. ***
Comment 2 Frederik Schwarzer 2016-10-12 13:17:47 UTC
I am sorry but I do not understand, where the problem is. It seems to crash within Qt and if (as you say) several applications crash, it indeed seems to be a problem a bit lower in the stack.

Have you contacted the slackware team packaging Qt? They might know something about this.
Comment 3 Andrew Crouthamel 2018-11-01 13:48:39 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 4 Bug Janitor Service 2018-11-16 11:44:25 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 5 Bug Janitor Service 2018-12-02 03:50:16 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!