On Fri, 2007-08-24 at 21:21 -0400, A. Costa wrote: > When the 'abiword' file is missing, 'Desktop/SpaceMonger.exe' starts OK. > When the 'abiword' file is present, 'Desktop/SpaceMonger.exe' fails as > per Bug#424923.
Great, I can reproduce this behaviour myself now! > The file is attached, it might be worth pointing out the garbage > characters on line #4, and line #15 looks guilty... > > % nl -b a ~/.local/share/applications/abiword-usercustom.desktop | grep > '[^1]4\|15' > 4 Name[ja]=AbiWord ������������������������ > 15 MimeType=application/x-executable; Yes, as you pointed out in the other mail, this is the japanese translation, you probably don't have the correct fonts installed. > Questions that come to mind: if 'abiword-usercustom.desktop' is what > causes it, then what caused that this unfavorable mutation? Are the > garbage characters normal? Why should 'nautilus' properties for > 'Desktop/SpaceMonger.exe' show 'wine'? The -usercustom.desktop files are created when you manually add an application to a mimetype it doesn't support. Maybe you added it by mistake sometime in the past? I have added the steps necessary to reproduce the bug in the upstream report; https://bugs.freedesktop.org/show_bug.cgi?id=6320 I will leave it to them to figure out why Nautilus didn't list abiword and why it gave a warning. Thank you for the fast replies to my questions and the detailed answers, it made it much easier to figure this one out. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part