I see the same behaviour on 23.10:
-- Boot 59578cca6bcf4df3a3266c0da78a053f --
May 07 16:20:19 mylaptop systemd[2503]: Starting xdg-desktop-portal.service -
Portal service...
May 07 16:21:09 mylaptop xdg-desktop-por[2885]: Failed to create settings
proxy: Error calling StartServiceByName for
or
Thank you for the advice, that's very helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782239
Title:
Attempted install of 18.04 on a Dell Alienware 17 R5
To manage notifications about this b
Public bug reported:
Grub boot loader failed to install the boot loader on the SDD. I'm
attempting to install onto a SATA disk on the machine. The primary disk,
as installed by Dell, is a PCI experss SSD and this has Windows on - the
Ubuntu system isn't able to communicate with this drive.
Proble
I installed the 2.6.32-32 kernel in https://launchpad.net/~serge-
hallyn/+archive/kernel and I see the same kvm guest crashes on my AMD
Opteron host (the system in bug 799166) that I observed with the stock
2.6.32-32 kernel.
wmldev@1p19l3j:~/standard_tests/test1$ aptitude show
linux-image-2.6.32-
Serge - I will try it in the next couple of days and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
To manage notifications abou
>From bug 799166:
Current prerelease kernel 2.6.32-33 doesn't fix this issue for me.
This issue is restricted to AMD processors.
Falling back to 2.6.32-31 is an alternative work-around.
For me, modifying the Linux command line in our guests is an undesirable
workaround and I will be using 2.6.3
Ok, running the guest with clock=acpi_pm added to the Linux command
line, whilst the host is running the 2.6.32-32 kernel has given me
stable behaviour for 20 minutes with constant CPU usage, so it very much
looks like this is a duplicate of bug 790789.
--
You received this bug notification becau
** Summary changed:
- KVM virtual machines crash with host on linux-image-2.6.32-32-server on AMD
processor
+ KVM guests freeze on an AMD-based host since it was upgraded to kernel
2.6.32-32
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
A better title for this would be "KVM guests freeze on AMD-based host
since upgrade to kernel 2.6.32-32"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799166
Title:
KVM virtual machines crash with h
Did the 2.6.32-33 kernel provided by Serge solve the issue?
I see this report is for an AMD machine; it might possibly be related to
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/799166 although
in that case there was no "kvm-clocksource has been installed" message
in the logs prior to a
I've just noticed that although I refer to 2.6.32-32-server in my bug
report, the Dell T105 for which I submitted the bug was running
2.6.32-32-generic. I have observed the same behaviour for
2.6.32-32-server on our other Dell T105 and confirmed that in each case,
the crashes occur for 2.6.32-32 an
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799166
Title:
KVM virtual machines crash with host on linux-image-2.6.32-32-server
on AMD processor
To manage notifications about this bug go to:
http
Public bug reported:
Binary package hint: qemu-kvm
Since the 31st May I've been seeing random crashes in the virtual
machines that we run on an AMD processor based system in our office. We
run Ubuntu 10.04 on this server, which is a Dell T105 and I keep it
patched with all the updates. The virtua
I experience this problem on my Dell Vostro 3700 laptop, which is Ubuntu
certified for 10.10 64 bit (though I am running the 32 bit version of
10.10). Like coclocotero, I see ping round trips to a local system of
hundreds of milliseconds, making the system unusable for ssh sessions.
The problem ca
This is a me too:
I tripped over this bug using 3ware 3DM2 and was able to work around by
using an IP address for my email server.
I'm running 10.04 as well:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS"
--
Lucid
I made use of Mika's patch on a 10.04 system and found it solved my
problem.
I had been confused and thought that there was something wrong with
my/the apparmor config for libvirt, because there were a few apparmor
audit messages in the log, but in fact, it was this issue with the
bridge interface
I can confirm that the process of removing, then re-inserting the
dvb_bt8xx kernel module is required with i386 Ubuntu 9.10 and i386
Ubuntu 10.04 when using the Nebula DigiTV (PCI) card.
I'm still using the workaround of removing, then re-inserting the module
(with a script) every time I want to w
I can confirm that the process of removing, then re-inserting the
dvb_bt8xx kernel module works for me with i386 Ubuntu 9.04 and a Nebula
DigiTV DVB-T (PCI) card. I shall see if I can stick that in my startup
scripts as a workaround.
--
Nebula DigiTV DVB-T (PCI) no longer works
https://bugs.launc
I've just put a 2.6.32rc8 vanilla kernel on my i386 Ubuntu 9.04 system
and it does not solve the problem for me. I have the search for channels
problem and the same errors in the system as other posters (
mt352_write() to reg 5d failed (err = -6)! etc).
--
Nebula DigiTV DVB-T (PCI) no longer work
19 matches
Mail list logo
