Bug 13900 - DOSbox does not load for Mageia5
Summary: DOSbox does not load for Mageia5
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Damien Lallement
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-12 08:33 CEST by Lewis Smith
Modified: 2015-05-20 08:23 CEST (History)
1 user (show)

See Also:
Source RPM: dosbox-0.74-9.mga5
CVE:
Status comment:

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

Description Lewis Smith 2014-08-12 08:33:32 CEST 
Description of problem:

The DOSbox window appears briefly, then disappears.
$ dosbox
DOSBox version 0.74
Copyright 2002-2010 DOSBox Team, published under GNU GPL.
---
CONFIG:Loading primary settings from config file /home/lewis/.dosbox/dosbox-0.74.conf
Exit to error: MSG:Can't load messages: /usr/share/dosbox/i18n/default

It works OK under Mageia 4.

Version-Release number of selected component (if applicable):
dosbox-0.74-9.mga5

How reproducible:
Always. I do not think the desktop in use effects the matter.

Steps to Reproduce:
1. Launch DOSbox from a menu or command line.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2014-08-13 14:44:11 CEST 
Possibly broken by:
r611406 | dams | 2014-04-02 16:26:58 -0400 (Wed, 02 Apr 2014) | 1 line

fix i18n support (mga#12599)
------------------------------------------------------------------------
r590091 | dams | 2014-02-12 22:16:01 -0500 (Wed, 12 Feb 2014) | 3 lines

- add a script to add i18n support to dosbox as requested on mga#12599
- add i18n files as Source1

Assignee: bugsquad => mageia

Comment 2 Samuel Verschelde 2015-05-19 20:27:57 CEST 
I think it was fixed by AlexL

Status: NEW => RESOLVED
CC: (none) => loginov_alex
Resolution: (none) => FIXED

Comment 3 Lewis Smith 2015-05-20 08:23:06 CEST 
I think that I have successfully tried DOSbox in more recent releases, so confirm it was fixed.
Note You need to log in before you can comment on or make changes to this bug.