Hi all,
I am facing this issue too, and although I can confirm the patch can be
easily backported to Trusty (we run Mitaka on Trusty), some of our
customers have VMs started with the old qemu and I cannot live migrate
anymore or update qemu without stopping and starting the VM.
Do you have any
We have the same issue. Using "delaycompress" suppresses the "gzip:
stdin: file size changed while zipping" error but upstart will continue
to write on .1 file until this is actually gzipped, which is quite
annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm affected too by the "log flooding" issue, although I can start VMs.
[4220163.899438] type=1400 audit(1447230173.207:7763726):
apparmor="DENIED" operation="open" profile="libvirt-a9c8bb9b-f2cc-4e4f-
b7b1-c6152d8029c4" name="/run/shm/lttng-ust-wait-5" pid=69948 comm
="qemu-system-x86"
I'm affected too by the "log flooding" issue, although I can start VMs.
[4220163.899438] type=1400 audit(1447230173.207:7763726):
apparmor="DENIED" operation="open" profile="libvirt-a9c8bb9b-f2cc-4e4f-
b7b1-c6152d8029c4" name="/run/shm/lttng-ust-wait-5" pid=69948 comm
="qemu-system-x86"
This bug affects me as well on a Ubuntu 14.04.
What is the best workaround here? I see two possibilities:
* changing permission on /var/log to 0755 and ownership from root to syslog user
* adding OPTIONS=--force to /etc/default/munge?
which one is the best?
--
You received this bug
Sorry, I just tried changing the ownershipt of /var/log, and munge is
still complaining:
root@node-09-01-00:~# ls -ld /var/log
drwxr-xr-x 17 syslog root 4096 Sep 21 21:43 /var/log
root@node-09-01-00:~# service munge start
* Starting MUNGE munged
...fail!
munged: Error: Logfile is insecure:
This bug also affects my Ubuntu Precise FAI server. Just to be clear: is
there any reason why the fix was not backported to precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008250
Title:
Any news on this? Why is it marked as invalid?
** Changed in: vm-builder (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1245486
Any news on this? Why is it marked as invalid?
** Changed in: vm-builder (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245486
Title:
package
Public bug reported:
File /etc/sysctl.d/30-iscsitarget.conf contains an invalid value for key
net.ipv4.tcp_mem
The bug is particularly annoying as it blocks upgrades of procps, which
in turn blocks a lot of other packages.
Please note that this bug has been fixed in debian:
Public bug reported:
File /etc/sysctl.d/30-iscsitarget.conf contains an invalid value for key
net.ipv4.tcp_mem
The bug is particularly annoying as it blocks upgrades of procps, which
in turn blocks a lot of other packages.
Please note that this bug has been fixed in debian:
I am already using python 2.7:
antonio@kenny:~$ namei `which python`
f: /usr/bin/python
d /
d usr
d bin
l python - python2.7
- python2.7
antonio@kenny:~$ python --version
Python 2.7.5+
antonio@kenny:~$ sudo apt-get install ubuntu-vm-builder
[sudo] password for antonio:
Reading package
Tanks to google, I've got it: im-config, follow the instructions and
then logout and login again (need to restart X11).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224732
Title:
Custom keyboard
I have the same issue.
Dex, can you please explain how the workaround work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224732
Title:
Custom keyboard shortcuts don't work
To manage
I am already using python 2.7:
antonio@kenny:~$ namei `which python`
f: /usr/bin/python
d /
d usr
d bin
l python - python2.7
- python2.7
antonio@kenny:~$ python --version
Python 2.7.5+
antonio@kenny:~$ sudo apt-get install ubuntu-vm-builder
[sudo] password for antonio:
Reading package
Public bug reported:
Running do-release-upgrade from raring to soucy
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: python-vm-builder 0.12.4+bzr488-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Public bug reported:
Running do-release-upgrade from raring to soucy
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: python-vm-builder 0.12.4+bzr488-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
*** This bug is a duplicate of bug 685438 ***
https://bugs.launchpad.net/bugs/685438
I have the same issue on Ubuntu 12.04 x86_64, solved installing hal.
Why gnome-lirc-properties does not depend on hal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 877438 ***
https://bugs.launchpad.net/bugs/877438
I have the same issue, but on intel cards.
My system:
MacBookPro9,2
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
Intel® Core™ i7-3520M CPU @
19 matches
Mail list logo
