© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello!
Sorry for my bad english... ;-)
I'm a newbies with Linux Mint 9 KDE. But, i'm "ubuntu's fan" since 2006...
I've installed LM9 KDE on two machines, the first one : acer P4, 1.5 gig ram and Intel GMA. The second : Dell Inspiron 6000, 512 mo ram and Intel chipset GMA.
Both have the problem. The package mountall 2.15 is up to date like ubuntu lucid. On ubuntu lucid, no problem (see this bug report : https:/
If i press ESC to go back under plymouth and i press "C" key, the the boot finished with no problem or the boot stalls with a blank screen and the message "GLib-WARNING **: getpwuid_r(): falied due to unknown user id (0)". If i press right arrow key instead of C under plymouth, the boot finished without problems.
I think that there are two problems in this bug (two questions in fact) :
1) Fsck is really finished when plymouth stalls ? If yes, is not a big problem, "press right arrow key" continues the boot process. "Press C" abort the scan, is not a solution to prevent disk errors.
2) What process causes the problem? Mountall ? Plymouth? Ureahead ? I've read that one user have uninstalled Ureahead package and he shall have no problems after. I've not tested. I don't find this forum...
Anyone can confirm that the fsck process is good and finished BEFORE the problem occurs and if the disk is safe or not? It's important for the security and the stability of the system. (disk crashs, errors no repared, ...) If the fsck prosess is good and finished, press "right arrow key" continues the boot without problem. Modify fstab files is not a good idea for me.
Thank's!