Bug 230688 - Kde lacks buttonevent to pm-utils setup tool
Summary: Kde lacks buttonevent to pm-utils setup tool
Status: RESOLVED DUPLICATE of bug 221715
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Danny Al-Gaaf
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-23 13:34 UTC by Kristian Alvestad
Modified: 2007-01-02 10:28 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristian Alvestad 2006-12-23 13:34:24 UTC 
I still have not been able to make my laptop go to s2ram by closing the lid. I am unable to change the behaviour of the buttons at all in KDE. This is a severe flaw in 10.2, There should not be such switches to new software (from powersaved to pm-utils) without presrving the current featureset.

I smell NIH syndrome (allthough i thought powersaved was invented here)
Comment 1 Siegfried Olschner 2006-12-24 08:36:50 UTC 
Kristian, thank you for the feedback. But please please provide vendor and type of your laptop and describe the application and the buttons more precise. No one here knows _all_ tools, features and options.

Stefan, I think it's your turn, changed component to "mobile devices".
Comment 2 Stefan Behlert 2006-12-29 19:49:08 UTC 
You are talking about the configuration of the button events in kpowersave? That will be solved with an update. Please open a separate bug for the non-working s2ram, and have a look at the opensuse-pages for hints.
Comment 3 Danny Al-Gaaf 2007-01-02 10:28:15 UTC 
Due to comment #2 please open a new bug for s2ram.

Btw. please check for already existing bugs before open a new one the next time. This save time for you and us. This is a duplicate of 221715

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