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!
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!
FS#19875 - [assaultcube] doesn't save screenshots and configs
Attached to Project:
Community Packages
Opened by Julian Rother (sda) - Sunday, 20 June 2010, 20:39 GMT
Last edited by Thomas Dziedzic (tomd123) - Friday, 02 July 2010, 20:09 GMT
Opened by Julian Rother (sda) - Sunday, 20 June 2010, 20:39 GMT
Last edited by Thomas Dziedzic (tomd123) - Friday, 02 July 2010, 20:09 GMT
|
DetailsDescription:
Assault Cube does not load any configs at startup and don't save screenshots. I'm not sure, but I think thats because the start script (/usr/bin/assaultcube) cd's to /usr/share/assaultcube. If I try to create a screenshot, it wants to save the pic in "screenshots/%s_%s_%s.bmp" (src/main.cpp, l.153) which is /usr/share/assaultcube/screenshots/... . Thats read-only and so no screenshot is created. Maybe change it to ~/.assaultcube_v1.0/screenshots/... . The config issue is same, it loads the script "config/saved.cfg" (src/main.cpp, l.635) thats /usr/share/assaultcube/config/saved.cfg and should be ~/.assaultcube_v1.0/config/saved.cfg. Steps to reproduce: Just start the game, set the nick and restart it. |
This task depends upon
Closed by Thomas Dziedzic (tomd123)
Friday, 02 July 2010, 20:09 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in pkgrel 2
Friday, 02 July 2010, 20:09 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in pkgrel 2
I checked their bug tracker, and people who had this same exact issue were told to change the permissions of their folder.
I filed a bug upstream which proposes writing to a user's home folder.
https://sourceforge.net/tracker/?func=detail&aid=3023807&group_id=123597&atid=697089
In the mean time, you could just change the permissions to make it work for now.
Patches are welcome!