Bug 170432

Summary:	several hd accessing (causing wake ups) from konsole
Product:	[Applications] konsole	Reporter:	Bráulio Barros de Oliveira <brauliobo>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	robertknight
Priority:	NOR
Version:	2.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bráulio Barros de Oliveira 2008-09-05 01:52:28 UTC

Version:           2.2 (using 4.1.64 (KDE 4.1.64 (KDE 4.2 >= 20080828)), compiled sources)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.26-ARCH

hello,

as I was pursuing less watts consumption on my computer, the hd was the last target.

after some help from the lkml list, i could trace the problem (http://lkml.org/lkml/2008/9/4/499). noatime and nodiratime options did it!

but after going back to kde, the hd clicks (i'm using hd apm set to 128) came back.
after killing konsole it almost disappeared.

the konsole had tabs with powertop, iotop and htop, and no keyboard activity was on (so no bash history access).

that's all.
bráulio

Comment 1 Robert Knight 2008-09-05 11:34:26 UTC

> the konsole had tabs with powertop, iotop and htop,
> and no keyboard activity was on (so no bash history access). 

If you have applications running in Konsole then of course it will use power to process the output from them and refresh the screen.  

I'm not sure where the HDD activity is coming from but apart from the blinking cursor (if you have it enabled), Konsole should not be waking up regularly for anything while idle.

Do you still see HDD activity caused by Konsole while it has no running applications?

Comment 2 Bráulio Barros de Oliveira 2008-09-11 18:10:04 UTC


*** This bug has been marked as a duplicate of bug 170868 ***

Comment 3 Pino Toscano 2008-09-11 19:07:31 UTC

Sorry, but you don't dup specific bugs for general (and too generic) ones.

Comment 4 Robert Knight 2008-09-22 04:14:47 UTC

I cannot reproduce this locally.  Konsole sits idle as it is supposed to when nothing is running in the terminal.  If you have running applications in the terminal then of course it will wake up to print the output from them.  

If you can point more specifically to circumstances under which Konsole is waking up when it shouldn't be then I'll re-open this.