Bug 435110

Summary:	The Spider Solitaire app crashes when completing the solitaire layout.
Product:	[Applications] kpat	Reporter:	constantine <myainetwork>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	aacid, kde-games-bugs-null
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description constantine 2021-03-29 13:09:12 UTC

Application: kpat (19.12.3)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-67-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:

The layout of the cards in Spider Solitaire was not completed on the last column (although it was completely filled).

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a2a9ecec0 (LWP 369496))]

Thread 7 (Thread 0x7f1a20b79700 (LWP 369502)):
#0  futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5598b332de18) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5598b332ddc8, cond=0x5598b332ddf0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5598b332ddf0, mutex=0x5598b332ddc8) at pthread_cond_wait.c:638
#3  0x00007f1a22b05e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007f1a22b05a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f1a2137a700 (LWP 369501)):
#0  futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5598b332de18) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5598b332ddc8, cond=0x5598b332ddf0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5598b332ddf0, mutex=0x5598b332ddc8) at pthread_cond_wait.c:638
#3  0x00007f1a22b05e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007f1a22b05a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f1a21b7b700 (LWP 369500)):
#0  futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5598b332de18) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5598b332ddc8, cond=0x5598b332ddf0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5598b332ddf0, mutex=0x5598b332ddc8) at pthread_cond_wait.c:638
#3  0x00007f1a22b05e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007f1a22b05a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f1a2237c700 (LWP 369499)):
#0  futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5598b332de18) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5598b332ddc8, cond=0x5598b332ddf0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5598b332ddf0, mutex=0x5598b332ddc8) at pthread_cond_wait.c:638
#3  0x00007f1a22b05e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007f1a22b05a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f1a28b81700 (LWP 369498)):
#0  0x00007f1a2ecceaff in __GI___poll (fds=0x7f1a1c0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f1a2d01836e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1a2d0184a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f1a2f3b9583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f1a2f3604db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f1a2f198785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f1a2db1eefa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f1a2f1999d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f1a29b26700 (LWP 369497)):
#0  0x00007f1a2ecceaff in __GI___poll (fds=0x7f1a29b25ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f1a2cbbbc1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f1a2cbbd90a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f1a2a336298 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f1a2f1999d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f1a2d87c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1a2ecdb293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f1a2a9ecec0 (LWP 369496)):
[KCrash Handler]
#6  0x00005598b2b3ef9a in ?? ()
#7  0x00007f1a2f38d458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f1a2f38d458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f1a2f38d458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f1a2f39a51e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f1a2f38dcf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f1a2fe4da66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f1a2fe570f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f1a2f36193a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f1a2f3b88b0 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f1a2f3b91e4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f1a2d01817d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f1a2d018400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f1a2d0184a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f1a2f3b9565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f1a2f3604db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f1a2f368246 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00005598b2ae9e3a in ?? ()
#24 0x00007f1a2ebe00b3 in __libc_start_main (main=0x5598b2ae80f0, argc=3, argv=0x7fff08925408, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff089253f8) at ../csu/libc-start.c:308
#25 0x00005598b2aeaaee in ?? ()
[Inferior 1 (process 369496) detached]

Possible duplicates by query: bug 434725, bug 434236, bug 434205, bug 434192, bug 433533.

Reported using DrKonqi

Comment 1 Albert Astals Cid 2021-03-29 16:50:30 UTC

always or just sometimes?

Comment 2 constantine 2021-03-30 17:03:34 UTC

(In reply to Albert Astals Cid from comment #1)
> always or just sometimes?

2-3 times maybe in month

Comment 3 Albert Astals Cid 2021-03-30 20:32:23 UTC

The backtrace is sadly not useful :/

I know it's a hassle but it would be nice if you can record the game numbers (they show up in the window title) when playing and maybe we can try to see if certain game numbers are more crashy than others.

Also since you're in Ubuntu can you please follow the instructions at https://wiki.ubuntu.com/Debug%20Symbol%20Packages and install these packages
 kpat-dbgsym libqt5core5a-dbgsym libqt5widgets5-dbgsym libglib2.0-0-dbgsym

Then when it crashes next time it will hopefully be able to create a more useful backtrace, please attach it here.

Comment 4 Stephan Kulow 2023-02-27 07:44:57 UTC

We need that info - or we better close the bug.

Comment 5 Bug Janitor Service 2023-03-14 03:45:38 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 6 Bug Janitor Service 2023-03-29 03:45:45 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!