Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10316 - Xmoto need alot of CPU for Start and Quit

Attached to Project: Arch Linux
Opened by mike (manhunt) - Tuesday, 29 April 2008, 18:01 GMT
Last edited by Travis Willard (Cerebral) - Thursday, 01 May 2008, 17:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Travis Willard (Cerebral)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The new version of Xmoto 0.4.2 freeze and need about 1 min 100% of the Cpu in the menu when it normally checks Internet Highscores and new Levels, but it also happens when I disable this functions. The same thing happens when I want to Quit Xmoto but only for 20sec.

I have tried to delete my .xmoto level, now the same thing happens but only for 20sec maybe one reason is the tinier number of levels (1400lvl to ~150levl)

Additional info:
* package version(s)
xmoto-0.4.2-1-i686.pkg.tar.gz

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Travis Willard (Cerebral)
Thursday, 01 May 2008, 17:47 GMT
Reason for closing:  Won't fix
Additional comments about closing:  I don't fix upstream software, sry.
Comment by Aaron Griffin (phrakture) - Thursday, 01 May 2008, 17:29 GMT
Assigning to Travis, but I imagine he will close this - please file upstream bugs with the upstream developers
Comment by Travis Willard (Cerebral) - Thursday, 01 May 2008, 17:47 GMT
I usually give xmoto a run before I upload it, and never noticed anything like this. Again, unless we've got some problem with the way we've packaged this (which we shouldn't - I've packaged every older version the same way), it's an upstream bug.

Loading...