FretsOnFire.py crashed with error in setMode()

Bug #149733 reported by Tshirtz
98
This bug affects 4 people
Affects Status Importance Assigned to Milestone
fretsonfire (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Intrepid by Dogge

Bug Description

Binary package hint: fretsonfire

crashed when opening in a generic video enviroment. ( no restricted driver use) probably not abiug since It is using opengl and I dont have that enabled.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 6 03:47:36 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/share/games/fretsonfire/game/FretsOnFire.py
InterpreterPath: /usr/bin/python2.5
Package: fretsonfire-game 1.2.451.dfsg-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python ./FretsOnFire.py
ProcCwd: /usr/share/games/fretsonfire/game
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['./FretsOnFire.py']
SourcePackage: fretsonfire
Title: FretsOnFire.py crashed with error in setMode()
Uname: Linux Akina86 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
Tshirtz (tshirtz1013) wrote :
Revision history for this message
bigdoby (bigdoby-gmail) wrote :

i have the same error in ubuntu 8.04

Revision history for this message
Federico (dreamerman88it) wrote :

me too!!!

Revision history for this message
jaylaprade (protcron) wrote :

I believe that this problem is caused by the DefaultDepth parameter in the xorg.conf

sudo vi /etc/X11/xorg.conf

look for

DefaultDepth

you should see: DefaultDepth 16

Change that to:

DefaultDepth 24

And then restart X (you could use ctrl-alt-backspace)

FretsonFire should run now, but there are other problems that need correcting. I think that the /usr/share/games/fretsonfire/songs directory needs to be writable to the user, then there is also a problem of the current version crashing on x86-64 compiles. I think that is a problem with the compile itself. Looks like this needs more bug reports.

Revision history for this message
Hew (hew) wrote :

Fretsonfire 1.2.512.dfsg-3 is now in Intrepid. Could you please test if the problem still exists in this latest version? Thanks in advance.

Changed in fretsonfire:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
jaylaprade (protcron) wrote :

That worked!!!

I am going to test on 3 other systems this evening. I'll report then.

Revision history for this message
Hew (hew) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in fretsonfire:
status: Incomplete → Fix Released
Revision history for this message
Hew (hew) wrote :

Reopening and triaging. This bug still exists in fretsonfire-game 1.2.512.dfsg-3 as reported by duplicate bug 276377.

Changed in fretsonfire:
status: Fix Released → Triaged
Revision history for this message
xteejx (xteejx) wrote :

Still a recurring problem, see my own bug 329219, cannot even open the program without it crashing, dump reports available at the bug report. Thank you.

Revision history for this message
Per Kongstad (p-kongstad) wrote :

We experience the same issue. The program is crashing immediately.

Revision history for this message
Karol Hevessy (khevessy) wrote :

same error but using restricted nvidia modules

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. I am unable to reproduce this in Lucid, therefore it may be fixed, so it would help us greatly if you could test with it so we can work on getting it fixed. Thanks again and we appreciate your help.

Changed in fretsonfire (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
xteejx (xteejx) wrote :

Works perfectly fine in Maverick. Marked Fix Released.

Changed in fretsonfire (Ubuntu):
status: Incomplete → Fix Released
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.