** Patch added: "0001-zfs-fix-LINUX_ROOT_DEVICE-when-grub-probe-fails.patch"
https://bugs.launchpad.net/grub/+bug/1908796/+attachment/5445128/+files/0001-zfs-fix-LINUX_ROOT_DEVICE-when-grub-probe-fails.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
If you install Xen on your Ubuntu 20.04 system with ZFS, the system
becomes unbootable because the adjustments made by Canonical to GRUB by
providing 10_linux_zfs to override 10_linux aren't done to 20_linux_xen
as well. I'm not asking for the same level of zys integration
Relates to bug #1632694, but the issue that user reported is fixed
because of the changes Canonical made to include 10_linux_zfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908796
Title:
I've submitted a more permanent fix to the upstream project.
https://lists.gnu.org/archive/html/grub-devel/2020-12/msg00239.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632694
Title:
This should be fixed in recent Ubuntu's with the change to using
10_linux_zfs because it detects the zpool differently than how upstream
GRUB does it. Upstream GRUB however is still busted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
[Impact]
Xen guest time is not stable after a migration.
[Test Case]
Create a Xen guest and migrate it. Check dmesg.
[ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 187.251137] OOM killer disabled.
[ 187.251137] Freezing remaining
This is fixed in bionic with Ubuntu-4.15.0-59.66. Looking to get this
ported into xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845033
Title:
xenbus: Avoid deadlock during suspend due to
Public bug reported:
[Impact]
Xen guests may hang during resume after a migration or suspend.
[Test Case]
Create a Xen guest and run this script and then suspending the VM:
import pyxs, time
c = pyxs.client.Client(xen_bus_path="/dev/xen/xenbus")
c.connect()
c.transaction()
This was marked as invalid being told to upgrade but the issue is
present in the latest Ubuntu release so there's nothing to upgrade to.
** Changed in: openarena (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was marked as invalid being told to upgrade but the issue is
present in the latest Ubuntu release so there's nothing to upgrade to.
** Changed in: ioquake3 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This issue is still present on 16.10, 17.04, 17.10 and I'd be willing to
bet it will happen with 18.04. So hardly invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651561
Title:
openarena
Sure enough removing the 'hugepages' package has solved the issue.
** Changed in: lightdm
Status: New => Invalid
** Changed in: lightdm-gtk-greeter
Status: New => Invalid
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
** Changed in: unity-greeter (Ubuntu)
Well the ioctl() call isn't really an issue because stderr isn't hooked
to a tty in the way that a greeter is started up so that's normal.
The EAGAIN is interesting because I recently installed a package dealing
with hugepages and it created some rules in /etc/security/limits.d
--
You received
Just prior to the SIGTRAP I see a mmap() fail with EAGAIN and a failing
ioctl() call. This is from the attached strace with the other noise
trimmed out.
4108 mmap(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_ST
ACK, -1, 0
4108 <... mmap resumed> ) = -1 EAGAIN
Unfortunately that didn't work. I went back to the versions that 16.10
originally shipped with and its still broken. I'm guessing some data
file that gets generated got corrupted and its causing this but I'm
unable to find it. I've taken an strace of lightdm-gtk-greeter showing
the failure to help
The lightdm.log is very repetitive so I just snipped out the last run
since they all appear to be identical.
** Attachment added: "snippet from lightdm.log"
https://bugs.launchpad.net/lightdm/+bug/1662244/+attachment/4816174/+files/lightdm.log
--
You received this bug notification because
Thanks for the response Robert. I'll give both a shot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
To manage notifications about this
I've tried lightdm-gtk-greeter and kylin-greeter and the same crash
occurs. So I'm back to thinking this issue is with lightdm. Some data or
configuration its passing to the greeter is causing it to fail.
I've removed all the dot directories (.cache, .config, .dbus, .gconf,
and .local) inside of
Here's the backtrace I'm getting out of unity-greeter. Unfortunately
there's no debug symbols available for it to find what's at the bottom
of the stack trace.
#0 _g_log_abort (breakpoint=breakpoint@entry=1) at ././glib/gmessages.c:487
#1 0x75c8a64d in g_logv (log_domain=0x75ccbd6e
** Also affects: lightdm
Importance: Undecided
Status: New
** Also affects: unity-greeter (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lightdm
** No longer affects: lightdm (Ubuntu)
** Summary changed:
- lightdm fails to start
+ unity-greeter crashes
Realized that it's likely unity-greeter because I'm seeing a lot of...
[25886.110278] traps: unity-greeter[820] trap int3 ip:7fb856a35241
sp:7fff145ad0f0 error:0 in libglib-2.0.so.0.5000.0[7fb8569e5000+11]
I've got libglib2.0 2.50.2-2ubuntu1 so I tried to roll back to 2.50.0-1
but that
So this issue bit me in a weird way. I had my bridge called "xenbr0" and
the result of these two interacting gives me absolutely no DNS
resolution since the /etc/resolv.conf just pointed to 127.0.0.53 and
didn't include the DNS server from my "xenbr0". Renaming the bridge to
"renbr0" caused it to
Public bug reported:
lightdm is failing to start. Best guess is because of unity-session-
manager. This is from .xsession-errors.
dbus-update-activation-environment: setting
_=/usr/bin/dbus-update-activation-environment
upstart: click-user-hooks main process (4028) terminated with status 1
Public bug reported:
Loading vm file vm/ui.qvm...
File "vm/ui.qvm" found in "/usr/lib/openarena/baseoa/pak6-patch088.pk3"
...which has vmMagic VM_MAGIC_USE_NATIVE.
... trying pak6-patch088/ui
Loading DLL file /usr/lib/openarena/baseoa/pak6-patch088/uix86_64.so instead.
Loading DLL file:
Public bug reported:
I recently installed Ubuntu 16.04.1 Server (amd64) and unrelated to this
issue the installer made some bad assumptions leaving me with a non-
bootable system. I booted the installation media again and selected
"Rescue Mode" and had it drop me to a root shell in my
Any word on seeing this package published? This ticket hasn't seen an
update in 4 months. I can confirm that Ubuntu 12.04.3 Server out of the
box on amd64 and i386 will not work with DRDB and requires smb's fixed
debs from #17 and #18 (respectively).
--
You received this bug notification because
Any word on seeing this package published? This ticket hasn't seen an
update in 4 months. I can confirm that Ubuntu 12.04.3 Server out of the
box on amd64 and i386 will not work with DRDB and requires smb's fixed
debs from #17 and #18 (respectively).
--
You received this bug notification because
It is a bug when its impossible to set the initial password so it always
tells you that your password is invalid because there is no password set
for the keyring. The issue here is that the code Ubuntu adds for Nova
client initializes the keyring incorectly.
** Changed in: python-novaclient
It is a bug when its impossible to set the initial password so it always
tells you that your password is invalid because there is no password set
for the keyring. The issue here is that the code Ubuntu adds for Nova
client initializes the keyring incorectly.
** Changed in: python-novaclient
** Also affects: python-novaclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1020238
Title:
nova client keeps
** Also affects: python-novaclient (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/1020238
Title:
nova client keeps asking for a keyring password
You can reproduce this problem very quickly on a freshly installed
Ubuntu 12.04 system with Folsom by following the user manual line for
line due to bug #1064749
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Here's the debug info from Folsom.
$ nova --debug delete 3935bacf-63c5-4b19-9375-f067d75d56e6
REQ: curl -i http://192.168.200.135:35357/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H User-
Agent: python-novaclient -d '{auth: {tenantName: dev,
As pointed out to me by ev0ldave in #openstack the way to fix this is to
figure out exactly what the instance ID is.
$ mysql -u root -p
mysql USE nova;
mysql SELECT id, host, hostname FROM instances;
...
mysql UPDATE instances SET deleted=1, deleted_at=2012-10-10 14:56:30,
vm_state=deleted WHERE
You can reproduce this problem very quickly on a freshly installed
Ubuntu 12.04 system with Folsom by following the user manual line for
line due to bug #1064749
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Here's the debug info from Folsom.
$ nova --debug delete 3935bacf-63c5-4b19-9375-f067d75d56e6
REQ: curl -i http://192.168.200.135:35357/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H User-
Agent: python-novaclient -d '{auth: {tenantName: dev,
As pointed out to me by ev0ldave in #openstack the way to fix this is to
figure out exactly what the instance ID is.
$ mysql -u root -p
mysql USE nova;
mysql SELECT id, host, hostname FROM instances;
...
mysql UPDATE instances SET deleted=1, deleted_at=2012-10-10 14:56:30,
vm_state=deleted WHERE
The issue is that several distros install the KVM patched version of
qemu-img as kvm-img. The upstream package has a hardcoded build time
check for qemu-img so unless you install qemu, it will error for you on
those distros. In Gentoo, we handled this with a patch that makes the
check run-time and
So this has been marked fixed but the only fix that appears to be
available is Upgrade the Jaunty alpha or compile the entire X.org stack
by hand. Which really doesn't seem like a reasonable fix for someone
interested in a stable system (i.e. Intrepid).
--
[855GM] 3D programs crash withAssertion
39 matches
Mail list logo
