Bug 376371 – xmoro doesn't work well when run from menu

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 376371 - xmoro doesn't work well when run from menu

Summary:	xmoro doesn't work well when run from menu

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	xmoto (Show other bugs)
Sub Component:
Version:	8
Hardware:	x86_64 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Gwyn Ciesla
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-11-11 14:29 EST by Rafał Polak
Modified:	2007-11-30 17:12 EST (History)
CC List:	0 users

See Also:
Fixed In Version:	xmoto-0.3.4-1.fc8
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-11-11 15:56:34 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Rafał Polak 2007-11-11 14:29:52 EST

Description of problem:
Xmoto when run from gnome-menu doesn't have sound and hangs when I want to quit.
But when run from console it works perfect, sound is present and it doesn't hang
on quit (it also doesn't show any errors in console).

Version-Release number of selected component (if applicable):
xmoto-0.3.3-2.fc8

How reproducible:
always

Steps to Reproduce:
1.run xmoto from menu
2.press quit/exit button
3.
  
Actual results:
there is no sound and game hangs on quit

Expected results:
there is sound and xmoto doesn't hang on quit

Additional info:
works well when run from console with simple command "xmoto"

Comment 1 Rafał Polak 2007-11-11 15:56:34 EST

All problems have been solved by today's update to version xmoto-0.3.4-1.fc8.

Note You need to log in before you can comment on or make changes to this bug.