On Sunday 09 May 2010 14:34:11 Roman Naumann wrote:
> On Friday 07 May 2010 20:26:46 András Csányi wrote:
> > On 7 May 2010 19:33, Roman Naumann <firstname.lastname@example.org> wrote:
> > > Hi,
> > >
> > > when I suspend my computer, KDE locks the session. This usually
> > > happens, when I close my laptop lid.
> > >
> > > When I open it again, it takes 1 to 20 seconds (seamingly random)
> > > untill the login screen appears. During this time, I just see a black
> > > screen and a mouse pointer (somewhere), but I cannot move it.
> > Suspend is that when the computer isn't off just the things stays in
> > memory, isn't? When the contents of the memory is writed to the disk
> > and the machine is get off that is the hibernate function, isn't?
> > It is possible that when you close the lid the contents of memory
> > writed to the disk and reading this few hundred Mbyte - on my laptop
> > KDE is eating ~800 Mbyte memory, the hungry Beast!
- takes that
> > long time what you mentioned?
> > I'm not a big hacker just I'm thinking over it. :$
> Hmm, I guess I should have specified what kind of 'suspend' I meant:
> Suspend to ram. Not suspend to disk!
> When I close the laptop lid, kde does NOTHING but lock the screen. I
> disabled all other power management actions in kde's systemsettings.
> The suspend is done by a script independend of kde, and that's working just
> fine. It's only kde taking that long..
> Even if kde ignored my settings and writes and reads stuff from disk when I
> close/open the laptop lid: A second after I close the lid, the LED on the
> laptop begins to blink, saying that the computer is suspended to ram.
> Kde could never write the whole ram to disk in that second.
What does your resume script look like?
I'm thinking maybe you have hardware that is taking ages (or is just
unreliable) to wake up and resume, and kde depends on that hardware. Video
drivers and wireless ethernet comes to mind.
alan dot mckinnon at gmail dot com