Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed.

Bug #613995 reported by Randakar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
criticalmass (Fedora)
Won't Fix
Medium
criticalmass (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: criticalmass

criticalmass tries to start (fullscreen), gets my screens (dual-screen setup) into 640x480 video mode, and then crashes and burns with the following error:

criticalmass: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed.

Leaving my desktop behind in 640x480 isn't funny, I tell you. Why doesn't X recover from something like that gracefully?
But I digress ..

I also found this bug in the RedHat bugzilla, so I'm not the only one. Here is the bug ID:

https://bugzilla.redhat.com/show_bug.cgi?id=575432

I will come back later and fill in any other details such as the backtrace you folks undoubtedbly need ;-)
---
Architecture: i386
DistroRelease: Ubuntu 10.04
Package: criticalmass 1:1.0.0-1.2ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video

---
Architecture: i386
DistroRelease: Ubuntu 10.04
Package: criticalmass 1:1.0.0-1.2ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video

Revision history for this message
In , Bill (bill-redhat-bugs) wrote :

Description of problem:
INFO: Adding LevelPack [levelpacks/CritterPack.xml]
INFO: Initialization complete OK.
INFO: sounds/humm.wav not cached -> loading...
WARNING: ziStream_seek not implemented!
WARNING: ziStream_seek attempt to seek to offset -4 whence 1
WARNING: ziStream_seek not implemented!
WARNING: ziStream_seek attempt to seek to offset 0 whence 1
INFO: Entering Main loop.
critter: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed.
Aborted (core dumped)

Version-Release number of selected component (if applicable):
CriticalMass-1.0.2-7.fc12

How reproducible:
Just start the program. If run in fullscreen mode, aborts and leaves resolution screwed up. Leaves the above error message visible if run from cli.

Steps to Reproduce:
1. Start program, as e.g. /usr/bin/critter +fullscreen 0
2. ...
3. aborts.

Actual results:
Crashes.

Expected results:
Opportunity to try out this game.

Additional info:
Backtrace shows assertion triggered in r200_dri.so, so *could* be a bug in the DRI radeon driver, but haven't seen this crash in any other games.

Quick backtrace (don't have debuginfo installed yet):

(gdb) bt
#0 0x008a9416 in __kernel_vsyscall ()
#1 0x0014da91 in raise () from /lib/libc.so.6
#2 0x0014f35a in abort () from /lib/libc.so.6
#3 0x00146be8 in __assert_fail () from /lib/libc.so.6
#4 0x006327c3 in radeon_validate_texture_miptree () from /usr/lib/dri/r200_dri.so
#5 0x0061c15a in ?? () from /usr/lib/dri/r200_dri.so
#6 0x0061ca90 in r200UpdateTextureState () from /usr/lib/dri/r200_dri.so
#7 0x00611a64 in r200ValidateState () from /usr/lib/dri/r200_dri.so
#8 0x00612144 in ?? () from /usr/lib/dri/r200_dri.so
#9 0x00ed01dc in _tnl_draw_prims () from /usr/lib/dri/libdricore.so
#10 0x00ed02c5 in _tnl_vbo_draw_prims () from /usr/lib/dri/libdricore.so
#11 0x00ecec92 in vbo_save_playback_vertex_list () from /usr/lib/dri/libdricore.so
#12 0x00e4093c in ?? () from /usr/lib/dri/libdricore.so
#13 0x00e4356d in _mesa_CallList () from /usr/lib/dri/libdricore.so
#14 0x00eb8957 in ?? () from /usr/lib/dri/libdricore.so
#15 0x02b3bb5f in glCallList () from /usr/lib/libGL.so.1
#16 0x08062fc4 in ?? ()
#17 0x0809486a in ?? ()
#18 0x080567db in std::ios_base::Init::~Init() ()
#19 0x0809c7de in ?? ()
#20 0x00139bb6 in __libc_start_main () from /lib/libc.so.6
#21 0x0804c4a1 in std::ios_base::Init::~Init() ()

Revision history for this message
In , Hans (hans-redhat-bugs) wrote :

Changing component to mesa as that is where the assert is which gets triggered.

Revision history for this message
In , Hans (hans-redhat-bugs) wrote :

*** Bug 596431 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Bill (bill-redhat-bugs) wrote :

Still happening now:

INFO: Initialization complete OK.
INFO: sounds/humm.wav not cached -> loading...
WARNING: ziStream_seek not implemented!
WARNING: ziStream_seek attempt to seek to offset -4 whence 1
WARNING: ziStream_seek not implemented!
WARNING: ziStream_seek attempt to seek to offset 0 whence 1
INFO: Entering Main loop.
critter: radeon_mipmap_tree.c:450: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed.
Aborted (core dumped)

Revision history for this message
In , Bill (bill-redhat-bugs) wrote :

Also, please, please, please make it so that when the games crash my desktop isn't left resized to 640x480. It's harder to find the terminal to type the "xrandr -s 0" command into than it was to pan around one that was switched with the old vidmode extension :(

Randakar (randakar)
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Randakar (randakar) wrote :

Startup log.

Revision history for this message
Randakar (randakar) wrote :

I've added the line: "set resolutions = 1280x960,1152x864,1024x768" to the configuration file in ~/.critter/critter_config.txt before generating that startup log. That didn't actually fix the crash, but it did prevent criticalmass from putting my screen in 640x480 first.

Revision history for this message
Randakar (randakar) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
description: updated
Revision history for this message
Randakar (randakar) wrote :

apport information

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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

Changed in criticalmass (Fedora):
importance: Unknown → Medium
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.