[Desktop-packages] [Bug 1617866] Re: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1"
Mystery solved and apologies for the invalid bug report. There was an old gnome-power-statistics in /usr/local/bin This laptop has been updated from 12.04 to 16.04 without skipping any intermediate steps and apparently at some point I felt the need to install gnome-power-statistics manually. ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617866 Title: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1" Status in gnome-power-manager package in Ubuntu: Invalid Bug description: Using 16.04 with Unity, noticed that the battery icon does no longer give you the option to get more information with a right click. Running gnome-battery-statics from the command line gives: gnome-power-statistics: error while loading shared libraries: libupower-glib.so.1: cannot open shared object file: No such file or directory I have libupower-glib3 installed, which is supposed to provide libupower-glib.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1617866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617866] Re: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1"
Requested output is attached. ** Attachment added: "Output of ldd -r /usr/bin/gnome-power-statistics" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1617866/+attachment/4731539/+files/gnome_power_statistic.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617866 Title: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1" Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: Using 16.04 with Unity, noticed that the battery icon does no longer give you the option to get more information with a right click. Running gnome-battery-statics from the command line gives: gnome-power-statistics: error while loading shared libraries: libupower-glib.so.1: cannot open shared object file: No such file or directory I have libupower-glib3 installed, which is supposed to provide libupower-glib.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1617866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617866] Re: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1"
I found a workaround: Manually installing libupower- glib1_0.9.23-2ubuntu1_amd64.deb from 14.04 proposed fixes the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617866 Title: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1" Status in gnome-power-manager package in Ubuntu: New Bug description: Using 16.04 with Unity, noticed that the battery icon does no longer give you the option to get more information with a right click. Running gnome-battery-statics from the command line gives: gnome-power-statistics: error while loading shared libraries: libupower-glib.so.1: cannot open shared object file: No such file or directory I have libupower-glib3 installed, which is supposed to provide libupower-glib.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1617866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617866] [NEW] gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1"
Public bug reported: Using 16.04 with Unity, noticed that the battery icon does no longer give you the option to get more information with a right click. Running gnome-battery-statics from the command line gives: gnome-power-statistics: error while loading shared libraries: libupower- glib.so.1: cannot open shared object file: No such file or directory I have libupower-glib3 installed, which is supposed to provide libupower-glib.so ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617866 Title: gnome-power-statistics dies with " error while loading shared libraries: libupower-glib.so.1" Status in gnome-power-manager package in Ubuntu: New Bug description: Using 16.04 with Unity, noticed that the battery icon does no longer give you the option to get more information with a right click. Running gnome-battery-statics from the command line gives: gnome-power-statistics: error while loading shared libraries: libupower-glib.so.1: cannot open shared object file: No such file or directory I have libupower-glib3 installed, which is supposed to provide libupower-glib.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1617866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576514] Re: After upgrade to Xenial Duplicity crashes "No module named lockfile"
** Changed in: duplicity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576514 Title: After upgrade to Xenial Duplicity crashes "No module named lockfile" Status in duplicity package in Ubuntu: Invalid Bug description: After upgrade to Xenial Duplicity crashes with: Traceback (most recent call last): File "/usr/bin/duplicity", line 45, in from lockfile import LockFile as FileLock ImportError: No module named lockfile - The solution suggested here https://bugs.launchpad.net/duplicity/+bug/1284880 does not work since python-lockfile is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1576514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576514] Re: After upgrade to Xenial Duplicity crashes "No module named lockfile"
Version 0.7.06 (Under Ubuntu 16.04) My further investigation found that this is not an Ubuntu bug. This happened because my home directory has an Anaconda installation. Changing the order in the PATH statement to make use of the Ubuntu Python2 installation fixed the problem (i.e. putting /home/$USER/anaconda last). So should be marked invalid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576514 Title: After upgrade to Xenial Duplicity crashes "No module named lockfile" Status in duplicity package in Ubuntu: New Bug description: After upgrade to Xenial Duplicity crashes with: Traceback (most recent call last): File "/usr/bin/duplicity", line 45, in from lockfile import LockFile as FileLock ImportError: No module named lockfile - The solution suggested here https://bugs.launchpad.net/duplicity/+bug/1284880 does not work since python-lockfile is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1576514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576514] [NEW] After upgrade to Xenial Duplicity crashes "No module named lockfile"
Public bug reported: After upgrade to Xenial Duplicity crashes with: Traceback (most recent call last): File "/usr/bin/duplicity", line 45, in from lockfile import LockFile as FileLock ImportError: No module named lockfile - The solution suggested here https://bugs.launchpad.net/duplicity/+bug/1284880 does not work since python-lockfile is installed ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrade to Xenial Duplicity crashes with: - [code] + Traceback (most recent call last): - File "/usr/bin/duplicity", line 45, in - from lockfile import LockFile as FileLock + File "/usr/bin/duplicity", line 45, in + from lockfile import LockFile as FileLock ImportError: No module named lockfile - [/code] + - The solution suggested here https://bugs.launchpad.net/duplicity/+bug/1284880 does not work since python-lockfile is installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576514 Title: After upgrade to Xenial Duplicity crashes "No module named lockfile" Status in duplicity package in Ubuntu: New Bug description: After upgrade to Xenial Duplicity crashes with: Traceback (most recent call last): File "/usr/bin/duplicity", line 45, in from lockfile import LockFile as FileLock ImportError: No module named lockfile - The solution suggested here https://bugs.launchpad.net/duplicity/+bug/1284880 does not work since python-lockfile is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1576514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
