Closing this bug as the problem seems to be fixed for the original
reporter.
** Changed in: fs-uae (Ubuntu)
Status: New => Fix Released
** Changed in: fs-uae (Ubuntu)
Assignee: (unassigned) => John Paul Adrian Glaubitz (glaubitz)
--
You received this bug notification because you are
fs-uae-launcher 2.6.2 as of Ubuntu 16.04 works fine. So I guess it was
already fixed before _OR_ the error depends on the environment (Python
version or locale settings) so it is fixed by 16.04 environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi Paul!
I just uploaded fs-uae 2.8.0 to Debian unstable (the original source of
the package you are using). Once Ubuntu has imported the latest version
of my package from Debian, you can test whether this issue has been
mitigated.
Adrian
--
You received this bug notification because you are a
I now deleted the old configs, but I can't create new configs using files (hard
disk directory trees etc.) from non-ascii too.
The new config seems to trigger the same bug, or isn't even saved in the first
place.
If I move all files (HD dirs) to another location sporting ascii-only
pathes, it w
This worked on Ubuntu 12.04, but fails on 14.04. The configuration
files originated from the 12.04 version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525715
Title:
Regression: fs-uae-launcher
