Issues with ports (lr-prboom, eduke32)

Zering

@mitu I don't understand what information you want me to provide, there is nothing in the directory you've just indicated.

It doesn't crash when I install from binary, and for the most part the module works, but it crashes and kicks me back to Emulation Station after a few minutes of gameplay, ie. if I try to save or load.

Is there a different log for that type of crash that I can access and copy here?

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

It doesn't crash when I install from binary, and for the most part the module works, but it crashes and kicks me back to Emulation Station after a few minutes of gameplay, ie. if I try to save or load.

Then you should have a log file in /dev/shm, called runcommand.log. Get the contents of the file and post it here. If you reboot your system, then the file will be deleted, so it's important you look for it immediately after the crash.

Zering

@mitu All right, seems easy enough.

If the system hangs and I have to do a hard reboot, can I find a log for that as well?

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

If the system hangs and I have to do a hard reboot, can I find a log for that as well?

Not sure, but your should install SSH and access the Pi via WinSCP or FileZilla. The interface/game might be locked, but the system might still work.

Zering

@mitu I've got WinSCP. The reason I was asking is I've just tried reproducing the crash on eduke32 and instead of sending me back to ES the game just hung on the loading screen. If it hangs, what can I do with WinSCP to try and find a solution to the issue?

mitu

@Zering Same advice - try to get a log file.

Zering

@mitu So I managed to find a log file after the latest crash (it didn't hang this time, it went back to ES when I tried to load my game). It's a whopping 14000 lines, is that normal?

link text

Trying to make sense of this thing is like reading chinese backwards with blinders on to me, so if anybody can offer any guidance I'd be very grateful.

mitu

The log is filled with the same error message over and over:

[...]
Wrote eduke32.cfg
Error writing settings.cfg: Too many open files
*** Error in `/opt/retropie/ports/eduke32/eduke32': double free or corruption (!prev): 0x017d6488 ***

Can you check if the settings.cfg file is writable by the pi user ? It should be in \\retropie\configs\ports\duke3d.

Zering

@mitu I can edit it with WinSCP. Here are the contents :

// this file is automatically generated by EDuke32
unbindall
unbound Alt_Fire
unbound Mouse_Aiming
unbound Toggle_Crosshair
unbound Show_DukeMatch_Scores
unbound Dpad_Select
unbound Dpad_Aiming
unbound Alt_Weapon
osdeditpal "12"
osdtextpal "12"
osdtextshade "2"
r_borderless "0"
r_usenewaspect "0"
vid_gamma "1.200000"
r_upscalefactor "2"
r_ambientlight "1.250000"
vid_gamma "1.200000"
wchoice "3457860291"

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

@mitu I can edit it with WinSCP. Here are the contents :

That's not what I asked. Can you check the file's permissions and post a screenshot ?

Zering

@mitu Ah sorry. Is this what you want?

link text

(That second line had my name and email adress on)

mitu

No quite, I meant from WinSCP. What user are you using for WinSCP ?

Zering

@mitu Is that what WinSCP asks for on login?

quicksilver

@Zering yes are you logging in as user "pi" or user "root"

Zering

@quicksilver pi.

Figured it out : link text

mitu

The permissions are fine. Delete or rename the file, then run the game again, re-do your settings and then exit. Run a game again and see if you get any crash.

Zering

@mitu All right, I'll try it and update. Thank you for your patience.

Edit : Looks like it works. Four reloads without a crash. Thank you so much!

Incidentally, I've found this on the github wiki :

'NAM however will run and continue to run everytime you start it up but it changes the eduke32.cfg file located in .etc/eduke32 on its own and breaks duke3d and all expansion packs till you manually modify eduke32.cfg selectedgrp field back to duke3d.grp. I've tried multiple times and nam breaks duke 3d and any expansion packs every single time. To avoid this change the permissions on the eduke3d.cfg file so no one can change it. And then you can run duke 3d the expansion packs and nam without anything breaking or having to modify anything after running nam.'

I am wondering if this is the same glitch?