Bug 4316

Summary:	Crash in ksudoku when press "Difficulty" and choose any option
Product:	Mageia	Reporter:	Börje Säfsten <borje.safsten>
Component:	RPM Packages	Assignee:	John Balcaen <balcaen.john>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kdegames4	CVE:
Status comment:
Attachments:	ksudoku-debug kdegames4-debug ksuduku-debug2

Description Börje Säfsten 2012-01-28 14:56:20 CET

Description of problem:Ksudoku crash when press "Difficulty" and choose any of the options


Version-Release number of selected component (if applicable):ksudoku 4.8.0 1.mga2


How reproducible: Every time


Steps to Reproduce:
1.Start ksudoku
2.Press Difficulty
3.Choose any option

Comment 1 Manuel Hiebel 2012-01-29 11:40:50 CET

please do the following:
1) enable the "core release debug"
2) install the following packages: gdb ksudoku-debug
3) run the following command from a terminal:
   gdb -q ksudoku
4) then type "run"
5) when it segfaults, type "bt" and copy back the stack trace in a file you'll
attach (not paste) to this bug report
Thanks

Keywords: (none) => NEEDINFO

Comment 2 Börje Säfsten 2012-01-29 22:03:56 CET

Created attachment 1459 [details]
ksudoku-debug

Manuel Hiebel 2012-01-30 01:07:51 CET

Attachment 1459 mime type: application/octet-stream => text/plain

Comment 3 Manuel Hiebel 2012-01-30 01:17:32 CET

Arf no usefull backtrace :/

John can you reproduce ? do you know how to get a better strace ?

(I have found nothing at upstream https://bugs.kde.org/buglist.cgi?quicksearch=product%3Aksudoku )

Keywords: NEEDINFO => (none)
Assignee: bugsquad => balcaen.john
Source RPM: ksudoku => kdegames4

Comment 4 Börje Säfsten 2012-01-30 19:25:37 CET

(In reply to comment #3)
> Arf no usefull backtrace :/
> 
> John can you reproduce ? do you know how to get a better strace ?
> 
> (I have found nothing at upstream
> https://bugs.kde.org/buglist.cgi?quicksearch=product%3Aksudoku )

Well, I should have told you. I did enable core release debug, but there was no ksudoku-debug. gdb was already installed, so I run only gdb. That's why  result is bad.

Comment 5 Dave Hodgins 2012-01-30 19:41:50 CET

Try installing kdegames4-debug from Core Updates Debug and then running
gdb again.

CC: (none) => davidwhodgins

Comment 6 Börje Säfsten 2012-01-30 22:03:15 CET

Created attachment 1466 [details]
kdegames4-debug

Hope this will do

Manuel Hiebel 2012-01-31 10:57:16 CET

Attachment 1466 mime type: application/octet-stream => text/plain

Comment 7 Börje Säfsten 2012-01-31 19:43:47 CET

Created attachment 1475 [details]
ksuduku-debug2

More on ksudoku-debug. I missed that I code press "return" and continue.

D Morgan 2012-02-01 01:03:16 CET

Attachment 1475 mime type: application/octet-stream => text/plain

Comment 8 John Balcaen 2012-02-02 00:05:21 CET

Should be fixed with the next kdegames package

Status: NEW => RESOLVED
CC: (none) => balcaen.john
Resolution: (none) => FIXED

Comment 9 Börje Säfsten 2012-02-02 16:36:45 CET

(In reply to comment #8)
> Should be fixed with the next kdegames package

Yes, working now after today's update.