[Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
I understand. Saying "the default is true" is a bit puzzling, but after reading https://github.com/mvo5/unattended-upgrades/blob/master /unattended-upgrade#L1957 , the conditional makes sense since the default [object] is defined as "True". It also makes sense how this works for proposed-16.04 since that line isn't even mentioned in the config but "True" is pushed in the script anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
Balint, I'm confused on your statement in the other dup bug report (https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1357093/comments/129 ) that this is fixed in 18.04, but looking at line 60 in the "50unattended-upgrades.Ubuntu" file in the current package (1.1ubuntu1.18.04.7): //Unattended-Upgrade::Remove-Unused-Kernel-Packages "false"; ...it appears to me that 2 modifications are needed before any kernels are auto-removed. I saw your Nov 9th commit to switch it to "true", but doesn't the line still needs to be commented out in order to activate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
I'm seeing this on Antergos recently. Have you been using gksu recently and otherwise-strange terminal errors started popping up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297437] Re: warning "Application already exists, re-requesting properties"
Looks like this bug needs to be re-opened because I'm getting the same behavior on Lubuntu 16.04 LTS. I noticed under "autostart applications" in the "default LXDE applications" settings, the "application indicator" was unselected, so I selected it -- the warnings went away, but the indicators in the system tray completely vanished (including network/wifi options)...even after attempting to manually add/remove them from the panel options. Unselected it again, rebooted, indicators are back but also the warning as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297437 Title: warning "Application already exists, re-requesting properties" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1297437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183692] Re: Not enough disk space for kernel security update on /boot
*** This bug is a duplicate of bug 1357093 *** https://bugs.launchpad.net/bugs/1357093 Apparently, according to this page: https://help.ubuntu.com/community/RemoveOldKernels -- you're ultimately responsible for keeping /boot clean because there's no "automatic" mechanism by which old kernels are purged. I've found in my Lubuntu 16.04 installation that the easiest way of doing this is simply "sudo apt autoremove" but in other distros like LM, I would simulate a run first by doing a "sudo apt-get -s autoremove" to ensure nothing odd will get removed (such as VLC if xplayer is removed as VLC will act as an orphan dependency in that situation.) Many "unneeded dependency" packages can get marked as "auto removable" -- not just old kernels. Btw, that Ubuntu article mentions autoremove not "purging" the old kernels...in my own testing on Lubuntu 16.04, the old kernels were indeed marked as "auto removable"...I simply did "sudo apt autoremove" and that freed up /boot to 25% used (a "freshly-normal" size with LVM), so I'm assuming that was an error (or someone else can correct me here.) The "unattended-upgrades" package was NOT installed by default...that's apparently another error in the article, as it says, "The unattended- upgrades package, included with the default install of all Ubuntu flavors..." If you're on LM, then do the byobu -> "purge old kernels" method described here: https://forums.linuxmint.com/viewtopic.php?p=1242953#p1242953 -- for whatever reason, the devs there don't mark old kernels as "auto removable" so you need to jump these extra hoops on Mint. Personally, I think a clear warning message should appear in the Ubiquity installer when choosing to select LVM encryption about how /boot needs to be *manually* cleaned after 3-4 kernel installs. That shouldn't be too hard to do right? It seems like there's a new kernel every 2 weeks these days -- which only compounds the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183692 Title: Not enough disk space for kernel security update on /boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1183692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec
Allowing "obsolete" codecs to run is an absolutely terrible idea. For those of you on 14.04, I'd recommend updating libav-tools by PPA following this answer: http://askubuntu.com/a/851192 That's your best bet so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Does anyone have this problem in Linux Mint 18? "Unattended-Upgrade ::Remove-New-Unused-Dependencies" also does not exist for me but the package was last updated a month ago, which leads me to believe the configuration file "50unattended-upgrades" wasn't "replaced" with the new version. Also, the package has other issues including not fetching from the correct repos as it's a stock Ubuntu config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183692] Re: Not enough disk space for kernel security update on /boot
Actually I think this is the parent bug for anyone watching: https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1357093 LM18 has a really poor implementation of "unattended-upgrades" and isn't properly configured by default and (as a part of the package) isn't running a pseudo-apt-autoremove command built into the latest version. If any of you are reading this and are on 16.04, is "unattended- upgrades" installed by default? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183692 Title: Not enough disk space for kernel security update on /boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1183692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183692] Re: Not enough disk space for kernel security update on /boot
My parents got this error message on their LM18 box. They are not technical people; that's why they have Mint installed. When I heard about this, my jaw literally dropped. Can someone tell me what the point is to store old and "insecure" kernels? Considering the frequency with which Ubuntu has been pushing out security kernels this year, you would think maybe the last one (or two maximum) is kept in case of a corrupt condition -- not all of them -- unnecessarily clogging their /boot partition. This needs to be worked on. Immediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183692 Title: Not enough disk space for kernel security update on /boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1183692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
@cpollock, I don't know your situation specifically so I would be speculating at best. But, if I were in your position I might do the following (but only do these steps at your own risk and have backups of your data elsewhere): 1. delete any and all listed printers in your printer manager. 2. purge the foo2zjs drivers (I'm not familiar with the "correct" way of doing this so ask someone else.) 3. ensure hplip is fully-purged from your system by doing something like a "sudo apt purge hplip hplip-data" 4. now, install hplip and use hp's own drivers as explained in #22. Something curious from your log: hpmud is a component of hplip so perhaps it was installed at one time and wasn't properly purged before you installed the foo2zjs drivers and now colord is complaining that it can't see your 1020's color profile because foo2zjs isn't allowing it (pure speculation again.) 5. If those steps don't solve it, then perhaps purging and re-installing cups and then re-doing the steps over again might. Good luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Btw, for those of you with the cups scheduler messages as well and still want to share with samba shares, you can disable just printer sharing and that will also effectively get rid of these messages as well. The guide to do that is here: https://forums.linuxmint.com/viewtopic.php?p=1231018#p1231018 Be sure to reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Btw @cpollock, I noticed you have a 1020 printer. HP uses a convoluted method to ensure you accept their license agreement to install their proprietary driver for this particular printer. If you haven't already done so by first installing the hplip gui and then manually running the hp setup, then go ahead and do a "sudo apt-get install hplip-gui", turn on the printer, then "delete" the printer listed in your list of installed printers, then do a "hp-setup", accept the license agreement, follow the instructions to complete installation, reboot, and now you're free to uninstall "hplip-gui" if you want. (Just don't also uninstall "hplip".) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
I was referring to the cups scheduler. You might have issues with applications (or system applications as in the case with samba) trying to perpetually connect to your devices' embedded colour profiles and fails spectacularly when said profile no longer is accessible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Regarding: "Aug 8 06:38:33 tau systemd[1]: Started CUPS Scheduler. Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12325]: No such device or address" This bug is successfully resolved by removing "samba" and "samba-common" in synaptic. Apparently colord has severe issues with printer sharing when the device is not longer available (possibly by default gufw rules.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
