Public bug reported:
karmic 64
linux 2.6.30-9
grub2
Grub2 fails to launch any OS.
Rectified by modifying grub.cfg of the lines
search --no-floppy --fs-uuid --set 4afcadf1-b2a6-..
to
search --fs-uuid --set 4afcadf1-b2a6-..
ie., by removing "--no-floppy"
Note: this was done by lau
Last update of grup-pc on 24th June still needs "--no-floppy" to be
removed from grub.cfg. (see my bug 391028). Additionally, need to wait
at least 15 secs before entering grub entry, (Set time out to at least
15 secs); otherwise it will go to shell mode.
--
grub2 update adds --no-floppy to "sear
After latest update of Aug 11th, grub.cfg was regenerated and the old
(and wrong) uuid number was reinstated for the Hardy partition. I had
previously manually edited the grub.cfg to reflect the correct uuid to
enable me to boot into Hardy.
--
Grub2 did not update uuid changes
https://bugs.launc
Colin, attached is file for grub.cfg, parted and blkid.
Hardy partition is sda8 (hd0,8)-in grub2 naming convention.
Note old uuid for hardy is 4afcadf1-b2a6-465f-bb67-c9d7d5103a2f
and new uuid is 606840d0-3e10-4e6b-9aba-c445d082832b
Repeat, both old and new Hardy is on grub2, not g
Yes, it still has the "--no-floppy" in grub.cfg. But it is boots okay now even
with this.
Sorry I didn't make this clearer. Also converted my '1st grub' partition and
my Hardy from grub legacy to grub2.
All works fine. Interesting though, Hardy grub2 does not contain the
"--no-floppy" lines, an
Problem is resolved in update of 16 Jul. Thanks guys.
I'll go convert my Hardy and my dedicated grub partition now to grub2.
--
grub2 update adds --no-floppy to "search " lines
https://bugs.launchpad.net/bugs/391044
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Karmic 64
Linux kubuntu 2.6.31-4-
Reinstalled Hardy in another partition and installed grub2 in Hardy.
Both old and new Hardy have grub2 installed and in the same partition.
Uuid for Hardy was changed following the reinstallation.
Booted into Karmic and updated grub by 'sudo
I do not have any problem as per my post on 2009-07-16. The grub.cfg still has
the "--no-floppy" lines but it boots okay. This works even if that (Karmic)
boot/grub is not set to mbr as this was the case in mine. I had a dedicated
'first grub' (on grub2) which boots to the Karmic grub config. I
Latest kernel change of 2.6.31-6 seems to have resolved this problem.
The correct UUID number has been reinstated. Thanks again.
--
Grub2 did not update uuid changes
https://bugs.launchpad.net/bugs/406774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I'm using Kubuntu Lucid. Similarly affected. Have to start from CLI with
'startx'. Noted too /etc/init/kdm.conf also have line 'and tty-device-
added KERNEL=tty7'. To date, problem not fixed.
--
gdm does not start X unless remove "tty-device-added KERNEL=tty7" from upstart
gdm.conf
https://bugs
No, Johan, don't think it is related to bug 495100. It's just that
sometimes auto login works, most times it didn't. But I recall a warning
that explicitly states that autologin does not work when I downloaded
alpha1. So I did not file bug for it. But I always reset my locale so
that Thunderbird3 c
p...@kubuntu:~$ kaffeine -v
Qt: 4.5.2
KDE: 4.3.3 (KDE 4.3.3)
Kaffeine: 1.0-pre2
p...@kubuntu:~$ xine -v
The program 'xine' is currently not installed. You can install it by typing:
sudo apt-get install xine-ui
xine: command not found
--
Bug report automatic
https://bugs.launchpad.net/bugs/481132
Public bug reported:
Karmic 64
Kde 4.3.1
Linux kubuntu 2.6.31-10-generic
Extreme slow boot at boot splash. Tried various workarounds but found
that disabling autologin at systems settings, convenience did the trick.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Extreme
Public bug reported:
Karmic 64
Kde 4.3.1
Linux 2.6.31-10-generic
Latest update of 16 Sept 2009 disables wired ethernet connection eth0.
Need to comment out line #iface eth0 inet dhcp in interfaces of /etc/network to
reenable networking.
Other usual methods, (ifconfig, ifup, networkmanager) were
I have sata hd, but I think problem is that I started with Karmic alpha2 and
update and upgrade till alpha6. I have this suspicion because the usplash is
still there, which I understand it shouldn't be there for alpha6.
When I enabled passwordless autologin, the usplash will take about 3 to 5 min
** Attachment added: "lspci -- dmesg"
http://launchpadlibrarian.net/35564000/lspci%20--%20dmesg
--
Bug report automatic
https://bugs.launchpad.net/bugs/481132
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kaffeine in ubuntu.
--
kubuntu-b
Public bug reported:
Binary package hint: kaffeine
Karmic 64
2.6.31-14-generic #48-
kde 4.3.3
After upgrading karmic 64 to kde 4.3.3 from kde 4.3.2 through ppa,
kaffeine does not play, in fact, it gums up the system, memory, both cpu
and swap rises slowly to 100% and have to kill kaffeine proc
After some upgrades, reinstalled xserver-xorg-video-nouveau to try out.
Booted okay with my plymouth uninstalled. Then reinstalled plymouth, and
the problem returned and can only be booted with the 'splash' removed
(again) at grub kernel menu.
The problem seems (to me) not to be with nouveau but w
lspci -vvnn attached
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/40953232/lspci.txt
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
If at grub menu, delete 'splash', will it still boot?
Refer my bug report 537853.
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in u
Commenting out the kdm line (Scott James Remnant) in pre-stop script
behaves exactly like booting up grub without 'splash'. It boots alright
but without the plymouth splash (small ubuntu text with 5 red dots).
Shutting down has the plymouth screen, like booting without splash.
--
boot hangs on sp
Modifying plymouth.conf as per Steve Langasek leaves the plymouth screen
hanging, confirming Joe Crollard findings. Had to force reboot.
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug notification because you are a member of Kubu
@Steve Langasek, attached is my plymouth.conf
Good call, I think i've comment out the "fi" as well. Will amend and report
back as soon as this report is sent.
Thanks!
** Attachment added: "plymouth.txt"
http://launchpadlibrarian.net/41069422/plymouth.txt
--
boot hangs on splash screen, doe
To avoid errors, copied and paste your plymouth.conf. However result is
same; ie, plymouth splash does not appear at boot up (but boots okay to
lucid).
Thanks again.
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug notification b
Added Scott's ppa to repo, rebooted. same as before (boots to lucid okay, no
plymouth splash).
Rebooted to be sure, and (luck of luck), the plymouth splash appears with the
disk check (for 30 mounts).
And to make doubly sure, rebooted one more time, (of course disk check will not
be there); the
Okay, thanks a lot, everybody.
Have fun. I sure did.
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kubuntu-bugs mail
Problem solved. See bug 538524. Problem is traced to plymouth splash screen
where kdm is not booted.
Thanks.
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
A better way to boot 2.6.32-16 is to modify grub.cfg to remove splash and quiet.
Since this had happened earlier in Karmic alpha, just wondering if this is
something unavoidable.
(not a criticism, just trying to understand). If this is due to programming
constraints, that is quite alright as alp
Removing "nouveau" interface solved the problem. Can boot with quiet and splash.
However 'plymouth' still starts with error.
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Here's the attached lspci, dmesg and Xorg log. No xorg.conf file.
Thanks.
** Attachment added: "xorg.txt"
http://launchpadlibrarian.net/40907376/xorg.txt
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, w
One file per message? here's lspci
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/40907385/lspci.txt
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
And dmesg
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/40907398/dmesg.txt
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
By any chance did you install plymouth? If yes, you may encounter problems.
Refer
https://bugs.launchpad.net/bugs/538524.
If no, you may want to try out new nvidia driver 'nouveau'.
--
KDM skips login screen and hangs while trying to load KDE
https://bugs.launchpad.net/bugs/528926
You received
I reported on bug 437283
However 2.6.32-15-generic boots okay.
Goh Lip
** Affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
--
kdm does not start
https://bugs.launchpad.net/bugs/537853
You received this bug notification because you are a member of Kubuntu
Bugs
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33230838/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/33230839/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/33230840/ProcStatus.txt
--
Burnin
Public bug reported:
Burning image files in K3b does not terminate.
Need to force quit K3b after completion of job.
ProblemType: Bug
Architecture: amd64
Date: Wed Oct 7 22:13:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.2-0ubuntu1
ProcEnviron:
Latest update of 8th Oct resolved problem.
Thanks.
--
Burning image file in K3b does not terminate
https://bugs.launchpad.net/bugs/445472
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.ubun
I am not sure if this information is important, but after kernel change
to 2.6.31-7-generic, there is now 2 entries of old and new UUID for the
Hardy sda8 partition.
Under header of " Ubuntu Linux", it shows the new and correct UUID.
Under header of " Debian GNU/Linux", it shows the old and wrong
Public bug reported:
Karmic 64
Kernel 2.6.31-7
Kde 4.3.00
After kernel change to 2.6.31-7, shutdown or reboot hangs at prompt with
following message...
Checking for unattended-upgrades: *Asking all remaining processes to
terminate
Noted that /var/log/unattended-upgrades/ is empty.
** Affects:
Thanks, Scott and Robbie, I had just downloaded and reinstalled Alpha6
in the same partition about 2 hours ago and fully updated and uploaded,
so I am unable to replicate my previous problem now. If it helps,
Robbie, I am sure the sudo apt-get update and upgrade showed no packages
to install or be
Public bug reported:
After update to 2.6.31-11-generic today, system boots to login prompt.
To go to kdm, have to login and at prompt, enter sudo kdm start.
ProblemType: Bug
Architecture: amd64
Date: Sun Sep 27 01:04:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kd
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32492467/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/32492468/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/32492469/ProcStatus.txt
--
kdm do
Latest update of kde 4.4 rc1 on 12th Jan resolved problem.
--
gdm does not start X unless remove "tty-device-added KERNEL=tty7" from upstart
gdm.conf
https://bugs.launchpad.net/bugs/491162
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Issuing "halt" command in grub prompt reboots the computer instead of
shutting down completely. This happens only in UEFI systems and not in
bios-legacy which works as it should. Computer does power down but
restarts again.
Also, this happens in some mother boards but not oth
Thanks. Tested 2.02~beta2-35 and confirm halt works in uefi.
Also in bios-legacy, halt command works completely to shutdown.
Prior to this, in bios-legacy, 'halt' hangs and does not reboot.
So confirm this update fixes both uefi and bios-legacy to complete
computer shutdown.
--
You received this
Adam, you're right in your original post that initrd is the cause of the delay.
Other non-Ubuntu based distros do not have the long 50 secs wait to boot OS at
usb. (same kernel)
It's just 13 secs vs 50secs. (haven't tried Debian distros).
One would think after 5 years, something ought to be done
Is this related to this bug?
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/577120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669023
Title:
boot screen takes about 90 seconds between grub a
Is this related to this bug?
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/577120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577120
Title:
Grub 2 long delay while loading Ubuntu kernel
To
Sorry, I meant to write the above comment on this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/669023
Apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577120
Title:
Grub 2 long d
I think the problem is more widespread.
See
https://answers.launchpad.net/ubuntu/+question/155990
https://answers.launchpad.net/ubuntu/+question/156370
https://answers.launchpad.net/ubuntu/+source/grub2/+question/156252
https://answers.launchpad.net/mythbuntu/+question/156239
--
You received thi
Lubuntu Maverick alpha 3 exhibits same problem, I renamed "gnome-power-
backlight-helper" to "gnome-power-backlight-helper_somethingelse" and
problem disappeared.
--
[Maverick Alpha] asks for root permission to do: gnome-power-backlight-helper
--get-max-brightness
https://bugs.launchpad.net/bugs
51 matches
Mail list logo
