Bug 1251680 - gpsbabel fails on non-ascii file names
gpsbabel fails on non-ascii file names
Product: Fedora
Classification: Fedora
Component: gpsbabel (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ralf Corsepius
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-08 12:30 EDT by Göran Uddeborg
Modified: 2016-07-19 13:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 13:25:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Göran Uddeborg 2015-08-08 12:30:49 EDT
Description of problem:
Gpsbabel can not open files containing non-ascii letters.

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

How reproducible:
Every time.

Steps to Reproduce:
1. echo '<loc></loc>' > göran.loc
2. gpsbabel -i geo -f göran.loc -o gpx -F göran.gpx

Actual results:
An error message:
Cannot open 'göran.loc' for read.  Error was 'No such file or directory'.

Expected results:
A file "göran.gpx", empty of waypoints.

Additional info:
Strace:ing the process reveals that it tries to open "gran.loc", with the "ö" removed.

This has been discussed in the thread here:  https://sourceforge.net/p/gpsbabel/mailman/gpsbabel-misc/thread/CAGusYNtHsjyGu09aXd2HRybAxQbxYnXRG34tdKXTzHoaVexUBQ%40mail.gmail.com/#msg33587737

If I understand the discussion correctly, it would work if gpsbabel were compiled using Qt5 rather than Qt4.  Changing the build requirements from qt-devel to the appropriate qt5-*-devel package(s) might be enough to avoid this problem.
Comment 1 Fedora End Of Life 2016-07-19 13:25:28 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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