[Bug 1510731] Re: Can't use crypto in manual disk setup Kubuntu 15.10
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 installed. As I previously noted, I can accomplish this (install boot into non- encrypted sda1 and root into LUKS-encrypted sda2) using Ubuntu 15.10 and Ubuntu 16.04. So this seems to be a Kubuntu specific problem. For those interested in attempting to accomplish this with Ubuntu 15.10 or Ubuntu 16.04, here are a few tips: (1) Use a standalone copy of gparted to create at least two partitions, the first (sda1) for boot and the second (sda2) for root. That is, create the desired partitions before starting the Ubuntu installation. Although you could use less, I typically use 1 GB for sda1. (2) During the Ubuntu install, select the "something else" option. Configure the installer to install boot (/boot) into the non-encrypted sda1. (I typically format sda1 to EXT4, but many recommend using EXT2.) Using the "create physical volume for encryption" option, create a LUKS- encrypted volume on sda2. Wait a bit (sometimes a minute or more), and "sda2_crypt" will appear among the list of installable locations. Configure the installer to install root (/) into the "sda2_crypt" previously created. (I typically format sda2_crypt to EXT4.) (3) At least as of now, do NOT attempt to install home or any other directories into separate partitions. Just stick to installing boot into sda1 and root into sda2_crypt. (You can have other partitions on your disk, but don't attempt to install anything into them.) (4) Do NOT attempt to create a swap partition during installation. Instead, acknowledge the warning regarding the lack of swap space during installation and move on to the next step. (You can create a swap file on sda2_crypt once installation is complete. Or if you really want a swap partition, there are ways of creating them after installation, provide you have left some space on your disk when creating partitions using gparted.) For those who want to install boot (/boot) into non-encrypted sda1, root (/) into LUKS-encrypted sda2, and home (/home) into into LUKS-encrypted sda3, please see my bug report at https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510731 Title: Can't use crypto in manual disk setup Kubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409309] Re: Please update to virt-manager 1.2.1 in Wily
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 (ppa:jacob/virtualisation) for the most recent versions of virt-manager and qemu. And so far, Jacob Zimmermann's ppa has worked pretty well for me. I know that this is a bit off topic, but... I do wish that Ubuntu would consider creating an OFFICIAL ppa at which the most recent versions of virt-manager and qemu (and possibly xen) can be found, much like "ppa:graphics-drivers/ppa" provides an official ppa at which the latest nvidia drivers can be found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409309 Title: Please update to virt-manager 1.2.1 in Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1409309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409309] Re: Please update to virt-manager 1.2.1 in Wily
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409309 Title: Please update to virt-manager 1.2.1 in Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1409309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990997] Re: Firefox interface is horribly laggy in a variety of situations, with delayed scrolling and typing
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: https://addons.mozilla.org/en-US/firefox/addon/noscript/ After activating NoScript, you'll need to allow certain scripts to run for some sites to function properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990997 Title: Firefox interface is horribly laggy in a variety of situations, with delayed scrolling and typing To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/990997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510731] Re: Can't use crypto in manual disk setup Kubuntu 15.10
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 drive), I have been able to create a LUKS-encrypted volume on sda2, and I have been able to install boot (/boot) into non-encrypted sda1, and root (/) into LUKS-encrypted sda2. I have noticed, however, that, after creating the LUKS-encrypted volume on sda2 (using the create the next partition as "physical volume for encryption" that you mention), I sometimes have to wait a bit (sometimes a minute or more) before "sda2_crypt" (or something like that, I don't recall the exact label) is created, into which I can install root. Maybe your installation hangs t this point? Although the above works for me, I have NOT been able to install boot (/boot) into non-encrypted sda1, root (/) into LUKS-encrypted sda2, and home (/home) into into LUKS-encrypted sda3. Rather, although I am able to create all of the LUKS-encrypted volumes, the installer hangs during installation when the following is displayed: “Creating ext4 system for /home in partition #1 of Encrypted volume (sda3_crypt)...” See https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194 for the issue that I'm describing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510731 Title: Can't use crypto in manual disk setup Kubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523194] [NEW] Can't install /home into separate LUKS encrypted volume
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 installation of 15.10 and 16.04 (onto a non-UEFI system with a gpt formatted drive), I have been able to create a LUKS-encrypted volume on sda2, and I have been able to install boot (/boot) into non-encrypted sda1, and root (/) into LUKS-encrypted sda2. All is good in that simple situation. (To get this to work, I skip creating a swap partition, and then create a swap file in sda2 after installation has completed.) However, when using the “something else” option presented during installation of 15.10 and 16.04, after creating LUKS-encrypted volumes on sda2 and sda3, I have not been able to install boot (/boot) into non- encrypted sda1, root (/) into LUKS-encrypted sda2, and home (/home) into into LUKS-encrypted sda3. Rather, although I am able to create the LUKS-encrypted volumes, the installer hangs during installation when the following is displayed: “Creating ext4 system for /home in partition #1 of Encrypted volume (sda3_crypt)...” For what its worth, I am able to accomplish the above installation (/home on LUKS-encrypted sda3) using the net-installer for 15.10. Also, I was able to accomplish the above installation (/home on LUKS-encrypted sda3) using the graphical installer for 15.04. So it seems that some sort of regression has crept into the graphical installer for 15.10 and 16.04. ** 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/1523194 Title: Can't install /home into separate LUKS encrypted volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1523194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie
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 to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 honestly, I don't know what logs I should be looking for. I did, however, run top and noticed that one root process was at over 100% cpu usage while the desktop was frozen. Please see top.png attached to Comment #19. With regard to the QEMU logs on my host, I found nothing noteworthy. I'm just a hobbyist, and tracking down bugs is a bit beyond my skill level. With that in mind, I hope maybe you or someone else who is more capable than me would be willing to create an Ubuntu 15.04 VM and look a little further into this. Who knows, maybe this is just a quirk of my system. But if someone else can reproduce what I'm seeing, then this is probably a pretty big issue, even if not always noticeable. Regards, GizmoChicken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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: (1) I haven't run into this problem with Ubuntu 15.04 when running bare-metal on my Intel-based laptop or when running bare-metal on my AMD-based desktop; (2) however, the above is highly reproducible (almost ALWAYS happens) in VMs run on my Intel-based laptop. (I haven't yet tested any Ubuntu 15.04 VMs on my AMD-based desktop.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 highly reproducible (almost ALWAYS happens) in Ubuntu 15.04 VMs run on my Intel-based laptop. (I haven't yet tested any Ubuntu 15.04 VMs on my AMD-based desktop.); (3) The above is highly reproducible (almost ALWAYS happens) in Ubuntu 15.04 VMs run on my Intel-based laptop, regardless of whether I boot the VM using systemd or upstart ; and (4) The above does NOT seem to occur in Ubuntu 14.04.2 VMs run on my Intel-based laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1432492/+attachment/4390509/+files/unfrozen2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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: unfrozen1.png https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1432492/+attachment/4390508/+files/unfrozen1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1432492/+attachment/4390506/+files/frozen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1432492/+attachment/4390510/+files/top.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432492] Re: Firefox and Thunderbird freezes entire system after a few seconds of use
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 page doesn't seem to cause a crash. However, opening Ubuntu.com, for example, causes a very rapid system freeze with Firefox in 15.04. Also, I've noticed that if I wait long enough (generally more than 10 minutes), the system can sometimes partially unfreeze, but then the desktop background is black, and text in menus and pretty much everywhere else are garbled, leaving the system unusable until reboot. I'll also not that such freezes do NOT occur when using Chrome. Oh, and I'm testing on with fully updated, but otherwise nearly clean installs, of 15.04 and 14.04.2, both running Firefox 37.0.2. (The freezes occurred both before and after installing Chrome in 15.04.) To reiterate, Firefox causes freezes with 15.04, but NOT with 14.04.2. GizmoChicken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432492 Title: Firefox and Thunderbird freezes entire system after a few seconds of use To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1432492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434712] Re: Can't swipe from the right in the setup at first launch
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: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434712] Re: Can't swipe from the right in the setup at first launch
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. 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: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434712] Re: Can't swipe from the right in the setup at first launch
@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 testing the desktop on many devices), I hope that you might consider proposing to whomever bundles up new releases the possibility of issuing, as soon as possible, a release that only adds those fixes that are currently ready for merger, including, of course, your fix for this bug. -- 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: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434712] Re: Can't swipe from the right in the setup at first launch
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 http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ Upon first boot into the freshly installed system, I got the tutorial. Upon rebooting using the installation disk, and selecting the try ubuntu option, I can find that that an empty file named wizard-has-run is already present in .config/ubuntu-system-settings/ on the system disk. But even though the empty file named wizard-has-run is already present on the system disk, upon booting again into the freshly installed system, I still get the tutorial. Perhaps the situation would be different if I had added the empty file named wizard-has-run immediately after installation of, but before first boot into, the system. I don't know. I haven't tried that. But again, I can confirm that, at least for me, under the circumstances described above, the presence of an empty file named wizard-has-run in .config/ubuntu-system-settings/ does NOT prevent the tutorial from starting. -- 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: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434712] Re: Can't swipe from the right in the setup at first launch
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 suggestion made by Edward Oakeley (comment #1) to add a 'skip intro' button for those of us who can't swipe with our mice. -- 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: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1434712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409308] Re: Request: Please update to QEMU 2.2 in Vivid
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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1409308] Re: Request: Please update to QEMU 2.2 in Vivid
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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385292] Re: can't rename files in nautilus
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 IBus, I had this problem both on 14.10 and on 15.04. On 14.10, I had this problem when using the Nvidia 331 driver from the repository and when using the Nvidia 346 driver from the ppa:xorg-edgers/ppa. In the case of 15.04, I also had this problem when using the Nvidia 331 driver from the repository and when using the Nvidia 346 driver from the ppa:xorg-edgers/ppa. However, I have NEVER had this problem (whether or not my keyboard input method system was set to IBus) on on 14.10 and on 15.04 when using the NOUVEAU driver. Granted, I only tested for a short while with the nouveau driver, so I can't say for certain that the nouveau is immune to the problem. QUESTION: Has anybody experienced this bug when using the NOUVEAU driver? If not, maybe the what we're seeing is an interaction between the Nvidia driver and IBus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385292 Title: can't rename files in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1385292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409974] [NEW] Request: Please update to virt-viewer 2.0 in Vivid
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409974 Title: Request: Please update to virt-viewer 2.0 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-viewer/+bug/1409974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409308] Re: Request: Please update to QEMU 2.2 in Vivid
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 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1409308] Re: Request: Please update to QEMU 2.2 in Vivid
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 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409309] [NEW] Request: Please update to virt-manager 1.1.0 in Vivid
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409309 Title: Request: Please update to virt-manager 1.1.0 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1409309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409308] [NEW] Request: Please update to QEMU 2.2 in Vivid
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 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1409308] [NEW] Request: Please update to QEMU 2.2 in Vivid
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 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1409308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377489] Re: Utopic: Cannot install with full disk encryption in Utopic
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377489 Title: Utopic: Cannot install with full disk encryption in Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1377489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377489] Re: Utopic: Full disk encryption not working in Utopic
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1377489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377489] Re: Utopic: Cannot install with full disk encryption in Utopic
** 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: Utopic: Cannot install with full disk encryption in Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1377489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310174] Re: cryptsetup should be included and installed by default in ubuntu 14.04
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 to Ubuntu. https://bugs.launchpad.net/bugs/1310174 Title: cryptsetup should be included and installed by default in ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1310174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 896402] Re: Unity should provide an API for summoning the Dash
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 manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/896402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371274] Re: Unable to use the widevine plugin with chromium
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1371274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 896402] Re: Unity should provide an API for summoning the Dash
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 to Ubuntu. https://bugs.launchpad.net/bugs/896402 Title: Unity should provide an API for summoning the Dash To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/896402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335681] [NEW] Request: Please update to version 1.0.1 in Utopic
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 March 22, 2014, and that version 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.1 from ppa:jacob/virtualisation, and it's working great for me. Any chance we can get virt-manager updated to version 1.0.1 (or newer when available) in the repository for Utopic? ** Affects: virt-manager (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/1335681 Title: Request: Please update to version 1.0.1 in Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1335681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322835] Re: Google Street View not working properly on Firefox 29
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: http://askubuntu.com/questions/486161/street-view-goes-to-black -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322835 Title: Google Street View not working properly on Firefox 29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1322835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322835] Re: Google Street View not working properly on Firefox 29
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322835 Title: Google Street View not working properly on Firefox 29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1322835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289440] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type]
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: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 7 guest using VFIO. Given that VFIO was working before the update, I'm guessing that the update is the cause. -- 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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root: Bus 'pcie.0' not found Oh, and I tried starting another Windows 7 VM using Virt-Manager (without VFIO or any any sort of passthrough), and that VM also crashed with a BSOD just after boot. That VM also had been running just fine with previous test versions of QEMU 2.0. So my system doesn't like something about this latest test version of QEMU. -- 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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 7 guest using VFIO. Given that VFIO was working before the update, I'm guessing that the update is the cause. -- 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root: Bus 'pcie.0' not found Oh, and I tried starting another Windows 7 VM using Virt-Manager (without VFIO or any any sort of passthrough), and that VM also crashed with a BSOD just after boot. That VM also had been running just fine with previous test versions of QEMU 2.0. So my system doesn't like something about this latest test version of QEMU. -- 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213337] Re: Update to latest upstream version
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 for me. I too hope that we can get virt-manager updated to version 1.0.0 in the repository for Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213337 Title: Update to latest upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1213337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 be a good contact, if needed. Here's a link to his github profile: https://github.com/awilliam -- 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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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. https://bugs.launchpad.net/bugs/1284793 Title: [FFE] Merge qemu 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 be a good contact, if needed. Here's a link to his github profile: https://github.com/awilliam -- 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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. https://bugs.launchpad.net/bugs/1284793 Title: [FFE] Merge qemu 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 the problem that I previously reported with VFIO. That is, my VM now seems to be properly running under KVM with VGA passthrough using the VFIO option. Of course, I haven't thoroughly tested for other issues, but VFIO does seem to be working. Will you be updating ppa:ubuntu-virt/candidate to include this fix any time soon? I'd much prefer installing subsequent updates using the ppa. Regards, GizmoChicken -- 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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 the problem that I previously reported with VFIO. That is, my VM now seems to be properly running under KVM with VGA passthrough using the VFIO option. Of course, I haven't thoroughly tested for other issues, but VFIO does seem to be working. Will you be updating ppa:ubuntu-virt/candidate to include this fix any time soon? I'd much prefer installing subsequent updates using the ppa. Regards, GizmoChicken -- 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 flawlessly under Qemu 1.7, but it won't even start under Qemu 2.0. Here's the error message that I get when I try to start that VM: qemu-system-x86_64: /build/buildd/qemu-2.0~git-20140305.f55ea62/hw/pci/pcie.c:240: pcie_cap_slot_hotplug_common: Assertion `((pci_dev-devfn) 0x07) == 0' failed. Here are the startup commands that work flawlessly with Qemu 1.7, but that don't work with Qemu 2.0: sudo vfio-bind :03:00.0 :03:00.1 :00:12.0 :00:12.2 :00:16.0 :00:16.2 \ sudo qemu-system-x86_64 \ -enable-kvm \ -M q35 \ -m 4096 \ -cpu host \ -daemonize \ -smp 4,sockets=1,cores=4,threads=1 \ -bios /usr/share/qemu/bios.bin \ -vga none \ -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root \ -device vfio-pci,host=03:00.0,bus=root,addr=00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=03:00.1,bus=root,addr=00.1 \ -device ahci,bus=pcie.0,id=ahci \ -drive file=/images/Win7img,id=disk,format=raw \ -device ide-hd,bus=ahci.0,drive=disk \ -device vfio-pci,host=00:12.0,bus=pcie.0 \ -device vfio-pci,host=00:12.2,bus=pcie.0 \ -device vfio-pci,host=00:16.0,bus=pcie.0 \ -device vfio-pci,host=00:16.2,bus=pcie.0 \ Any thoughts on why the above isn't working under qemu 2.0? For more info about VFIO, have a look here: https://bbs.archlinux.org/viewtopic.php?id=162768 -- 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 to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284793] Re: [FFE] Merge qemu 2.0
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 flawlessly under Qemu 1.7, but it won't even start under Qemu 2.0. Here's the error message that I get when I try to start that VM: qemu-system-x86_64: /build/buildd/qemu-2.0~git-20140305.f55ea62/hw/pci/pcie.c:240: pcie_cap_slot_hotplug_common: Assertion `((pci_dev-devfn) 0x07) == 0' failed. Here are the startup commands that work flawlessly with Qemu 1.7, but that don't work with Qemu 2.0: sudo vfio-bind :03:00.0 :03:00.1 :00:12.0 :00:12.2 :00:16.0 :00:16.2 \ sudo qemu-system-x86_64 \ -enable-kvm \ -M q35 \ -m 4096 \ -cpu host \ -daemonize \ -smp 4,sockets=1,cores=4,threads=1 \ -bios /usr/share/qemu/bios.bin \ -vga none \ -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root \ -device vfio-pci,host=03:00.0,bus=root,addr=00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=03:00.1,bus=root,addr=00.1 \ -device ahci,bus=pcie.0,id=ahci \ -drive file=/images/Win7img,id=disk,format=raw \ -device ide-hd,bus=ahci.0,drive=disk \ -device vfio-pci,host=00:12.0,bus=pcie.0 \ -device vfio-pci,host=00:12.2,bus=pcie.0 \ -device vfio-pci,host=00:16.0,bus=pcie.0 \ -device vfio-pci,host=00:16.2,bus=pcie.0 \ Any thoughts on why the above isn't working under qemu 2.0? For more info about VFIO, have a look here: https://bbs.archlinux.org/viewtopic.php?id=162768 -- 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: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255558] Re: Can't type my password after cold boot
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 that this problem does NOT affect me in any circumstances under 13.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255558] Re: Can't type my password after cold boot
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952891] Re: qemu-system-x86_64 crashed with SIGABRT on first start wizard
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 something wrong during the auto configuration phase. Does the first start wizard create a configuration file that can be later manipulated? If so, where is it? And where can I find some documentation for this program? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952891 Title: qemu-system-x86_64 crashed with SIGABRT on first start wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aqemu/+bug/952891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] Re: “Unable to connect to libvirt” when using virt-manager with the xl toolstack and Xen 4.2.1
** 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 4.2.1 in Ubuntu 13.10 (and also in Ubuntu 13.04).
+ SUMMARY: I get “Unable to connect to libvirt” when using virt-manager
+ with the xl toolstack and Xen 4.2.1
- BACKGROUND: I am testing a fully updated (as of May 15) installation of
+ BACKGROUND: I am testing a fully updated (as of May 30) installation of
Ubuntu 13.10 that includes the following packages:
- libvirt (1.0.5-0ubuntu1))
- virt-manager (0.9.4-2ubuntu3)
+ libvirt (1.0.5-0ubuntu1)
+ virt-manager (0.9.5-1ubuntu1)
xen-hypervisor-4.2-amd64 (4.2.1-0ubuntu3.1)
Upon setting TOOLSTACK=xm in /etc/default/xen (as well as making a few
needed tweaks to /etc/xen/xend-config.sxp), libvirt and virt-manager
worked great. Yippee!
I guess that I should be happy that the xm toolstack still works with
Xen 4.2.1 and quit while I'm ahead, but...
According to libvirt's documentation:
libxl: Starting with Xen 4.2, the legacy XenD/xm toolstack is
deprecated in favor of libxl, also commonly called libxenlight. libvirt
supports this new Xen toolstack via the libxl driver. If XenD is
enabled, the legacy xen driver consisting of the above mentioned
channels will be used. If XenD is disabled, the libxl driver will be
used.
See http://libvirt.org/drvxen.html.
In view of the above, I attempted to use xl (instead of xm) by setting
TOOLSTACK=xl in /etc/default/xen. And after doing so (both with and
without, the above mentioned tweaks to /etc/xen/xend-config.sxp), I
received the following error when attempting to start virt-manager:
Unable to connect to libvirt.
unable to connect to 'localhost:8000': Connection refused
Verify that:
- A Xen host kernel was booted
- The Xen service has been started
Libvirt URI is: xen:///
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/connection.py, line 1027, in
_open_thread
self.vmm = self._try_open()
File /usr/share/virt-manager/virtManager/connection.py, line 1009, in
_try_open
flags)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to 'localhost:8000': Connection refused
-
Here the output from var/log/libvirt/libvirtd.log
2013-05-18 05:44:47.614+: 1304: info : libvirt version: 1.0.5
2013-05-18 05:44:47.614+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.615+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.617+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.618+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.618+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.619+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
2013-05-18 05:44:47.635+: 1304: error : do_connect:103 : internal error
failed to connect to xend
2013-05-18 05:44:47.636+: 1304: error : xenDaemonOpen_tcp:700 : unable to
connect to 'localhost:8000': Connection refused
2013-05-18 05:45:13.647+: 1289: error : virNetSocketReadWire:1362 :
Cannot recv data: Connection reset by peer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180281
Title:
“Unable to connect to libvirt” when using virt-manager with the xl
toolstack and Xen 4.2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] Re: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
** 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:
libvirt (1.0.5-0ubuntu1))
virt-manager (0.9.4-2ubuntu3)
xen-hypervisor-4.2-amd64 (4.2.1-0ubuntu3.1)
Upon setting TOOLSTACK=xm in /etc/default/xen (as well as making a few
needed tweaks to /etc/xen/xend-config.sxp), libvirt and virt-manager
worked great. Yippee!
I guess that I should be happy that the xm toolstack still works with
Xen 4.2.1 and quit while I'm ahead, but...
According to libvirt's documentation:
libxl: Starting with Xen 4.2, the legacy XenD/xm toolstack is
deprecated in favor of libxl, also commonly called libxenlight. libvirt
supports this new Xen toolstack via the libxl driver. If XenD is
enabled, the legacy xen driver consisting of the above mentioned
channels will be used. If XenD is disabled, the libxl driver will be
used.
See http://libvirt.org/drvxen.html.
In view of the above, I attempted to use xl (instead of xm) by setting
TOOLSTACK=xl in /etc/default/xen. And after doing so (both with and
without, the above mentioned tweaks to /etc/xen/xend-config.sxp), I
received the following error when attempting to start virt-manager:
Unable to connect to libvirt.
unable to connect to 'localhost:8000': Connection refused
Verify that:
- - A Xen host kernel was booted
- - The Xen service has been started
+ - A Xen host kernel was booted
+ - The Xen service has been started
Libvirt URI is: xen:///
Traceback (most recent call last):
- File /usr/share/virt-manager/virtManager/connection.py, line 1027, in
_open_thread
- self.vmm = self._try_open()
- File /usr/share/virt-manager/virtManager/connection.py, line 1009, in
_try_open
- flags)
- File /usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
- if ret is None:raise libvirtError('virConnectOpenAuth() failed')
+ File /usr/share/virt-manager/virtManager/connection.py, line 1027, in
_open_thread
+ self.vmm = self._try_open()
+ File /usr/share/virt-manager/virtManager/connection.py, line 1009, in
_try_open
+ flags)
+ File /usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
+ if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to 'localhost:8000': Connection refused
+
+
+ Here the output from var/log/libvirt/libvirtd.log
+
+ 2013-05-18 05:44:47.614+: 1304: info : libvirt version: 1.0.5
+ 2013-05-18 05:44:47.614+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.615+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.617+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.618+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.618+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.619+: 1304: error : xenHypervisorDoV2Sys:1006 :
Unable to issue hypervisor ioctl 3166208: Permission denied
+ 2013-05-18 05:44:47.635+: 1304: error : do_connect:103 : internal error
failed to connect to xend
+ 2013-05-18 05:44:47.636+: 1304: error : xenDaemonOpen_tcp:700 : unable to
connect to 'localhost:8000': Connection refused
+ 2013-05-18 05:45:13.647+: 1289: error : virNetSocketReadWire:1362 :
Cannot recv data: Connection reset by peer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180281
Title:
“Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] Re: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
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 that XenD/xm has been deprecated in Xen 4.2. But since XenD/xm is still working and in widely used by many, Xen isn't exactly warning anyone about the deprecation. But they are gently encouraging users to make the move as soon as practical. Are you able to check that the documentation you found applies to the version of libvirt that you're using, please? and It's probably also worth checking whether this bug affects upstream libvirt or just the Ubuntu packaging. I posted questions relate to this bug on the virt-tools- l...@redhat.com and libvirt-us...@redhat.com lists. Based on the replies that I received, I'm under the impression that libvirt 1.0.5 (which I'm using) has been made to work with the xl toolstack in a few rpm based distros, including Fedora and openSUSE. However, I can't say for certain whether it is working straight from upstream or whether those distros include their own patched versions. I realize that this bug report is still somewhat incomplete. But I want to leave it open with the hope that others will post additional information here. Hopefully, if enough post here, we'll be able to figure out what's going wrong. Thanks! GizmoChicken ** Changed in: libvirt (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/1180281 Title: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] Re: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180281 Title: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] Re: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180281 Title: “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180281] [NEW] “Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
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 (1.0.5-0ubuntu1))
virt-manager (0.9.4-2ubuntu3)
xen-hypervisor-4.2-amd64 (4.2.1-0ubuntu3.1)
Upon setting TOOLSTACK=xm in /etc/default/xen (as well as making a few
needed tweaks to /etc/xen/xend-config.sxp), libvirt and virt-manager
worked great. Yippee!
I guess that I should be happy that the xm toolstack still works with
Xen 4.2.1 and quit while I'm ahead, but...
According to libvirt's documentation:
libxl: Starting with Xen 4.2, the legacy XenD/xm toolstack is
deprecated in favor of libxl, also commonly called libxenlight. libvirt
supports this new Xen toolstack via the libxl driver. If XenD is
enabled, the legacy xen driver consisting of the above mentioned
channels will be used. If XenD is disabled, the libxl driver will be
used.
See http://libvirt.org/drvxen.html.
In view of the above, I attempted to use xl (instead of xm) by setting
TOOLSTACK=xl in /etc/default/xen. And after doing so (both with and
without, the above mentioned tweaks to /etc/xen/xend-config.sxp), I
received the following error when attempting to start virt-manager:
Unable to connect to libvirt.
unable to connect to 'localhost:8000': Connection refused
Verify that:
- A Xen host kernel was booted
- The Xen service has been started
Libvirt URI is: xen:///
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/connection.py, line 1027, in
_open_thread
self.vmm = self._try_open()
File /usr/share/virt-manager/virtManager/connection.py, line 1009, in
_try_open
flags)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to 'localhost:8000': Connection refused
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Tags: libvirt libxl virt-manager xen xl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180281
Title:
“Unable to connect to libvirt” when using xl toolstack with Xen 4.2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 else revert to mainline 3.8.0 after the install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 than 3.8.0-7. But other than with 3.8.0-19 (with which mirroring doesn't work properly), I haven't yet had a chance to test more recent kernels. Of possible interest to some, rolling back to Linux 3.8.0-7-generic also cured a recent problem in which HDMI audio wasn't working with my Radeon card. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 So the problem seems to integral to the recent kernels updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 mainline 3.8.2 kernel. (I haven't yet tried later mainline kernels.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897008] Re: HDMI: no sound
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 appeared with the Ubuntu 3.8.0-18-generic kernel. I can also confirm that HDMI audio DOES work in Ubuntu 13.04 with the following mainline kernels: 3.8.0, 3.8.1, 3.8.2, 3.8.6, and 3.8.8. (I'll just add that lots of other problems appeared with 3.8.1, 3.8.2, 3.8.6, and 3.8.8. But for me, most everything seems to work well with mainline 3.8.0.) Interesting to note that HDMI audio works with mainline 3.8.6 and mainline 3.8.8, but not with Ubuntu 3.8.0-18 or Ubuntu 3.8.0-19, which are based on mainline 3.8.6 and mainline 3.8.8, respectively. I haven't had a chance to obtain also-info yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897008 Title: HDMI: no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169761] Re: 3.8.0-18 Kernel causes HDMI Audio to stop working
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. Interesting to note that HDMI audio works with mainline 3.8.6 and mainline 3.8.8, but not with Ubuntu 3.8.0-18 or Ubuntu 3.8.0-19, which are based on mainline 3.8.6 and mainline 3.8.8, respectively. See http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html I'll also add that, at least for me, lots of other problems (including inability to mirror monitors) are present with 3.8.1, 3.8.2, 3.8.6, and 3.8.8. See https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1167301 But most everything seems to be working well with mainline 3.8.0 and Ubuntu 3.8.0-7. So for me, mainline 3.8.0 and Ubuntu 3.8.0-7 are my only current options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169761 Title: 3.8.0-18 Kernel causes HDMI Audio to stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 in Ubuntu 13.04 on my AMD Radeon HD6670 are: Ubuntu 3.8.0-7-generic Mainline 3.8.0 I hope to perform a clean install soon after Ubuntu 13.04 is officially released. If this bug hasn't been fix by then, I'd like to revert to one of the above kernels after the clean install. But unfortunately, if Ubuntu 3.8.0-7-generic isn't readily available for download at that time, I'll likely be forced to use mainline 3.8.0. So here's hoping that older (pre-release) Ubuntu kernels will be available after the official release of Ubuntu 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: REGRESSION: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897008] Re: HDMI: no sound
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 kernel versions 17, 18, and 19, but none of those kernel versions worked for me with HDMI audio. I would imagine that some versions between 7 and 17 also work. Unfortunately, versions 7, 17, 18, and 19 are the only versions that I have readily available for testing. So the problem seems to integral to the recent kernels updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897008 Title: HDMI: no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897008] Re: HDMI: no sound
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897008 Title: HDMI: no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 available (until very recently) in Ubuntu 12.10. So the report isn't asking for a new feature, but rather is asking for a previous feature to be restored. And indeed, since a 1024x768 resolution doesn't display properly for me on either of my monitors, a mirrored display set up is not workable for me without this feature. So at least in my case, that previously available feature (ability to mirror display across two monitors using a resolution equal to that of the lower resolution of the two monitors) was not only greatly appreciated, but was heavily relied upon. So please consider this bug to be of High importance. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897008] Re: HDMI: no sound
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 above mentioned workaround (adding radeon.audio=1 to my GRUB boot options) no longer works. In fact, after the update, HDMI audio can't even be seen as an audio output option any longer. What's changed in the last week or so? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897008 Title: HDMI: no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167301] Re: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)
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 with the above described hardware setup, the highest resolution available is 1024x768 (4:3). I'll just add that: - In an earlier daily release of Ubuntu 13.04 (back in late December of 2012, if I recall correctly), the highest resolution available was 1360x768 (16:9) when using the mirror displays option on the same hardware setup as described above. So something related to this problem in 13.04 seems to have changed in late December of 2012. - Up until very recently, Ubuntu 12.10 also offered a resolution of 1360x768 (16:9) when using the mirror displays option on the same hardware setup as described above. But in a very recent update of (sometime in April of 2013), 12.10 also now only offers a resolution of 1024x768 (4:3) when using the mirror displays option on the same hardware setup. So something related to this problem in 12.10 seems to have changed in early April of 2013. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167301 Title: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1167301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053471] Re: YATE 4.2.0.2 is available for Ubuntu 12.04
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. https://bugs.launchpad.net/bugs/1053471 Title: YATE 4.2.0.2 is available for Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yate/+bug/1053471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1046450] Re: Xorg freeze with NVidia GT 610 graphics card under Xen
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 recently replaced my Nvidia GeForce card with a Gigabyte Radeon HD 6670 and it seems to work pretty well, at least for watching HD video and so forth, with Ubuntu 12.10 beta 2 as dom0 using the open source driver. And the card's 100mm fan is nearly silent under normal use. But to get HDMI audio output working with the open source driver, I had to edit the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub to read as follows: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash radeon.audio=1 Interestingly, although my 6670 worked well with the open source driver, I couldn't get it to work with Ubuntu 12.10 beta 2 as dom0 using the AMD proprietary driver. Xorg doesn't seem to start. There is probably a fix for this, but I'm satisfied with the open source driver, so I haven't spent much time on it. See http://forums.linuxmint.com/viewtopic.php?f=189t=102193 I'll just add to the above that I am now happily running *Ubuntu 12.10* as dom0 using the open source driver. I manage my guest domains using virt-manager, the configuration required lots of research, but not much effort once I found the right procedure. But that's the subject of a future bug report. Regards, GizmoChicken On Wed, Nov 28, 2012 at 3:25 AM, Hans Maier 1046...@bugs.launchpad.netwrote: Hey, is there anything new concerning this bug? I'm using Ubuntu 12.10 with Nvidia 460 GTX (driver 304.43) and have the exact same problem and i'd really like to use the xen kernel but not with nouveau driver :) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1046450 Title: Xorg freeze with NVidia GT 610 graphics card under Xen Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: 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 goes blank just after seeing the initial Ubuntu splash screen. and always before the LightDM login screen is displayed. I'll just add that I have experienced nearly the same issue using the 304.43 driver obtained from ppa:ubuntu-x-swat/x-updates. However, when attempting run Ubuntu 12.04 as dom0 in Xen using the 304.43 driver, I can get to the LightDM login screen, but then my screen invariably goes blank when I attempt to start Unity from LightDM. I'll further add that the Nvidia card was installed to replace an older graphics card (which I no longer have and don't recall the make, but am pretty sure it didn't have an Nvidia chipset) whose cooling fan had died. I never had any problems running Ubuntu as dom0 in Xen with that older card. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Sep 5 12:38:38 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation Device [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8408] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) MachineType: Gigabyte Technology Co., Ltd. GA-770TA-UD3 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-30-generic root=UUID=b855b70b-955b-4759-b106-385cb970ada5 ro
[Bug 1046450] Re: Xorg freeze with NVidia GT 610 graphics card under Xen
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 invariably goes blank just after seeing the initial Ubuntu splash screen. and always before the LightDM login screen is displayed. I'll just add that, at least currently, I can load Unity under Ubuntu 12.10 as dom0 in Xen using the default nouveau driver. However, video under Ubuntu 12.10 as dom0 in Xen is slow and choppy with the nouveau driver. I'll report that bug elsewhere when I get a chance. -- 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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1046450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046450] [NEW] Xorg freeze with NVidia GT 610 graphics card under Xen
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 goes blank just after seeing the initial Ubuntu splash screen. and always before the LightDM login screen is displayed. I'll just add that I have experienced nearly the same issue using the 304.43 driver obtained from ppa:ubuntu-x-swat/x-updates. However, when attempting run Ubuntu 12.04 as dom0 in Xen using the 304.43 driver, I can get to the LightDM login screen, but then my screen invariably goes blank when I attempt to start Unity from LightDM. I'll further add that the Nvidia card was installed to replace an older graphics card (which I no longer have and don't recall the make, but am pretty sure it didn't have an Nvidia chipset) whose cooling fan had died. I never had any problems running Ubuntu as dom0 in Xen with that older card. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Sep 5 12:38:38 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation Device [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8408] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) MachineType: Gigabyte Technology Co., Ltd. GA-770TA-UD3 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-30-generic root=UUID=b855b70b-955b-4759-b106-385cb970ada5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-770TA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd05/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-770TA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770TA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-770TA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze nvidia precise running-unity ubuntu xen -- 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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1046450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046450] Re: Xorg freeze with NVidia GT 610 graphics card under Xen
-- 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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1046450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
