As the original report says, this doesn't seem to be an upstream issue.
As I reported there, Fedora with libvirt 1.2.5 didn't have this problem;
and on the Xen4CentOS packages, neither libvirt 0.10 nor libvirt 1.2.10
had this problem. In all cases, if you booted under Xen, virsh would
find Xen
Public bug reported:
Release: Trusty (14.04)
Package version: 5.3-1ubuntu1
Standard practice for IRC programs is (1) to log the chats to a file,
and (2) when re-opening a channel for which you have logs, to insert
logs from the previous session at the top (so you don't lose the history
if you
Ah, thanks -- yep, that looks like just the issue.
Ubuntu does seem to ship bash-completion (in a package named bash-
completion), looks like inherited directly from Debian. Let me know if
you need me to try to duplicate this and report this upstream.
** Package changed: emacs24 (Ubuntu) =
Ok, I pulled from the branch mentioned in that error report, and things
seem fixed now. Thanks for finding that bug for me -- my google-fu
completely failed me.
** Changed in: emacs24 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
Sorry -- got confused there for a second... Yes, I apparently forgot
that I had installed bash-completion.el manually. This is probably not
a bug in Ubuntu then; let me leave this in incomplete temporarily and
I'll close it if it's confirmed.
** Package changed: bash-completion (Ubuntu) =
Public bug reported:
I'm using emacs with the following two lines in my ~/.emacsrc:
(require 'bash-completion)
(bash-completion-setup)
In an emacs shell window, I noticed that the git tab-complete wasn't
working; but the stg tab-complete was. In a normal terminal window,
both worked just fine.
** Package changed: emacs-defaults (Ubuntu) = emacs23 (Ubuntu)
** Package changed: emacs23 (Ubuntu) = emacs24 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370449
Title:
emacs bash
Public bug reported:
Using virt-installer with libvirt/libxl in 14.04 I saw this:
http://pastebin.com/6pbS6Db7
# virt-install --connect=xen:/// --name u14.04 --ram 1024 --disk
U1L1.img,size=2 --location
http://ftp.ubuntu.com/ubuntu/dists/raring/main/installer-amd64/
Starting install...
Public bug reported:
If you boot under Xen in Trusty, and install virt-install, if you don't
specify a URI it gives you this warning:
WARNING KVM acceleration not available, using 'qemu'
If you specify -c xen:/// on the command-line, however, it works
properly.
Similarly, if after creating a
Public bug reported:
Using virt-installer with libvirt/libxl in 14.04 I saw this:
http://pastebin.com/6pbS6Db7
# virt-install --connect=xen:/// --name u14.04 --ram 1024 --disk
U1L1.img,size=2 --location
http://ftp.ubuntu.com/ubuntu/dists/raring/main/installer-amd64/
Starting install...
Public bug reported:
If you boot under Xen in Trusty, and install virt-install, if you don't
specify a URI it gives you this warning:
WARNING KVM acceleration not available, using 'qemu'
If you specify -c xen:/// on the command-line, however, it works
properly.
Similarly, if after creating a
The attached patch relaxes the font requirements.
** Patch added: relax-font-requests.diff
https://bugs.launchpad.net/ubuntu/+source/ygraph/+bug/1074476/+attachment/3564106/+files/relax-font-requests.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Blueprint changed by GeorgeDunlap:
Work items set to:
Work items:
[lars-kurth] sort contributions pie chart by percentage: TODO
[dunlapg] Link to slides that were shown: DONE
[ijc] Ian and Adam discuss grub2 booting Xen first: TODO
[dunlapg] MaaS for installing Xen: TODO
[dunlapg] Upstream getty
Sorry -- it appears that the problem isn't in brasero, but in Linux,
which insists that my CDROM drive is actually an SD reader. (I don't
have an SD reader.) Command-line CD-writing tools also have problems,
but give more informative messages (like, /dev/sdc isn't a writer,
here's a description:
Releases / architectures tested:
* precise, amd64
- AMD: works
- Intel: works
* quantal, i386
- AMD: works
- Intel: Works
* quantal, amd64
- AMD: fails
- Intel: fails
In all cases I use the pxe config template above, just replacing the
filename; and in all cases, I downloaded from the gb
Public bug reported:
I downloaded the Ubuntu 12.10 server install CD, but brasero doesn't
seem to recognize my CD burner. Below are the steps I took:
1. Running brasero with just the image file
brasero /build/tmp/ubuntu-12.10-beta-server.iso
The window comes up and recognizes the .iso file,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060107
Title:
brasero doesn't see my CD burner
To manage notifications about this bug go to:
Tim: Thanks for responding. I just checked the GB mirror, and it looks
like there are binaries for linux and initrd.gz labelled 1 October.
However, they don't work on either of my two test boxes either. :-)
The boxes are in a machine room, but I'll try to morrow to see if I can
boot from a CD or
Joseph: Thank you for response. However, those instructions don't apply to me:
* As the title of the bug says, I'm not using grub, I'm using pxeboot.
* If you look at the config I provided above, you will see that it does not
contain quiet, splash, or any of the other config options that wiki
[Attachment] Raw serial output, starting with the serial BIOS and ending
with the kernel being loaded but not printing any output. cat
exile.log in a terminal window to see exactly what I see on my serial
console.
** Attachment added: exile.log
It looks like this bug is back in some form for the 12.10 beta:
virt-install -n vi-test -r 512 --disk path=/vm/vi-test.img,size=4 -c
/vm/iso/ubuntu-12.10-beta1-server-amd64.iso --network network=default
--connect=xen:/// --vnc --noautoconsole -v
Starting install...
Creating storage file
It looks like the patch mentioned above changes the path *to* /usr/lib
/xen-default/ According to this debian bug conversation, the right
solution is to just use qemu-dm, and allow the toolstack to figure out
the path to the binary:
The attached file is a replacement for the fix-ubuntu-xen-qemu-dm-path.patch.
It does two things:
* Removes all absolute paths for qemu-dm and hvmloader, making them just
qemu-dm and hvmloader respectively
* Changes the xml template for the emulate and bootloader fields to be
filePath rather
Public bug reported:
Ubuntu version: 12.10 Beta
I downloaded the netboot files linux and initrd.gz for 12.10 beta
from the following URL:
http://gb.archive.ubuntu.com/ubuntu/dists/quantal/main/installer-
amd64/current/images/netboot/ubuntu-installer/amd64/
And I used the following pxeconfig
Replacing quantal with precise above (i.e., using the amd64 netboot
images from precise from the same locations and with the same config
file) works fine as well.
** Package changed: ubuntu = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Due to the nature of the issue I have encountered, I am unable to run
anything on the systems *using 64-bit quantal*. I did manage to install
the 32-bit version of quantal, but I'm afraid running the tool may
confuse people, since it will (no doubt) report a 32-bit kernel.
Let me know if you'd
Public bug reported:
I have a system set up with 2 disks; sda and sdb. sdb contains an lvm
volume group that contains logical volumes that contain disk images for
virtual machines, some of which are Linux-based. When I tried to set up
guided partitioning using just sda, after selecting Finish
OK, I just had to re-install, and ran into this same bug. This should
only take five minutes for someone who knows the Ubuntu package system
to fix. I'd post a patch myself, if it wouldn't involve several hours
of learning the ropes first...
--
You received this bug notification because you
I just downloaded the most recent ubuntu update (2.6.35-24) and the sd
card works! There goes my holiday kernel hacking project... :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/670181
Title:
FWIW, I'm an OS developer in my real life; don't generally do coding in
my off time, but I'm going to take a look at this over my Christmas
holidays and see if I can sort out what the problem is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just to add a new data point:
I noticed today that I had a bunch of kernels from 10.04 lying around my
/boot. Since it worked perfectly the very day I upgraded (several weeks
ago), I thought maybe going back to an earlier kernel version would do
it. So I added the last 10.04 kernel to grub,
FWIW I'm using the default 10.10 kernel:
$ uname -a
Linux silas 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 i686
GNU/Linux
And I have a Ricoh host controller:
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 SD Host controller: Ricoh Co Ltd R5C822
Public bug reported:
Binary package hint: mercurial-common
After upgrading, emacs complained about not being able to find the file
mercurial, which is required in my .emacrc.
Looking at my 9.10 system, the file it wants is /usr/share/emacs/site-
lisp/mercurial.el, which is owned by
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50797347/Dependencies.txt
--
Mercurial mode in emacs not packaged properly
https://bugs.launchpad.net/bugs/597683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The XDG_SESSION_COOKIE seems to be set properly now (or at least, it's
not causing problems). XAUTHORITY isn't being set, but with only one X
server it's easy to set it programmatically with export
XAUTHORITY=/tmp/.gdm*. It's probably best that XAUTHORITY not be set
by default, so this issue can
The XDG_SESSION_COOKIE seems to be set properly now (or at least, it's
not causing problems). XAUTHORITY isn't being set, but with only one X
server it's easy to set it programmatically with export
XAUTHORITY=/tmp/.gdm*. It's probably best that XAUTHORITY not be set
by default, so this issue can
Public bug reported:
Description:Ubuntu 8.04.1
Release:8.04
When logging in to a machine through ssh (without -X or -Y), XAUTHORITY
is not set; and when logging in non-interactively, XDG_SESSION_COOKIE is
not set. This prevents programs started over an ssh session to connect
to the
** Summary changed:
- ssh not setting XAUTHORITY, XDB_SESSION_COOKIE
+ ssh not setting XAUTHORITY, XDG_SESSION_COOKIE
** Description changed:
Description: Ubuntu 8.04.1
Release: 8.04
When logging in to a machine through ssh (without -X or -Y), XAUTHORITY
- is not set; and when
38 matches
Mail list logo
