1.0 bugs

F

flyboy

Guest
1.0 bugs (Linux Only)

I have just started using 1.0 for linux. Love the new graphics :)

Bugs so far:

Install path typo:
During install the default install path spelt privateer as privater. Made me wonder where the directory went when I spelt it correctly moments later.

setup Segmentation fault :
Setup program in bin directory seg faults, so I cannot easily change my config.

Item mass + ugrade space inconsistency:
My starting ship has a bunch of upgrades weighing 10 and using 0 upgrade space, while the purchasable upgrades typically weigh 0 and take 1 upgrade space. If I sell one of my starting upgrades the game sticks it with the ones for sale, but the stats for weight and upgrade space seem to get averaged for the stack.
 
did you run
privateer --setup (that's the symlink we made)

that should work ok :)

or bin/vegastrike.sh --setup
that's where the symlink is by default pointed to

the path is privater so it wouldn't conflict with the linux beta
otherwise the Loki would give some unintelligable error about "must select at least one destination" until the user uninstalled the beta...
we figured a misspelling that was present in the original dos version (installed to c:\privater) would be more palpable than a cryptic error message

besides the symlink should still go in /usr/bin/

and tabcomplete should still result in finding privater
 
Well I tried:

$bin/vegastrike.sh --setup
vsinstall.sh: line 21: 14895 Segmentation fault $CURPWD/setup
 
hmm that's worrysome...try it in gdb
what system are you running... I had a setup problem last time I released--but I could swear I made triple sure to fix it this time
 
if those don't work I guess you have to edit ~/.privateer100/vegastrike.config by hand
it's quite easy --we'll help

it works on FC and Debian Stable...that I know
 
Downloading those files now.

Using Mandrake 9.1.

I will try using gdb, but I haven't used it in years, and need to read the man page on it.
Feel free to tell me the commands to use though :)
 
Those other two setup programs segfaulted as well

Here is the trace from 'setup'

$ gdb bin/setup
GNU gdb 5.3-22mdk (Mandrake Linux)
Copyright 2002 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 "i586-mandrake-linux-gnu"...(no debugging symbols found)...
(gdb) run
Starting program: /space/packages/vegastrike/privateer/bin/setup
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x40364cab in gdk_rgb_set_min_colors () from /usr/lib/libgdk-1.2.so.0
(gdb) backtrace full
#0 0x40364cab in gdk_rgb_set_min_colors () from /usr/lib/libgdk-1.2.so.0
No symbol table info available.
#1 0x0819f914 in main_module ()
No symbol table info available.
#2 0x080744c0 in gtk_rc_parse_engine ()
No symbol table info available.
#3 0x08073c58 in gtk_rc_parse_style ()
No symbol table info available.
#4 0x080737ed in gtk_rc_parse_statement ()
No symbol table info available.
#5 0x08073008 in gtk_rc_parse_any ()
No symbol table info available.
#6 0x08072496 in gtk_rc_parse_file ()
No symbol table info available.
#7 0x08072521 in gtk_rc_parse ()
No symbol table info available.
#8 0x0807227c in gtk_rc_init ()
No symbol table info available.
#9 0x0805f6e9 in gtk_init_check ()
No symbol table info available.
#10 0x0805f771 in gtk_init ()
No symbol table info available.
#11 0x08052dec in InitGraphics ()
No symbol table info available.
#12 0x08052b5b in Start ()
No symbol table info available.
#13 0x08056f75 in main ()
No symbol table info available.
#14 0x400a57f7 in __libc_start_main () from /lib/i686/libc.so.6
No symbol table info available.
(gdb)
 
that's in GDK somewhere... looks like an error message I got when running in 256 color mode on windows way back when--- wonder what version of gdk you're running
 
gdk 2.2.1 I think. I will try upgrading to see what happens.
 
I had some other gdk libs saying version 0.22.0 if that's any help.

Anyway I tried to upgrade using rpms, and ended up in package dependency hell :-(

I probably won't succeed in upgrading. I'm not really a hardcore linux user.
 
Hello, I use Fedora Core release 3 (Heidelberg) /fully updated today/.
loki_setup: 2 Unable to find file 'setup.base.xml' in '/tmp/selfgz3051425982'
loki_setup: 2 Unable to find file 'setup.music.xml' in '/tmp/selfgz3051425982'
loki_setup: 2 Unable to find file 'vslogo.xpm' in '/tmp/selfgz3051425982'
Setup fails for me too, and here's what I get:
---
...
(gdb) run
Starting program: /home/mr700/local/privater/bin/setup
(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)...(nodebugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x047f6caf in gdk_rgb_init () from /usr/lib/libgdk-1.2.so.0
(gdb) backtrace full
#0 0x047f6caf in gdk_rgb_init () from /usr/lib/libgdk-1.2.so.0
No symbol table info available.
#1 0x00b18561 in theme_init () from /usr/lib/gtk/themes/engines/libbluecurve.so
No symbol table info available.
#2 0x080851fb in gtk_theme_engine_get ()
No symbol table info available.
#3 0x080744c0 in gtk_rc_parse_engine ()
No symbol table info available.
#4 0x08073c58 in gtk_rc_parse_style ()
No symbol table info available.
#5 0x080737ed in gtk_rc_parse_statement ()
No symbol table info available.
#6 0x08073008 in gtk_rc_parse_any ()
No symbol table info available.
#7 0x08072496 in gtk_rc_parse_file ()
No symbol table info available.
#8 0x080737dd in gtk_rc_parse_statement ()
No symbol table info available.
#9 0x08073008 in gtk_rc_parse_any ()
No symbol table info available.
#10 0x08072496 in gtk_rc_parse_file ()
No symbol table info available.
#11 0x08072521 in gtk_rc_parse ()
No symbol table info available.
#12 0x0807227c in gtk_rc_init ()
No symbol table info available.
#13 0x0805f6e9 in gtk_init_check ()
No symbol table info available.
#14 0x0805f771 in gtk_init ()
No symbol table info available.
#15 0x08052dec in InitGraphics ()
No symbol table info available.
#16 0x08052b5b in Start ()
No symbol table info available.
#17 0x08056f75 in main ()
No symbol table info available.
(gdb)
---
rpm -qf /usr/lib/libgdk-1.2.so.0
gtk+-1.2.10-33
with vssetup.dynamic
---
Starting program: /home/mr700/local/privater/bin/vssetup.dynamic

Program received signal SIGSEGV, Segmentation fault.
0x047f6caf in gdk_rgb_init () from /usr/lib/libgdk-1.2.so.0
(gdb) backtrace full
#0 0x047f6caf in gdk_rgb_init () from /usr/lib/libgdk-1.2.so.0
No symbol table info available.
#1 0x00a56561 in theme_init () from /usr/lib/gtk/themes/engines/libbluecurve.so
No symbol table info available.
#2 0x0808339b in gtk_theme_engine_get ()
No symbol table info available.
#3 0x08072660 in gtk_rc_parse_engine ()
No symbol table info available.
#4 0x08071df8 in gtk_rc_parse_style ()
No symbol table info available.
#5 0x0807198d in gtk_rc_parse_statement ()
No symbol table info available.
#6 0x080711a8 in gtk_rc_parse_any ()
No symbol table info available.
#7 0x08070636 in gtk_rc_parse_file ()
No symbol table info available.
#8 0x0807197d in gtk_rc_parse_statement ()
No symbol table info available.
#9 0x080711a8 in gtk_rc_parse_any ()
No symbol table info available.
#10 0x08070636 in gtk_rc_parse_file ()
No symbol table info available.
#11 0x080706c1 in gtk_rc_parse ()
No symbol table info available.
#12 0x0807041c in gtk_rc_init ()
No symbol table info available.
#13 0x0805d889 in gtk_init_check ()
No symbol table info available.
#14 0x0805d911 in gtk_init ()
No symbol table info available.
#15 0x08050f8c in InitGraphics (argc=0xbffff520, argv=0xbffff524) at ../../vssetup/src/include/display_gtk.cpp:33
title = "mns to show in the display\r\n\000onfiguration file\r\n", '\0' <repeats 12 times>, "L\205\004\b0\201\004\b\a\001\000\000\000\000\000\000-\000\002\227\000\001\000\000\000�\033\b\001\000\000\200�\237-\000\200\234-\000�r-\000B�004\bLb\034\000\237-\000h\034\000\000\000\000\000��\000\016�\000�\004\b�\000 ", '\0' <repeats 11 times>, "�.\000\211.\0008\003.\000\210b\034\000\a\000\000\000`h\034\000h\034\000S38\a5�004\b\237-"...
static_text = "\000\000\000\000\000\000\000\000 �4\232,\000\b\000\000\000\000\000\000\022\000\000\000\000\b\000\000\000u0\002\000\001\000\000\000\002\000\000\000\b\000\000\000\000\000\000\000\000 \021\000\001\000\000\000\000\000\000\000\000\000\000\000\000\000\000\017�001\000\204\022\000\220��\000\000\b\000\017\200\001\000\000\000\000\000\000\000\000\000u0\002\000\000\000\000\000\204\022\0000\001\000\000\000\000\000\000\t*\000\002\000\000\000x�`��\006\000\000\000\000H@\0000\000\000\000\000\000\000\000\003\000\000\000\204\000\000�\210��\033\b�\237-\000¥,\000\b\000\000\000"...
lbl = (_GtkWidget *) 0x2d9fb4
#16 0x08050cfb in Start (argc=0xbffff520, argv=0xbffff524) at ../../vssetup/src/include/central.cpp:26
No locals.
---Type <return> to continue, or q <return> to quit---
#17 0x08055115 in main (argc=1, argv=0xbffff5a4) at ../../vssetup/src/c/setup.cpp:83
i = 36
pwent = (passwd *) 0x40507c
HOMESUBDIR = {static npos = 4294967295, static nilRep = {len = 0, res = 0, ref = 1, selfish = false},
dat = 0x81b2d58 ".privateer100"}
version = (FILE *) 0x81b3230
---
(gdb) run
Starting program: /home/mr700/local/privater/bin/vssetup
dynamic-link.h:62: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed.

Program received signal SIGABRT, Aborted.
0x08158fe1 in kill ()
(gdb) backtrace full
#0 0x08158fe1 in kill ()
No symbol table info available.
#1 0x08158d4f in raise ()
No symbol table info available.
#2 0x08135ec0 in abort ()
No symbol table info available.
#3 0x08132f12 in __assert_fail ()
No symbol table info available.
#4 0x0814c6df in _dl_map_object_from_fd ()
No symbol table info available.
#5 0x0814d784 in _dl_map_object ()
No symbol table info available.
#6 0x0815025a in dl_open_worker ()
No symbol table info available.
#7 0x0814f9de in _dl_catch_error ()
No symbol table info available.
#8 0x081505f2 in _dl_open ()
No symbol table info available.
#9 0x081510f8 in do_dlopen ()
No symbol table info available.
#10 0x0814f9de in _dl_catch_error ()
No symbol table info available.
#11 0x081510b3 in dlerror_run ()
No symbol table info available.
#12 0x08151168 in __libc_dlopen ()
No symbol table info available.
#13 0x08149b45 in __nss_lookup_function ()
No symbol table info available.
#14 0x08149840 in __nss_lookup ()
No symbol table info available.
#15 0x0814a67d in __nss_passwd_lookup ()
No symbol table info available.
#16 0x081459ff in getpwuid_r ()
No symbol table info available.
#17 0x0814579f in getpwuid ()
No symbol table info available.
#18 0x0804c493 in main (argc=1, argv=0xbffff5b4) at ../../vssetup/src/c/setup.cpp:59
i = 36
pwent = (passwd *) 0xbffff5b4
HOMESUBDIR = {static npos = 4294967295, static nilRep = {len = 0, res = 0, ref = 1, selfish = false},
dat = 0x1 <Address 0x1 out of bounds>}
version = (FILE *) 0x815165f
(gdb)
---
I copied setup from older (0.9) release and it worked fine. Editing the config file (~/.privateer100/vegastrike.config) by hand looks easy too (uncommenc and comment xml regions).
 
I got vegastrike 0.4.3 from CVS and after a few tryies i got it compiled. The new dynamic vssetup, which I copied as privater/bin/setup, works fine and is 27724 bytes big (1695521 for the original). I'll probably try to make an rpm If I have time and figure out how to...
 
Just got 1.0 downloaded (without corruptions), everything else seems OK (can hear armor hit sound etc.) but that mesher is really bugging me... Makes playing Remake in fullscreen IMPOSSIBLE. Every time I'm jumping into a new sector that hasn't been "meshed" yet, game minimizes itself to the taskbar.

There must be Some kind of trick that forces the mesher to stay in the background? If mesher would be pure dos-application, I could at least select the way mesher runs (full screen/minimized/window) from its properties but apparently because it is win32-application I can only choose between compatibility modes and few other options...

*UPDATE* Well I decided to give it a try and actually fixed this annoyance by myself... Anyone else suffering of the mesher-problem:

1) rename bin/mesher.exe to _mesher.exe
2) get http://www.nic.fi/~aape/BIN/MESHER.EXE and put it in bin-folder
3) right-click on that file and select Properties.
4) From Program-sheet select Run: minimized.

And no more disturbing mesher... Oh and naturally I take no responsibilities if someone manages to screw things up with this file :)
 
I dunno if this is a bug or one of those 'working as intended' weirdneses, but here it is:

When I afterburner and then hit ` to turn my ship without changing vector, I keep going the rate my afterburner had reached when I hit ` with no energy use.
 
as designed--it shouldn't take energy to keep your ship going on the same vector it was going... you know the whole "Objects in motion remain in motion...."

if you think it's unfair...don't press the key or hack vegastrike.config to take it out
 
Acimus said:
Just got 1.0 downloaded (without corruptions), everything else seems OK (can hear armor hit sound etc.) but that mesher is really bugging me... Makes playing Remake in fullscreen IMPOSSIBLE. Every time I'm jumping into a new sector that hasn't been "meshed" yet, game minimizes itself to the taskbar.
Click to expand...
If you were playing an unpatched game you wouldn't be having that problem. Newer versions of the patch will supposedly be changed to avoid the issue. You have to understand: the game is stable, the patch is barely alpha.
 
hellcatv said:
as designed--it shouldn't take energy to keep your ship going on the same vector it was going... you know the whole "Objects in motion remain in motion...."

if you think it's unfair...don't press the key or hack vegastrike.config to take it out
Click to expand...
Truly, it shouldn't take energy to do what I described. However, it DOES take energy to fly in that exact same straight line at that same velocity with the afterburner on and not holding `. Maybe the afterburner has fore and aft jets that neutralize itself when you disengage it? Anyway the behavior just seemed a little inconsistent to me and I . . . . . think I just got it worked out in my mind, tell me if this is right:

By holding ` you turn off the ship's thrust vector corrections, or disconnect the computer that somehow keeps your ship going the direction the nose is pointed, and lock everything in its current configuration. Or something. Whether real or not, this idea justifies it in my mind as not a bug. :)
 
You must log in or register to reply here.
Back
Top