[Bug 1477455] Re: Incorrect instructions leave automatic updates blocked when /boot is full
Brian, Just wanted to note the average user isn't going to understand that message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477455 Title: Incorrect instructions leave automatic updates blocked when /boot is full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1477455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477455] Re: Incorrect instructions leave automatic updates blocked when /boot is full
Hello. I submitted this bug in 2015. See bug #1460396. In that report I included a short patch for update-manager which would allow checking for enough space for a new kernel, but it got little attention. Although @Alberto mentioned patching update-manager would be over- engineering, it's better to at least add a check, than to do nothing.. Since 2015.. My solution makes sure there is enough room for the current kernel size + 10MB headroom in case of a large increase. It does no harm to make a simple check prior to an upgrade and prompt the user that they may not have enough room for the upgrade, and to go to a URL with instructions on how to run an apt autoremove, or to use synaptic to remove specific old kernels, etc. No harm. It's better to give a recommendation instead of letting users who are just that, users, fend for themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477455 Title: Incorrect instructions leave automatic updates blocked when /boot is full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1477455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791770] Re: empty vpn
** Summary changed: - empty vpn + empty vpn ** Summary changed: - empty vpn + Empty VPN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791770 Title: Empty VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/791770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573401] [NEW] package qml-module-ubuntu-performancemetrics-gles failed to install/upgrade
Public bug reported: Ran into this issue after do-release-upgrade from 15.10 to 16.04 failed to successfully upgrade all my packages. do-release-upgrade worked fine on my desktop, but failed on laptop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: qml-module-ubuntu-performancemetrics-gles 1.3.1918+16.04.20160404-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 21:35:22 2016 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/PerformanceMetrics/BarGraph.qml', which is also in package qtdeclarative5-ubuntu-ui-toolkit-plugin:amd64 1.3.1627+15.10.20150908-0ubuntu1 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: ubuntu-ui-toolkit-gles Title: package qml-module-ubuntu-performancemetrics-gles 1.3.1918+16.04.20160404-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/PerformanceMetrics/BarGraph.qml', which is also in package qtdeclarative5-ubuntu-ui-toolkit-plugin:amd64 1.3.1627+15.10.20150908-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-ui-toolkit-gles (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573401 Title: package qml-module-ubuntu-performancemetrics-gles failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit-gles/+bug/1573401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491685] Re: Xen/Xorg blank screen [vivid]
Hello. Just installed Xen again, this time v 4.5, and no graphical session is possible still. I am working on finding out a configuration that works, and will make an update if a solution is found or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491685 Title: Xen/Xorg blank screen [vivid] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1491685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543888] [NEW] LightDM crashes/hangs during resume from suspend
Public bug reported: Description:Ubuntu 15.10 Release:15.10 lightdm: Installed: 1.16.7-0ubuntu1 Candidate: 1.16.7-0ubuntu1 Version table: *** 1.16.7-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.16.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages Expected: To be able to resume from suspend and be able to reliably use my desktop. What happened: Sometimes the UI is completely nonresponsive to keystrokes or mouse input after opening the lid of the computer. I am forced to cut the power. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 9 18:20:50 2016 InstallationDate: Installed on 2014-11-28 (438 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2016-01-14 (26 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543888 Title: LightDM crashes/hangs during resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1543888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491685] [NEW] Xen/Xorg blank screen [vivid]
Public bug reported: System using Xen kernel boots up all the way until after the startup log says "Starting LightDM [OK]." Then the screen goes black and is unresponsive. Using the normal kernel 3.19 works fine. Using proprietary Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 2 19:52:41 2015 DistUpgraded: 2015-09-01 20:33:24,490 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0898] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0898] InstallationDate: Installed on 2015-09-01 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MSI MS-7673 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-09-02 (0 days ago) dmi.bios.date: 08/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.19 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P67A-G45 (MS-7673) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.19:bd08/01/2012:svnMSI:pnMS-7673:pvr2.0:rvnMSI:rnP67A-G45(MS-7673):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7673 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Sep 2 19:36:39 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491685 Title: Xen/Xorg blank screen [vivid] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1491685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439769] Re: various linux packages being marked as manually installed, still prevents 'apt-get autoremove' from doing the right thing for kernels
The reasons to why old kernels are not intentionally being marked for autoremoval (as of 2008-11-04) is because it was considered too dangerous, and apt has an exception to not tag linux-image-* packages for autoremoval because _we_ had no idea which kernels actually worked for a system. However, I had thought that this problem had been addressed using last- good-boot for grub after runlevel 2 was reached, here: https://wiki.ubuntu.com/KernelTeam/removing-old-kernels But since the wiki hasn't been updated since '08, maybe that is not true anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439769 Title: various linux packages being marked as manually installed, still prevents 'apt-get autoremove' from doing the right thing for kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1439769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460396] Re: Old kernels filling up /boot, causing failed updates
The reasons to why old kernels are not intentionally being marked for autoremoval (as of 2008-11-04) is because it was considered too dangerous and apt has an exception to not tag linux-image-* packages for autoremoval because we had no idea which kernels actually worked for a system. However, I had thought that this problem had been addressed using last- good-boot for grub after runlevel 2 was reached, here: https://wiki.ubuntu.com/KernelTeam/removing-old-kernels But since the wiki hasn't been updated since '08, maybe that is not true anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460396 Title: Old kernels filling up /boot, causing failed updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1460396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460396] Re: Old kernels filling up /boot, causing failed updates
Not sure what format the bugtracker/devs like to use for submitted patches. Here's the diff output between original and updated utils.py uploaded earlier. ** Attachment added: "diff output between original and updated utils.py uploaded earlier" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1460396/+attachment/4407537/+files/utils_diff.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460396 Title: Old kernels filling up /boot, causing failed updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1460396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460396] [NEW] Old kernels filling up /boot, causing failed updates
Public bug reported: Description:Ubuntu 14.04.2 LTS Release:14.04 update-manager: Installed: 1:0.196.13 Candidate: 1:0.196.13 Version table: *** 1:0.196.13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.196.11 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages After running Trusty for about a year, I had easily 3GB worth of old kernels sitting in my /boot folder. For users that don't know about pruning old kernel versions, much less what kernels are, this is a problem since update-manager refuses to continue the update process when /boot doesn't have enough space. My friend who I had installed Ubuntu for was complaining about updates not working, so I took a look and this is what was happening. His /boot partition is too small to have so many ~200mb kernel images. We need a user-friendly way to inform the user that this is happening, and then suggest an automated course of action (apt-get remove oldest kernel + ensure at least one previous verified working kernel (such as purge_old_kernels in https://launchpad.net/ubuntu/+source/bikeshed)), and if it fails, a link to detailed instructions on how to remove old kernels manually. Attachment is updated ~/update-manager-0.196.13/UpdateManager/Core/utils.py that includes function ensure_enough_room_for_kernel() that only informs the user if there isn't enough space for a kernel upgrade. It has not been implemented in _main_, I figure the main package devs would want to do that themselves, be it to use for removing the oldest kernel version, or having the user pick from a list of installed kernels which to remove. Thanks. -Tyler Dinsmoor ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Patch added: "update-manger/UpdateManager/Core/utils.py added func. ensure_enough_room_for_kernel() to be used in bugfix." https://bugs.launchpad.net/bugs/1460396/+attachment/4407448/+files/utils.py ** Description changed: Description: Ubuntu 14.04.2 LTS Release: 14.04 update-manager: - Installed: 1:0.196.13 - Candidate: 1:0.196.13 - Version table: - *** 1:0.196.13 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:0.196.11 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: 1:0.196.13 + Candidate: 1:0.196.13 + Version table: + *** 1:0.196.13 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:0.196.11 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages After running Trusty for about a year, I had easily 3GB worth of old kernels sitting in my /boot folder. For users that don't know about pruning old kernel versions, much less what kernels are, this is a problem since update-manager refuses to continue the update process when /boot doesn't have enough space. My friend who I had installed Ubuntu for was complaining about updates not working, so I took a look and this is what was happening. His /boot partition is too small to have so many ~200mb kernel images. We need a user-friendly way to inform the user that this is happening, and then suggest an automated course of action (apt-get remove oldest kernel + ensure at least one previous verified working kernel (such as purge_old_kernels in https://launchpad.net/ubuntu/+source/bikeshed)), and if it fails, a link to detailed instructions on how to remove old kernels manually. Attachment is updated ~/update-manager-0.196.13/UpdateManager/Core/utils.py that includes function ensure_enough_room_for_kernel() that only informs the user if there isn't enough space for a kernel upgrade. It has not been implemented in _main_, I figure the main package devs would want to do that themselves, be it to use for removing the oldest kernel version, or having the user pick from a list of installed kernels which to remove. Thanks. - -Tyler Dinsmoor + -Tyler Dinsmoor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460396 Title: Old kernels filling up /boot, causing failed updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1460396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
