Bug 880280

Created attachment 652033 [details]
File: backtrace

Created attachment 652034 [details]
File: build_ids

Created attachment 652035 [details]
File: cgroup

Created attachment 652036 [details]
File: core_backtrace

Created attachment 652037 [details]
File: dso_list

Created attachment 652038 [details]
File: environ

Created attachment 652039 [details]
File: limits

Created attachment 652040 [details]
File: maps

Created attachment 652041 [details]
File: open_fds

Created attachment 652042 [details]
File: proc_pid_status

Created attachment 652043 [details]
File: var_log_messages

Created attachment 652044 [details]
File: smolt_data

Did it work with megaglest 3.6.0.3? I would like to know
it before reassigning the bug, but I am almost certain it
is an mesa/drm issue.

The backtrace is when doing this call:

	for(Layers::iterator layer= layers.begin(); layer!= layers.end(); ++layer)
		(*layer)->renderVisibleLayer();
	glDisableClientState(GL_VERTEX_ARRAY);
=>	glBindBuffer(GL_ARRAY_BUFFER_ARB,0);
	glBindBuffer(GL_ELEMENT_ARRAY_BUFFER_ARB,0);

It should be useful to give some information about video card,
at least "$ lspci |grep VGA".

From what I noticed from loaded objects it is an intel card.
so you may want to follow mostly procedures described at
http://intellinuxgraphics.org/how_to_report_bug.html

Yes, it's mesa/drm issue. Sorry for my bad english. I think, I will report this bug to intellinuxgrafics.org later. megaglest 3.6.0.3 also not work.

[Raistlin@mobile ~]$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
[Raistlin@mobile ~]$ 

It's the intel GMA 3100. Netvook is the Acer AOD260. I have some other issues with grafics in KDE and with some other games, thanks for your advise.

Sorry for not reassigning it before to mesa, but here it goes.

Not the current bug, but glest might want to consider not making its segfault handler reenter the main loop, that can't possibly do anything good.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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