[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 264730] monitor is powered off after 10 minutes although contrary powerdevil settings
From:       Dario Freddi <drf () kde ! org>
Date:       2012-01-20 12:29:40
Message-ID: E1RoDbA-0005jK-QD () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=264730





--- Comment #44 from Dario Freddi <drf kde org>  2012-01-20 12:29:40 ---
First of all, I remember you I am not paid for doing that, and I'd gladly avoid
taking orders from somebody who's currently getting in the way of my (free)
work and most of all, not paying me. Please fix your attitude if you want to
help keeping a constructive discussion.

I linked you the new bug I am tracking for this issue, and I NEVER said I am
not fixing this bug, which is something you totally made up - I said this
specific bug report tracks too many different causes and hence is no longer
useful for tracking this issue. Got the difference? If you can find the part
where I say "I do not care about this bug and will never fix it" I will gladly
offer you a beer, but I am afraid you won't get one, because I never said that.

Your profiles are 1) from an older KDE version 2) currently not enough and
hardly useful for tracking the issue. Wonder why at this stage those
information are insufficient? The bug described initially in this thread is
probably fixed in 4.8 for the cause described in THIS report, but likely
reappeared thanks to another change, and I was able to find that out thanks to
Garth, who has been kind enough to follow my directions and giving out some
concrete help. Now, would you still use a bug which has outdated, misleading,
and confusing information for tracking this issue, which is proven to be
different?

Now, please continue the discussion on the new bug (which is bug 291926) to
make everyone's life easier (the bug needsinfo, maybe you can provide them),
since I think I provided enough reasons why this issue should be disregarded.
If bug 291926's symptoms does not match yours, you are more than welcome to
open a new issue detailing your symptoms and possibly attaching a log of kded4,
which at this stage is probably the only useful data, since I just double
checked today there is apparently no issue in profile handling which might lead
to such a behavior. The problem likely lies in faulty inhibition (which is
291926 case) or faulty initialization of the action (which is something I am
unable to reproduce here).

Just to end that, I urge everybody to stop commenting on this issue once again,
since we're wasting everyone's time here.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]