Problem still exists in Karmic Alpha 5 released today.
--
Unknown media types in /usr/share/mime/packages/kde.xml
https://bugs.launchpad.net/bugs/289592
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Problem still exists in Karmic Alpha 5 released today.
--
"unknown media type" during update
https://bugs.launchpad.net/bugs/193325
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.ubuntu.com
Redid commands in #8 again and it worked this time.
Thanks!
--
Upgrading of apturl to 0.4.0ubuntu3 fails
https://bugs.launchpad.net/bugs/422825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Did the steps in #8 and I the problem remains:
Calculating upgrade... Done
The following NEW packages will be installed:
apturl-common
The following packages will be upgraded:
apturl
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/26.9kB of archives.
After this op
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/31186673/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/31186674/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/31186675/Dmesg.txt
** Attachment
Public bug reported:
Binary package hint: apturl
apt-get dist-upgrade fails to install apturl.
It appears there is an extraneous leading '.' in the path mentioned
below...
Calculating upgrade... Done
The following packages will be upgraded:
apturl
1 upgraded, 0 newly installed, 0 to remove an
Hum... Looks like HAL is now deprecated in Karmic. How confusing to
leave a deprecated service running when it does nothing.
Looks like some PolicyKit magic is required. If someone can point me to
appropriate info I'll give it a shot.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bu
Someone point me to a resource for debugging/tracing DeviceKit so I can
convert my HAL Policy files to DeviceKit.
Thanks.
--
9.04 -> 9.10 hal fails to parse /etc/hal/fdi/policy/* files
https://bugs.launchpad.net/bugs/421150
You received this bug notification because you are a member of Ubuntu
Bu
Hum... Looks like Ubuntu is deprecating HAL.
Reading http://www.ubuntu.com/testing/karmic/alpha4 there's the
statement...
hal deprecation
Karmic Alpha 4's underlying technology for power management, laptop
Hotkeys, and handling storage devices and cameras maps was moved from
"hal" (which is goin
Doing a 'strace -o /tmp/trace -f hald --verbose=yes --daemon=no >
hald.log 2>&1' then a grep afterward show no access to /etc is made by
HAL.
r...@home1:~/bin# grep etc hald.log
r...@home1:~/bin# grep policy hald.log
14:13:48.538 [I] mmap_cache.c:87: policy: offset=000f178c, size=33448
r...@home
Related to commend #12.
Both speaker-test -Dplug:front and aplay -Dplug:front $(locate
Noise.wav) work with or without comment #33 packages.
Changing /etc/pulse/default.pa per comment #7 fixes output at least.
###fix### #7 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/178442
load-mod
HAL Policies no longer seem to work -
https://bugs.launchpad.net/ubuntu/+bug/421150
If someone can tell me how to trace/debug pulseaudio startup and HAL
policy parsing, I'll try to figure out a HAL Policy for this card as
it's the only card out of a dozen I've tried on Ubuntu that works at
all.
A
Answer to comment #33 is no change for this card with these packages
installed.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
da...@home1:~$ lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu karmic (development branch)
Release:9.10
Codename: karmic
2.6.31-8-generic
--
9.04 -> 9.10 hal fails to parse /etc/hal/fdi/policy/* files
https://bugs.launchpad.net/
Public bug reported:
After upgrading from 9.04 -> 9.10 /etc/hal/fdi/policy/* files are no
longer parsed.
I've changed /etc/default/hal to include DAEMON_OPTS="--verbose=yes
--use-syslog" and I see no syslog output at all in /var/log/syslog or
any other log file. Maybe this is a bug too.
If a hal
Currently this bug is set to be fixed in Alpha 6.
Click https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/419911 for
an example of one set of commands to structure a GPT disk for Grub 2.
Maybe this will assist this bug being fixed in Alpha 5 instead of Alpha
6.
--
create BIOS Boot Partiti
The following script can be used from a LiveCD to initially structure a
GPT disk properly.
There still seems to be some problem where update-grub is never run when
a new kernel is installed, even when correct GPT structure is in place.
Be sure to run update-grub after any kernel update for grub.c
This bug is now showing up in Karmic-Alpha5+.
I've installed the 2009-08-27 daily snapshot + updates (including
2.6.31-8-generic) and this problem persists.
Per the above, simply removing outdated lines from /etc/fstab fixes this
problem.
And this will be an amazingly frustrating experience for
Partial fix to create a bootable system is to create a GPT friendly
partition map. The explanation for this is long and circuitous. Google
parted + GPT + howto for details.
Here's one parted map which allows GPT disks (> 2Tb) to be used
smoothly, meaning grub without blocklists.
http://bugs.debia
All well and good.
Please update this bug with a set of commands to create a BIOS Boot
Partition so this bug can be circumvented until the fix is done.
Thanks.
--
create BIOS Boot Partition on GPT
https://bugs.launchpad.net/bugs/417724
You received this bug notification because you are a member
It appears this problem is queued to be fixed in Alpha 6. Guess I try
Fedora.
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/417724
covers what appears to be the fix.
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.lau
This bug does not appear in 9.04 as I can install it just fine and
appears to specifically relate to grub 2 + large drives.
I've recreated this bug manually installing on small partitions, on a
single partition on one drive with swap on another and even on a
pristine drive cleaned by way of...
dd
I've begun to consider this may be a problem with the installer
recognising disks correctly.
I'm installing on a 2TB WD20EADS-00R disk.
Attached is the fdisk -l which appears to be setting this disk up as a
GPT (EFI/Apple bootable) disk.
Maybe because I have a Mac sitting next to the machine I'm
After many experiments here's the cleanest way to recover from this to a
bootable system.
mount /dev/sda1 /mnt -o rw
mount --bind /dev /mnt/dev
chroot /mnt
apt-get update
apt-install grub-pc
Just follow instructions and reboot.
--
update-grub never runs because ubiquity crashed with InstallStep
** Attachment added: "Syslog"
http://launchpadlibrarian.net/30906844/syslog.gz
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.launchpad.net/bugs/419911
You received this bug notification because you are a member of Ubuntu
Bugs,
Looks like install.py is dying.
Attached is the installer debug log.
** Attachment added: "Install Debug File"
http://launchpadlibrarian.net/30906730/debug.gz
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.launchpad.net/bugs/4
I'll leave this machine in this state for a bit.
If someone likes me to gather more data or try to run any commands
manually to recover, post the exact commands here.
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.launchpad.net/bu
** Attachment added: "Installer"
http://launchpadlibrarian.net/30906711/version
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.launchpad.net/bugs/419911
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 419911 ***
https://bugs.launchpad.net/bugs/419911
Dup of 419911 which relates to Karmic-Alpha5-0827 daily snapshot.
** This bug has been marked a duplicate of bug 419911
update-grub never runs because ubiquity crashed with InstallStepError in
configure_b
*** This bug is a duplicate of bug 419911 ***
https://bugs.launchpad.net/bugs/419911
Dup of 419911.
--
ubiquity crashed with IOError in __process()
https://bugs.launchpad.net/bugs/411221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 419911 ***
https://bugs.launchpad.net/bugs/419911
** This bug is no longer a duplicate of bug 290635
ubiquity crashed with AttributeError in step_name()
** This bug has been marked a duplicate of bug 419911
update-grub never runs because ubiquity crashe
*** This bug is a duplicate of bug 419911 ***
https://bugs.launchpad.net/bugs/419911
Dup of 419911 which relates to Karmic-Alpha5-0827 daily snapshot.
** This bug has been marked a duplicate of bug 419911
update-grub never runs because ubiquity crashed with InstallStepError in
configure_b
*** This bug is a duplicate of bug 419911 ***
https://bugs.launchpad.net/bugs/419911
** This bug has been marked a duplicate of bug 419911
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
--
9.10 Alpha 4 has no grub.cfg after install
https:/
I tried this... which failed...
mount /dev/sda1 /mnt -o rw
mount --bind /dev /mnt/dev -o rw
mount --bind /proc /mnt/proc -o rw
chroot /mnt
apt-get install linux-image-2.6.31-7-generic --reinstall
This reinstall worked with no errors and machine is still bricked -
black screen on boot.
--
update
** Visibility changed to: Public
--
update-grub never runs because ubiquity crashed with InstallStepError in
configure_bootloader()
https://bugs.launchpad.net/bugs/419911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Colin Watson wrote:
> update-grub is just a thin wrapper around grub-mkconfig, as is
> documented in 'man update-grub'; you can use grub-mkconfig to write the
> configuration file to some different place.
>
> GRUB 1 was never really declared stable, and GRUB 2 is not yet entirely
> ready for a 2.0
Colin Watson wrote:
> If you don't have a /var/log/installer/syslog to attach, then please
> describe *in as much detail as you can* what state your machine was in
> before you started the installation, and exactly which options you
> selected during installation. Your goal here is to give us enoug
Colin Watson wrote:
> update-grub is just a thin wrapper around grub-mkconfig, as is
> documented in 'man update-grub'; you can use grub-mkconfig to write the
> configuration file to some different place.
>
> GRUB 1 was never really declared stable, and GRUB 2 is not yet entirely
> ready for a 2.0
Nandan Vaidya wrote:
> I think you will need to run this:
>
> $ sudo apt-get install grub-pc
> $ sudo grub-install /dev/sda (replace sda with the correct drive letter)
> $ sudo update-grub
>
> You can do this from a Live CD by mounting the parition where karmic is
> installed and doing a chroot
Fixed... And what a can of worms.
This is a nightmare for first time Ubuntu users like me. I almost
switched back to Fedora or any other distro.
First point GRUB 1 shows as version 0.97 and GRUB 2 shows as version
1.96 which is extremely confusing.
I've tried a variety of fresh installs and upgr
So the real problem appears to be this.
Installing 9.10 to a disc as an overwrite of 9.04 appears to confuse the
Grub installation process.
Neither Grub 1 or Grub 2 install. There is neither a menu.lst or
menu.cfg so the machine bricks.
I'll now try loading this onto a fresh disk and see what oc
This fails as there's no /dev/sda* active.
--
9.10 Alpha 4 has no grub.cfg after install
https://bugs.launchpad.net/bugs/417209
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.ubuntu.com
htt
Now I'm further confused as 'grub-install -v' shows "GRUB 1.96" instead
of "GRUB 2.xx".
I'll take your advice and try the above.
Thanks.
--
9.10 Alpha 4 has no grub.cfg after install
https://bugs.launchpad.net/bugs/417209
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
After much travail it's become clear something is badly broken in 9.10
Alpha 4.
On a fresh install to disc the disc structure is written, except
grub.cfg is missing so machines black screen.
And update-grub is very stupid. There's no way to tell it to produce
/boot/grub.cfg
Public bug reported:
This system installs, boots, runs 9.04 with no problems.
Also doing an 'update-manager -d' updates to 9.10 and all is well.
It's just fresh installs which appear broken.
http://cdimage.ubuntu.com/releases/karmic/alpha-4/karmic-
desktop-i386.iso is the ISO file I used.
I us
201 - 245 of 245 matches
Mail list logo
