Bug 191246

Summary:	SIGABRT crash when closing without playing
Product:	[Applications] knetwalk	Reporter:	Robert Kosten <robert.kosten>
Component:	general	Assignee:	Fela Winkelmolen <fela.kde>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	andresbajotierra, coates, harryangell, kde-games-bugs-null, robert.kosten
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Robert Kosten 2009-05-01 13:29:51 UTC

Version:           3.0.0 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Closing knetwalk via window close button causes a signal 6 SIGABRT when no game move has been made before.

Environment: Kubuntu 8.10 with backports

Steps to reproduce:
Launch knetwalk
Close it via window close button immediately (rotating any piece will change the behavior)

Comment 1 Parker Coates 2009-05-01 20:49:34 UTC

Cannot reproduce here using both latest trunk and OpenSUSE 11.1 packages. Maybe it's a packaging issue?

Does quitting through the menu give the same behaviour?

Comment 2 Robert Kosten 2009-05-03 07:48:43 UTC

Just tested it: Yes, both menu and Ctrl+Q give the same result.

Comment 3 Dario Andres 2009-07-18 22:16:19 UTC

If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdegames-dbg" package. Thanks

Comment 4 Dario Andres 2009-07-18 22:16:34 UTC

*** Bug 200687 has been marked as a duplicate of this bug. ***

Comment 5 Robert Kosten 2009-07-19 10:08:17 UTC

I'm afraid I since moved to 9.04 and the bug has disappeared there (didn't have kdegames installed yet, but just tested it). Since I intend to move to another Distro again anyway, I guess I'll install 8.10 for testing again and see if I can reproduce it with that, give me a few hours.

Comment 6 Robert Kosten 2009-07-19 13:33:38 UTC

Can't reproduce it anymore, must've either been a side effect of something else on the system, or fixed in a subsequent patch. Either was, I'd suggest closing this.

Comment 7 Parker Coates 2009-07-19 15:50:46 UTC

Robert, in the future, feel free to close bugs that you've reported yourself if your confident the issue no longer exists.