Bug 139902 - kbounce crashes when game over
Summary: kbounce crashes when game over
Status: RESOLVED DUPLICATE of bug 127779
Alias: None
Product: kbounce
Classification: Applications
Component: general (show other bugs)
Version: 0.5
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: schimmi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 14:20 UTC by Lars Noodén
Modified: 2007-02-03 16:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Noodén 2007-01-11 14:20:18 UTC
Version:           0.5 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3)
Compiler:          Target: powerpc-linux-gnu
OS:                Linux (ppc) release 2.6.17-10-powerpc

kbounce seems to work fine.  However, when the game is over, it crashes.  The backtrace function says that no useful backtrace is available.
Comment 1 Bram Schoenmakers 2007-01-11 18:25:28 UTC
Please install kdegames-dbg and try again.
Comment 2 Lars Noodén 2007-01-11 19:12:38 UTC
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.

Using host libthread_db library "/lib/libthread_db.so.1".
0x077479f0 in ?? ()
#0  0x077479f0 in ?? ()
#1  0x077477a4 in ?? ()
#2  0x07189318 in ?? ()
#3  0x071a3b44 in ?? ()
#4  <signal handler called>
#5  0x07f77e7c in ?? ()
#6  0x07f77e70 in ?? ()
#7  0x07f81d48 in ?? ()
#8  0x07f81fe4 in ?? ()
#9  0x0801191c in ?? ()
#10 0x080127d8 in ?? ()
#11 0x08014c0c in ?? ()
#12 0x06a3d53c in ?? ()
#13 0x06a3e458 in ?? ()
#14 0x06ef8004 in ?? ()
#15 0x06a74108 in ?? ()
#16 0x069ab94c in ?? ()
#17 0x069ae59c in ?? ()
#18 0x0727e7d8 in ?? ()
#19 0x06914a84 in ?? ()
#20 0x06997a0c in ?? ()
#21 0x069327b8 in ?? ()
#22 0x069d0584 in ?? ()
#23 0x069d0244 in ?? ()
#24 0x069ae1f4 in ?? ()
#25 0x0801554c in ?? ()
#26 0x076c1728 in ?? ()
#27 0x076c1978 in ?? ()
#28 0x00000000 in ?? ()
Comment 3 ville palo 2007-01-14 19:38:20 UTC
There is a similiar bug report in ubuntu BTS
https://bugs.launchpad.net/ubuntu/+source/kdegames/+bug/78784

This is what you see, if you run kbounce from terminal

$ kbounce
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
ASSERT: "_data[name].type()==value.type()" in /build/buildd/kdegames-3.5.5/./libkdegames/highscore/kexthighscore_item.cpp (164)
QGArray::at: Absolute index 4 out of range
KCrash: Application 'kbounce' crashing... 
Comment 4 Бирюлин Илья 2007-01-20 00:19:49 UTC
Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47035330668336 (LWP 6369)]
0x00002ac743f07500 in nanosleep () from /lib64/libc.so.6
#0  0x00002ac743f07500 in nanosleep () from /lib64/libc.so.6
#1  0x00002ac743f07339 in sleep () from /lib64/libc.so.6
#2  0x00002ac73ee44faf in KCrash::startDrKonqi ()
   from /usr/lib64/libkdecore.so.4
#3  0x00002ac73ee59474 in KCrash::defaultCrashHandler ()
   from /usr/lib64/libkdecore.so.4
#4  0x00002ac743ea2030 in killpg () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()
Comment 5 Lars Noodén 2007-01-20 17:11:38 UTC
Running kbounce in a terminal on my system gives the following message:

$ kbounce
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
ASSERT: "_data[name].type()==value.type()" in /build/buildd/kdegames-3.5.5/./libkdegames/highscore/kexthighscore_item.cpp (164)
QGArray::at: Absolute index 4 out of range
KCrash: Application 'kbounce' crashing...
Comment 6 Bram Schoenmakers 2007-02-03 16:21:57 UTC
Looks like a dupe.

*** This bug has been marked as a duplicate of 127779 ***