SUMMARY
  $ skrooge myfile.skg
doesn't open the file, and thereafter often the skrooge process doesn't go away when I quit it.

STEPS TO REPRODUCE
1. In a shell, navigate to, or near, the directory with your .skg file
2. Enter skrooge myfile.skg, or skrooge ./myfile.skg, or skrooge path/to/myfile.skg
3. Then quit Skrooge.

OBSERVED RESULT
Skrooge shows red [ERR-5]: Failed to open './myfile.skg', and this is the only output in its History pane.

If I export SKGTRACE=5, the console output includes
##    <virtual SKGError SKGDocument::load(const QString&, const QString&, bool, bool) RC=[ERR-4]: Impossible to copy '' to 'file:///tmp/skrooge.AYeHxj'       

this is the only error in the console output, it doesn't have the same ERR-5.
Indeed there is a 0-length /tmp/skrooge.AYeHxj file, that isn't cleaned up.


EXPECTED RESULT
Skrooge should be able to use a relative path. If after the error I do File > Open, the file open dialog shows the contents of the directory where I started Skrooge, so it knows the current working directory.

The workaround is to specify the absolute path on the command line, e.g.
  $skrooge `pwd`/myfile.skg

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora 29 KDE spin
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
After I quit Skrooge and its window goes away, the process is often still running; `ps` reports state SNLl and strace reports it's polling fd 5; /proc/<SKROOGE_PID>/fd/5 is 'anon_inode:[eventfd]'. And then when I start skrooge again from the command line, it crashes. I will file that separate bug.