Bug 2015328 - crawl -tiles crashes when selection question mark (manual)
Summary: crawl -tiles crashes when selection question mark (manual)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: crawl
Version: 34
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Antonio T. sagitter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-18 23:25 UTC by thecjester
Modified: 2022-02-06 15:20 UTC (History)
2 users (show)

Fixed In Version: crawl-0.27.1-2.fc34 crawl-0.27.1-2.fc35 crawl-0.28.0-1.fc36
Clone Of:
Environment:
Last Closed: 2022-02-06 15:20:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Crash report created after crash (9.90 KB, text/plain)
2021-10-18 23:25 UTC, thecjester
no flags Details

Description thecjester 2021-10-18 23:25:14 UTC
Created attachment 1834431 [details]
Crash report created after crash

Description of problem:

On any crawl-tiles game, hitting "?" to bring up the manual crashes the game.

Version-Release number of selected component (if applicable):

crawl-tiles-0.27.1-1.fc34.x86_64.rpm 

How reproducible:

Occurs each time I attempted this


Steps to Reproduce:
1. Start a new game and get to the main dungeon screen
2. Hit "?" (Question mask)


Actual results:

Game crashes with:

ASSERT(fp) in 'command.cc' at line 1137 failed. (Failed to open 'crawl_manual.txt'!)


Expected results:

Get list of game commands

Additional info:

Comment 1 Fedora Update System 2021-10-19 13:50:26 UTC
FEDORA-2021-d647993776 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d647993776

Comment 2 Fedora Update System 2021-10-19 13:50:31 UTC
FEDORA-2021-4878eddd17 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4878eddd17

Comment 3 Fedora Update System 2021-10-19 16:13:16 UTC
FEDORA-2021-4878eddd17 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4878eddd17`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4878eddd17

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2021-10-20 13:48:08 UTC
FEDORA-2021-d647993776 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d647993776`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d647993776

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-10-27 02:09:04 UTC
FEDORA-2021-4878eddd17 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2021-10-29 23:09:06 UTC
FEDORA-2021-d647993776 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Klemen Košir 2022-02-06 08:49:13 UTC
The problem persists on Fedora 35, with crawl-tiles 0.27.1-2.

After some testing, it looks like `crawl` works because the `docs` directory is under `/usr/share/crawl`, but it crashes with `crawl-tiles`.
By copying the `docs` directory under `/usr/share/crawl-tiles`, the help menus can be opened in `crawl-tiles` without crashing.

Comment 8 Fedora Update System 2022-02-06 15:16:51 UTC
FEDORA-2022-fc7bfc706f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fc7bfc706f

Comment 9 Fedora Update System 2022-02-06 15:20:32 UTC
FEDORA-2022-fc7bfc706f has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


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