[Linux] How To Install Return of Reckoning

[xpander]

I'm having an issue after updating Wine to 11.0 regarding "mouse capture". Clicking in the game window no longer capture the mouse.

This causes problem when using mouse+right click to move my characters because it looks like when the mouse "virtually" leaves the game window my character starts to spin around quickly.

Could it be a setting inside the game or somewhere else that I need to tweak ?

fullscreen or windowed?

anyway, those types of issues usually are WM(window manager) bugs.
-try running with proton 11 then, it should have some fullscreen hack patches that normal wine doesn't have
-try gamescope if your wm doesn't behave good
-try different wm

[leubac]

I'm having an issue after updating Wine to 11.0 regarding "mouse capture". Clicking in the game window no longer capture the mouse.

This causes problem when using mouse+right click to move my characters because it looks like when the mouse "virtually" leaves the game window my character starts to spin around quickly.

Could it be a setting inside the game or somewhere else that I need to tweak ?

fullscreen or windowed?

anyway, those types of issues usually are WM(window manager) bugs.
-try running with proton 11 then, it should have some fullscreen hack patches that normal wine doesn't have
-try gamescope if your wm doesn't behave good
-try different wm

I tried both fullscreen or windows without luck. When trying to run with GE-Proton11-6-x86_64 the RoR launcher never appears and I get the following log:

Code: Select all

Launcher.exe
Start monitoring process.
gamemodeauto: 
INFO: umu-launcher version 1.4.4 (3.12.3 (main, Jul 15 2026, 23:46:41) [GCC 13.3.0])
INFO: steamrt4 is up to date
INFO: Running 'GE-Proton11-6-x86_64' using runtime 'steamrt4'
INFO: Running 'steamrt4' using runtime 'host'
pressure-vessel-wrap[9773]: E: Le processus fils s’est terminé avec le code 1: bwrap: setting up uid map: Permission denied

Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256

Do you have any idea why this runner gives this error ?

Before I try gamescope or a different WM I prefer to have the runner working.
Before Lutris got updated to 0.5.22 the runner used was correctly handling mouse capture. I can't remember which runner it was though.

[rorswar]

I'm having an issue after updating Wine to 11.0 regarding "mouse capture". Clicking in the game window no longer capture the mouse.

This causes problem when using mouse+right click to move my characters because it looks like when the mouse "virtually" leaves the game window my character starts to spin around quickly.

Could it be a setting inside the game or somewhere else that I need to tweak ?

fullscreen or windowed?

anyway, those types of issues usually are WM(window manager) bugs.
-try running with proton 11 then, it should have some fullscreen hack patches that normal wine doesn't have
-try gamescope if your wm doesn't behave good
-try different wm

I tried both fullscreen or windows without luck. When trying to run with GE-Proton11-6-x86_64 the RoR launcher never appears and I get the following log:

Code: Select all

Launcher.exe
Start monitoring process.
gamemodeauto: 
INFO: umu-launcher version 1.4.4 (3.12.3 (main, Jul 15 2026, 23:46:41) [GCC 13.3.0])
INFO: steamrt4 is up to date
INFO: Running 'GE-Proton11-6-x86_64' using runtime 'steamrt4'
INFO: Running 'steamrt4' using runtime 'host'
pressure-vessel-wrap[9773]: E: Le processus fils s’est terminé avec le code 1: bwrap: setting up uid map: Permission denied

Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256

Do you have any idea why this runner gives this error ?

Before I try gamescope or a different WM I prefer to have the runner working.
Before Lutris got updated to 0.5.22 the runner used was correctly handling mouse capture. I can't remember which runner it was though.

I vaguely remember having something similar a long time ago. Forcing Lutris to run as a virtual desktop resolved it, I believe. Sorry I can’t be more specific … it’s been a while.

[xpander]

I tried both fullscreen or windows without luck. When trying to run with GE-Proton11-6-x86_64 the RoR launcher never appears and I get the following log:

Code: Select all

Launcher.exe
Start monitoring process.
gamemodeauto: 
INFO: umu-launcher version 1.4.4 (3.12.3 (main, Jul 15 2026, 23:46:41) [GCC 13.3.0])
INFO: steamrt4 is up to date
INFO: Running 'GE-Proton11-6-x86_64' using runtime 'steamrt4'
INFO: Running 'steamrt4' using runtime 'host'
pressure-vessel-wrap[9773]: E: Le processus fils s’est terminé avec le code 1: bwrap: setting up uid map: Permission denied

Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256

Do you have any idea why this runner gives this error ?

Before I try gamescope or a different WM I prefer to have the runner working.
Before Lutris got updated to 0.5.22 the runner used was correctly handling mouse capture. I can't remember which runner it was though.

Quick ecosia search about the error you are getting seems to be related to appArmor profile. No idea what apparmor is. Some ubuntu thing?
https://github.com/DevToys-app/DevToys/issues/1373

[leubac]

I tried both fullscreen or windows without luck. When trying to run with GE-Proton11-6-x86_64 the RoR launcher never appears and I get the following log:

Code: Select all

Launcher.exe
Start monitoring process.
gamemodeauto: 
INFO: umu-launcher version 1.4.4 (3.12.3 (main, Jul 15 2026, 23:46:41) [GCC 13.3.0])
INFO: steamrt4 is up to date
INFO: Running 'GE-Proton11-6-x86_64' using runtime 'steamrt4'
INFO: Running 'steamrt4' using runtime 'host'
pressure-vessel-wrap[9773]: E: Le processus fils s’est terminé avec le code 1: bwrap: setting up uid map: Permission denied

Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256

Do you have any idea why this runner gives this error ?

Before I try gamescope or a different WM I prefer to have the runner working.
Before Lutris got updated to 0.5.22 the runner used was correctly handling mouse capture. I can't remember which runner it was though.

Quick ecosia search about the error you are getting seems to be related to appArmor profile. No idea what apparmor is. Some ubuntu thing?
https://github.com/DevToys-app/DevToys/issues/1373

Yes AppArmor is Ubuntu security related (see https://ubuntu.com/blog/ubuntu-23-10-re ... namespaces if interested). So, configuring AppArmor properly allowed me to run the game with Proton and re-enabling mouse capture. Thanks for help.

[rorswar]

Every time there is a patch (and thank you for them!), I end up having to restart the launcher endless times before all files are downloaded as it keeps freezing up.

It worked fine this morning after I updated last night, but after today’s server reset it doesn’t even get past “downloading (1/2)”.

It doesn’t seem to matter if I have VPN (I always have) or off. Am at a loss and can’t log in.

Does anyone have any idea?

[xpander]

Every time there is a patch (and thank you for them!), I end up having to restart the launcher endless times before all files are downloaded as it keeps freezing up.

It worked fine this morning after I updated last night, but after today’s server reset it doesn’t even get past “downloading (1/2)”.

It doesn’t seem to matter if I have VPN (I always have) or off. Am at a loss and can’t log in.

Does anyone have any idea?

Maybe
-try making sure some random older wine processes haven't hanged(still running)
KillallWineProcess script if you want

Spoiler:

Code: Select all

#/bin/sh


pids=$(
    ls -l /proc/*/exe 2>/dev/null |
    grep -E 'wine(64)?-preloader|wineserver|winedevice.exe' |
    perl -pe 's;^.*/proc/(\d+)/exe.*$;$1;g;'
)

if ((${#pids})); then
    echo $pids
    kill $pids
    
    sleep 1
    
    pids=$(
        ls -l /proc/*/exe 2>/dev/null |
        grep -E 'wine(64)?-preloader|wineserver|winedevice.exe' |
        perl -pe 's;^.*/proc/(\d+)/exe.*$;$1;g;'
    )
    
    if ((${#pids})); then
        kill -9 $pids
    fi
fi

notify-send -t 2000 'WineKiller' 'All known WINE processes are killed now!' --icon=jockey

-restart your router ofc
-restart networking on your linux distro
-try different proton/wine version

[rorswar]

Every time there is a patch (and thank you for them!), I end up having to restart the launcher endless times before all files are downloaded as it keeps freezing up.

It worked fine this morning after I updated last night, but after today’s server reset it doesn’t even get past “downloading (1/2)”.

It doesn’t seem to matter if I have VPN (I always have) or off. Am at a loss and can’t log in.

Does anyone have any idea?

Maybe
-try making sure some random older wine processes haven't hanged(still running)
KillallWineProcess script if you want

Spoiler:

Code: Select all

#/bin/sh


pids=$(
    ls -l /proc/*/exe 2>/dev/null |
    grep -E 'wine(64)?-preloader|wineserver|winedevice.exe' |
    perl -pe 's;^.*/proc/(\d+)/exe.*$;$1;g;'
)

if ((${#pids})); then
    echo $pids
    kill $pids
    
    sleep 1
    
    pids=$(
        ls -l /proc/*/exe 2>/dev/null |
        grep -E 'wine(64)?-preloader|wineserver|winedevice.exe' |
        perl -pe 's;^.*/proc/(\d+)/exe.*$;$1;g;'
    )
    
    if ((${#pids})); then
        kill -9 $pids
    fi
fi

notify-send -t 2000 'WineKiller' 'All known WINE processes are killed now!' --icon=jockey

-restart your router ofc
-restart networking on your linux distro
-try different proton/wine version

Tried all that, to no avail.

I did use Claude and it suggested my WiFi settings might be on power saving mode. Disabled it, and seems to be working a bit better.

[xpander]

I did use Claude and it suggested my WiFi settings might be on power saving mode. Disabled it, and seems to be working a bit better.

Good to hear. wifi powersaving problem is also documented on the troubleshooting section of the first post.

[rorswar]

I did use Claude and it suggested my WiFi settings might be on power saving mode. Disabled it, and seems to be working a bit better.

Good to hear. wifi powersaving problem is also documented on the troubleshooting section of the first post.

Ugh, totally missed that. Thank you.