KDE Login screen appears before fsck is finished with home partition

Bug #497662 reported by RProgrammer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Base
Unknown
High
kdebase-kde4 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I use Kubuntu 9.10 with KDE 4.3.2
My home folder is on its own partition (which is much larger than the root partition).

When fsck runs on boot, as it does periodically, it scans both my root and home partitions.
However, before it's finished with the home partition, the login screen appears and quickly replaces the fsck messages.
If I'm not quick enough to catch that fsck is running and try to log in, all heck breaks loose since my home folder is empty.
I can watch fsck by switching to the F8 tty, but I have to know to do that.

ProblemType: Bug
Architecture: i386
CRDA:
 country 98:
  (2402 - 2472 @ 40), (3, 27), NO-OUTDOOR
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x90440000 irq 22'
   Mixer name : 'SigmaTel STAC9221 A1'
   Components : 'HDA:83847680,106b0a00,00103401'
   Controls : 22
   Simple ctrls : 14
DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Date: Thu Dec 17 01:38:41 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=187d787a-9377-474e-9f4b-0eef8e2a9f5e
HotplugNewDevices:

HotplugNewMounts:

MachineType: Apple Computer, Inc. MacBook1,1
Package: linux-image-2.6.31-16-generic 2.6.31-16.53
ProcCmdLine: root=UUID=bee7e834-cd79-4467-8c27-fbf200e504aa ro quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-16-generic N/A
 linux-firmware 1.25
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
Uname: Linux 2.6.31-16-generic i686
UserAsoundrc:

UserAsoundrcAsoundconf:

WpaSupplicantLog:

XsessionErrors:
 (polkit-gnome-authentication-agent-1:2082): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (evince:29872): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/sean/.recently-used.xbel', but the parser failed: Failed to open file '/home/sean/.recently-used.xbel': Permission denied.
 (evince:29872): Gtk-WARNING **: Attempting to store changes into `/home/sean/.recently-used.xbel', but failed: Failed to create file '/home/sean/.recently-used.xbel.R1804U': Permission denied
 (evince:29872): Gtk-WARNING **: Attempting to store changes into `/home/sean/.recently-used.xbel', but failed: Failed to create file '/home/sean/.recently-used.xbel.34904U': Permission denied
 (evince:29872): Gtk-WARNING **: Attempting to store changes into `/home/sean/.recently-used.xbel', but failed: Failed to create file '/home/sean/.recently-used.xbel.KCQW4U': Permission denied
dmi.bios.date: 10/12/06
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MB11.88Z.0061.B03.0610121324
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.version: Mac-F4208CC8
dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMB11.88Z.0061.B03.0610121324:bd10/12/06:svnAppleComputer,Inc.:pnMacBook1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208CC8:rvrPVT:cvnAppleComputer,Inc.:ct10:cvrMac-F4208CC8:
dmi.product.name: MacBook1,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

Revision history for this message
RProgrammer (h-root-rprogrammer-net) wrote :
Andy Whitcroft (apw)
tags: added: karmic
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

I am making an educated guess that this is the right package. I'm not sure if there should be a check by X to confirm fsck has completed before calling xdm/kdm or if kdm should check to see if fsck is still working on the home directory before prompting the user for a login.

affects: linux (Ubuntu) → kdebase-kde4 (Ubuntu)
Changed in kdebase-kde4 (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

https://bugs.kde.org/show_bug.cgi?id=219141

Thank you for taking the time to report this bug and helping to make Ubuntu better!

Changed in kdebase-kde4 (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

  ------- Comment #1 From Oswald Buddenhagen 2009-12-18 14:53:36 -------

not our fault if ubuntu fails to get the boot sequence right ...

Changed in kdebase-kde4 (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

I am not sure who should get involved but this bug sounds pretty serious. The KDE folks believe this is a Ubuntu issue. I asked for feedback and clarification upstream but they are ignoring me.

In either case this should be relatively easy to fix but preventing KDE from launching prior to fsck completing.

Revision history for this message
Dave Walker (dogatemycomputer) wrote :

 RProgrammer:

I am not sure how comfortable you are with scripting but I do not see why we could not write a short workaround script that would prevent X from launching until after fsck has completed. It could be a short loop to confirm fsck has completed and if not then sleep for some period of time.

We could do this as a startup service (/etc/rc5.d), in /etc/X11/init/initrc or in /etc/X11/Xsession. Of course any updates to the latter two files would probably mean any changes would be overwritten.

Hopefully others will chime in with their own solutions until we can get you an official fix.

Revision history for this message
RProgrammer (h-root-rprogrammer-net) wrote :

Thanks, but it's not a critical problem, just annoying.

Changed in kdebase:
status: Unknown → Invalid
Changed in kdebase:
status: Invalid → Unknown
Changed in kdebase:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.