Warzone2100 fails to close
-
xZachtmx
- New user
- Posts: 2
- Joined: 24 Dec 2009, 05:26
Warzone2100 fails to close
Hi i want to help develop Warzone2100 and im using ubuntu karmic 9.10. At a point i got warzone to work but then for some reason whe i try to exit z it stops at the ending screen (that says pumpkin studios) an does not exit until i reboot. i do not know why this is happening but even after i did a fresh install of ubuntu the problem persisted. right now im using vesion 2.2.4 source code but the bug also happened on earlier versions. Does anyone have a clue?
-
KukY
- Regular

- Posts: 1859
- Joined: 20 Mar 2009, 21:56
Re: Warzone2100 fails to close
Anyone that wants to develop is welcome.
That looks like a bug, but you need to report it!
This isn't a good report, devs need more info.
What you wrote explains almost nothing.
That looks like a bug, but you need to report it!
This isn't a good report, devs need more info.
What you wrote explains almost nothing.
-
stiv
- Warzone 2100 Team Member

- Posts: 876
- Joined: 18 Jul 2008, 04:41
- Location: 45N 86W
Re: Warzone2100 fails to close
First guess is a problem shutting down the sound subsystem. Running from the command line so you can see messages often gives a clue.
-
xZachtmx
- New user
- Posts: 2
- Joined: 24 Dec 2009, 05:26
Re: Warzone2100 fails to close
Well this only happens in fullscreen aparently O.o... i cant see output from terminal because i cant exit without rebooting.. runs fine in windowed so im stumpped. I will report it.
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
Same problem here. Btw, sound subsistem is fine, I was playing music during the game - the sound is there on exit.
strace -c warzone2100 output below if you needed. I loaded savegame and exited. Btw, the problem usually occurs after countinious gameplay.
strace -c warzone2100 output below if you needed. I loaded savegame and exited. Btw, the problem usually occurs after countinious gameplay.
Code: Select all
info |02:29:34: [rebuildSearchPath] * Failed to remove path /home/alikebabay/.warzone2100-2.2/ again
info |02:29:34: [rebuildSearchPath] * Failed to remove path /usr/local/data/ again
info |02:29:34: [rebuildSearchPath] * Failed to remove path /usr/local/share/warzone2100/ again
AL lib: alBuffer.c:1079: exit(): deleting 1 Buffer(s)
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
91.73 64.623875 250 258098 4739 read
12.35 8.699095 307 28336 lseek
10.68 7.520345 676 11121 8 stat64
4.10 2.886050 921 3134 1136 open
1.77 1.244406 2741 454 mmap2
0.97 0.684051 213 3217 poll
0.04 0.025592 3199 8 shmctl
0.03 0.022393 3199 7 geteuid32
0.03 0.019194 3199 6 _llseek
0.02 0.012796 3199 4 recv
0.01 0.009608 3203 3 waitpid
0.01 0.009597 3199 3 rt_sigprocmask
0.01 0.009597 3199 3 getgid32
0.01 0.009597 3199 3 SYS_331
0.01 0.009597 3199 3 semop
0.01 0.009597 3199 3 semctl
0.01 0.009597 3199 3 shmat
0.01 0.006398 3199 2 1 mlock
0.01 0.006398 3199 2 shmget
0.00 0.003199 3199 1 execve
0.00 0.003199 3199 1 statfs
0.00 0.003199 3199 1 getrlimit
0.00 0.003199 3199 1 getegid32
0.00 0.003199 3199 1 set_thread_area
0.00 0.003199 3199 1 set_tid_address
0.00 0.003199 3199 1 set_robust_list
0.00 0.003199 3199 1 getsockopt
0.00 0.003199 3199 1 semget
0.86 0.604491 1956 309 writev
0.82 0.579093 1990 291 munmap
0.75 0.529437 257 2059 4 close
0.56 0.396642 2216 179 fcntl64
0.48 0.335054 2295 146 71 access
0.34 0.241745 3099 78 mprotect
0.16 0.114363 3091 37 sched_yield
0.15 0.106358 2532 42 rt_sigaction
0.13 0.089668 27 3275 getpid
0.08 0.057542 992 58 getdents
0.07 0.051205 2438 21 2 connect
0.07 0.051179 2437 21 socket
0.06 0.044776 1866 24 kill
0.06 0.040771 1406 29 clock_gettime
0.05 0.033587 2584 13 uname
0.05 0.031985 2132 15 pipe
0.03 0.023990 2399 10 getsockname
0.03 0.022388 1866 12 getdents64
0.03 0.022378 1017 22 time
0.03 0.020791 2310 9 1 readlink
0.03 0.020791 2310 9 getuid32
0.03 0.020791 2310 9 getpeername
0.03 0.020791 2310 9 5 send
0.03 0.020791 2310 9 setsockopt
0.03 0.019189 1744 11 clone
0.02 0.011817 1970 6 unlink
0.02 0.011194 1866 6 ftruncate64
0.01 0.005597 1866 3 shmdt
-0.00 -0.000801 -801 1 times
-0.02 -0.012035 -343 35 fsync
-0.02 -0.013500 -48 276 brk
-0.05 -0.037702 -369 102 write
-0.23 -0.162608 -781 208 mremap
-0.80 -0.561462 -168 3315 8 ioctl
-1.15 -0.810925 -418 1937 nanosleep
-1.99 -1.399256 -723 1934 522 futex
-1.59 -1.117181 -398 2798 fstat64
-3.42 -2.410308 -680 3539 3428 lstat64
-3.78 -2.662251 -789 3370 select
-13.82 -9.738944 -793 12271 gettimeofday
------ ----------- ----------- --------- --------- ----------------
100.00 70.448005 340917 9925 total
Last edited by Kamaze on 28 Dec 2009, 00:38, edited 1 time in total.
Reason: Added some delicious code tags.
Reason: Added some delicious code tags.
-
Zarel
- Elite

- Posts: 5770
- Joined: 03 Jan 2008, 23:35
- Location: Minnesota, USA
Re: Warzone2100 fails to close
Have you tried running a stack trace?
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
Stack trace? not sure what is it..
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
I made a little bit of research. This is a SIGSEGV trouble, because of ALSA. viewtopic.php?f=14&t=71
I am trying to use the solution found here: http://tweetmeme.com/story/363541072/ho ... australien
Lets see how it works...
I am trying to use the solution found here: http://tweetmeme.com/story/363541072/ho ... australien
Lets see how it works...
-
Zarel
- Elite

- Posts: 5770
- Joined: 03 Jan 2008, 23:35
- Location: Minnesota, USA
Re: Warzone2100 fails to close
A segfault would not cause Warzone to fail to close...
A stack trace is where you output the stack. You get it by attaching GDB to a program and running "backtrace" or "bt".
A stack trace is where you output the stack. You get it by attaching GDB to a program and running "backtrace" or "bt".
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
Ok, the solution worked:) Now warzone closes without problems and the sound is fine. However, it started to crash unexpectedly. Any ideas?
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
Can you please give me the shell command I should execute? (ubuntu 9.10)Zarel wrote:A segfault would not cause Warzone to fail to close...
A stack trace is where you output the stack. You get it by attaching GDB to a program and running "backtrace" or "bt".
-
Zarel
- Elite

- Posts: 5770
- Joined: 03 Jan 2008, 23:35
- Location: Minnesota, USA
Re: Warzone2100 fails to close
Send us the crash dump? (It should be in /tmp/)commander wrote:Ok, the solution worked:) Now warzone closes without problems and the sound is fine. However, it started to crash unexpectedly. Any ideas?
No need; it appears you already fixed the freeze.commander wrote:Can you please give me the shell command I should execute? (ubuntu 9.10)
-
commander
- Greenhorn
- Posts: 6
- Joined: 27 Dec 2009, 04:27
Re: Warzone2100 fails to close
There is no crash dump in /tmp... Crash happens after I load savegame. This is a transport mission, so as soon as I put units in the transport the game crashes. I am attaching a savegame files in zip archive.
You do not have the required permissions to view the files attached to this post.
-
kainalu
- Rookie

- Posts: 22
- Joined: 10 Jan 2010, 11:52
Re: Warzone2100 fails to close
I get this all the time with Linux games. It has to do with a certain incompatibility with the pulse audio server. The best temporary fix is to install and use old-fasioned ALSA without PULSE. Since I have to look how to do that under the new Ubuntu, Try this for now:
a temporary solution:
sudo apt-get install htop ( a nicer top-like program)
WHEN THE GAME FREEZES:
push 'ctrl+alt+F1'
log in using your normal username and password
run "htop".
find the warzone2100 process and highlight it with the keyboard arrows
push F9 (kill)
push 9, then enter. This will kill Warzone
push 'ctrl+alt+F7' to get back to Ubuntu.
a temporary solution:
sudo apt-get install htop ( a nicer top-like program)
WHEN THE GAME FREEZES:
push 'ctrl+alt+F1'
log in using your normal username and password
run "htop".
find the warzone2100 process and highlight it with the keyboard arrows
push F9 (kill)
push 9, then enter. This will kill Warzone
push 'ctrl+alt+F7' to get back to Ubuntu.
-
cybersphinx
- Inactive

- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Warzone2100 fails to close
Run "killall -9 warzone2100".kainalu wrote:WHEN THE GAME FREEZES:
push 'ctrl+alt+F1'
log in using your normal username and password
This will kill Warzone
push 'ctrl+alt+F7' to get back to Ubuntu.