Thanks for reporting this bug. Please reply if it is still an issue in
a supported release.
** Changed in: ruby1.8 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.8 in Ubuntu.
** Changed in: ruby1.8 (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.8 in Ubuntu.
https://bugs.launchpad.net/bugs/992122
Title:
package ruby1.8 1.8.7.352-2ubuntu1 failed to
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: net-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: xen (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1014746
Thanks for reporting this bug. Please reply if it is still an issue in
a supported release.
** Changed in: libsdl1.2 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue in
a supported release.
** Changed in: libapache2-mod-python (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
** Changed in: pm-utils (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: ruby1.8 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.8 in Ubuntu.
** Changed in: corosync (Ubuntu)
Importance: Undecided = High
** Changed in: corosync (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: ruby1.8 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.8 in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: ssl-cert (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ssl-cert in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: pm-utils (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. We briefly had a 'trusty' machine type,
with a corresponding libvirt patch to handle it. When we renamed the
trusty machine type we dropped the libvirt patch to handle it.
We should either re-introduce the libvirt patch to handle the trusty
machine type for those
Ah, are you running a saucy or trusty backport kernel?
the precise cgroup-lite still is 'start on mounted MOUNTPOINT=/sys',
whereas later it had to become 'MOUNTPOINT=/sys/fs/cgroup',
It sounds like we need to update the precise job to handle both cases.
--
You received this bug notification
Yes, thanks Michael, as we discussed on irc this needs to be fixed in
device-tree-compiler in precise (and quantal).
Once that is done we can remove the versioned dependency in trusty qemu.
** Also affects: device-tree-compiler (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Hm, the CVE link was added by a (errant?) bot... I removed the link.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1295072
Title:
qemu 1.7 should build-depend on libfdt-dev higher
Hi Amir,
please open a new bug for the crash you are seeing. Indeed
revno should be an int not str in vcsersion.py
--
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/1287943
Title:
** Also affects: device-tree-compiler (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706137
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1304008
Title:
user not added to libvirtd group with iso trusty
Re-marking confirmed for qemu to remind us that we must remove the
version from the libfdt-dev dependency for qemu.
** Description changed:
+ ==
+ Impact: libfdt-dev is unusable
+ Fix: we use the patch from debian wheezy to export the needed .h file.
+ Test case:
Filed bug 1304538 for the cgroup-lite bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/936756
Title:
lxc complains about cgroup not available
To manage notifications about this bug
Public bug reported:
From raring kernel onward, /sys/fs/cgroup is mounted separately.
cgroup-lite in raring and later therefore has the upstart job start on
mounted MOUNTPOINT=/sys/fs/cgroup instead of MOUNTPOINT=/sys.
Now that precise users are using HWE kernels, cgroup-lite in precise
must be
: Undecided = High
** Changed in: qemu (Ubuntu)
Status: New = Triaged
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https
And it is not just with vnc either.
** Changed in: qemu (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed
** Changed in: cgroup-lite (Ubuntu Precise)
Status: Confirmed = Invalid
** Changed in: cgroup-lite (Ubuntu Quantal)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgroup-lite in Ubuntu.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To manage
2f487a3d40faff1772e14da6b921900915501f9a was ok, so bisecting right now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To
Hm, bisect is pointing at 6ff45f01c734e1ad051f19913449e2577c9f4b7d
which is very unlikely. I'll have to keep playing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
Pretty sure that commit b533f658a98325d0e47b36113bd9f5bcc046fdae is the
first bad commit.
This is interesting. The commit is correct in that kvm_vm_ioctl()
returns -errno, not -1, on error. However, the caller,
kvm_physical_sync_dirty_bitmap, on seeing the error, shortcuts some
extra errors to
At the point when the ioctl fails, this is the backtrace:
(gdb) where
#0 kvm_physical_sync_dirty_bitmap (section=0x7fffd820) at
/home/serge/src/qemu/kvm-all.c:446
#1 0x5580e30c in kvm_log_sync (listener=optimized out,
section=optimized out) at /home/serge/src/qemu/kvm-all.c:803
#2
(which means my comment #8 is off track - the caller in this case is
checking the return value, then aborting - and this is the exact same
backtrace as we get anyway)
** Changed in: qemu (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification
It seems reasonable that if we are requesting writing a dirty bitmap,
and kernel says it's not dirty, we ignore that failure? I.e. ignore
ENOENT?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Looking at arch/x86/kvm/x86.c, ENOENT (only) happens when
memslot-dirty_bitmap is NULL in kvm_vm_ioctl_get_dirty_log().
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
ioctl
Signed-off-by: Serge Hallyn serge.hal...@ubuntu.com
---
kvm-all.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/kvm-all.c b/kvm-all.c
index 82a9119..7b7ea8d 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -441,10 +441,13 @@ static int
kvm_physical_sync_dirty_bitmap
Hi Beltran,
Which release are you doing this on? Trusty vm builds fine for me on
trusty.
--
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/1287943
Title:
vm-builder needs trusty
Alternatively, we could have lxc-console attach to tty0 when lxc.tty =
0
That seems reasonable.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1303756
Title:
make lxc-console work
** Also affects: user-setup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1304008
Title:
user not added to libvirtd group with
Please give us a url for an iso we can use to install, and the install
options you are using. I'll see if I can reproduce with 14.04's qemu
and with upstream git HEAD.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
The 2.0 release was pushed to 14.04 archive tonight (and I failed to put
this bug# in the changelog)
** Changed in: qemu (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Please reply if you still have this issue on a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/671898
Please see
https://www.berrange.com/posts/2013/08/12/running-a-full-fedora-os-inside-a-libvirt-lxc-guest/
for an example of how to use virt-install with livirt-lxc.
** Changed in: libvirt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
Thanks for submitting this bug. Are you able to reproduce this at will
(i.e. by connecting from a particular client)?
Is it possible to run
apport-collect 1276414
on the server to post some details about the configuration?
** Changed in: samba (Ubuntu)
Importance: Undecided = High
**
Hi - I notice that this hasn't yet gotten an ack/nack from the release
team.
Ping?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1294823
Title:
FFE: create a trusty machine type
To
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1297487
Title:
MTU not honored in virtio vnet
To manage
Marking medium for lxc as lxc works around this now using a mutex :(
** Changed in: cgmanager (Ubuntu)
Importance: Critical = High
** Changed in: lxc (Ubuntu)
Importance: Critical = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: cgmanager (Ubuntu)
** Description changed:
Before cgmanager, lxc-container-default-with-nesting needed to allow the
container to mount fstype=cgroup. This is no longer needed and is not
safe, therefore should no longer be allowed.
-
- (This ignores the fact that proc and sys mounts under /var/cache/lxc
-
Verified that simply removing the line:
# mount fstype=cgroup - /sys/fs/cgroup/**,
stops cgroup-lite from mounting the cgroupfs, while cgmanager continues
to work.
I'm going to assign this to stgraber just to get his opinion on whether
he still needs cgroups mountable in some cases for
Quoting Stéphane Graber (stgra...@stgraber.org):
I absolutely agree we should be getting rid of this from the profile
ASAP.
Would you call this a bug or a feature? (Shall I seek FFE?)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
, preventing
the rmdir.
The rmdir should simply be ignored, as the directory will simply go away
after the next reboot, and is harmless in the meantime.
** Affects: cgroup-lite (Ubuntu)
Importance: High
Assignee: Serge Hallyn (serge-hallyn)
Status: Triaged
** Changed in: cgroup
** Changed in: cgroup-lite (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgroup-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1300481
Title:
cgroups-umount must
*** This bug is a duplicate of bug 1300481 ***
https://bugs.launchpad.net/bugs/1300481
Thanks for reporting this bug. I believe this is a duplicate of bug
1300481 which was fixed earlier today in cgroup-lite v1.9. I will mark
it a duplicate of that. If you believe that is wrong, please
Public bug reported:
Before cgmanager, lxc-container-default-with-nesting needed to allow the
container to mount fstype=cgroup. This is no longer needed and is not
safe, therefore should no longer be allowed.
(This ignores the fact that proc and sys mounts under /var/cache/lxc
allow bypassing
** Changed in: qemu-kvm (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1297487
Title:
MTU not honored in virtio vnet
To manage notifications
Excellent, I was hoping for that. Thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1284793
Title:
[FFE] Merge qemu 2.0
To manage notifications about this bug go
It looks like this is https://bugs.launchpad.net/bugs/1297651
A patch should be coming soon to fix it. (In the meantime you
should be able to get the previous version's debs from the ppa
by hand; If that's a problem please let me know)
--
You received this bug notification because you are a
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Precise)
Status: New = Confirmed
** Changed in: libvirt (Ubuntu Precise)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix
Thanks for reporting this bug. I assume this is fixed in the version in
trusty? I'll mark this as affecting saucy. There is a bit of a backlog
for fixes to libvirt in saucy, but I've put this down on my list for the
next set (hopefully in 2 weeks).
** Also affects: libvirt (Ubuntu Saucy)
Thanks for reporting this bug. I wonder if this may have been fixed
since 1.7 - Are you able to reproduce this with the qemu version in ppa
:ubuntu-virt/candidate? (That is the version which we hope will end up
in 14.04 before release)
** Changed in: qemu-kvm (Ubuntu)
Status: New =
That is an odd looking list - why is qemu-system-x86 still on 1.7.0,
while qemu-system-common is on 2.0?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1257352
Title:
kvm hangs
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1297487
Title:
MTU not honored in virtio vnet
To manage
Thanks, but that looks like the version currently in 14.04 archive.
Could you test with the 2.0~git-20140325.7b770c7-0ubuntu1 package which
is in ppa:ubuntu-virt/candidate?
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
Ok, sorry, in comment #4 you had said you were on 1.7. There are some
netdev commits between 1.7 and 2.0 so before marking this as affecting
upstream I wanted to make sure you'd tested git head (which you
effectively have).
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
** Changed in: iscsitarget (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
https://bugs.launchpad.net/bugs/1298093
Title:
iscsi_trgt: module verification failed
To
** Changed in: maas (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1297942
Title:
MAAS overwrites DEFAULT_MAAS_URL on upgrade
To manage
This seems like a bug in dpkg or apt, as both cups-browsed and ssh jobs
were apparently not stopped.
Setting up cups-browsed (1.0.40-0ubuntu1.1) ...
start: Job is already running: cups-browsed
invoke-rc.d: initscript cups-browsed, action start failed.
dpkg: error processing cups-browsed
Thanks for reporting this bug.
The syslog messages in question were not themselves followed by a long
delay before the next message, so this may or may not be the cause of
your boot slowdown. Is it possible for you to install the bootchart
package? It will create a .png image which should show
** Changed in: tgt (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1294267
Title:
tgt doesn't export some LUNs after a reload operation (SIGHUP)
Thanks for taking the time to report this bug. It doesn't look like
it's been addressed upstream at all (no catching of sighup going on in
git head).
** Changed in: tgt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Setting up tomcat6 (6.0.35-1ubuntu3.3) ...
Configuration file `/etc/logrotate.d/tomcat6'
== File on system created by you or by a script.
== File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package
Thanks - if I understand Simon's reply correctly, this bug is then
invalid as the wrong behavior is only happening in a debug mode (where
we would expect to continue on error to continue debugging). Please
shout if I misunderstood.
** Changed in: dnsmasq (Ubuntu)
Status: New = Invalid
--
THe DpkgTerminalLog.txt shows
Restarting web server apache2AH00558: apache2: Could not
reliably determine the server's fully qualified domain name, using
127.0.1.1. Set the 'ServerName' directive globally to suppress this
message
Please edit /etc/hosts and add a fully qualified domain
Setting up ruby1.9.1 (1.9.3.194-8.1ubuntu2.1) ...
update-alternatives: error: alternative gem can't be master: it is a slave of
ruby
dpkg: error processing ruby1.9.1 (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent
Thanks for reporting this bug. Assuming this is still an issue, please
try 'sudo rm -rf /usr/share/doc/snmpd/*' followed by 'sudo apt-get
install -f'. Please reply if you are still having issues.
** Changed in: net-snmp (Ubuntu)
Status: New = Incomplete
--
You received this bug
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: libsdl1.2 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: nss (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: net-tools (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: rsync (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: pm-utils (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: screen (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue.
** Changed in: rsync (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/407837
Title:
Cannot resume Jaunty Jackalope after selecting Hibernate
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Is this still an issue on lucid? Does anyone know if it is fixed in
later releases?
To be honest given the workaround in comment #2 I'm not sure this is a
bug in screen, as opposed to cron not exporting the user's environment
to his jobs.
** Changed in: screen (Ubuntu)
Importance: Undecided
Thanks for reporting this bug. Please reply if it is still an issue on
a supported release.
** Changed in: pm-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
I've not yet been able to definitively reproduce this. (On a bad nested
qemu setup i had some issues which i think were unrelated). I've tried
on a trusty laptop, and on a faster machine with a trusty container on a
trusty kernel. Starting with the images you posted for me each time.
--
You
The newest 2.0 candidate qemu at ppa:ubuntu-virt/candidate now has a
patch to define the trusty machine type and make it default. Since this
by itself would break libvirt, the ppa now also has a libvirt package
recognizing 'trusty' as a i440fx machine type.
--
You received this bug notification
How are you starting the VM? Could you try specifying -M pc-i440fx-1.7
or -M pc-i440fx-2.0 ? With the latest upload the default became
'trusty', which could cause windows to say this is new hardware.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1291651
Title:
mention -B best in lxc-create manpage
To manage
1301 - 1400 of 6024 matches
Mail list logo
