Forums » Bugs
Linux Ubuntu 11.10 Exit error
Here's what in the terminal window when I exit VO. When I hit Logoff, it doesn't drop me to the normal screen, but thought this might help. I have noticed that if I play a long time (hours), this happens, but not if I'm playing for a short time.
These warnings are during the game.... not part of the exiting error.
warning: Unknown nb_ctl request: 12
warning: The VAD has been replaced by a hack pending a complete rewrite
warning: Unknown nb_ctl request: 12
warning: The VAD has been replaced by a hack pending a complete rewrite
vendetta: ../iup/itable.c:285: iupTableRemove: Assertion `it && key' failed.
Segmentation fault
These warnings are during the game.... not part of the exiting error.
warning: Unknown nb_ctl request: 12
warning: The VAD has been replaced by a hack pending a complete rewrite
warning: Unknown nb_ctl request: 12
warning: The VAD has been replaced by a hack pending a complete rewrite
vendetta: ../iup/itable.c:285: iupTableRemove: Assertion `it && key' failed.
Segmentation fault
Same here
However, if I run in FULL WINDOW mode it will drop to the normal screen, however if you run system monitor you will see that vendetta is still running in the backround and not halted. Also it's using 98% to 200% CPU
If I run in WINDOWED Moded then it just freezes on exit, and I have to force quite.
Either way I have to force quite, but with Windowed it freezes at the quite screen and with FULL Window mode it closes the screen but vendetta is still running or froze in the backround
My logs don't say anything about segmentation fault though.
However, if I run in FULL WINDOW mode it will drop to the normal screen, however if you run system monitor you will see that vendetta is still running in the backround and not halted. Also it's using 98% to 200% CPU
If I run in WINDOWED Moded then it just freezes on exit, and I have to force quite.
Either way I have to force quite, but with Windowed it freezes at the quite screen and with FULL Window mode it closes the screen but vendetta is still running or froze in the backround
My logs don't say anything about segmentation fault though.
vendetta: ../iup/itable.c:285: iupTableRemove: Assertion `it && key' failed.
Segmentation fault
Happened again just now. This time I was only in the game for about 30 min. I was thinking that it was related to being online a long time. Not the case I guess.
I do know that any configurations you change don't get saved to wgaf.cfg. There have been times I've changed a bind or alias while playing, and if I get this error on exit, those changes did not get saved.
Segmentation fault
Happened again just now. This time I was only in the game for about 30 min. I was thinking that it was related to being online a long time. Not the case I guess.
I do know that any configurations you change don't get saved to wgaf.cfg. There have been times I've changed a bind or alias while playing, and if I get this error on exit, those changes did not get saved.
I'm running on Ubuntu 11.10 64-bit and I don't have these issues. Are you both running on the 32-bit version?
I'm running the 64-bit version,
3.0.0-16-generic #27-Ubuntu SMP Tue Jan 24 19:14:19 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
google "Unknown nb_ctl request: 12" and you get info about teamspeak.
but this also shows up when VO exits nicely. So only the last message above must be the cause of the strange exit issue;
vendetta: ../iup/itable.c:285: iupTableRemove: Assertion `it && key' failed.
Segmentation fault
3.0.0-16-generic #27-Ubuntu SMP Tue Jan 24 19:14:19 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
google "Unknown nb_ctl request: 12" and you get info about teamspeak.
but this also shows up when VO exits nicely. So only the last message above must be the cause of the strange exit issue;
vendetta: ../iup/itable.c:285: iupTableRemove: Assertion `it && key' failed.
Segmentation fault
I'm running 64bit too
New info
I noticed that it's not only freezing when I hit the quit button from the login screen to exit, but also when I hit esc
I only noticed cause I was thinking I would still get this options screen to make some changes and hit esc from the login screen instead of the quit button and noticed the same effect.
I have no idea what this means but just wanted to report on this additional info
Happy hacking
I noticed that it's not only freezing when I hit the quit button from the login screen to exit, but also when I hit esc
I only noticed cause I was thinking I would still get this options screen to make some changes and hit esc from the login screen instead of the quit button and noticed the same effect.
I have no idea what this means but just wanted to report on this additional info
Happy hacking
One last thing to mention for this in case you didn't know
This freezing on exit that I have is NOT on logout
In otherwords I can logout, then back in again no problems
This only occurrs for pressing the (quit) button or pressing (esc) once you have already logged off
Just FYI wanted to ad this information
This freezing on exit that I have is NOT on logout
In otherwords I can logout, then back in again no problems
This only occurrs for pressing the (quit) button or pressing (esc) once you have already logged off
Just FYI wanted to ad this information
Seems to be fixed now
After VO Server restart last night April 9 - 2012
This morning I noticed that login takes a long long time almost seems stuck at (entering universe), However, it does log in and also will logout and quit.
And vo is no longer running in the backround as well.
I didn't do anything else to my system since I could not fix it and yet could still play vo so I didn't worry about it that much.
Anyhow just wanted to report that it's now exiting on my system just fine
Thanks
After VO Server restart last night April 9 - 2012
This morning I noticed that login takes a long long time almost seems stuck at (entering universe), However, it does log in and also will logout and quit.
And vo is no longer running in the backround as well.
I didn't do anything else to my system since I could not fix it and yet could still play vo so I didn't worry about it that much.
Anyhow just wanted to report that it's now exiting on my system just fine
Thanks