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#48641 - [assaultcube] Error in `ac_client': corrupted double-linked list: 0x000000000985a3e0
Attached to Project:
Community Packages
Opened by Erwan Josset (AnEuzvil) - Sunday, 20 March 2016, 11:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 April 2016, 20:52 GMT
Opened by Erwan Josset (AnEuzvil) - Sunday, 20 March 2016, 11:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 April 2016, 20:52 GMT
|
DetailsDescription: The latest update ( 4:46 UTC 2015-12-10 ) causes an application crash on the map "ac_cavern" and still other cards sometimes . Tested on several machines.
Additional info: * package version(s) assaultcube 1.2.0.2-2 * config and/or log files etc. OpenAL Error (A004): invalid operation, line 367 *** Error in `ac_client': corrupted double-linked list: 0x000000000985a3e0 *** Steps to reproduce: Start the game in a shell and choose "ac_cavern" 
assaultcube crash
(24.8 KiB)
|
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Thursday, 14 April 2016, 20:52 GMT
Reason for closing: Won't fix
Additional comments about closing: Reporter isn't terribly responsive and also I really don't see how this is a packaging problem. Segfaults are very likely upstream's thing to fix.
Thursday, 14 April 2016, 20:52 GMT
Reason for closing: Won't fix
Additional comments about closing: Reporter isn't terribly responsive and also I really don't see how this is a packaging problem. Segfaults are very likely upstream's thing to fix.
Comment by Sven-Hendrik Haase (Svenstaro) -
Monday, 04 April 2016, 12:34 GMT
How is this a packaging problem? Is there anything for us to do to fix this?
Comment by Erwan Josset (AnEuzvil) -
Saturday, 09 April 2016, 07:54 GMT
I downgraded to 1.2.0.2-1 version that works very well and the frozen update.
Comment by Sven-Hendrik Haase (Svenstaro) -
Saturday, 09 April 2016, 23:37 GMT
I still don't see how this is a packaging problem.