For the record : [~]$ ls -l /usr/local/lib/libimobiledevice.so.6* lrwxrwxrwx 1 root root 25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6 -> libimobiledevice.so.6.0.0 -rwxr-xr-x 1 root root 143216 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6.0.0
So, those were made 'quite some time ago'. [~]$ mkdir Backup [~]$ sudo mv /usr/local/lib/libimobiledevice.* Backup [sudo] password for davidmaxwaterman: [~]$ ls -l /usr/local/lib/libimobiledevice.so.6* ls: cannot access '/usr/local/lib/libimobiledevice.so.6*': No such file or directory [~]$ ldd -r /usr/lib/upower/upowerd | grep imobile libimobiledevice.so.6 => /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 (0x00007f45cde6e000) I wonder if it is something to do with one of the mobile development SDKs I have installed - Android or Tizen? I'm not completely sure what you mean by 'Does it work' (i've had a few problems with this upgrade so things are getting a bit blurry). However : [~]$ gnome-settings-daemon --replace ^C [~]$ That seems to run, if that is what you mean. However, that works when I move the libraries back too : [Backup]$ sudo mv * /usr/local/lib [Backup]$ ls -l /usr/local/lib/libimobiledevice* -rw-r--r-- 1 root root 2330698 Apr 12 15:32 /usr/local/lib/libimobiledevice.a -rwxr-xr-x 1 root root 1041 Apr 12 15:32 /usr/local/lib/libimobiledevice.la lrwxrwxrwx 1 root root 25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so -> libimobiledevice.so.6.0.0 lrwxrwxrwx 1 root root 25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6 -> libimobiledevice.so.6.0.0 -rwxr-xr-x 1 root root 143216 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6.0.0 [Backup]$ gnome-settings-daemon --replace ^C [Backup]$ But, as I mentioned, I still have the workaround implemented - ie before filing this bug, I did : $ sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 and that is still effective : [Backup]$ ls -l /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 lrwxrwxrwx 1 root root 45 May 4 11:03 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 -> /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 And the ldd output shows it is linked to the .so.2 version : libusbmuxd.so.2 => /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 (0x00007f3d97305000) IMO, the /usr/lib/upower/upowerd binary should be relinked against the .so.4 version (or plain .so), then it would use a version that is installed by default : [Backup]$ ls -l /usr/lib/x86_64-linux-gnu/libusbmuxd.so* lrwxrwxrwx 1 root root 19 Jan 4 23:13 /usr/lib/x86_64-linux-gnu/libusbmuxd.so -> libusbmuxd.so.4.0.0 lrwxrwxrwx 1 root root 45 May 4 11:03 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2 -> /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 lrwxrwxrwx 1 root root 19 Jan 4 23:13 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4 -> libusbmuxd.so.4.0.0 -rw-r--r-- 1 root root 31224 Jan 4 23:13 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 You can see the dates there, indicating the manually symlinked version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577760 Title: Screen Display 'Apply' fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1577760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs