GNOME Bugzilla – Bug 760466
Shotwell will not start when symlinked to root filesystem
Last modified: 2016-04-23 20:12:09 UTC
I'm trying to make a shotwell extension (package) for tinycorelinux. Basically any tinycorelinux extension is a loop mounted squashfs package symlinked to the root filesystem - i.e. all installed files are under /tmp/tcloop/shotwell/usr/local symlinked to /usr/local When I try to start shotwell, it complains that it cannot find tag_sidebar_context.ui at /tmp/tcloop/shotwell/usr/bin. If I copy the actual shotwell binary to /usr/local/bin then things work as expected, even though all the other files installed by shotwell are still symlinked to the filesystem. Shotwell is about the only app (out of hundreds) that behaves like this - is there a way to make things work without copying it to the file system (which defeats the purpose of squashfs)?
Just to clarify: $ ls -l `which shotwell` lrwxrwxrwx 1 root root 43 Jan 11 18:49 /usr/local/bin/shotwell -> /tmp/tcloop/shotwell/usr/local/bin/shotwell $ shotwell ... Error loading UI file /tmp/tcloop/shotwell/usr/local/bin/ui/tag_sidebar_context.ui: Failed to open file '/tmp/tcloop/shotwell/usr/local/bin/ui/tag_sidebar_context.ui': No such file or directory $ sudo cp /tmp/tcloop/shotwell/usr/local/bin/shotwell /usr/local/bin $ ls -l `which shotwell` -rwxr-xr-x 1 root root 7093056 Jan 11 18:51 /usr/local/bin/shotwell $ shotwell ... [works as advertised]
Weird. I'll have a look
*** This bug has been marked as a duplicate of bug 747374 ***