Member Avatar for linux

I attempted running this game/toy/application called "Phun" () which is a 2-D physics simulator.

Whenever I try to run it, I get the error:

alex@alex-laptop:~/Desktop/Phun$ ./phun_beta_2_5_linux32 
Parsing autoexec.cfg...
Creating window...
Segmentation fault (core dumped)
alex@alex-laptop:~/Desktop/Phun$

I read somewhere that this may be a cause of me needing to update my graphics driver for my Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller .

1. How can I update it? Where are the drivers for this card? (Yes, I searched online)
2. What does this error mean, and do I really need to update my card to fix it? I disabled pixel shading in autoexec.cfg and tried running with pixel shading and without it. Still crashes with the segmentation fault.

Direct download:
Direct download (64-bit):

Thanks in advance!
-- Alex

  • 2 Contributors
  • 3 Replies
  • 519 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by DimaYasny

Dani AI

Generated

A brief follow-up for future readers: confirmed the crash was resolved after the application author released an updated build, and reported it runs on Kubuntu. For others who hit a segfault in OpenGL apps on Intel Mobile 945GM (GMA 950), the likely causes are a userland/driver mismatch (Mesa vs. the binary), a shader/GL-path the binary uses that exercises a driver bug, or missing/incorrect kernel DRM modules. The checklist below helps narrow it down and produce useful debugging information for the app author or your distro maintainers.

Basic checks and quick tests:

  • Verify the kernel driver and module for the VGA device and that Mesa is providing GL.
  • See what GL renderer the system reports; if that shows "software" or a mismatched renderer the binary may be picking the wrong path.
  • Try running the program with software GL to see if it avoids the crash (this separates driver bugs from the app itself).
  • Collect an Xorg log, glxinfo output, and a gdb backtrace to include in a bug report if needed.

Example diagnostic commands you can run (adjust for your distro):

lspci -nnk | grep -A3 -i vga
lsmod | grep i915
glxinfo | grep "OpenGL renderer"
cat /var/log/Xorg.0.log | egrep -i "drm|intel|dri|error|fail"
LIBGL_ALWAYS_SOFTWARE=1 ./phun      # runs using software GL
gdb --args ./phun
  (gdb) run
  (gdb) backtrace full

If software GL works, update your distro packages for Mesa, xserver, and the kernel (these supply the Intel i915 DRM and Mesa drivers). Avoid random binary "Intel" drivers — prefer distro packages or official upstream Mesa builds. When filing a bug to the app developer include: glxinfo output, relevant Xorg.0.log excerpts, and the gdb backtrace; that lets them reproduce a crash and target the fix more quickly.

Recommended Answers

All 3 Replies

Member Avatar for linux

Thank you for the link.

However, my error was fixed in the most recent release, which was released literally 30 minutes after I posted that.

Member Avatar for DimaYasny

yeah, I checked, it works on my kubuntu

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.