steve wrote:I understand perfectly well that there is an issue. Please tell me what I can do about it.
I do not use the Chrome web browser, but from what I have read it had a similar issue wanting libudev.so.0 when the system instead used libudev.so.1. I think the fix was Chrome updated its installer to look for libudev.so.0 and, if it didn't find it, it created the libudev.so.0 link file to libudev.so.1.3.5 but it created the link within its own Chrome directory for safety instead of putting it in the Linux /lib folder. Could Cumulus MX do something like that where when it is first ran, it verifies libudev.so.0 exists and, if it doesn't, it creates a libudev.so.0 link within the Cumulus MX folder and works?
http://askubuntu.com/questions/369310/h ... tart-again
At least for Chrome versions form 28 to 37, the Chrome binary can use whichever of libudev.so.0 or libudev.so.1 is present on the system. With the fix to Chromium/Chrome Issue 226002 (which went into the unstable channel in April 2013), the installer determines which one to use. The binary references libudev.so.0; the installer creates a symbolic link from /opt/google/chrome/libudev.so.0 to the libudev.so.1 on the system if libudev.so.0 is not found.
Note that it would be a bad idea to create one in /usr/lib. Major version numbers in libraries change when the newer version is incompatible. Creating this symbolic link works well for Chrome because it only uses features that are compatible between version 0 and version 1. Other applications might crash or produce corrupt data if you force them to run with the wrong version.
The method used by the Chrome package works well under most circumstances, but it's still a dirty hack, and it has a limitation. If the libudev0 package is uninstalled after Chrome is installed, which is likely to happen when you upgrade Ubuntu, then Chrome will still be set up to use libudev.so.0 but the file won't be available anymore. To fix this, cause the installation script to run again, and this time detect that libudev.so.0 is not available so it should create the symbolic link to use libudev.so.1 instead. You can re-run the installation script by running dpkg-reconfigure google-chrome-stable as root.