[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#345500: marked as done (klaptopdaemon does suspend-to-RAM on kde startup)

Your message dated Fri, 6 Mar 2009 01:28:36 +0530
with message-id <200903060128.38381.rrs@researchut.com>
and subject line Closing Bug
has caused the Debian Bug report #345500,
regarding klaptopdaemon does suspend-to-RAM on kde startup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
345500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345500
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: klaptopdaemon
Version: 4:3.4.3-2
Severity: normal


Since the author didn't open the bug and it was getting archived in a
week, I'm opening this new bug report.

I'm afraid to say that this defect is still not fixed in
klaptopdaemon-3.4.2

The automatic suspend problem of as soon as klaptopdaemon starts up when
KDE is started, is still there. If I remove the rc file for klaptopdaemon
and start KDE, it works. But then when I again configure klaptopdaemon and
select "Suspend" in the "Button Actions" tab for "LID Close Switch" and
select Apply, the laptop goes into and endless loop of suspend (susped-to-RAM).

Note: I've got another laptop (Dell D600) on which this particular issue isn't
seen, though that laptop doesn't resume at all, instead upon resume it simply
resets the machine. Let's not get into this laptops problem. This was just
for your information that maybe it could help you.

So, since another make laptop isn't having exactly the same problem, I
come up with this question in my mind. Maybe you could answer it.
On Default/Stock Linux Kernels where Suspend1 is the only suspend
mechanism, how does klaptopdaemon handle "suspend-to-RAM" and "suspend-to-DISK".
If it does that with the help of ACPI, then we might narrow it down
hoping that the ACPI support for my actual laptop (against which this defect
was filed) has a broken ACPI implementation.

If klaptopdaemon doesn't use ACPI and uses some other mechanism of its
own to trigger "suspend-to-RAM" and "suspend-to-DISK" events, then definitely
it should be a klaptopdaemon related defect which still isn't fixed in
3.4.2

Thanks for all your effort and patience.

Regards,

rrs
-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-skas3-v8.2
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages klaptopdaemon depends on:
ii  kdelibs4c2a              4:3.4.3-2       core libraries for all KDE applica
ii  libc6                    2.3.5-8         GNU C Library: Shared libraries an
ii  libgcc1                  1:4.0.2-5       GCC support library
ii  libqt3-mt                3:3.3.5-1       Qt GUI Library (Threaded runtime v
ii  libstdc++6               4.0.2-5         The GNU Standard C++ Library v3
ii  libxtst6                 6.8.2.dfsg.1-11 X Window System event recording an

klaptopdaemon recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Closing this because klaptopdaemon is part of KDE3 and is not maintained 
anymore.

Ritesh
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

--- End Message ---
Reply to: