We need more information then that to narrow the problem because i'm not able to reproduce at all here.
For example have you got some nfs/samba/usb share available when it's happening ?

CC: (none) => balcaen.john

I've seen this too, and not just after login.  The problem is, I think, related to unresponsive NFS mounts.  KDE in general, and Dolphin in particular, is *way* too sensitive to these and appears to wait many seconds, sometimes minutes,for them to respond.  The KDE file chooser seems to have a similar problem.

You should be able to reproduce it by mounting an NFS share and then shutting down the system exporting it.

CC: (none) => ftg

Stuff work fine since I use 4 others distrib mageia1 and mandriva2010.2 (each 32 & 64 bits versions) and fortunately I have no problem with them.
More generally, problems occur with distrib based on the new kernel 3.xxx (mageia2, fedora16) when the 4 above mentioned distrib are based on the "old" but reliable kernel 2.6.xxx.
Perhaps problems come from the fact that I have an old stuff (Intel Q9550 on socket 775).

Status: NEW => REOPENED

(In reply to comment #2)
> I've seen this too, and not just after login.  The problem is, I think, related
> to unresponsive NFS mounts.  KDE in general, and Dolphin in particular, is
> *way* too sensitive to these and appears to wait many seconds, sometimes
> minutes,for them to respond.  The KDE file chooser seems to have a similar
> problem.
> 
> You should be able to reproduce it by mounting an NFS share and then shutting
> down the system exporting it.
I'm aware of the nfs problem (cf https://bugs.kde.org/show_bug.cgi?id=158606 ). here i wanted to know the condition of this freeze.

(In reply to comment #3)
> Stuff work fine since I use 4 others distrib mageia1 and mandriva2010.2 (each
> 32 & 64 bits versions) and fortunately I have no problem with them.
> More generally, problems occur with distrib based on the new kernel 3.xxx
> (mageia2, fedora16) when the 4 above mentioned distrib are based on the "old"
> but reliable kernel 2.6.xxx.
> Perhaps problems come from the fact that I have an old stuff (Intel Q9550 on
> socket 775).
It does not really help to narrow the problem here.
Did you try using an « old » kernel on your mageia2 ?
Also please do not change the bug status to Reopened since this bug was never closed.

Status: REOPENED => NEW

I have tried to boot mageia2 using kernel 2.6.38.8; it didn't work and splash stopped at midboot.
Worse: when booting mageia2 with 3.3.6 kernel; it ruins my mdadm-builded backup raid6 volume (level=6, raid-devices=6, metadata=1.2) by removing one or two components. This doesn't happen with kernel-2.6.38xxx based distributions.
I have to rebuild it using mageia1 by security, but it wastes times.
Furthermore, when opening mail client thunderbird, with mageia2, it needs delay before my imap gmail account be synchronized; it's not the case under mageia1, the synchronization is immediately done.
The same when opening firefox (server is not found, please try again...)

I have natively reinstalled mageia2-x86_64, that is, I haven't upgraded an already existing mageia1, and the bug disappeared; just after logged in, opening any applications is a little bit slow, but after everything normally work.
Upgrading mageia1 with mageia2 seems bring some troubles

Status: NEW => RESOLVED
Resolution: (none) => FIXED