warzone2100 crashed with SIGSEGV

StacktraceTop:pie_RemainingPasses () at piedraw.c:797
drawTiles (camera=0x3f, player=<value optimized out>) at display3d.c:951
draw3DScene () at display3d.c:583
displayWorld () at display.c:1519
gameLoop () at loop.c:551

Does Warzone 2100 still crash?

Unfortunately it seems to be intermittent. I have gone upstream and had some discussions with the developers. Various crashes are known. I'm trying to see if I can narrow down the issue for easy replication. Other OpenGL apps do not have the issue. The code is in beta status and not considered fully production quality at this time. As this is a known problem upstream, Im moving the bug to confirmed.

Please note if you have a URL for an upstream bug. Thanks.

Yeah I would have done a bugwatch here on LP but the way upstream is handling dev is through their forums and PMs. Thanks

Mailinglist and bugtracker...

Dennis the upstream Dev said their preferred location for the beta 4 bugs and feedback is their forums.

http://forums.wz2100.net/viewforum.php?f=19

The revision in the Intrepid repo's as I indicated is beta, beta four. Its not production.

Are you now saying that the Devs on the warzone project have changed and now want to use their ticketing system for betas? Can you please not be cryptic in your bug comments, thanks.

We want bugs reported in our bug ticketing system. However, the version that you have this bug report against (r1436) is ancient and known to be very buggy. It is also not an officially released version. So reporting bugs against this revision has no purpose and will merely be closed.

In regards to this specific bug, a possible workaround may be to turn off shadows.

From the way I understood the bug comments, this bug also exists on beta 4, which is the latest development release.

nullack: You confirm this bug on the version of Warzone 2100 in Intrepid?

The bug is intermittent and I am currently trialling with the video config suggested as a workaround. No crashes so far.

I encourage the upstream team to release a new beta release if their code is ready for it. Many enthusiasts of their work - myself included - would be happy to test any new builds they have. Im thankful for the great game. By having more frequent test releases the community will be better able to help the upstream devs. Thanks.

> Dennis the upstream Dev said their preferred location for the beta 4 bugs and feedback
> is their forums.
Must be a misunderstanding. We prefer to get bugreports of current releases through the bugtracker (and if that is impossible through the mailinglist).

Invalid since it refers to an extremely outdated unsupported version.

Not invalid - the revision causing these problems is the current revision available in the Intrepid repos ~ 2.1.0~1.beta4-2. We cant classify current version level packages in the repos as invalid bug reports simply because newer upstream revisions might be available. As Jaunty has a newer package when this is backported to the production Intrepid or Jaunty enters production the fix could be considered to be released.

Fix released as current dev cycle has the upstream production release version 2.1

I had just finished the third away mission and clicked on Continue game.

I am beginning to think the problem may be in either the latest Linux kernel or in the latest KDE. These problems started with the last upgrade for me. Everything was fine before that.

"Package: warzone2100 2.1.0~0.svn1436-1"

For comparison, Warzone recently passed r10000, and the latest version is 2.3 beta 10.

This is an old bug that is probably fixed. Please create a new bug ticket in the issue tracker to report your new and probably-unrelated crash.