** Attachment added: "hardware-summary"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/760008/+attachment/2031350/+files/hardware-summary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "media-info"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/760008/+attachment/2031351/+files/media-info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760008
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/760008/+attachment/2031352/+files/partman
** Changed in: debian-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Public bug reported:
Binary package hint: unity
Upon first logging into a system installed in OEM mode, the desktop
appeared corrupted. (See screenshot.) This was installed with the 3rd
party software option enabled in ubiquity, so the nvidia drivers were
automatically installed.
Multiple subs
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/bugs/769033/+attachment/2082579/+files/Screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769033
Title:
Graphical corru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769043
Title:
Cannot manually specify a mount point in the manual partitoner
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Public bug reported:
Binary package hint: ubiquity
When creating partitions or selecting existing partitions in the manual
partitioning tool, the mount point box does not accept keyboard input.
The dropdown still works, so the default values (/, /home, etc.) can
still be selected, but a new one c
FYI, still an issue on a fresh install of 10.10.
For reference, the system also does not mute the internal speakers when
headphones are plugged in. (I think I filed a bug about this but I
don't have the number handy.) Not sure if that's related or not.
--
Audio not directed to external speaker
Public bug reported:
After install on an HP Proliant DL365 of the amd64 ubuntu-server build
from 20100727, the following occurs:
Illegal OpCode
EAX=F000 EBX=0004 ECX=05FF EDX=0001
EBP=FBF0 ESI=7F18 EDI=0001
DS=CF00 ES= FS= GS=
CS:EIP
We've tried a number of things now, including the workarounds above and
updating the firmware on the system and RAID controller. More details:
This seems to be a GRUB issue, actually. This occurs immediately upon
attempting to boot, and we can't invoke the grub menu at all.
At this point the fi
Public bug reported:
Binary package hint: grub
Several systems in the hardware testing lab are unable to install grub.
So far the only systems I have seen affected have been HP Proliant
systems.
An example:
Today's daily build, ubuntu-server amd64 20100707
HP Proliant ML115
Relevant part of sys
** Attachment added: "syslog and partman logs from 10.10 install"
http://launchpadlibrarian.net/51514606/logs.tgz
--
grub-probe error: cannot find a GRUB drive
https://bugs.launchpad.net/bugs/602758
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Attachment added: "lspci -vnvn from working 10.04 LTS install"
http://launchpadlibrarian.net/51514654/lspci
--
grub-probe error: cannot find a GRUB drive
https://bugs.launchpad.net/bugs/602758
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Incidentally, attempts to install legacy grub or LILO on these systems
also fails. (I can collect logs if necessary.) Other Ubuntu releases
(10.04 LTS, 8.04 LTS) install correctly so it does not appear to be a
hardware issue.
--
grub-probe error: cannot find a GRUB drive
https://bugs.launchpad.
Public bug reported:
After installation on an IBM x3250 and an IBM x3650, the maverick daily
images do not boot.
With image 20100826 I receive the following message when trying to boot:
It appears your computer has less than 277K of low ("DOS") RAM.
Syslinux needs at least this amount to boot.
** Attachment added: "/var/log/boot"
https://bugs.launchpad.net/bugs/625294/+attachment/1522887/+files/boot
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625294/+attachment/1522888/+files/dmesg
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "lspci -vnvn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625294/+attachment/1522889/+files/lspci
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member of Ub
** Attachment added: "/var/log/messages"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625294/+attachment/1522890/+files/messages
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a mem
** Attachment added: "/var/log/syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625294/+attachment/1522891/+files/syslog
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member
** Attachment added: "uname -a"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625294/+attachment/1522892/+files/uname
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member of Ubunt
This no longer seems to occur. (However, I am now seeing bug 625294 on
this hardware.)
--
maverick kernel panic on IBM System x3650 M2 and System x3250 M3
https://bugs.launchpad.net/bugs/601142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Binary package hint: partman-iscsi
When attempting to install the maverick daily image (in this case,
20100827) to systems with iscsi devices, the disk devices are not
detected.
In the partitioner, the only option available is "Configure iSCSI
volumes". When selected, the o
** Attachment added: "hardware-summary"
https://bugs.launchpad.net/bugs/625309/+attachment/1522937/+files/hardware-summary
--
iscsi hardware not detected for install
https://bugs.launchpad.net/bugs/625309
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/partman-iscsi/+bug/625309/+attachment/1522938/+files/partman
--
iscsi hardware not detected for install
https://bugs.launchpad.net/bugs/625309
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/partman-iscsi/+bug/625309/+attachment/1522939/+files/syslog
--
iscsi hardware not detected for install
https://bugs.launchpad.net/bugs/625309
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Note that this is happening on multiple systems; the attached logs are
from one affected system.
--
iscsi hardware not detected for install
https://bugs.launchpad.net/bugs/625309
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Yes, this is a regression from 10.04 LTS.
--
Unable to boot maverick daily images -- RAM not detected
https://bugs.launchpad.net/bugs/625294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Public bug reported:
Binary package hint: ubiquity
Running a maverick beta candidate image (20100831.1) of kubuntu-
alternate amd64 in OEM mode.
OEM mode completed successfully, but when running the user creation
wizard afterward I received the following traceback:
Traceback (most recent call l
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/627549/+attachment/1532319/+files/syslog
--
ubiquity crashed in kubuntu oem mode
https://bugs.launchpad.net/bugs/627549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/627549/+attachment/1532320/+files/dmesg
--
ubiquity crashed in kubuntu oem mode
https://bugs.launchpad.net/bugs/627549
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "Contents of /var/log/installer"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/627549/+attachment/1532329/+files/installer.tar.gz
--
ubiquity crashed in kubuntu oem mode
https://bugs.launchpad.net/bugs/627549
You received this bug notification because you are a
Public bug reported:
Binary package hint: ubiquity
ubiquity can be minimized during the install. If this is done outside
of the Live CD mode, there is no taskbar and thus no obvious way to
bring the window back. (It can be restored via alt-tab but this is not
easily discoverable.)
The minimize
Public bug reported:
Binary package hint: ubiquity
During partitioning, new Xubuntu partitions are incorrectly marked as
Ubuntu instead. Existing partitions with Xubuntu installed are reported
correctly.
(See screenshot.)
Observed with Xubuntu maverick 20100901 i386 image on VirtualBox.
** Af
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/bugs/628221/+attachment/1534878/+files/Screenshot.png
--
Partitioner shows Xubuntu as "Ubuntu Maverick"
https://bugs.launchpad.net/bugs/628221
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: apport
When running ubuntu-bug without an argument, the user is presented with
a friendly series of questions to help narrow down their problem.
However, the window title is "apport-gtk" which is the name of the
binary and not descriptive. A better title
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/52260324/Dependencies.txt
--
apport-gtk has a geeky window title
https://bugs.launchpad.net/bugs/608222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Public bug reported:
Binary package hint: sudo
Testing the maverick RC image (20100928.1) for edubuntu amd64 on
VirtualBox.
When booting in the standard live image, 'sudo' and other commands
requiring root work correctly.
When booting in 'persistent' mode on the same live image, 'sudo' returns:
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/650570/+attachment/1650451/+files/Dependencies.txt
--
sudo does not work in live image in persistent mode
https://bugs.launchpad.net/bugs/650570
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: ubiquity
Found on maverick amd64 RC candidate (20100928.1) edubuntu image.
The slideshow image for the "Great desktop software" slide has a LOLcat
rather than an application screenshot. This may not be a bug but does
not appear to be in the same style a
** Attachment added: "I Can Has Screenshot"
https://bugs.launchpad.net/bugs/650586/+attachment/1650574/+files/ICanHas.png
--
edubuntu slideshow has strange screenshot for applications slide
https://bugs.launchpad.net/bugs/650586
You received this bug notification because you are a member of U
I have played more with this... this also occurs on the i386 image as
well as xubuntu and plain ubuntu images. Reformatting my casper-rw
device as ext3 (rather than ext2) did not have any effect either.
--
sudo does not work in live image in persistent mode
https://bugs.launchpad.net/bugs/650570
Public bug reported:
Binary package hint: ubiquity
Discovered testing the maverick amd64 alternate release candidate
(20100928.1) image in OEM mode in VirtualBox.
oem-config-prepare appears to run correctly after install. However,
after rebooting, the OEM user is again logged in and the initial
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/650703/+attachment/1651101/+files/Dependencies.txt
** Attachment added: "OemConfigLog.gz"
https://bugs.launchpad.net/bugs/650703/+attachment/1651102/+files/OemConfigLog.gz
** Attachment added: "UbiquityDm.gz"
htt
Public bug reported:
Binary package hint: ubiquity
Using daily-live amd64 build 20100803.1
Ubiquity crashed during the partitioning stage when attempting a side-
by-side install. The live session started successfully after ubiquity
crashed.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package:
** Attachment added: "Casper.gz"
http://launchpadlibrarian.net/53003260/Casper.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/53003261/Dependencies.txt
** Attachment added: "UbiquityDebug.gz"
http://launchpadlibrarian.net/53003262/UbiquityDebug.gz
** Attachmen
I was using 512MB of RAM, which was previously listed as the bare
minimum for the desktop install on the System Requirements wiki page[1].
However, I see that as of June of this year (revision 51) that was
changed to 1GB instead; I will increase the ram in my VM to the new
minimum requirement for f
10.04.1 shows the same issue.
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/601131/+attachment/1553866/+files/Screenshot.png
--
linux-image-2.6.32-23-generic panics on IBM System x3650 M2 and System x3250 M3
https://bugs.launchpad.net/bugs/601131
** Attachment added: "Casper.gz"
https://bugs.launchpad.net/bugs/628563/+attachment/1536391/+files/Casper.gz
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/628563/+attachment/1536392/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.laun
My mistake. This bug may be invalid then, but I'll let wiser heads than
mine decide.
Though is it worth filing another bug about it being difficult to tell
which is the existing install and which is the new install? I assume
most people will be coming from Windows, but it's possible that someone
Public bug reported:
Binary package hint: ubiquity
When booting kubuntu in OEM mode, the addition of the manufacturer
system name field causes the "Try Kubuntu" / "Install Kubuntu" graphics
to be cut off. See attached screenshot.
This is with kubuntu desktop amd64 image 20100902.1 on VirtualBox
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/bugs/628808/+attachment/1537255/+files/Screenshot.png
--
maverick kubuntu OEM mode graphics are cut off
https://bugs.launchpad.net/bugs/628808
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: ubiquity
Using the kubuntu desktop amd64 beta candidate image (20100902.1) there
does not appear to be any way to resize existing partitions and no
message to this effect is given. This is on a VirtualBox instance with
an 8G drive. There is no automatic
** Attachment added: "Casper.gz"
https://bugs.launchpad.net/bugs/628815/+attachment/1537282/+files/Casper.gz
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/628815/+attachment/1537283/+files/Dependencies.txt
** Attachment added: "UbiquityDebug.gz"
https://bugs.
** Attachment added: "No automatic resize option"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628815/+attachment/1537288/+files/Screenshot-1.png
--
Cannot resize from kubuntu partitioner
https://bugs.launchpad.net/bugs/628815
You received this bug notification because you are a m
** Attachment added: "No manual resize option"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628815/+attachment/1537289/+files/Screenshot-2.png
--
Cannot resize from kubuntu partitioner
https://bugs.launchpad.net/bugs/628815
You received this bug notification because you are a memb
As pointed out by cjwatson above, the manual partitioner does work and I
was misinterpreting the use of the control. (It silently fails to do
anything at all when an invalid amount of space is specified, but that
is a separate bug.)
However I still do not have the automatic resize option.
--
Ca
Public bug reported:
Binary package hint: ubiquity
After installing the maverick DVD beta candidate of kubuntu i386
(20100902.1) via ubiquity started from the live environment, I get a
dialog box saying:
Installation Complete
Installation has finished. You can continue testing ${RELEASE} now, b
** Attachment added: "Screenshot.png"
https://bugs.launchpad.net/bugs/628964/+attachment/1537632/+files/Screenshot.png
--
kubuntu maverick "Installation Complete" message shows "${RELEASE}" rather than
release name
https://bugs.launchpad.net/bugs/628964
You received this bug notification be
Ameet,
This system was installed via PXE, but this bug doesn't come into play
until attempting to boot from the local disk after install. So PXE
should not be a factor here.
Per cjwatson's request, I tried changing grub options (removing the
GRUB_HIDDEN_TIMEOUT options from /etc/default/grub and
** Attachment added: "maverick /var/log/boot.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599046/+files/boot.log
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification because
** Attachment added: "maverick /var/log/dmesg"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599047/+files/dmesg
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification because you a
** Attachment added: "maverick /var/log/installer/hardware-summary"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599048/+files/hardware-summary
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received thi
** Attachment added: "maverick /var/log/installer/initial-status.gz"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599049/+files/initial-status.gz
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received t
** Attachment added: "maverick /var/log/installer/syslog"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599054/+files/installer-syslog
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug noti
** Attachment added: "maverick lspci -vnvn"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599055/+files/lspci
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification because you are
** Attachment added: "maverick /var/log/installer/partman"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599056/+files/partman
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification
** Attachment added: "maverick /var/log/syslog"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599057/+files/syslog
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification because you
** Attachment added: "maverick uname -a"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/641259/+attachment/1599061/+files/uname
--
grub does not appear to load after maverick post-beta install
https://bugs.launchpad.net/bugs/641259
You received this bug notification because you are a m
I ran this after booting into maverick from the grub installed during
the 10.04 LTS install.
This produces the following:
ubu...@ubuntu:~$ sudo grub-install --debug-image=all /dev/cciss/c0d0
Installation finished. No error reported.
Booting into maverick after this was run worked successfully.
401 - 470 of 470 matches
Mail list logo
