| source, amd64,
arm64, armhf, i386, powerpc, ppc64el, s390x
pidgin | 1:2.10.12-0ubuntu6 | yakkety/universe | source, amd64,
arm64, armhf, i386, powerpc, ppc64el, s390x
Respectfully,
Ramon Grullon
** Changed in: pidgin (Ubuntu)
Status: Triaged => Fix Released
--
You recei
Tested the patch package (pre-SRU) on trusty and it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709670
Title:
logrotate never recovers if the statefile is corrupted
To
Public bug reported:
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the
statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to
corrupt the file
- Re-run "/etc/cron.daily/logrotate" and you
Thank you for reporting this bug to Ubuntu. Lucid reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I've tried recreating this bug with your release and was unable to,
given the information you've provided. Please upgrade to
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578213
Title:
[swift][ceph][radosgw] Can not create container with the same name
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718509
Title:
python paste dumping raw input
To manage notifications about this bug go to:
Currently experiencing this issue at customer site where there is a permission
issue as nagios user can't access this directory, this particular mount
point/directory is owned by root and the permission set on this is 700.
ubuntu@XXnagios-1:/snap/core/7270$ /usr/lib/nagios/plugins/check_disk
Currently experiencing this issue at customer site where there is a
permission issue as nagios user can't access this directory, this
particular mount point/directory is owned by root and the permission set
on this is 700.
The -X tracefs is not working. Would a new check be needed for tracefs
The reason why this alert pops out is related to running sosreport on this
node. Nagios can not access it - which is good as this directory is only
accessible by root:
# ll /sys/kernel/debug/ | grep trac
drwx-- 8 root root 0 Jul 9 09:06 tracing/
To validate/replicate this behaviour, please
Public bug reported:
Cause: Pacemaker implicitly ordered all stops needed on a Pacemaker
Remote node before the stop of the node's Pacemaker Remote connection,
including stops that were implied by fencing of the node. Also,
Pacemaker scheduled actions on Pacemaker Remote nodes with a failed
14 matches
Mail list logo
