I am not sure if this is relevent to anyone here, but the situation seemed similar in fashion, so I thought I'l just mention it. Here is the thraed I started to ask about it, and there is a link to the flyspray that was quickly closed as an upstream problem (rightly so).
]]>All the best,
-HG
]]>To be honest I'd consider this a bug in shotwell that should be fixed upstream, seems very odd that you can make the app but not run it until it's make install'd and executed from the installed location.
Thinking on more arch terms (as I understand them); This bug only occurs if you modified /etc/profile. Archlinux cannot start notifying users of breakages that may occur from all kinds of various configurations. I'm not saying that we should never notify users of potential breakages, but there should be limits and in my opinion this falls outside those limits.
]]>What happened in my case is that I moved from Debian to Arch, bringing along a legacy path.
I still think that it is worth warning people about the consequences of a non-standard PATH,
since the problems it can cause are very subtle and hard to diagnose -- witness the shotwell
case.
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/core_perl
A solution is to remove /bin, /sbin, and /usr/sbin from one's legacy PATH in .profile/.bashrc, etc.
Perhaps users should be warned about this in the upgrade instructions on the homepage.
Thanks to Sid Karunaratne (sakaru) for isolating this problem.
]]>