Still a problem in hirsute
** Attachment added: "bluetooth settings UI"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+attachment/5512392/+files/Screenshot%20from%202021-07-21%2009-43-30.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
```
systemctl suspend-then-hibernate
Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep"
not supported
```
Note the verb change!
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3
ProcVersionSignature: Ubuntu
I've looked through all the stacks of running processes and can't see
anything that looks tpg / iscsi related present that could be holding
the mutex - at least per
https://github.com/torvalds/linux/blob/818dbde78e0f4f11c9f804c36913a7ccfc2e87ad
- but perhaps the Ubuntu kernel has some patch that
Public bug reported:
I have a block device exported from zfs, and from time to time it drops
off the network, after which operations such as targetctl restore will
hang.
When it hangs it is stuck in core_tpg_del_initiator_node_acl:
```
[<0>] core_tpg_del_initiator_node_acl+0x8e/0x120
Public bug reported:
They seem to pair ok, but don't show up as sound hardware, either
microphone or speaker/headphones.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic
That was when the USB-power/HDMI/DP adapter was plugged in the other side. The
relevant log entries from lower down are:
```
[622581.193592] usb 3-8: new high-speed USB device number 71 using xhci_hcd
[622581.342507] usb 3-8: device descriptor read/all, error -71
[622581.469590] usb 3-8: new
Public bug reported:
Not sure if this should be on kvm or libvirt etc. Anyhow, back in 2017
kvm with nested enabled running hyper-v running vms was documented as
being a thing that works, but trying to make that work today I'm just
getting blue screens and recovery boots of Windows.
cat
Public bug reported:
I have a MS LifeCam Cinema, which is known to work with Ubuntu in the
past, though forum posts show it no longer working as of ~18.04.
I recently went back to Ubuntu as an actual desktop OS with 20.04 on a
dell xps 13, which has a somewhat average webcam in the lid, so tried
It is super snappy but doesn't work any better: one of the external
monitors, or the other but not both.
I'm unfamiliar with Wayland, and Googling around has not found any
equivalent tools to xrandr to let me interrogate what the system thinks
is going on, so I've included a screenshot of the
Thank you for the response. I think these might fall into the third
category of 'VESA is its own special story' ?
I bought both the adapters from the dell configurator at the time I
bought the machine.
This is the part that flakes:
https://www.dell.com/en-us/shop/accessories/apd/470-acfc
The
Public bug reported:
I have some early dell 4k 60hz screens - the ones which report 2 panels
internally for DP 60Hz - horrid hack I know; I recently got a new XPS
laptop and put Ubuntu on it.
That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens
I bought two slightly different
FWIW I encountered the same Operation not permitted error upgrading from
19.10 to 20.04, in a hyper-V VM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874620
Title:
error: failed to register the
Public bug reported:
https://en.wikipedia.org/wiki/MD5#Collision_vulnerabilities - MD5 is
comprehensively broken at this point. Debsums still claims to be using
md5.
Perhaps it is time to either remove debsums as being insufficient to the
task, or upgrade the hash that debsums uses to a stronger
Can confirm the Azure kernel also fixes enhanced sessions when combined
with appropriate windows side metadata shenanigans.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766857
Title:
[Hyper-V]
Just created a new VM and wondered why enhanced mode logins in hyper-V
weren't working and encountered this.
$ uname -a
Linux cognite-lifeless 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor
I've moved this back to Ubuntu where it belongs - there's no software
changes needed to Launchpad that I can see : making the wiki page better
or clearer etc. If the consensus within Ubuntu is that a different
solution would be better, then please do bring this discussion back to
Launchpad itself.
Public bug reported:
Install was in a hyperV vm.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: xrdp 0.9.9-1
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 8 08:41:55
** Description changed:
- Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
+ Photo of failed machine, and video of a second lockup at
+ https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic
Public bug reported:
Sorry that this is a little vague, I ran into it and didn't run it down
to ground; this was on the cosmic daily server installer build.
hardware: 4 HDD;s, 1 NVMe SSD.
configuration: 1x 512MB ESP per drive, then for the HDDs the second partition
for an mdraid raid5 set.
hint if testing this - add module_blacklist=bcache to your kernel boot
line to boot and reset the metadata :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809748
Title:
8k bcache NULL pointer
Public bug reported:
Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
after doing a wipefs on the cache drive the BUG still occured; wipefs's
the backing drive corrected that. I haven't yet tried wiping just the
backing drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
after doing a wipefs on the cache drive the BUG still occured; wipefs's
the backing drive corrected that. I haven't yet tried wiping just the
backing drive.
** Summary changed:
- 8k bcache cache NULL pointer deref on mount / can't boot
+ 8k bcache NULL pointer deref on mount / can't boot
--
sb.magicok
sb.first_sector 8 [match]
sb.csum 5A3217E583DB5B86 [match]
sb.version 0 [cache device]
dev.label (empty)
dev.uuid2a9e0dfd-acd0-4750-85ae-b347d7580e2b
dev.sectors_per_block 16
dev.sectors_per_bucket
cache superblock info - sb.magicok
sb.first_sector 8 [match]
sb.csum 5A3217E583DB5B86 [match]
sb.version 0 [cache device]
dev.label (empty)
dev.uuid2a9e0dfd-acd0-4750-85ae-b347d7580e2b
dev.sectors_per_block 16
This should perhaps be moved to the kernel; its not clear that userspace
is doing anything wrong. I've filed #1809748 for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662407
Title:
bcache
Public bug reported:
After creating a bcache cache device with an 8k block size (see
#1662407), a kernel oops happens every time device is probed.
I'm not sure that there is any userspace bug present in #1662407 at all
- it may just be kernel. I've attached a dmesg there, but can't actually
get
[ 2938.649666] bcache: register_bcache() error /dev/nvme0n1p2: Bad block/bucket
size
[ 2945.532897] bcache: register_bdev() registered backing device md127
[ 2945.533124] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 2945.533863] PGD 0 P4D 0
[ 2945.535162] Oops:
I can reproduce adding such a cache triggering an OOPS in 18.10:
make-bcache -o 7741440 -w 8k -B /dev/md127 -C /dev/nvme0n1p2
RIP 0010:create_empty_buffers+0x29/0x110
CallTrace
create_page_buffers
block_read_full_page
check_disk_change
__add_to_page_cache_locked
blkdev_readpage
...
--
You
Public bug reported:
Since https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881239 the
vfs_aio_linux driver was removed, but the manpage for was not, which was
very confusing in debugging why things weren't working.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
When I upgraded to bionic, samba broke. The failure was nonobvious until
I ran it in interactive mode.
testparm should be able to check I think?
anyhow, the config issue was that vfs_aio_linux had been removed, but my
config still said
vfs objects = aio_linux
and testparm
Public bug reported:
The docs
https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes#Upgrading_from_Ubuntu_16.10
say to use do-release-upgrade but:
$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found.
Asking for a development version instead throws a traceback:
$ sudo
Public bug reported:
The docs
https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes#Upgrading_from_Ubuntu_16.10
say to use do-release-upgrade but:
$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found.
Asking for a development version instead throws a traceback:
$ sudo
It is in suggests. This means that the default behaviour - the happy
path - for users is poor. Ubuntu's kernels support aufs, and aufs is the
default graph driver.
At a minimum I'd suggest recommends.
But aufs-tools is a) tiny - Installed-Size: 228 and b) has no further
deps (other than libc) -
** Changed in: docker.io (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/1603244
Title:
docker - Cannot start container
To manage notifications about this bug
Public bug reported:
Oct 06 14:48:13 linux-dev docker[1317]:
time="2016-10-06T14:48:13.909019154+13:00" level=error msg="Couldn't run
auplink before unmount /var/lib/docker/tmp/docker-aufs-union929083141: exec:
\"auplink\": executable file not found in $PATH"
Oct 06 14:48:29 linux-dev
Public bug reported:
Ubuntu unbundles urllib3 from requests, but the Python metadata for the
python-requests package is missing urllib3 - which needs to be pinned to
the exact version that requests had bundled to avoid failures (at least
while their support model is
Public bug reported:
Ubuntu unbundles urllib3 from requests, but the Python metadata for the
python-requests package is missing urllib3 - which needs to be pinned to
the exact version that requests had bundled to avoid failures (at least
while their support model is
** Changed in: subunit
Importance: High = Wishlist
** Summary changed:
- Test failures if subunit module is installed
+ Test failures if tests are run from an installed copy of subunit
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: subunit
Importance: High = Wishlist
** Summary changed:
- Test failures if subunit module is installed
+ Test failures if tests are run from an installed copy of subunit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: pip (Ubuntu) = python-pip (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250980
Title:
package pip (not installed) failed to install/upgrade: trying to
overwrite
** Package changed: pip (Ubuntu) = python-pip (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046231
Title:
pip's man page is out of date
To manage notifications about this bug go to:
The patch is pretty small, I think this is a good candidate for a SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367907
Title:
Segfault in gc with cyclic trash
To manage notifications about
So this indicates that the wrong copy of subunit is being picked up by
the test suite in this mode. Would love a patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to subunit in Ubuntu.
https://bugs.launchpad.net/bugs/1268421
Title:
So this indicates that the wrong copy of subunit is being picked up by
the test suite in this mode. Would love a patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268421
Title:
Test failures if
+1 on disabling cloudsigma by default.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1316475
Title:
trusty hang on first boot post deploy
To manage notifications about this
+1 on disabling cloudsigma by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316475
Title:
trusty hang on first boot post deploy
To manage notifications about this bug go to:
** Changed in: tripleo
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
https://bugs.launchpad.net/bugs/1280941
Title:
metadata agent throwing
** Changed in: tripleo
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280941
Title:
metadata agent throwing AttributeError: 'HTTPClient' object has no
Public bug reported:
Upgrading a saucy fresh installed machine to trusty and boom :(.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: shim-signed 1.6+0.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion:
It seems to be looking for /boot/grub/x86_64-efi/load.cfg - a file that
doesn't exist:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state
@ihar please do submit a patch :). Note that the requirements.txt in
question is neutrons one.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
https://bugs.launchpad.net/bugs/1280941
Title:
metadata
@ihar please do submit a patch :). Note that the requirements.txt in
question is neutrons one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280941
Title:
metadata agent throwing AttributeError:
I've reproduced this recently with saucy, without the --max-resize
option, but only resizing to 20-30G from a 2G base, which is well within
the heuristics ext4 has.
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of
Steven's report is with saucy as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure with raring
To manage notifications about this bug go to:
Yeah, thanks - I just rechecked and found operator error. Mea culpa and
sorry for the used [human] bandwidth looking at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280936
Title:
** Description changed:
+ impact
+ --
+
+ any concurrent use of libvirt may lockup libirt
+
+ test case
+ -
+
+ use libvirt concurrently, specifically in nwfilter + createDomain calls.
+
+ regression potential
+
+
+ upstream stable branch update - should be
I've just hit this
[518820.279862] type=1400 audit(1392708646.017:161): apparmor=DENIED
operation=create parent=1 profile=/usr/sbin/dhcpd pid=26521
comm=dhcpd family=packet sock_type=dgram protocol=8
It started when I added a config stanza for a subnet that is on ib1 and
restarted dhcpd - but
Public bug reported:
In the upstart job it says:
# /etc/default/libvirt-bin will be deprecated soon.
# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.
script
[ -r /etc/default/libvirt-bin ] . /etc/default/libvirt-bin
exec
Public bug reported:
In the upstart job it says:
# /etc/default/libvirt-bin will be deprecated soon.
# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.
script
[ -r /etc/default/libvirt-bin ] . /etc/default/libvirt-bin
exec
Public bug reported:
I wrote this up here - http://lists.openstack.org/pipermail/openstack-
operators/2014-January/003893.html originally .
Firstly, outbound GRE packets are sent just fine. On a machine running
1.10.2, they are received and processed correctly.
Inbound GRE packets are not
Public bug reported:
I wrote this up here - http://lists.openstack.org/pipermail/openstack-
operators/2014-January/003893.html originally .
Firstly, outbound GRE packets are sent just fine. On a machine running
1.10.2, they are received and processed correctly.
Inbound GRE packets are not
Indeed - running
sudo iptables -t mangle -A POSTROUTING -o lxcbr0 -p udp -m udp --dport
68 -j CHECKSUM --checksum-fill
In the host permits networking to work correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
I just noticed this about a week ago when I was leaving Hong Kong after
the ODS. My older containers (e.g. precise, or lucid) are failing to
bring up networking. Checking syslog in the container:
Nov 23 06:39:59 subunit-lucid dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
Adding
iptables -t mangle -A POSTROUTING -o ${LXC_NETWORK} -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill
to /etc/init/lxc-net.conf
will fix it on boot for anyone suffering this - I'm happy to wrap that
up in a debdiff if this is considered an appropriate fix.
--
You received
I can see this:
dhcp3 (3.1.3-2ubuntu3.5) lucid-proposed; urgency=low
* Include patch from RedHat/Fedora to deal with hardware/xen/virtio offload
of UDP checksums. (LP: #930962)
* Update apparmor profile to add required the network packet raw rule
for the checksum change.
-- Stéphane
Public bug reported:
I just noticed this about a week ago when I was leaving Hong Kong after
the ODS. My older containers (e.g. precise, or lucid) are failing to
bring up networking. Checking syslog in the container:
Nov 23 06:39:59 subunit-lucid dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
Indeed - running
sudo iptables -t mangle -A POSTROUTING -o lxcbr0 -p udp -m udp --dport
68 -j CHECKSUM --checksum-fill
In the host permits networking to work correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can see this:
dhcp3 (3.1.3-2ubuntu3.5) lucid-proposed; urgency=low
* Include patch from RedHat/Fedora to deal with hardware/xen/virtio offload
of UDP checksums. (LP: #930962)
* Update apparmor profile to add required the network packet raw rule
for the checksum change.
-- Stéphane
Adding
iptables -t mangle -A POSTROUTING -o ${LXC_NETWORK} -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill
to /etc/init/lxc-net.conf
will fix it on boot for anyone suffering this - I'm happy to wrap that
up in a debdiff if this is considered an appropriate fix.
--
You received
See bug 1254338 - the 'fix' in the isc dhcp packages doesn't help at
all for folk with existing containers: adding a mangle rule to the
lxcbr0 in lxc-net.conf helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We may have found some more data on the situation: bug 1233024 reports
on a failure to resize with the same images..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure
Nuts, wrong reference...
We may have found some more data on the situation: bug 1233008 reports
on a failure to resize with the same images..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Public bug reported:
I had dnsmasq running on a VM, with isc-dhcp-relay configured to relay
dhcp requests to it; it relayed them fine, but not the replies. I found
some sporadic reports of this, but no bug in ubuntu, so am filing one
here.
It should be straight forward to reproduce - setup a vm
Public bug reported:
libvirt installs and uses dnsmasq, but that stops dhcp-helper from
running (and vice verca).
The bind-interfaces option to dnsmasq is meant to stop it listening
globally, but it still appears to do so, and dhcp-helper also listens
globally even when serving just one
Public bug reported:
Deploying a raring cloud image with a 2.7G filesystem to 2TB hard disk
crashes in resizefs
[ 143.673885] 0800 880bd4b87f60 880bca8b7d00 8125b
e47
[ 143.673945] Call
interestingly quantal didn't resize, but it didn't lockup either.
Definitely more investigation warranted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure with raring
huh,
root@undercloud-notcompute-jws3awlsb2kh:/home/heat-admin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 1.8T 0 disk
��sda1 8:1020G 0 part /
** Changed in: diskimage-builder
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227420
Title:
apt-xapian-index's postinst runs a background process which
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
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/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage notifications about
https://bugs.launchpad.net/python-troveclient/+bug/1223522 reported
about the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223097
Title:
[MIR] python-troveclient
To manage notifications
http://lists.gnu.org/archive/html/qemu-devel/2013-04/msg02662.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180021
Title:
I/O errors seen on tmpfs
To manage notifications about this bug go
** Changed in: subunit
Assignee: (unassigned) = Robert Collins (lifeless)
** Changed in: subunit
Milestone: None = next
** Changed in: subunit
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: subunit
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025392
Title:
FTBFS with Python 3.3: tests fail
To manage notifications about this
Stable memory use after three days. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug
Stable memory use after three days. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
This is much better for me, but I have seen an increase of 1M over 5
hours so far - so there may be another lower-frequency leak. I will
file a new bug if I find that to be the case.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This is much better for me, but I have seen an increase of 1M over 5
hours so far - so there may be another lower-frequency leak. I will
file a new bug if I find that to be the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The apt-mirror man page has a typo.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: apt-mirror 0.4.9-1
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon Aug 12
Public bug reported:
The TypeError occured in apport itself, so probably won't show up as a
crash report...
robertc@lifelesshp:~$ ubuntu-bug apt-mirror
Gtk-Message: Failed to load module overlay-scrollbar
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call
(updating as a debug step:
# grub-install --debug-image=all /dev/sdb
Installation finished. No error reported.
# grub-install --debug-image=all /dev/sdc
Installation finished. No error reported.
# grub-install --debug-image=all /dev/sdd
Installation finished. No error reported.
# grub-install
Last screen of output:
https://plus.google.com/u/0/105660309458564946897/posts/1LXdj9kxFBR
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208268
Title:
grub not recognising my GPT+mdadm+lvm layout
*-core
description: Motherboard
product: M61P-S3
vendor: Gigabyte Technology Co., Ltd.
physical id: 0
version: x.x
serial: Wed Jan 17 06:42:56 2007
*-firmware
description: BIOS
vendor: Award Software International, Inc.
Or http://paste.ubuntu.com/5950640/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208268
Title:
grub not recognising my GPT+mdadm+lvm layout
To manage notifications about this bug go to:
irc discussion:
2.1 TB of disks are often inaccessible from BIOS Int13H calls.
the mdadm layout should permit identifying the array without reading
past 2.1GB, LVM likewise.
Colin suggests that grub2 may be taking errors from Int13h to mean 'LBA
is bust' when in actual fact it works, just
Public bug reported:
I have a setup that AIUI is supported, but grub doesn't handle it for
some reason.
I have 4 3TB disks in a non-UEFI AMD 64-bit PC.
Each disk has a 10MiB Bios Boot Partition, and the remainder in a 'linux raid'
partition.
MDADM then has the 4 linux raid partitions in RAID6.
** Description changed:
I have a setup that AIUI is supported, but grub doesn't handle it for
some reason.
I have 4 3TB disks in a non-UEFI AMD 64-bit PC.
Each disk has a 10MiB Bios Boot Partition, and the remainder in a 'linux
raid' partition.
MDADM then has the 4 linux raid
Running vms:
$ virsh list
IdName State
1 seed running
6 baremetal_2running
I have virt-manager connected showing both cpu usage and host cpu usage.
With
Public bug reported:
libvirtd is using excessive amounts of memory after a week or so of uptime:
uptime
07:47:15 up 9 days, 21:49, 16 users, load average: 1.06, 2.20, 1.70
from top (sorry for the truncated line, window got resized before I copied it
out.
18978 root 20 0 7334m 6.6g 672
1 - 100 of 1475 matches
Mail list logo
