crashed playing computer

[livingdaylight]

Binary package hint: qgo

couldn't see how to play any person so i clicked on play computer. Human (black) was to start but when i placed the first stone it crashed.

[ville palo (vi64pa)]

Thanks for the bug. Could you attach the crash dump to this report? Did this happen on dapper, edgy or feisty?

[livingdaylight (livingdaylight)]

sorry, i'm new to reporting bugs and not very good at it.

Yes, it happend on Edgy. Let me know if there is anything else i can help
you with

On 15/01/07, ville palo <email address hidden> wrote:
>
> Thanks for the bug. Could you attach the crash dump to this report? Did
> this happen on dapper, edgy or feisty?
>
> ** Changed in: qgo (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
[phone]
www.my.opera.com/livingdaylight

[ville palo (vi64pa)]

Can you find from /var/crash file named something like _bin_games_qgo* (not sure how it is named but at least it has qgo in its name). If so, please, attach it to this report.

[livingdaylight (livingdaylight)]

here's /var/crash/_usr_games_qgo.1000.crash attachment(hopefully, thx for your patience)

[ville palo (vi64pa)]

hmm, crash dump seems to have some similarities with crash dump in bug #71501. I'm afraid that this doesn't contain enough information to solve this problem.

Could you try to obtain debug traces if you can reproduce this.
Instructions how to do this can be found in:
 https://wiki.ubuntu.com/DebuggingProgramCrash

[livingdaylight (livingdaylight)]

I'm sorry, but it is beyond my capacity. I followed the wiki as far as
installing gdb but after typing gdb in comman line i could not follow
further. I'm sorry i couldn't be of real help with qgo.

On 15/01/07, ville palo <email address hidden> wrote:
>
> hmm, crash dump seems to have some similarities with crash dump in bug
> #71501. I'm afraid that this doesn't contain enough information to solve
> this problem.
>
> Could you try to obtain debug traces if you can reproduce this.
> Instructions how to do this can be found in:
> https://wiki.ubuntu.com/DebuggingProgramCrash
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
[phone]
www.my.opera.com/livingdaylight

[ville palo (vi64pa)]

If you want and if you have time please could you try the following:

After you have started gdb just type:

gdb qgo 2>&1 | tee gdb-qgo.txt

after enter, type:

run

qgo should start and now you can try to crash the qgo.
When crash happens, type:
bt full
info registers
thread apply all backtrace
quit

and now you should have gdb-qgo.txt file on your disk, attach it to this and bug report is ready.

[livingdaylight (livingdaylight)]

this is what i got before and now again following your isntruction:
http://paste.ubuntu-nl.org/1673/

On 15/01/07, ville palo <email address hidden> wrote:
>
> If you want and if you have time please could you try the following:
>
> After you have started gdb just type:
>
> gdb qgo 2>&1 | tee gdb-qgo.txt
>
> after enter, type:
>
> run
>
> qgo should start and now you can try to crash the qgo.
> When crash happens, type:
> bt full
> info registers
> thread apply all backtrace
> quit
>
> and now you should have gdb-qgo.txt file on your disk, attach it to this
> and bug report is ready.
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
[phone]
www.my.opera.com/livingdaylight

[ville palo (vi64pa)]

Uh, I'm so sorry, I meant that you have to start gdb with command:

gdb qgo 2>&1 | tee gdb-qgo.txt
then type:
run
and qgo should start.

and when the crash happens:
bt full
info registers
thread apply all backtrace
quit

[livingdaylight (livingdaylight)]

i don't get now the second lot of instructions: "and when the crash happens"
bt full
info registers
thread apply all backtrace
quit

???

do i copy and paste that line by line or the whole thing?

i've attached the output anyway

C.

On 15/01/07, ville palo <email address hidden> wrote:
>
> Uh, I'm so sorry, I meant that you have to start gdb with command:
>
> gdb qgo 2>&1 | tee gdb-qgo.txt
> then type:
> run
> and qgo should start.
>
> and when the crash happens:
>
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
[phone]
www.my.opera.com/livingdaylight

[ville palo (vi64pa)]

Yes, after qgo has crashed
in gdb terminal type:
bt full <enter>
info registers <enter>
thread apply all backtrace <enter>
quit <enter>

and now you should have a file gdb-qgo.txt and that should
be attached to this report.

[livingdaylight (livingdaylight)]

ok, hopefully the attached file should be the one you're looking for. By the
way i must commend you on your commitment to getting this issue sorted. Mind
you i didn't expect to be still at this myself either...

I hope we're there now

C

On 15/01/07, ville palo <email address hidden> wrote:
>
> Yes, after qgo has crashed
> in gdb terminal type:
> bt full <enter>
> info registers <enter>
> thread apply all backtrace <enter>
> quit <enter>
>
> and now you should have a file gdb-qgo.txt and that should
> be attached to this report.
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
[phone]
www.my.opera.com/livingdaylight

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/games/qgo
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1222707536 (LWP 12028)]
(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)
Qt: gdb: -nograb added to command-line options.
  Use the -dograb option to enforce grabbing.
(no debugging symbols found)
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
(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)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222707536 (LWP 12028)]
0xb7280df4 in _IO_str_overflow () from /lib/tls/i686/cmov/libc.so.6
(gd...

[ville palo (vi64pa)]

Thank you, but I'm still afraid that there is not enough data to solve this :-(. But there seems to be newer release for ubuntu at http://qgo.sourceforge.net/, if you could try that and hope that crash doesn't appear anymore.

[William Grant (wgrant)]

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.