Even though I don't use Kubuntu, just for kicks, I tried installing
Kubuntu 15.10 with boot (/boot) into non-encrypted sda1 and root (/)
into LUKS-encrypted sda2. I got the same result as reported by David
Schoen, namely, the installer failed to create "sda2_crypt" into which
root (/) could be
Thanks, Marc. The "kvm_hidden=on|off" feature in 1.3.1 is reportedly
helpful for those attempting to upgrade from Windows 7 to Windows 10.
So that alone may be enough to justify the bump.
Although I occasionally install from source, I usually rely on Jacob
Zimmermann's ppa
Thanks for the version update. Much appreciated!
I hope that I don't seem too ungrateful, but virt-manager is now up to 1.3.1.
Please see https://virt-manager.org/download/
Any chance we can get the most current version into Xenial?
--
You received this bug notification because you are a
As has been pointed out above, these problems are triggered in a variety
of situations. But for me, the most common culprits have been unwanted
scripts running in the background. I've found that running "NoScript
Security Suite" helps immensely. "NoScript Security Suite" can be found
here:
Have you tried with Ubuntu rather than Kubuntu? If not, you might want
to try with Ubuntu, just to rule out whether this is a Kubuntu specific
issue.
Using the “something else” option presented during installation of
Ubuntu 15.10 and Ubuntu 16.04 (onto a non-UEFI system with a gpt
formatted
Public bug reported:
For various reasons, I would prefer not to use the default full disk
encryption method (which relies on LVM) when installing Ubuntu. Rather,
I would prefer to install directly into multiple LUKS-encrypted volumes.
Using the “something else” option presented during
Looks like BlueZ 5.33 is now in Wiley. Great! Thanks much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162781
Title:
bluez package out of date, 5.23 is available in debian sid/jessie
To
Is this targeted for Wily?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162781
Title:
bluez package out of date, 5.23 is available in debian sid/jessie
To manage notifications about this bug go
Hi Dave,
I uploaded some screen captures that paint a better picture of what's
going on. Please see the attachments to my above comments.
You suggested that I attempt to ssh into the frozen VM and, if possible,
look at relevant logs. I was able to access my VM when its desktop was
frozen, but
I'm currently having a similar problem (system freeze) when running
Firefox in an Ubuntu 15.04 virtual machine (VM) under KVM/Qemu. That
is, the VM (but not the host) freezes within a few seconds after
visiting certain sites (including Ubuntu.com) using Firefox in the VM.
I'll just add that:
Just to expand on (and repeat some of) the above:
(1) I haven't run into this problem (system freeze when running visiting
certain sites, including Ubuntu.com, using Firefox) when running bare-metal on
my Intel-based laptop or when running bare-metal on my AMD-based desktop;
(2) The above is
unfrozen2.png - This is a screen capture of the 15.04 VM taken a little
after the screen capture depicted in unfrozen1.png. At this point, I
had closed Firefox. Note that my background image changed to black and
the the text is still garbled.
** Attachment added: unfrozen2.png
unfrozen1.png - This is a screen capture of the 15.04 VM taken several
minutes after the initial freeze. After several minutes, the desktop
unfroze. Note that the site (ubuntu.com) had loaded by the time the
desktop had unfrozen. However, although unfrozen, text is garbled.
** Attachment added:
frozen.png - This is a screen capture of the 15.04 VM just after the
desktop froze. Note that the site (ubuntu.com) had not fully loaded at
the time of the freeze.
** Attachment added: frozen.png
top.png - This is a screen capture of an ssh session taken while the
15.04 desktop was frozen by Firefox. Top is running. Note that a root
process at over 100% cpu usage.
** Attachment added: top.png
Hi Dave:
Sure, I'll do my best to provide more info. To be be candid, I'm a
little busy right now, so it may be a few days.
In the meantime, I'll just note that some sites seem to cause Firefox to
freeze the system more quickly than do other sites. For example,
opening only the default start
Great! Thanks so much!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434712
Title:
Can't swipe from the right in the setup at first launch
To manage notifications about this bug go to:
I agree with Mateo Salta: This is a show stopper for testing.
@Michael Terry: Can you please provide an estimate regarding when your
fix will get merged into Vivid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Michael Terry: Thanks so much for the clarification. I would guess
that whoever usually bundles up new releases of unity8 is waiting until
many other fixes are ready before releasing the next version. Sorry if
I'm being a pest, but given the severity of this bug (which effectively
prevents
At least for me, under the circumstances described below, the presence
of an empty file named wizard-has-run in .config/ubuntu-system-
settings/ does NOT prevent the tutorial from starting.
I installed Ubuntu Next fresh from the 08-Apr-2015 daily build from
I encountered the exact same bug (can't swipe from the right in the
setup at first launch) after installing Ubuntu Next to my non-
touchscreen laptop (CPU: Intel Core i3-2310M) using the 24-Mar-2015
daily build from http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-
live/current/
I second the
Thanks Serge!
--
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/1409308
Title:
Request: Please update to QEMU 2.2 in Vivid
To manage notifications about this bug go to:
Thanks Serge!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409308
Title:
Request: Please update to QEMU 2.2 in Vivid
To manage notifications about this bug go to:
I was also having this issue. For me, the solution of setting
Keyboard input method system to None ( System Settings - Language
Support - Language tab) offered by dess seems to be fix. Thanks dess!
Still, I want to add a bit more information:
When my keyboard input method system was set to
Public bug reported:
If possible to do so, please update to virt-viewer 2.0 in Vivid before
the feature freeze. Thanks!
** Affects: virt-viewer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the reply, Serge. No hurry. I'm currently using QEMU 2.2
from ppa:jacob/virtualisation on Utopic. It seems to be working well,
but I'd prefer to install it from the official repository when I upgrade
to Vivid. Thanks much!
--
You received this bug notification because you are a
Thanks for the reply, Serge. No hurry. I'm currently using QEMU 2.2
from ppa:jacob/virtualisation on Utopic. It seems to be working well,
but I'd prefer to install it from the official repository when I upgrade
to Vivid. Thanks much!
--
You received this bug notification because you are a
Public bug reported:
If possible to do so, please update to virt-manager 1.1.0 in Vivid
before the feature freeze. Thanks!
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
If possible to do so, please update to QEMU 2.2 in Vivid before the
feature freeze. Thanks!
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Public bug reported:
If possible to do so, please update to QEMU 2.2 in Vivid before the
feature freeze. Thanks!
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This issue in 14.10, whatever its cause may have been, seems to have
been fixed in the final release.
** Changed in: cryptsetup
Status: New = Fix Released
** Changed in: ubiquity (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of
** Also affects: ubiquity (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/1377489
Title:
Utopic: Full disk encryption not working in Utopic
To
** Summary changed:
- Utopic: Full disk encryption not working in Utopic
+ Utopic: Cannot install with full disk encryption in Utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377489
Title:
Cryptsetup is not currently being installed by default in Ubuntu 14.10
(Utopic). To avoid the issue mentioned by Minosone in comment #6,
cryptsetup should be installed by default, in my opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Anyone know whether such an API was ever added?
Anyone? Anyone? Bueller? Anyone?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896402
Title:
Unity should provide an API for summoning the Dash
To
Also affects Ubuntu 14.10 as of the time of this post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371274
Title:
Unable to use the widevine plugin with chromium
To manage notifications about
What's the status of this request? Was an API for summoning the Dash
ever added? Would be great if the the dash could be summoned directly
from a replacement launcher, such as from Cairo-Dock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
The version of virt-manager currently available in Utopic (version
0.9.5) was first released on April 01, 2013 and is pretty far out of
date. See https://git.fedorahosted.org/cgit/virt-manager.git/plain/NEWS
The most recent version of virt-manager (1.0.1) was released on
Works for me (at least for now) after following this link:
https://www.google.com/maps/preview/?force=webgl
Not quite why following the above links cures the issue, but so far, so
good.
Credit goes to darkhole who suggested using the above link in this post:
I'm having the same problem with Firefox 30 in conjunction with Intel
Sandybridge Mobile. As an alternative, Street View works just fine for
me in the 32-bit version (but not the 64-bit version) of Google Earth,
the .deb for which can be found at
http://www.google.com/earth/download/ge/agree.html
Serge, thanks so much for your hard work to get qemu 2.0 into the
repository. Much appreciated!
--
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
Serge, thanks so much for your hard work to get qemu 2.0 into the
repository. Much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284793
Title:
[FFE] Merge qemu 2.0
To manage
This bug also affects newly released linux-headers-3.14.0-031400-generic
(3.14.0-031400.201403310035) from kernel-ppa/mainline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289440
Title:
My previously reported issue with BSODs seems to be fixed in
2.0~git-20140327.3768d50-0ubuntu1.
--
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
My previously reported issue with BSODs seems to be fixed in
2.0~git-20140327.3768d50-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284793
Title:
[FFE] Merge qemu 2.0
To manage
Yep, that seems to be it. I look forward to the patch.
--
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
Yep, that seems to be it. I look forward to the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284793
Title:
[FFE] Merge qemu 2.0
To manage notifications about this bug go to:
VFIO was workng great with the last two (or three) QEMU 2.0 test version
versions prior to 2.0~git-20140325.7b770c7-0ubuntu1. But with
2.0~git-20140325.7b770c7-0ubuntu1, I get a BSOD and an error stating
that The Bios in this system is not fully ACPI compliant when
attempting to start my Windows
I attempted to start the VM using the commands listed in comment #9
above (with -M q35), which was working great until
2.0~git-20140325.7b770c7-0ubuntu1. I tried substituting -M pc-
i440fx-2.0 for -M q35 (Is that what you had in mind?), but got the
following error: qemu-system-x86_64: -device
VFIO was workng great with the last two (or three) QEMU 2.0 test version
versions prior to 2.0~git-20140325.7b770c7-0ubuntu1. But with
2.0~git-20140325.7b770c7-0ubuntu1, I get a BSOD and an error stating
that The Bios in this system is not fully ACPI compliant when
attempting to start my Windows
I attempted to start the VM using the commands listed in comment #9
above (with -M q35), which was working great until
2.0~git-20140325.7b770c7-0ubuntu1. I tried substituting -M pc-
i440fx-2.0 for -M q35 (Is that what you had in mind?), but got the
following error: qemu-system-x86_64: -device
The most recent version of virt-manager (1.0.0) is available in deb
packages from ppa:jacob/virtualisation. See
https://launchpad.net/~jacob/+archive/virtualisation?field.series_filter=trusty
I'm using virt-manager version 1.0.0 from ppa:jacob/virtualisation with
Trusty, and it's working great
Thanks Serge. Much appreciated! I'll test it later tonight or early
tomorrow.
By the way, the patch that you mentioned is from Igor Mammedov, who is
at RedHat. Alex Williamson, who is also at RedHat, plays a significant
role in implementing VFIO in qemu and the linux kernel, so he might also
Hi Serge,
Version 2.0~git-20140307.4c288ac-0ubuntu1 installed from ppa:ubuntu-
virt/candidat seems to be working great with VFIO. Thanks!
Regards,
GizmoChicken
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Thanks Serge. Much appreciated! I'll test it later tonight or early
tomorrow.
By the way, the patch that you mentioned is from Igor Mammedov, who is
at RedHat. Alex Williamson, who is also at RedHat, plays a significant
role in implementing VFIO in qemu and the linux kernel, so he might also
Hi Serge,
Version 2.0~git-20140307.4c288ac-0ubuntu1 installed from ppa:ubuntu-
virt/candidat seems to be working great with VFIO. Thanks!
Regards,
GizmoChicken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Serge,
I downloaded ALL of the test debs at
http://people.canonical.com/~serge/qemu-20140306-1/ and then installed
ALL of them using the sudo dpkg -i *.deb command. That's what you had
in mind, right?
Anyway, the good news is that the provided test version of Qemu 2.0.
seems to have fixed
Hi Serge,
I downloaded ALL of the test debs at
http://people.canonical.com/~serge/qemu-20140306-1/ and then installed
ALL of them using the sudo dpkg -i *.deb command. That's what you had
in mind, right?
Anyway, the good news is that the provided test version of Qemu 2.0.
seems to have fixed
Good news, bad news.
First the good news:
I have a few VMs that run under KVM using Virt-Manager. ALL of those
VMs are running great with Qemu 2.0.
The bad news:
I have one VM that runs under KVM with VGA passththrough using the VFIO
option. That VM, including VGA passthrough, works
Good news, bad news.
First the good news:
I have a few VMs that run under KVM using Virt-Manager. ALL of those
VMs are running great with Qemu 2.0.
The bad news:
I have one VM that runs under KVM with VGA passththrough using the VFIO
option. That VM, including VGA passthrough, works
Thanks Robert. Not sure if it helps, but I'll just add that the bug
occurs for me when using either an Nvidia GeForce GT610 or AMD Radeon
HD6670 video card. Also, the bug occurs for me when using either the
appropriate open source driver or the appropriate proprietary driver.
Also, I'll just add
This problem still affects me, even after applying updates. As
reported above by ionash, I am able to type (using my physical keyboard)
in my password after I turn on the on-screen keyboard. But without
first turning on the on-screen keyboard, my physical keyboard isn't
recognized.
--
You
I'm not sure whether I'm having the same issue as reported about, but...
I am unable to use AQEMU with Ubuntu 13.10. In my case, the first
start wizard seems to run. But then, after the first start wizard
completes, AQEMU won't restart.
Of course, the problem may very well be that I'm doing
** Summary changed:
- “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
+ “Unable to connect to libvirt” when using virt-manager with the xl toolstack
and Xen 4.2.1
** Description changed:
- SUMMARY: I get “Unable to connect to libvirt” when using xl toolstack
- with Xen
** Description changed:
SUMMARY: I get “Unable to connect to libvirt” when using xl toolstack
with Xen 4.2.1 in Ubuntu 13.10 (and also in Ubuntu 13.04).
BACKGROUND: I am testing a fully updated (as of May 15) installation of
Ubuntu 13.10 that includes the following packages:
Hi Robie,
I posted the output from var/log/libvirt/libvirtd.log in the bug report.
I'll respond to your questions/comments here:
Did you get the documentation with the XenD/xm deprecation warning from
somewhere tied to this version of libvirt, or from the website in
general?
It is well known
Oh, I'll just add that, although this issue has not, to my knowledge,
been reported as bug here on lauchpad, the issue has been mentioned by
others in various forums, including the following:
http://forums.linuxmint.com/viewtopic.php?f=42t=112013p=720628#p721199
--
You received this bug
Thanks much. And medium sounds about right. I'll just add that the
problem might actually be with libxl, which libvirt relies on to
communicate with xl, rather that with libvirt itself. But I'll have
that determination to someone with far more knowledge than me.
--
You received this bug
Public bug reported:
SUMMARY: I get “Unable to connect to libvirt” when using xl toolstack
with Xen 4.2.1 in Ubuntu 13.10 (and also in Ubuntu 13.04).
BACKGROUND: I am testing a fully updated (as of May 15) installation of
Ubuntu 13.10 that includes the following packages:
libvirt
Yep, I found Ubuntu 3.8.0-7-generic in one of my old backups. Too bad
Ubuntu doesn't maintain a repository of kernels from previous daily
builds. And actually, I'm surprised that they don't. Oh well. Guess
I'll either wait until this bug is fixed before a clean install of the
final release or
Regarding Ubuntu 13.04: I just noticed that I am NOT restricted to a
resolution of 1024x768 when using a kernel from an earlier daily build.
Rather, mirroring works properly again in Ubuntu 13.04 with the Linux
3.8.0-7-generic kernel.
Mirroring may also work with kernels that are more recent
Regarding Ubuntu 13.04: In addition to working properly with the Ubuntu
3.8.0-7-generic kernel, mirroring also works properly in Ubuntu 13.04
with the mainline 3.8.0 kernel. However, at least for me, mirroring
does NOT work properly in Ubuntu 13.04 with the mainline 3.8.1 kernel or
with the
QUESTION: I know where to find earlier mainline kernels. But are
earlier versions of the Ubuntu kernels available for download? If so,
from where? I'd like to test mirroring with the Ubuntu 3.8.0-8 and
3.8.0-9 kernels.
--
You received this bug notification because you are a member of Ubuntu
CORRECTION: Contrary to what I wrote in comment #37, the Ubuntu
3.8.0-17-generic kernel DOES support HDMI audio in Ubuntu 13.04.
However, at least for me, HDMI audio continues not to work with the
Ubuntu 3.8.0-18-generic kernel or with the Ubuntu 3.8.0-19-generic
kernel.
So the bug seems to have
I've also been having the same problem (no HDMI audio) with a Radeon HD
6670 beginning with the Ubuntu 3.8.0-18 kernel. I can confirm that HDMI
audio DOES work in Ubuntu 13.04 with my Radeon HD 6670 in combination
with the following mainline kernels: 3.8.0, 3.8.1, 3.8.2, 3.8.6, and
3.8.8.
Thanks Till. I tested a few more mainline kernels, including 3.8.3,
3.8.4, 3.8.5, 3.8.6, and 3.8.8. Unfortunately, mirroring also doesn't
work properly with any of those tested mainline kernels. So at present,
at least for me, the only relatively recent kernels that properly
support mirroring
Till, I'd be happy to provide the info that you're requesting. But
being a Linux neophyte, I'm not quite sure how/where to find it. What
command should I use to create, and/or where do I find, such a listing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Regarding Ubuntu 13.04: I just noticed that audio over HDMI can be made
to work using a kernel from an earlier daily release. In particular, so
long as I keep radeon.audio=1 added to my GRUB boot options, HDMI
audio works in Ubuntu 13.04 with the Linux 3.8.0-7-generic kernel.
I also tried
Hmm. That's strange. I've updated two different installations of
Ubuntu 13.04, and I lost HDMI audio for both of them. I'll update
again in a few days just to see if the problem corrects itself. If not
self-correcting, I'll try a clean install from the final release in a
few weeks.
--
You
Adding one more comment:
I notice that the importance if the original report was been changed
from High to Wishlist after triage.
Just to reiterate, the ability to mirror the display across two monitors
using a resolution equal to that of the lower resolution of the two
monitors was a feature
I've been testing Ubuntu 13.04 with an AMD Radeon HD 6670 graphics card
attached to a big screen TV via HDMI. Until very recently (within the
last week or so), adding radeon.audio=1 to my GRUB boot options had
allowed HDMI audio to work flawlessly.
But after a recent update to Ubuntu 13.04, the
Regarding Ubuntu 13.04: I have a similar problem with an AMD Radeon HD
6670 card connected to two monitors. One monitor (connected via DVI) has
resolution 1440x900 (16:10) and the other monitor (connected via HDMI)
has resolution 1360x768 (16:9).
In my case, when using the mirror displays option
I too hope to see YATE 4.2 added to the Ubuntu 12.04 LTS 12.10
repository. (I notice that YATE 4.2 is available for 13.04, but having
it available for LTS would be helpful.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hans,
Nvidia customer support told me that they don't support Xen dom0. So my
solution to this bug was to replace my Nvidia GeForce card with an AMD
Radeon card. Here's some info that I posted elsewhere:
Yep, it's a shame that Nvidia doesn't support Xen dom0 for most of their
cards.
I
I have tested the nvidia-current 304.43-0ubuntu2 driver with 12.10
beta 1.
As with 12.04, video from my Nvdia card is flawless when booting
directly into the standard kernel. However, when attempting run Ubuntu
12.10 as dom0 in Xen using the nvidia-current 304.43-0ubuntu2 driver,
my screen
Public bug reported:
I have an NVidia GT 610 graphics card with the nvidia-current
295.40-0ubuntu1.1 driver installed.Video is flawless when booting
directly into the standard kernel. However, when attempting run Ubuntu
12.04 as dom0 in Xen using the 295.40 driver, my screen invariably
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046450
Title:
Xorg freeze with NVidia GT 610 graphics card under Xen
To manage notifications about this bug go to:
87 matches
Mail list logo
