Bug 8103

Created attachment 3106 [details]
Error one

Created attachment 3107 [details]
error 2

(setting the official maintainer beside the commiter of most rebuild)

CC: (none) => juan.baptiste
Assignee: bugsquad => mageia
Source RPM: (none) => warsow

WIP. Thanks for the report.

Fixed, I pushed warsow-1.02-3.mga3 to cauldron, please test and report back.

Assignee: mageia => juan.baptiste

Hello

Thanks for the new package. When I launch warsow, i have again the error message :

"********************
ERROR: Could not find any shaders!
********************
Error: Error during initialization: Could not find any shaders!é

Then, to bypass this problem, if I launch manually the game with "warsow +set fs_basepath /usr/share/warsow/", I have a pink screen and then I must kill the process to retrieve my desktop. I have the message :

"UI Init: UI: Failed to initialize AngelScript
Unknown command "menu_force"
Checking for Warsow update."

Perhaps, It's because the three files cgame_i386.so*, game_i386.so* and ui_i386.so* are not present in /usr/share/warsow/basewsw ?

Just to be sure, please delete the .warsow-1.0 folder and make sure that you have warsow-1.02-3 installed.

Also please check that in /usr/lib{64}/games/warsow you have a directory called basewsw which is full of symbolic links pointing to files in /usr/share/warsow/basewsw/*.

Hello Juan

The install was done with a new install of mageia 3 32 bit. So it was the first install of warsow.

My rpm :
[vouf@localhost ~]$ rpm -qa |grep warsow
warsow-1.02-3.mga3.nonfree
warsow-data-1.02-2.mga3.nonfree

then :
[root@localhost basewsw]# pwd
/usr/lib/games/warsow/basewsw
[root@localhost basewsw]# ls -l
total 0
lrwxrwxrwx 1 root root 41 janv.  2 17:23 * -> ../../../../../usr/share/warsow/basewsw/*

or 

[root@localhost warsow]# pwd
/usr/lib/games/warsow
[root@localhost warsow]# ls -l
total 8
drwxr-xr-x 2 root root 4096 janv.  2 17:23 basewsw/
drwxr-xr-x 2 root root 4096 janv.  2 17:23 libs/

I think the symbolink is not correctly created by the rpm.

Then I have tried the next operations :

[root@localhost warsow]# mv basewsw/ basewsw_old
[root@localhost warsow]# ln -s ../../../../../usr/share/warsow/basewsw/ basewsw
[root@localhost warsow]# ls -l
total 8
lrwxrwxrwx 1 root root   40 janv.  2 19:00 basewsw -> ../../../../../usr/share/warsow/basewsw

The game launch correctly with this manipulation !! No error message and directly with the command warsow.

That's weird, with my local build symbolic links are correcly created:

[root@cauldron-laptop cauldron]# ll /usr/lib64/games/warsow/basewsw/
total 28
lrwxrwxrwx 1 root root 47 Jan  2 20:28 configs -> ../../../../../usr/share/warsow/basewsw/configs/
lrwxrwxrwx 1 root root 52 Jan  2 20:28 data0_10.pk3 -> ../../../../../usr/share/warsow/basewsw/data0_10.pk3
lrwxrwxrwx 1 root root 56 Jan  2 20:28 data0_10pure.pk3 -> ../../../../../usr/share/warsow/basewsw/data0_10pure.pk3
lrwxrwxrwx 1 root root 52 Jan  2 20:28 data1_10.pk3 -> ../../../../../usr/share/warsow/basewsw/data1_10.pk3
lrwxrwxrwx 1 root root 56 Jan  2 20:28 data1_10pure.pk3 -> ../../../../../usr/share/warsow/basewsw/data1_10pure.pk3
[...]

but the version built in the BS didn't do the same... I'll have to check.

Hello

Today, I have a new rpm : warsow-1.02-4.mga3.nonfree . The problem is still present. Symbolic are not correctly created.

[root@localhost basewsw]# pwd
/usr/lib/games/warsow/basewsw
[root@localhost basewsw]# ls -ltra
total 8
lrwxrwxrwx 1 root root   41 janv.  3 08:30 * -> ../../../../../usr/share/warsow/basewsw/*
drwxr-xr-x 4 root root 4096 janv.  3 08:30 ../
drwxr-xr-x 2 root root 4096 janv.  3 08:30 ./

Yes I know, I changed the way those symlinks are created but it still happens the same thing when the package is built on the BS... still looking.

Ok I think I got it, please install warsow-1.02-5 and warsow-data-1.02-3 and test.

Hello Juan Luis

Sorry for you, but it's not good :

"Initializing Shaders:
********************
ERROR: Could not find any shaders!
********************
Error: Error during initialization: Could not find any shaders"

There is not the symbolic link.

[vouf@localhost warsow]$ pwd
/usr/lib/games/warsow
[vouf@localhost warsow]$ ls -l
total 8
drwxr-xr-x 2 root root 4096 janv.  5 00:35 basewsw/
drwxr-xr-x 2 root root 4096 janv.  5 08:34 libs/"

[vouf@localhost basewsw]$ pwd
/usr/lib/games/warsow/basewsw
[vouf@localhost basewsw]$ ls -l
total 0

Please double check you are installing the correct version, I have tested in three different cauldron x86_64 boxes and the symlinks are created ok and the game launches fine:

[root@cauldron juancho]# urpmi warsow
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch
(medium "Nonfree Release")
  warsow                         1.02         5.mga3.nonfr> x86_64
  warsow-data                    1.02         3.mga3.nonfr> noarch
505MB of additional disk space will be used.
493MB of packages will be retrieved.
Proceed with the installation of the 2 packages? (Y/n) y

[...]

[root@cauldron juancho]# ll /usr/lib64/games/warsow/basewsw/
total 0
lrwxrwxrwx 1 root root 33 Jan  6 17:39 configs -> /usr/share/warsow/basewsw/configs/
lrwxrwxrwx 1 root root 38 Jan  6 17:39 data0_10.pk3 -> /usr/share/warsow/basewsw/data0_10.pk3
lrwxrwxrwx 1 root root 42 Jan  6 17:39 data0_10pure.pk3 -> /usr/share/warsow/basewsw/data0_10pure.pk3
lrwxrwxrwx 1 root root 38 Jan  6 17:39 data1_10.pk3 -> /usr/share/warsow/basewsw/data1_10.pk3
lrwxrwxrwx 1 root root 42 Jan  6 17:39 data1_10pure.pk3 -> /usr/share/warsow/basewsw/data1_10pure.pk3
lrwxrwxrwx 1 root root 48 Jan  6 17:39 dedicated_autoexec.cfg -> /usr/share/warsow/basewsw/dedicated_autoexec.cfg
[...]

Can anyone else test please ?

Installed a i586 VM and the symlinks are created but under /usr/lib64/games/warsow/basewsw instead of /usr/lib/games/warsow/basewsw but I don't understand why, it seems the %{_libdir} macro is expanding to /usr/lib64 on the BS... strange...

Hello Juan

With the rpm warsow-1.02-7.mga3.nonfree, the problem is solved. 

Thanks !! I close the bug

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Created attachment 4205 [details]
Here's full output from terminal

CC: (none) => kristoffer.grundstrom1983

I have x11-driver-video-nouveau as a driver for my Graphicscard.

I'm not using any other medias but the Core ones, see here:

[kristoffer@localhost ~]$ urpmq --list-media
Core Release
Core Release Debug
Nonfree Release
Nonfree Release Debug
Tainted Release
Tainted Release Debug
Core 32bit Release
Nonfree 32bit Release
Tainted 32bit Release

(In reply to Kristoffer Grundström from comment #18)
> I have x11-driver-video-nouveau as a driver for my Graphicscard.
> 
> I'm not using any other medias but the Core ones, see here:
> 
> [kristoffer@localhost ~]$ urpmq --list-media
> Core Release
> Core Release Debug
> Nonfree Release
> Nonfree Release Debug
> Tainted Release
> Tainted Release Debug
> Core 32bit Release
> Nonfree 32bit Release
> Tainted 32bit Release

My bad. Correction: I'm not using any unstable medias,

(In reply to Kristoffer Grundström from comment #18)
> I have x11-driver-video-nouveau as a driver for my Graphicscard.
> 
> I'm not using any other medias but the Core ones, see here:
> 
> [kristoffer@localhost ~]$ urpmq --list-media
> Core Release
> Core Release Debug
> Nonfree Release
> Nonfree Release Debug
> Tainted Release
> Tainted Release Debug
> Core 32bit Release
> Nonfree 32bit Release
> Tainted 32bit Release

You should also have the updates media enabled for each of the above.

CC: (none) => davidwhodgins

(In reply to Dave Hodgins from comment #20)
> (In reply to Kristoffer Grundström from comment #18)
> > I have x11-driver-video-nouveau as a driver for my Graphicscard.
> > 
> > I'm not using any other medias but the Core ones, see here:
> > 
> > [kristoffer@localhost ~]$ urpmq --list-media
> > Core Release
> > Core Release Debug
> > Nonfree Release
> > Nonfree Release Debug
> > Tainted Release
> > Tainted Release Debug
> > Core 32bit Release
> > Nonfree 32bit Release
> > Tainted 32bit Release
> 
> You should also have the updates media enabled for each of the above.

I did that & still no gui.

Hello

Curious, it worked before. I just reinstalled warsow and I actually found the problem on 64-bit mga.

A workaround is to execute the following command on a mga 64 bits:
cd /usr/lib64/games/warsow/
mv basewsw basewsw.old
ln -s ../../../../../usr/share/warsow/basewsw/ basewsw

(In reply to Jean Michel Varvou from comment #22)
> Hello
> 
> Curious, it worked before. I just reinstalled warsow and I actually found
> the problem on 64-bit mga.
> 
> A workaround is to execute the following command on a mga 64 bits:
> cd /usr/lib64/games/warsow/
> mv basewsw basewsw.old
> ln -s ../../../../../usr/share/warsow/basewsw/ basewsw

That fixed it, but maaaaaaaaaaaan it's one CPU-consuming game. It lags all the time.

Hi,

Same error Mageia 4 64bits :

# urpmi warsow
Le paquetage warsow-1.03-3.mga4.nonfree.x86_64 est déjà installé


Video memory information:
total memory free in the pool: (VBO:845, Tex:845, RBuf:845) MB
largest available free block in the pool: (V:629, Tex:845, RBuf:629) MB
total auxiliary memory free: (VBO:1774, Tex:1774, RBuf:1774) MB
largest auxiliary free block: (VBO:8, Tex:8, RBuf:8) MB
Initializing Shaders:
********************
ERROR: Could not find any shaders!
********************
Error: Error during initialization: Could not find any shaders!

CC: (none) => aranud
Whiteboard: (none) => MGA4TOO

I updated the game to 1.51, please test it in cauldron, I don't have one at hand right now to do it my self (but it runs fine locally built on mga 4).

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => OLD