New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unvanquished failed to start on Slackware 14.2 #944

Open
dslackw opened this Issue Jul 3, 2016 · 34 comments

Comments

Projects
None yet
7 participants
@dslackw
Copy link

dslackw commented Jul 3, 2016

Unvanquished 0.50 Linux x86_64 Jul  2 2016
cmdline: -libpath /usr/lib64/unvanquished -pakpath /usr/share/games/unvanquished/pkg
[FS] Lib path: /usr/lib64/unvanquished 
[FS] Home path: /home/dslackw/.unvanquished 
[FS] Pak search path: /usr/share/games/unvanquished/pkg 
[FS] Pak search path: /home/dslackw/.unvanquished/pkg 
[FS] Loading pak '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'... 
Warn: [FS] Could not find pak 'unvanquished' with version '0.49.0' required by '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3' 
Failed to load pak 'unvanquished': Missing dependency

Could not load base pak 'unvanquished', falling back to default

couldn't exec 'default.cfg' 
Warn: Couldn't read conhistory: No such file or directory 
----- Client Initialization ----- 
Loading RSA keys from pubkey 
Daemon RSA public-key found. 
----- Client Initialization Complete ----- 
Calling GetRefAPI… 
SDL_Init( SDL_INIT_VIDEO )...  
Using SDL Version 2.0.4 
]ATTENTION: default value of option force_s3tc_enable overridden by environment.
SDL using driver "x11" 
Initializing OpenGL display 
Display aspect: 1.778 
...setting mode -2: 
 1920 1080 
The change will take effect after restart. 
The change will take effect after restart. 
Warn: GLEW version < 2.0.0 doesn't support GL core profiles 
Using 24 Color bits, 24 depth, 8 stencil display. 
Using GLEW 1.13.0 
Using enhanced (GL3) Renderer in GL 2.x mode... 
Available modes: '1920x1080 ' 
GL_RENDERER: Gallium 0.4 on AMD RV730 (DRM 2.43.0, LLVM 3.8.0) 
Detected graphics driver class 'Mesa' 
Detected graphics hardware class 'AMD Radeon DX10-class' 
Initializing OpenGL extensions 
...ignoring GL_ARB_debug_output 
...found shading language version 130 
...using GL_ARB_half_float_pixel 
...using GL_ARB_texture_float 
...using GL_EXT_texture_integer 
...using GL_ARB_texture_rg 
...using GL_EXT_texture_filter_anisotropic 
...using GL_ARB_half_float_vertex 
...using GL_ARB_framebuffer_object 
...GL_ARB_get_program_binary found, but with no binary formats 
...using GL_ARB_buffer_storage 
...using GL_ARB_uniform_buffer_object 
...using GL_ARB_map_buffer_range 
...using GL_ARB_sync 
Warn: SSAO not used because GL_ARB_texture_gather is not available. 
glsl shaders took 8744 msec to build 
Warn: R_InitImages: could not load 'gfx/2d/consolechars' 
[FS] Loading pak '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'... 
Warn: [FS] Could not find pak 'unvanquished' with version '0.49.0' required by '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3' 
Failed to load pak 'unvanquished': Missing dependency

Could not load base pak 'unvanquished', falling back to default

https://postimg.org/image/46alnaje9/

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Jul 3, 2016

cmdline: -libpath /usr/lib64/unvanquished -pakpath /usr/share/games/unvanquished/pkg

Do you use a thirdparty package? If yes, the bug is in this package not in unvanquished itself.

[FS] Loading pak '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'...
Warn: [FS] Could not find pak 'unvanquished' with version '0.49.0' required by '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'
Failed to load pak 'unvanquished': Missing dependency

It looks like the package you use miss some data, it looks like it shipped the "unvanquished_0.50.0.pk3" pak but not the "unvanquished_0.49.0.pk3" one (and probably not the older one). There is a dependency mechanism is this paks and the previous ones are still needed (the newer paks just contains the newer stuff, it acts like a diff, you need the older data to get all the data).

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 5, 2016

We do not distirbute the Slackware package, so we cannot fix this (as @illwieckz pointed out).

@Viech Viech closed this Jul 5, 2016

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 5, 2016

Hi again,
I am a maintainer for Slackware package. https://slackbuilds.org/repository/14.2/games/unvanquished/
After download all data package in $HOME directory i got this message:
https://postimg.org/image/prbpy8hrr/

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 5, 2016

Hello @dslackw that appears to be a different error, I'm not sure if this can also happen when the data packages (including the gamelogic) don't match the engine binaries (@Kangz, @Amanieu?).

Can we get the console output in text form so that we can see which packages actually get loaded?

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 5, 2016

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 5, 2016

It does seem like all relevant files are present. I noticed that it uses cgame-x86_64.nexe. The two developers I just pinged should be able to tell if this a bug worthy a new issue or just a common configuration issue.

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 6, 2016

Does this issue should be reopened?

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 6, 2016

Yeah, I guess we can re-open the issue as the packaging looks good to me now and hence it may be a bug on our end.

@Viech Viech reopened this Jul 6, 2016

@Viech Viech added A-Engine and removed A-Distribution labels Jul 6, 2016

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 6, 2016

Yes the package builds normally. So I will wait for a solution from here.
Thank you

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 6, 2016

It may be that the virtual machine crashes. Can you try

  • launching daemon with -set vm.cgame.debugLoader 5, which will create cgame-nacl_loader.log in Unvanquished's folder in your home directory with more details on the crash, potentially,
  • launching daemon with -set vm.cgame.type 2, given that the cgame-native-exe (or so) that you compiled is in the same directory as daemon?
@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 6, 2016

Creates only the file cgame-nacl_loader.log without contents.
https://postimg.org/image/t1117mlep/

@Kangz

This comment has been minimized.

Copy link
Member

Kangz commented Jul 6, 2016

How about vm.cgame.type 2? If that crashes too, can you give us a backtrace?

@Amanieu

This comment has been minimized.

Copy link
Member

Amanieu commented Jul 6, 2016

@dslackw you need to run with vm.cgame.type 0 (the default) for vm.cgame.debugLoader to work

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 6, 2016

@dslackw

This comment has been minimized.

Copy link

dslackw commented Jul 8, 2016

Is there any developments in this issue?

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Jul 8, 2016

The error you get is very generic and unexplaining. As a package maintainer you will have a rather specific setup that may be hard for us to reproduce exactly. Ideally you would provide us with a backtrace of the crash. However, I'm no expert on the plenty of options in which you can start a gamelogc and on how to debug a specific one among those. I can just tell that I personally run the game within a debugger (e.g. gdb) with -set vm.cgame.type 3 -set vm.cgame.debug 1 if I want to debug the module that's crashing for you. However, it is then loaded from a shared object file (the cgame-native-dll.so that you may or may not have compiled, see ccmake and your build directory), which may or may not crash for you. So far we only know that the platform independent VM file shipped inside the pk3 crashes for you. It may be that you can compile and use breakpad support to get a binary crash dump in this case. @DolceTriade and @slipher should elaborate on that option in case you don't get a crash registered within gdb.

@slipher

This comment has been minimized.

Copy link
Contributor

slipher commented Jul 9, 2016

If there is a crash in the NaCl cgame, it already should have created crash dumps under ~/.unvanquished/crashdump. A crash in the engine or a shared object can be dumped if Breakpad is enabled by setting the USE_BREAKPAD option with CMake (but you could simply use gdb for such cases). Note that by a crash I mean a kind of fault that would trigger a signal handler.

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Oct 9, 2016

Hello, Slackware 14.2 user here, I installed the unvanquished package and when I run it normally i get this error :
Warn: Built-in shaders failed: Couldn't compile vertex shader: deformVertexes
And when I run it with my Nvidia GPU the error is :
Warn: Built-in shaders failed: Couldn't compile fragment shader: depthtile1
I used both versions, the prebuilt and the SlackBuild compiled one.
I also tried on another computer using Slackware 14.1 and on Windows, nothing works.
By the way aren't you the guy who made that Fluxbox+Slackware Video on youtube ? 😃

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Oct 9, 2016

Can you try the prebuilt binary and try to reproduce the issue with it to figure out if it's a building or packaging issue on slackware side or a bug in unvanquished?

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Oct 9, 2016

@Incognito4nonymous there is nothing in this thread that proves the slackware package your are trying to use is already working for someone else. It's a third-party effort we can't verify. @dslackw is your package works on your side?

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Oct 9, 2016

Oh blast, that's a big file.
I'll ask a friend to download it, and I'll come back to give my feedback.

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Oct 9, 2016

You can partially download unvanquished with bittorrent using that torrent file. This way you just disable all the map-*.pk3 and the tex-*.pk3 downloads. Of course you will not be able to load a map to play but you would be able to load the game itself. You can of course disable the win32.zip, win64.zip and mac.zip downloads too. You need all the unvanquished_*.pk3.

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Oct 9, 2016

If you download map-vega_b4.pk3, tex-common_2.0.pk3, and tex-vega_b4.pk3, you would be able to load the vega map and do a complete Unvanquished experience without downloading everything else. This way you will save 312M of download (you can fetch them later).

@dslackw

This comment has been minimized.

Copy link

dslackw commented Oct 10, 2016

@Incognito4nonymous yes i'am
@illwieckz nope, release 0.50.0 build perfect but not run :(

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Oct 10, 2016

Nice to meet you ! Your video made me dicover trance !
And actually the issue ain't Slackware specific, it also affects Windows, as I mentioned above I downloaded the multiplatform version first, and afterwards I used the Slackbuild since it worked neither on Linux than on Windows.
All the pkgs where downloaded from here.
So I think it is another issue. The Slackbuild builds flawlessly without any errors.

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Oct 17, 2016

So... No one has any idea of how I can solve this ? As I said I already downloaded the GitHub version before downloading the SlackBuild, so the issue ain't OS specific.
I really wanna play that game hard as I plan to use it's engine for some projects.

@dslackw

This comment has been minimized.

Copy link

dslackw commented Oct 17, 2016

I remember playing this game in the past... it is really awesome !!!

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Nov 3, 2016

Can you try with the moddb version ? The actual one seems to be broken.

@dslackw

This comment has been minimized.

Copy link

dslackw commented Nov 8, 2016

I downloaded version 42 from here, it is right ?
The same error.

@Viech

This comment has been minimized.

Copy link
Member

Viech commented Nov 9, 2016

The release on ModDB is outdated, the current version is Alpha 50.

Also @Incognito4nonymous please don't hijack other issues. Your error message is completely different from what @dslackw is experiencing. This issue is only for tracking @dslackw's problem. To clean this up, here are the relevant logs again:

http://pastebin.com/CraPG3vS
https://postimg.org/image/9y12jnptj/

As I said before, the error message is a rather generic one telling us that some virtual machine crashed. We need a backtrace as discussed before to find the underlying problem.

@Incognito4nonymous

This comment has been minimized.

Copy link

Incognito4nonymous commented Nov 12, 2016

Yeah, my confusion came out of the fact that I'm also using Slackware 14.2.

@Viech Viech added the S-Needs-Input label Dec 11, 2016

@dslackw

This comment has been minimized.

Copy link

dslackw commented Dec 22, 2018

Hi again,
After a successful building the new version 0.51.1 on Slackware 14.2:
https://pastebin.com/iV9anzfT

It still failed to start the game
Image: https://ibb.co/Lhw7GbR
Pastebin: https://pastebin.com/EwNY11Rv

Slackbuild: https://gitlab.com/dslackw/SlackBuilds/tree/master/unvanquished

Any advice?
Thanks

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Dec 23, 2018

This can be related to missing or miconfigured /dev/shm. On my distro it's mounted like this:

$ mount | grep shm
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

This is related to NativeClient I think.

@dslackw

This comment has been minimized.

Copy link

dslackw commented Dec 23, 2018

In my own:

$ mount | grep shm                                                     
tmpfs on /dev/shm type tmpfs (rw)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment