[Desktop-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack
Sorry about this silly question, but will this update be shipped in February? If it isn't tied to the HWE release schedule and can be released earlier, is there any way I can help test? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
This update fixes a bug that was in the last xorg update: https://www.kubuntuforums.net/showthread.php/72149-Mouse-artifact- introduced-in-7-26-update - I think the promotion of this to stable will be very helpful for kde neon. Tested on my laptop, the bug is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1696895] [NEW] bbswitch dkms builds for old kernel during kernel upgrade if currently active
Public bug reported: currently on xenial, with the hwe kernel. if bbswitch is active on the kernel, dkms builds for the old kernel, which means no bbwitch on reboot. Another dkms package had this issue, and apparently the fix is there. https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1687492 ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1696895 Title: bbswitch dkms builds for old kernel during kernel upgrade if currently active Status in bbswitch package in Ubuntu: New Bug description: currently on xenial, with the hwe kernel. if bbswitch is active on the kernel, dkms builds for the old kernel, which means no bbwitch on reboot. Another dkms package had this issue, and apparently the fix is there. https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1687492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1696895/+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 1565516] Re: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail
I am willing to be a lab rat if a dev could work with me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1565516 Title: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Fresh updated install of 16.04, installed nvidia-361 package. Upon reboot get to greeter can go no further. gpu-manager.log reports this, will attach full log - Is prime available? yes Is prime egl available? no Single card detected Selecting mesa Error: no alternative found for mesa Warning: no EGL alternative found for mesa Error: no alternative found for unblacklist Removing xorg.conf. Path: /etc/X11/xorg.conf Moved /etc/X11/xorg.conf to /etc/X11/xorg.conf.04032016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.16 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 13:39:23 2016 InstallationDate: Installed on 2016-04-03 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1565516/+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 1565516] Re: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail
I have a similar issue on my Inspiron 7559 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1565516 Title: Fails with skylake & nvidia 940m, removes xorg.conf boot up/log in fail Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Fresh updated install of 16.04, installed nvidia-361 package. Upon reboot get to greeter can go no further. gpu-manager.log reports this, will attach full log - Is prime available? yes Is prime egl available? no Single card detected Selecting mesa Error: no alternative found for mesa Warning: no EGL alternative found for mesa Error: no alternative found for unblacklist Removing xorg.conf. Path: /etc/X11/xorg.conf Moved /etc/X11/xorg.conf to /etc/X11/xorg.conf.04032016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.16 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 13:39:23 2016 InstallationDate: Installed on 2016-04-03 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1565516/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package
...but the launchpad comment tells me to mark it. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1320868 Title: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Bug description: $sudo apt-get remove nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done Package 'nvidia-current' is not installed, so not removed The following package was automatically installed and is no longer required: linux-image-generic Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up nvidia-331 (331.38-0ubuntu7) ... INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Traceback (most recent call last): File "/usr/bin/quirks-handler", line 65, in operation_status = main(options) File "/usr/bin/quirks-handler", line 44, in main quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, path=quirks_path) File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in __init__ self._system_info = self.get_system_info() File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in get_system_info return quirk_info.get_dmi_info() File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in get_dmi_info 'class', 'dmi', 'id', item)).read().strip() File "/usr/lib/python3.4/codecs.py", line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte dpkg: error processing package nvidia-331 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-331 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package
Sorry after reading SRU wiki I found out I am not supposed to do that. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1320868 Title: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Bug description: $sudo apt-get remove nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done Package 'nvidia-current' is not installed, so not removed The following package was automatically installed and is no longer required: linux-image-generic Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up nvidia-331 (331.38-0ubuntu7) ... INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Traceback (most recent call last): File "/usr/bin/quirks-handler", line 65, in operation_status = main(options) File "/usr/bin/quirks-handler", line 44, in main quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, path=quirks_path) File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in __init__ self._system_info = self.get_system_info() File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in get_system_info return quirk_info.get_dmi_info() File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in get_dmi_info 'class', 'dmi', 'id', item)).read().strip() File "/usr/lib/python3.4/codecs.py", line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte dpkg: error processing package nvidia-331 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-331 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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 1586933] Re: gpu-manager's drm output detection affects boot time
i tested 1:0.4.17.2 from proposed and the boot process was faster ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1586933 Title: gpu-manager's drm output detection affects boot time Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Bug description: SRU request: [Impact] The current drm code to probe the connected outputs is too resource intensive, and slow down the boot process. [Test Case] 1) Boot Ubuntu and run the following command, looking for gpu-manager: systemd-analize blame This will show how long gpu-manager took. Write down the number 2) Install the package from -proposed, and run systemd-analize blame. See if the number has become smaller. [Regression Potential] Low, all the changes are already included in Yakkety. _ Rather than calling drm directly, gpu-manager should simply check the outputs connector status by using the sysfs filesystem (e.g. /sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is already available. This should make gpu-manager a bit less resource intensive, especially on boot. The attached perf shows the problem in gpu-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package
I do not experience the bug with package version 1:0.4.17.2. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1320868 Title: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Bug description: $sudo apt-get remove nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done Package 'nvidia-current' is not installed, so not removed The following package was automatically installed and is no longer required: linux-image-generic Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up nvidia-331 (331.38-0ubuntu7) ... INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Traceback (most recent call last): File "/usr/bin/quirks-handler", line 65, in operation_status = main(options) File "/usr/bin/quirks-handler", line 44, in main quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, path=quirks_path) File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in __init__ self._system_info = self.get_system_info() File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in get_system_info return quirk_info.get_dmi_info() File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in get_dmi_info 'class', 'dmi', 'id', item)).read().strip() File "/usr/lib/python3.4/codecs.py", line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte dpkg: error processing package nvidia-331 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-331 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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 1626323] [NEW] after running "prime-select intel" and rebooting, nvidia modules stay loaded
Public bug reported: This is important for laptops since having the nvidia gpu on all the time drains battery. Running Ubuntu 16.04 with all updates nvidia-prime 0.8.2, nvidia drivers are at 370 from ppa:graphics-drivers ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1626323 Title: after running "prime-select intel" and rebooting, nvidia modules stay loaded Status in nvidia-prime package in Ubuntu: New Bug description: This is important for laptops since having the nvidia gpu on all the time drains battery. Running Ubuntu 16.04 with all updates nvidia-prime 0.8.2, nvidia drivers are at 370 from ppa:graphics- drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1626323/+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 1582876] Re: Unable to change user profile picture in 'user accounts'
*** This bug is a duplicate of bug 1581567 *** https://bugs.launchpad.net/bugs/1581567 I am able to change the profile picture on a fresh install. After running apt upgrade I am i able to change it. Another side effect is that changing my background doesn't change lightdm's background -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1582876 Title: Unable to change user profile picture in 'user accounts' Status in unity-control-center package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 unity-control-center: Installed: 15.04.0+16.04.20160413-0ubuntu1 Candidate: 15.04.0+16.04.20160413-0ubuntu1 Version table: *** 15.04.0+16.04.20160413-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status When trying to change a users profile picture it wont change, but if you log out and back in with a different sudo user you're able to change the picture of the other one. Not sure why this happens, but for sure this isn't intended this way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 21:39:10 2016 InstallationDate: Installed on 2016-04-18 (28 days ago) InstallationMedia: SourcePackage: unity-control-center UpgradeStatus: Upgraded to xenial on 2016-05-09 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1582876/+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
