This shows you the differences between two versions of the page.
support:known-issues [2010/01/08 08:59] adam added lib64 issue |
support:known-issues [2010/01/08 08:59] (current) adam |
||
---|---|---|---|
Line 69: | Line 69: | ||
Note that in all cases, the correct emblems should appear if you manually refresh the Nautilus window (eg. by hitting F5). | Note that in all cases, the correct emblems should appear if you manually refresh the Nautilus window (eg. by hitting F5). | ||
- | === I'm running a 64bit distribution and RabbitVCS doesn't work === | + | == RabbitVCS won't run in some 64 bit environments == |
Some distributions, such as 64 bit Fedora, put 64 bit libraries in the /usr/lib64 directory, whereas nautilus-python (the program that lets us extend nautilus) assumes all libraries are in the /usr/lib directory. This is a [[https://bugzilla.redhat.com/show_bug.cgi?id=474428|nautilus-python bug]]. The current workaround is to create a symlink: **ln -s /usr/lib64/libpython2.6.so /usr/lib/libpython2.6.so** | Some distributions, such as 64 bit Fedora, put 64 bit libraries in the /usr/lib64 directory, whereas nautilus-python (the program that lets us extend nautilus) assumes all libraries are in the /usr/lib directory. This is a [[https://bugzilla.redhat.com/show_bug.cgi?id=474428|nautilus-python bug]]. The current workaround is to create a symlink: **ln -s /usr/lib64/libpython2.6.so /usr/lib/libpython2.6.so** |