Dear Maintainer,

fs-uae-laiuncher instantly quits with:

   Exception: could not find case for path /root/FS-UAE

/root being the corretc home directory. I tried all remedies in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750355,
i.e. I deleted ~/FS-UAE (which was created by fs-uae), I don't have the user-dirs.dirs or related files in ~/.config
and I deleted ~/.config/fs-uae*, all to no avail.

strace'ing fs-uae-launcher gives:

   stat("/root", {st_mode=S_IFDIR|0700, st_size=24576, ...}) = 0
   stat("/root/FS-UAE", {st_mode=S_IFDIR|0700, st_size=6, ...}) = 0
   stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
   openat(AT_FDCWD, "/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
   stat("//ROOT", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
   openat(AT_FDCWD, "//ROOT", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3

and indeed, having a completely unrelated /ROOT symlink caused the
problem. Apparently, fs-uae-launcher has some very broken case test (/ROOT
and /root do not point to the same directory). Since debian doesn't
support case-insenstive installations (also not for home dirs), I would
suggest simply removing this bogus test.

Why are you running fs-uae as root? You're not supposed to do that!

Otherwise, this bug should rather reported upstream than here, but
again, I highly discourage running fs-uae as root.

Adrian

I don't see what this question could possibly have to do with the bug I
reported, unless the bug only manifests itself as root.

And why would that be?

Feel free to report it upstream, but this is the rtight place to report
(and document) bugs in debian, as this is where debian users will likely
look at until this is fixed.