Hmmm. I fail to see how KLaptopDaemon has anything to do with a bug report
against KWin? The problem (if it still exists) is in a combination of kwin
and laptop-mode-tools, which as nothing to do with KLaptopDaemon.

Cheers,
Bart

On Thu, Mar 4, 2010 at 04:51, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the kwin package:
>
> #364119: kwin writes to disk synchronously
>
> It has been closed by Olivier Vitrat <ovit.deb...@gmail.com>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Olivier Vitrat <
> ovit.deb...@gmail.com> by
> replying to this email.
>
>
> --
> 364119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364119
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> ---------- Forwarded message ----------
> From: Olivier Vitrat <ovit.deb...@gmail.com>
> To: 364119-d...@bugs.debian.org, 364119-qu...@bugs.debian.org
> Date: Wed, 3 Mar 2010 22:48:38 -0500
> Subject: Closing Debian bug 364119
> Hello,
> This is no longer maintained.
> See the comment at https://bugs.kde.org/146789
> "  -------  Comment #2 From  Dario Andres   2010-02-26 14:09:00   (-)
> [reply] -------
>
> I have personally contacted the KLaptopDaemon author/assigned and he
> confirmed
> that the tool is deprecated in KDE SC 4 (replaced by PowerDevil) and that
> there
> are no current efforts to support/maintain the KDE SC 3 version.
> Because of this, I will close the reports as UNMAINTAINED.
> Regards"
>
> I'm also closing the Debian bug report
> thanks
> Olivier
>
>
>
> ---------- Forwarded message ----------
> From: Bart Samwel <b...@samwel.tk>
> To: sub...@bugs.debian.org
> Date: Fri, 21 Apr 2006 18:09:19 +0200
> Subject: kwin writes to disk synchronously
> Package: kwin
> Severity: normal
>
> Hi there,
>
> I got a report from a laptop-mode-tools user saying that kwin kept his disk
> spun up. I checked his logs, and indeed it seems to be the case that his
> kwin process explicitly syncs pretty regularly. I straced my own kwin to
> confirm this behaviour, and I see the following:
>
> open("/home/bsamwel/.kde/share/config/kwinrulesrc6EREMa.new",
> O_RDWR|O_CREAT|O_EXCL, 0600) = 11
> umask(0)                                = 022
> umask(022)                              = 0
> fchmod(11, 0600)                        = 0
> getgid32()                              = 1000
> getuid32()                              = 1000
> fchown32(11, 1000, 1000)                = 0
> fcntl64(11, F_SETFD, FD_CLOEXEC)        = 0
> stat64("/home/bsamwel/.kde/share/config/kwinrulesrc",
> {st_mode=S_IFREG|0600, st_size=824, ...}) = 0
> getuid32()                              = 1000
> getgid32()                              = 1000
> fchmod(11, 0100600)                     = 0
> fchmod(11, 0600)                        = 0
> fcntl64(11, F_GETFL)                    = 0x2 (flags O_RDWR)
> fstat64(11, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0xb6705000
> _llseek(11, 0, [0], SEEK_CUR)           = 0
> write(11, "[1]\ndescription=(Default) Disabl"..., 824) = 824
> fdatasync(11)                           = 0
> close(11)                               = 0
> munmap(0xb6705000, 4096)                = 0
> rename("/home/bsamwel/.kde/share/config/kwinrulesrc6EREMa.new",
> "/home/bsamwel/.kde/share/config/kwinrulesrc") = 0
>
>
> and then:
>
>
> open("/home/bsamwel/.kde/share/config/kdeglobalsZbum9a.new",
> O_RDWR|O_CREAT|O_EXCL, 0600) = 11
> umask(0)                                = 022
> umask(022)                              = 0
> fchmod(11, 0600)                        = 0
> getgid32()                              = 1000
> getuid32()                              = 1000
> fchown32(11, 1000, 1000)                = 0
> fcntl64(11, F_SETFD, FD_CLOEXEC)        = 0
> stat64("/home/bsamwel/.kde/share/config/kdeglobals", {st_mode=S_IFREG|0600,
> st_size=5804, ...}) = 0
> getuid32()                              = 1000
> getgid32()                              = 1000
> fchmod(11, 0100600)                     = 0
> fchmod(11, 0600)                        = 0
> fcntl64(11, F_GETFL)                    = 0x2 (flags O_RDWR)
> fstat64(11, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0xb6705000
> _llseek(11, 0, [0], SEEK_CUR)           = 0
> write(11, "[$Version]\nupdate_info=kded.upd:"..., 4096) = 4096
> write(11, "ndow to Desktop 2=none\nWindow to"..., 1708) = 1708
> fdatasync(11)                           = 0
> close(11)                               = 0
> munmap(0xb6705000, 4096)                = 0
> rename("/home/bsamwel/.kde/share/config/kdeglobalsZbum9a.new",
> "/home/bsamwel/.kde/share/config/kdeglobals") = 0
>
>
> So, here's my question: is that call to fdatasync() really necessary? And
> can it be disabled somehow? It makes laptop mode pretty much unusable on
> KDE. :-(
>
>
> Cheers,
> Bart Samwel
>
>
>

Reply via email to