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 sinc
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):
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
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 t
*** 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 a
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, w
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 p
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
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 bee
@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. pur
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#p123101
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 g
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 not
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 h
14 matches
Mail list logo
