Dear Maintainer,

kajongg is often crash, It is almost can't been used.The dmesg has the
following errors:

[12396.242561] traps: kajongg[36797] general protection ip:7fcd4aa6a672
sp:7ffc5b4c6de8 error:0 in libQt5Core.so.5.11.3[7fcd4a876000+2a4000]
[12558.366470] kajongg[37179]: segfault at 1 ip 00007f54a0757195 sp
00007ffc934a0310 error 4 in QtCore.cpython-37m-x86_64-linux-
gnu.so[7f54a05f3000+166000]
[12558.366504] Code: 00 00 00 00 00 41 54 55 48 89 f5 53 48 85 ff 74 39 4c 8d
25 7d 34 0e 00 48 89 fb 49 8b 04 24 ff 90 c8 01 00 00 48 85 c0 74 0b <48> 8b 00
5b 5d 41 5c c3 0f 1f 00 48 85 ed 75 17 49 8b 04 24 48 89
[13285.417234] kajongg[39213]: segfault at 4 ip 00007f487669b195 sp
00007fff259ca0d0 error 4 in QtCore.cpython-37m-x86_64-linux-
gnu.so[7f4876537000+166000]
[13285.417267] Code: 00 00 00 00 00 41 54 55 48 89 f5 53 48 85 ff 74 39 4c 8d
25 7d 34 0e 00 48 89 fb 49 8b 04 24 ff 90 c8 01 00 00 48 85 c0 74 0b <48> 8b 00
5b 5d 41 5c c3 0f 1f 00 48 85 ed 75 17 49 8b 04 24 48 89

Kajongg is written in Python, it cannot cause a segementation error by itself.

The faulty package might be python3-pyqt5, please reassign your bug report to that package.

Somebody might want to make kajongg run with pyside instead of pyqt5 but
I currently have no time to do that.

Hello,

I accidentally found this bug report when I experienced the issue
reported at https://github.com/bit-team/backintime/issues/1095 (see
also: https://www.riverbankcomputing.com/static/Docs/PyQt5/gotchas.html#crashes-on-exit).
I haven't tried installing and running kajongg, so this may just be a
coincidence, but I hope this piece of information could be helpful.

Regards,
Samuel Plavec