This is Ceph Argonaut (from Folsom UCA); AIUI Ceph doesn't support/live
PG addition until Dumpling. Can you confirm? Are there any
workarounds?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261501
Public bug reported:
Shortly after starting up pg_activity dies with the following message:
FATAL: float() argument must be a string or a number
** Affects: pg-activity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
For hysterical raisins, ybin is not run on upgrade. This behaviour
creates a land mine for the administrator because it doesn't match the
behaviour of other boot loaders on Ubuntu (i.e. grub). Could we
please fix yaboot to run ybin on upgrade so a human doesn't have to
I'm also seeing this on a coworker's laptop. She has
4.2.0.11-0ubuntu0.12.04.2 installed and is running Saucy. Skype was
generating horrible noise (almost like microphone feedback) and
setting PULSE_LATENCY_MSEC=60 fixed it.
** Changed in: skype (Ubuntu)
Status: Incomplete = New
--
Steve Langasek steve.langa...@canonical.com writes:
I'm also seeing this on a coworker's laptop. She has
4.2.0.11-0ubuntu0.12.04.2 installed and is running Saucy. Skype was
generating horrible noise (almost like microphone feedback) and
setting PULSE_LATENCY_MSEC=60 fixed it.
How is skype
Public bug reported:
I woke up this morning to find multi-monitor support had broken.
However I configure the displays (e.g. mirroring), only one screen will
be on at a time. If I downgrade unity from
7.1.2+13.10.20131014.1-0ubuntu1 to 7.1.1+13.10.20131004-0ubuntu1 the
problem goes away and
I've just tried; multi-monitor works as expected with
7.1.2+13.10.20131011-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240074
Title:
multi-monitor regression
To manage notifications
But it also works now with 7.1.2+13.10.20131014.1-0ubuntu1. So it's
possible a reboot/session restart is sufficient to fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240074
Title:
Public bug reported:
Starting in Saucy, changing the value of the 'Lock screen after'
selector in the 'Brightness Lock' section of the GNOME control
centre has no effect as it's always overriden by the value for 'if
screen has been blank for' in activity-log-manager.
This is extremely confusing
I'm seeing the same thing in Saucy. This is a regression for me and
makes it impossible to take screenshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215492
Title:
Black screenshot in
Public bug reported:
We have a MAAS installation that was installed with original precise
MAAS (0.1+bzr482+dfsg-0ubuntu1) that was using the system (ISC) dhcpd.
When we upgraded it to the SRU MAAS
(1.2+bzr1373+dfsg-0ubuntu1~12.04.1), it unconditionally¹ disabled the
ISC dhcpd by shipping a
** Attachment added: Full log for relevant osd.
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1227327/+attachment/3827861/+files/ceph-osd.39.log.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Public bug reported:
After an unfortunate incident with dhcpd going away, we lost 3/6 of
our ceph cluster and had to remotely power cycle them to get them
back. Now that everything is back up, the ceph cluster has mostly
recovered but we had a couple of pg's stuck in an inconsistent state,
so I
Public bug reported:
AFAIK, the documented¹ way to set weights for an OSD is with:
ceph osd crush reweight {osd-id} {weight}
And this works... but only for as long as the ceph-osd daemon is
running. Because, with ceph 0.48.3-0ubuntu1~cloud0 from the Folsom
pocket of the Ubuntu Cloud Archive
The upstart job is shipped by the charm, not in the package.
Retargeting to the charm.
** Changed in: ceph (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Public bug reported:
We have a MAAS installation that was installed with original precise
MAAS (0.1+bzr482+dfsg-0ubuntu1) that was using the system (ISC) dhcpd.
When we upgraded it to the SRU MAAS
(1.2+bzr1373+dfsg-0ubuntu1~12.04.1), it unconditionally¹ disabled the
ISC dhcpd by shipping a
Public bug reported:
After an unfortunate incident with dhcpd going away, we lost 3/6 of
our ceph cluster and had to remotely power cycle them to get them
back. Now that everything is back up, the ceph cluster has mostly
recovered but we had a couple of pg's stuck in an inconsistent state,
so I
** Attachment added: Full log for relevant osd.
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1227327/+attachment/3827861/+files/ceph-osd.39.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
AFAIK, the documented¹ way to set weights for an OSD is with:
ceph osd crush reweight {osd-id} {weight}
And this works... but only for as long as the ceph-osd daemon is
running. Because, with ceph 0.48.3-0ubuntu1~cloud0 from the Folsom
pocket of the Ubuntu Cloud Archive
The upstart job is shipped by the charm, not in the package.
Retargeting to the charm.
** Changed in: ceph (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227370
James Page james.p...@ubuntu.com writes:
Any chance you could enable the profiler following:
http://ceph.com/docs/master/rados/troubleshooting/memory-profiling/
I have a hunch that this might actually be related to the version of
google-perftools with have in precise - but this at least
James Page james.p...@ubuntu.com writes:
Any chance you could enable the profiler following:
http://ceph.com/docs/master/rados/troubleshooting/memory-profiling/
I have a hunch that this might actually be related to the version of
google-perftools with have in precise - but this at least
Public bug reported:
ii ceph 0.48.3-0ubuntu1~cloud0
distributed storage and file system
Freshly started ceph-osd:
root 26317 1.7 0.4 612016 78224 ?Ssl 16:35 0:03
/usr/bin/ceph-osd --cluster=ceph -i 15 -f
ceph-osd after 6 months+:
root
Public bug reported:
ii ceph 0.48.3-0ubuntu1~cloud0
distributed storage and file system
Freshly started ceph-osd:
root 26317 1.7 0.4 612016 78224 ?Ssl 16:35 0:03
/usr/bin/ceph-osd --cluster=ceph -i 15 -f
ceph-osd after 6 months+:
root
Public bug reported:
We're running Ubuntu 12.04 LTS with Folsom from the Ubuntu Cloud
Archive. The swift-container package is 1.7.4-0ubuntu2.2~cloud0.
'swift-init all start' (which the juju charm hooks use) will start the
swift container sync service, but there is no upstart job for it.
This
Public bug reported:
dselect-upgrade in Ubuntu 12.04 LTS appears to have issues resolving
dependencies with multi-arch in play. Starting from a clean state:
| root@lamassu:~# apt-get update /dev/null; echo $?; apt-get dist-upgrade
/dev/null; echo $?; apt-get dselect-upgrade
| 0
| 0
| Reading
Public bug reported:
With Openstack Folsom, 'nova add-fixed-ip' doesn't appear to correctly
change the firewall rules on the compute host with the result that the
additional fixed IPs are unusable.
To reproduce, I did:
nova add-fixed-ip server uuid network uuid
nova show server uuid # --
Public bug reported:
With Openstack Folsom, 'nova add-fixed-ip' doesn't appear to correctly
change the firewall rules on the compute host with the result that the
additional fixed IPs are unusable.
To reproduce, I did:
nova add-fixed-ip server uuid network uuid
nova show server uuid # --
Public bug reported:
We recently upgraded our MAAS from 0.1+bzr482+dfsg-0ubuntu1 to
1.2+bzr1373+dfsg-0ubuntu1~12.04.1.
After doing this, we found that MAAS was trying (and thankfully
failing) to reinstall any node we rebooted. This appears be to
because the 'netboot' field which was add to the
Public bug reported:
We recently upgraded our MAAS from 0.1+bzr482+dfsg-0ubuntu1 to
1.2+bzr1373+dfsg-0ubuntu1~12.04.1.
After doing this, we found that MAAS was trying (and thankfully
failing) to reinstall any node we rebooted. This appears be to
because the 'netboot' field which was add to the
Public bug reported:
When trying to build upstart 1.9 from saucy on raring, I get the
following:
| configure.ac:11: option `serial-tests' not recognized
| autoreconf: automake failed with exit status: 1
Please consider adding a build-depends on automake = 1.12 when this
feature was added.
**
So it turns out that this is only reproducible when I'm running low
on memory. I rather optimistically run my 8Gb laptop without swap and
while trying to reproduce this again tonight I noticed that at the
point of the crash, the whole machine grinds to a halt and I got some
OOM killer spew in
This is with the standard package (i.e. no debug symbols), but FWIW,
this is some of the output when reproducing the crash under gdb:
| L 26654 2013-06-16 22:18:42 [CRT] Offset of directory Sony1, entry 0x2001 is
out of bounds: Offset = 0x0034ec76; truncating the entry
|
| L 26654 2013-06-16
Public bug reported:
While trying to export photos to a directory (as JPEG, with or without
metadata), I reproducibly get the following crash:
ERROR:/build/buildd/shotwell-0.14.1/src/Photo.vala:3323:photo_get_pixbuf_with_options:
assertion failed: (pixbuf != null)
I'm using Shotwell
Neil Wilson n...@aldur.co.uk writes:
No the IPv6 system prefers privacy addresses over standard addresses if not
explicitly told otherwise.
Server *userspace software* should tell the system explicitly what it wants
to do so that clients can connect to it.
You keep asserting this but don't
*** This bug is a duplicate of bug 1161306 ***
https://bugs.launchpad.net/bugs/1161306
Seeing the same thing here:
root 796 0.0 0.1 65792 14632 pts/18 SN+ 11:06 0:00
\_ /usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/tmp.ci/preinst install
root@ornery:~# strace -p
Still seeing this with raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060167
Title:
indicator doesn't always work properly after suspend
To manage notifications about this bug go to:
I had the same problem when upgrading from Q to R but I also had the
same crash from a running local django 'runserver' instance, so the root
cause for this may not be in python-novaclient.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I had the same problem when upgrading from Q to R but I also had the
same crash from a running local django 'runserver' instance, so the root
cause for this may not be in python-novaclient.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yeah, that's not going to happen. The debug log contains private and
sensitive information.
If a standalone test case is a hard requirement, I can probably work
something up, but it seems like an unnecessarily high bar to set for a
bug report which gives pretty explicit symptoms and log info
*sigh*, fine. Here is an example config, steps with which to
reproduce and messages output with debug turned all the way up.
| apt-get install asterisk sip-tester
|
| From the example-config.tar.gz copy into /etc/asterisk/:
|
| * asterisk.conf - set verbose and debug to 10
| *
** Attachment added: Example asterisk configs
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1130467/+attachment/3539101/+files/example-config.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
** Attachment added: /var/log/asterisk/messages
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1130467/+attachment/3539102/+files/messages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
Yeah, that's not going to happen. The debug log contains private and
sensitive information.
If a standalone test case is a hard requirement, I can probably work
something up, but it seems like an unnecessarily high bar to set for a
bug report which gives pretty explicit symptoms and log info
** Attachment added: Example asterisk configs
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1130467/+attachment/3539101/+files/example-config.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*sigh*, fine. Here is an example config, steps with which to
reproduce and messages output with debug turned all the way up.
| apt-get install asterisk sip-tester
|
| From the example-config.tar.gz copy into /etc/asterisk/:
|
| * asterisk.conf - set verbose and debug to 10
| *
** Attachment added: /var/log/asterisk/messages
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1130467/+attachment/3539102/+files/messages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
If the 'g' argument is passed to Dial(), the functionality provided by
the 'e' argument changes subtly (and, for us at least, breaks). If
'g' is passed to Dial(), when control is returned to the 'h'
extension, it returns in a different context, e.g.:
[Feb 19 19:01:46]
Public bug reported:
If the 'g' argument is passed to Dial(), the functionality provided by
the 'e' argument changes subtly (and, for us at least, breaks). If
'g' is passed to Dial(), when control is returned to the 'h'
extension, it returns in a different context, e.g.:
[Feb 19 19:01:46]
Public bug reported:
do-release-upgrade assumes that /usr/sbin/sshd exists if you are
upgrading over ssh. While that may seem intuitively true, it's not
always the case, e.g. I was upgrading a chroot on a machine via ssh.
The host/base OS had openssh-server installed; the chroot did not.
This was trying to upgrade a lucid chroot to precise, FWIW. The base OS
was also lucid, if it matters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123343
Title:
do-release-upgrade assumes
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete instance in ERROR status
To manage notifications about this bug go to:
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012551
Title:
Cannot delete instance in ERROR status
To manage notifications about this bug go to:
Public bug reported:
This is python-keystoneclient 1:0.1.3-0ubuntu1.1~cloud0 on Ubuntu 12.04.
| root@gidim:~# keystone user-delete james
| No handlers could be found for logger keystoneclient.client
| Could not find user: james (HTTP 404)
| root@gidim:~#
But it's not looking for a user; it's
Public bug reported:
It would be nice if keystone had option(s) to prompt for passwords, e.g.
when creating user. Being forced to put them in the command line can
lead to them leaking into shell history files and ps(1) output.
** Affects: python-keystoneclient (Ubuntu)
Importance:
Sorry, if it matters, I'm using keystone from python-keystoneclient
1:0.1.3-0ubuntu1.1~cloud0 on Ubuntu 12.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100116
Title:
add an option to
Public bug reported:
python-keystoneclient 1:0.1.3-0ubuntu1.1~cloud0 on Ubuntu 12.04.
The help output for keystone commands often incorrectly lists
mandatory arguments as optional, e.g.:
| root@gidim:~# keystone help user-role-add
| usage: keystone user-role-add --user-id user-id --role-id
Public bug reported:
| # TAG: visible_hostname
| # If you want to present a special hostname in error messages, etc,
| # define this. Otherwise, the return value of gethostname()
| # will be used. If you have multiple caches in a cluster and
| # get errors about
Sorry, this is squid3 3.1.19-1ubuntu3.12.04.1 on Ubuntu 12.04 LTS, FWIW.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1098641
Title:
visible_hostname defaults to hostname of first
Public bug reported:
| # TAG: visible_hostname
| # If you want to present a special hostname in error messages, etc,
| # define this. Otherwise, the return value of gethostname()
| # will be used. If you have multiple caches in a cluster and
| # get errors about
Sorry, this is squid3 3.1.19-1ubuntu3.12.04.1 on Ubuntu 12.04 LTS, FWIW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098641
Title:
visible_hostname defaults to hostname of first http_port IP,
Public bug reported:
In emacs24, gnus-summary-respool-article (B r) no longer works for me.
It prompts me for the backend to use (nnfolder), but then doesn't find
any servers for nnfolder and doesn't offer me any completions for the
server question and won't accept anything I type.
The relevant
Public bug reported:
When upgrading from 2012.1+stable~20120824-a16a0ab9-0ubuntu2.2 to
2012.1+stable~20120824-a16a0ab9-0ubuntu2.3 (lovely version numbers, by
the way), I'm getting the following spew from the postinst:
| Setting up keystone (2012.1+stable~20120824-a16a0ab9-0ubuntu2.3) ...
|
Public bug reported:
When upgrading from 2012.1+stable~20120824-a16a0ab9-0ubuntu2.2 to
2012.1+stable~20120824-a16a0ab9-0ubuntu2.3 (lovely version numbers, by
the way), I'm getting the following spew from the postinst:
| Setting up keystone (2012.1+stable~20120824-a16a0ab9-0ubuntu2.3) ...
|
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to be started:
Public bug reported:
After an unexpected host reboot, all the guests went away. I added
'--start_guests_on_host_boot=true' to /etc/nova/nova.conf and started
up nova-compute. It started some instances but then died on:
2012-12-19 11:11:47 CRITICAL nova [-] Domain not found: no domain with
Public bug reported:
When a server is shut down cleanly any running guest instances cleanly
go down, but they don't come back up automatically.
Fixing this appears to be as trivial as adding:
--start_guests_on_host_boot=true
To /etc/nova/nova.conf. Could we please consider doing that by
Public bug reported:
With vanilla Ubuntu 12.04 (including precise-proposed) we often see
instances get into a 'highlander' state. They're in an 'error' state,
like so:
RESERVATION r-n1d0t747 c519923c921a404c96ebc8210a4ec67a
juju-canonistack2, juju-canonistack2-10
INSTANCE
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to be started: No such file
Public bug reported:
After an unexpected host reboot, all the guests went away. I added
'--start_guests_on_host_boot=true' to /etc/nova/nova.conf and started
up nova-compute. It started some instances but then died on:
2012-12-19 11:11:47 CRITICAL nova [-] Domain not found: no domain with
Public bug reported:
When a server is shut down cleanly any running guest instances cleanly
go down, but they don't come back up automatically.
Fixing this appears to be as trivial as adding:
--start_guests_on_host_boot=true
To /etc/nova/nova.conf. Could we please consider doing that by
Public bug reported:
With vanilla Ubuntu 12.04 (including precise-proposed) we often see
instances get into a 'highlander' state. They're in an 'error' state,
like so:
RESERVATION r-n1d0t747 c519923c921a404c96ebc8210a4ec67a
juju-canonistack2, juju-canonistack2-10
INSTANCE
Robie Basak 1088...@bugs.launchpad.net writes:
What versions of facter and pciutils, please?
precise, so facter 1.6.5-1ubuntu1 and pciutils 1:3.1.8-2ubuntu5.
As far as I can see, this is no longer an issue in Raring.
Fair enough, we tend to focus on the LTSes.
Also, which SoC, in case
Public bug reported:
| james@ornery:~$ less /usr/share/doc/python-mode/NEWS.Debian.gz
| python-mode (1:6.0.10-1) unstable; urgency=low
|
| * The Debian package has been upgraded from python-mode.el 5.1 to 6.0, which
| introduces several API changes. Some of your customizations will need
Robie Basak 1088...@bugs.launchpad.net writes:
What versions of facter and pciutils, please?
precise, so facter 1.6.5-1ubuntu1 and pciutils 1:3.1.8-2ubuntu5.
As far as I can see, this is no longer an issue in Raring.
Fair enough, we tend to focus on the LTSes.
Also, which SoC, in case
Debian Bug report logs - #51988 texinfo: texi2dvi4a2ps cannot create
temporary directory
Wrong bug?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1088971
Title:
squid3 is not
Debian Bug report logs - #51988 texinfo: texi2dvi4a2ps cannot create
temporary directory
Wrong bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088971
Title:
squid3 is not compiled with ssl
Public bug reported:
'facter virtual' runs 'lspci' unconditionally on physical machines.
This causes warning spew on machines without PCI, e.g. arm.
| root@jenipapo:~# facter virtual
| pcilib: Cannot open /proc/bus/pci
| lspci: Cannot find any working access method.
| physical
| root@jenipapo:~#
Public bug reported:
'facter virtual' runs 'lspci' unconditionally on physical machines.
This causes warning spew on machines without PCI, e.g. arm.
| root@jenipapo:~# facter virtual
| pcilib: Cannot open /proc/bus/pci
| lspci: Cannot find any working access method.
| physical
| root@jenipapo:~#
Public bug reported:
In asterisk 1.8, calls to queues with a 'ringall' strategy will kill
the Dial() of all non-answering agents as soon as another agent
answers. This kill doesn't respect the 'g' option given to Dial(),
i.e. control is never returned to the dialplan. This appears to be a
Public bug reported:
In asterisk 1.8, calls to queues with a 'ringall' strategy will kill
the Dial() of all non-answering agents as soon as another agent
answers. This kill doesn't respect the 'g' option given to Dial(),
i.e. control is never returned to the dialplan. This appears to be a
FWIW, I worked around this by manually deleting the NSS based group
from /var/lib/dpkg/statoverride.
Adam tells me the inverted libc6/libc-bin dependency has been fixed in
raring. He's understandably queasy about doing that kind of a change
as an SRU. Other ways this could be fixed/worked
Public bug reported:
I've just had a lucid - precise upgrade explode in my face. libc-bin
was installed before libc6 and as a result, there was a period where
nss was broken, after libc-bin had been upgraded, but before libc6
had. nss being broken caused dpkg-statoverride to explode on almost
Public bug reported:
With the recent security upload of django, the self-tests will fail on
any site, if the MANAGERS variable is defined in settings.py. This is
because the admin gets mail about the SuspiciousOperation traceback
and the new test test_poisoned_http_host() only looks to see
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142
Title:
if-up.d/if-down.d scripts restart iSCSI inappropriately
To manage notifications about this bug go to:
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051892
Title:
[Quantal] Regression in TLS 1.2 workarounds
To manage notifications about this bug go to:
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage notifications about this
Jamie Strandboge ja...@ubuntu.com writes:
I can reproduce the first denial, but not the second. What website did
you visit that triggered this?
I got it before visiting a website. After bisecting through my plugins,
it appears to be lastpass which is trying to create the /run/shm/
semaphore.
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052897
Title:
'Show printers shared by other systems' greyed out after quantal
upgrade
To manage notifications about
Public bug reported:
Sep 25 20:45:33 ornery kernel: [ 66.044761] type=1400
audit(1348602333.026:81): apparmor=DENIED operation=file_lock parent=1
profile=/usr/lib/firefox/firefox{,*[^s][^h]}
name=/home/james/.local/share/unity-webapps/availableapps.db pid=3460
comm=firefox requested_mask=k
Public bug reported:
Ever since upgrading to Quantal the 'Show printers shared by other
systems' option is greyed out in System Settings - Printing. (And,
perhaps redundantly, advertised printers which I saw before the
upgrade, no longer appear.)
** Affects: cups (Ubuntu)
Importance:
** Patch added: Fix self tests when using UserProfile
https://bugs.launchpad.net/bugs/1051720/+attachment/3319352/+files/django.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051720
Title:
Public bug reported:
| $ python manage.py test
| Creating test database for alias 'default'...
|
.E
| ==
| ERROR: test_site_profile_not_available
Public bug reported:
I've just reinstalled a server for a 3rd party using Ubuntu 12.04.1
Server AMD64. I did so non-destructively, i.e. chroot'ed into what
would become /target, did 'mkdir old-machine; mv -iv * old-machine/'
and then had the partitioner re-use the partition as / without
** Attachment added: Example MOTD
https://bugs.launchpad.net/bugs/1038422/+attachment/3266582/+files/motd.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038422
Title:
IP report in motd
Public bug reported:
landscape-sysinfo should skip vlan interfaces (usually ethN.) when
reporting on the IP addresses of the system in the motd. See attached
for a sanitized but otherwise genuine example motd that shows why.
** Affects: landscape-client (Ubuntu)
Importance: Undecided
Chris Coulson chris.coul...@canonical.com writes:
Thanks, but how do you have that many summary files? Do you really
have that many folders (or is something else broken)?
Claire simply does have that many mail folders. As part of her
executive administrator role her Thunderbird is configured
Public bug reported:
My laptop failed to resume while I was working on a spreadsheet in
gnumeric and I had to hard power cycle it. And as a result I've now
lost several hours of work because gnumeric doesn't appear to
implement any sort of backup autosave.
(This is using gnumeric
Public bug reported:
TL;DR: when the CRL is missing on a node, puppet agent pluginsync
fails way too silently.
Me and several of my colleagues just spent about 6 hours debugging our
broken puppet infrastructure. In the end it turns out that the
problem was how we were serving the CRL on our
201 - 300 of 902 matches
Mail list logo
