ksirk crashed with SIGSEGV in QMetaObject::activate()

[John Smeed]

Binary package hint: kdegames

KsirK is very sensitive to version changes. After some updates, including yesterdays it starts and the instant you try to start a game it crashes. ( Completely vanishes. )
Suggest this game be used as part of a test bed for new changes. Is this a Jaunty problem or is it general. This happened in Jaunty.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/games/ksirk
Package: ksirk 4:4.2.1-0ubuntu1
ProcCmdline: /usr/games/ksirk -caption KsirK -icon ksirk
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdegames
StacktraceTop:
 ?? ()
 ?? ()
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
 ?? ()
Title: ksirk crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:Ksirk::KGameWindow::mouseMoveEvent (this=0x9e148c0,
Ksirk::KGameWindow::qt_metacall (this=0x9e148c0,
QMetaObject::activate () from /usr/lib/libQtCore.so.4
QMetaObject::activate () from /usr/lib/libQtCore.so.4
Ksirk::DecoratedGameFrame::mouseMoveEventReceived (

[Zoubidoo (zoubidoo)]

I can confirm that this problem is still occurring. The game is unusable in its present condition. Perhaps it should be dropped from the official repositories because it doesn't give a good impression?

[Jonathan Thomas (echidnaman)]

A fix has been committed for KDE 4.3 beta2, but I'll open up a jaunty nomination so that we can get an SRU for this.

[Jonathan Thomas (echidnaman)]

Fix released to karmic, proposing this for a jaunty SRU.

[Mikie Tim T (mttrace)]

I can confirm that it is still a problem in 4.2.2 amd64. Even after updating KDE to 4.2.4, it is still an issue. You have my vote for proposing the fix for Jaunty, as October is a long time to wait for a fix, otherwise.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f56ac0bc750 (LWP 6818)]
[New Thread 0x7f56948d8950 (LWP 6824)]
[New Thread 0x7f56950d9950 (LWP 6823)]
[New Thread 0x7f5695ae4950 (LWP 6820)]
[New Thread 0x7f5696b54950 (LWP 6819)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debuggi...

[michael (reeves-87)]

You may be missing a debug package. Just got this in KDE 4.2.4 on jaunty. This application needs to be fixed or removed from the official release package for jaunty. A stack trace is attached for reference.