** Changed in: ubuntu-release-notes
Status: In Progress => 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/1171099
Title:
kubuntu - plymouth not shown
To manage notifications abou
** Description changed:
+ === Release notes text ===
+
+ On boot of the installed system the graphical display is not initialised
+ until late in the boot exposing boot messages unnecessarily. Updating
+ kubuntu-settings will resolve this for subsequent boots.
+
+ ===
+
SRU: kubuntu-settings
Should be fixed through grub postinst fixes in saucy.
** Changed in: kubuntu-settings (Ubuntu Saucy)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.ne
** Branch linked: lp:ubuntu/saucy-proposed/grub-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about this bug go to:
htt
** Changed in: kubuntu-settings (Ubuntu Saucy)
Milestone: None => ubuntu-13.10
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To
This bug was fixed in the package kubuntu-settings - 1:13.04ubuntu12
---
kubuntu-settings (1:13.04ubuntu12) raring-proposed; urgency=low
* No-change upload to trigger update-grub to ensure that the boot entries
contain 'quiet splash' (LP: #1171099)
-- Harald SitterMon, 29 A
OK, then you are experiencing a different bug than this one (even though
the symptoms are similar). You should file a new bug.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/117109
I follow your advice, Scott. To fixe that bug i've reinstalled my OS (great
logic).
On the bootable key and after the install, on the first boot, plymouth was ok.
But on my system, KDE and all the system totaly freeze with the free
graphic driver.
On rescue mode, i've installed nvidia-current (3
On a fresh install, it was fixed for me once I ran the updates and
rebooted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about
** No longer affects: ubiquity (Ubuntu)
** No longer affects: ubiquity (Ubuntu Raring)
** No longer affects: ubiquity (Ubuntu Saucy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
ku
Other people can confirm that is really fixed?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about this bug go to:
h
Don't use the beta images anymore. Use the final ones. Do the install
with those, then update to the proposed packages. If that doesn't solve
it, you have a different bug. Also, this is still fix committed, since
the new package hasn't been released to -updates yet.
** Changed in: kubuntu-sett
I made a clean install (except home partition) of Kubuntu 13.04 beta. I
made all updates including proposed packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth
Then it's a different issue, unless you were doing upgrades during
installation which may not work around that (IIRC updates are installed
before grub-installer is ran). To that extent the fix is only partial,
but I don't think there is much opportunity for improvement
unfortunately, due to exactly
Not fixed for me with the proposed packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about this bug go to:
https://bugs.lau
** Changed in: kubuntu-settings (Ubuntu Raring)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
T
** Branch linked: lp:ubuntu/raring-proposed/kubuntu-settings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about this bug go to:
Fix for me too, but jump into bug 1083190
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not s
The proposed raring problem resolves the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - p
Analysis of the problem:
slangasek, ScottK: I think kubuntu-settings-desktop (providing
etc/default/grub.d/05_kubuntu.cfg) needs to pre-depend grub-pc ...
grub-pc.postinst looks for etc/default/grub OR etc/default/grub.d/* and if
found it will try to read the grub_default_cmdline from there, h
Hello Fabio, or anyone else affected,
Accepted kubuntu-settings into raring-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/kubuntu-
settings/1:13.04ubuntu12 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu Raring)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs
"quiet splash" in present in /etc/default/grub but i (still) have this
issue.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifi
** Description changed:
+ SRU
+
+ [Impact]
+ After installation Kubuntu will not show a boot splash until update-grub is
triggered. Instaed it will display native tty output which not only looks bad
but can worry users for no good reason (such as bluetooth daemon startup saying
'fail' simp
** Also affects: kubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kubuntu-settings (Ubuntu)
Status: New => Triaged
** Changed in: kubuntu-settings (Ubuntu)
Importance: Undecided => Medium
** Changed in: kubuntu-settings (Ubuntu)
Assignee: (unass
Suggested text for a release note:
A bug in the installer for Kubuntu 13.04 causes users to be shown a
console screen with verbose kernel messages after install instead of the
expected Kubuntu splash screen. Users can work around this bug by
running the following commands:
sudo sed -i -e's/^G
** Also affects: ubuntu-release-notes
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/1171099
Title:
kubuntu - plymouth not shown
To manage notifications a
I have just reproduced this problem here in a VM. Apparently, a
freshly-installed Kubuntu 13.04 system does not set either 'quiet' or
'splash' in the kernel commandline. Reassigning to ubiquity.
** Package changed: plymouth (Ubuntu) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
S
> ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic
root=/dev/mapper/kubuntu--vg-root ro
This shows that your system has been booted without the 'splash' option
- so the console-only prompt is the expected behavior. Was this how the
bootloader was configured after install, or are you doing somet
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
k
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171099
Title:
kubuntu - plymouth not shown
To manage notifications about this bug go
** Summary changed:
- kubuntu - plymouth not showed
+ kubuntu - plymouth not shown
** Description changed:
Hallo
- Testing kubuntu 20130421 amd64, at the start plymouth is not showed, only vt.
+ Testing kubuntu 20130421 amd64, at the start plymouth is not shown, only vt.
Attached screenshot
32 matches
Mail list logo
