Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229130 - kdebase: Suspend button can not be disabled
Summary: kdebase: Suspend button can not be disabled
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-17 18:14 UTC by Jonathan Rawle
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:14:51 UTC

Attachments (Terms of Use)

Description Jonathan Rawle 2007-02-17 18:14:30 UTC
Description of problem:

The suspend/hibernate button that was recently added to the logout dialogue can
not be disabled. The patch appears to hard-code them in so that they can only be
disabled along with shutdown/reboot, and not independently. The path of the
commands for shutdown and hubernate are also hard-coded.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log in to KDE
2. Log out
3. Note "Suspend Computer" button (changes to Hibernate when shift key pressed)
Actual results:
Suspend button is always in dialogue. No options to remove or configure it.

Expected results:
Some method to disable the Suspend button, even if it means editing a
configuration file.

Additional info:
Suspend and hibernate do not work correctly on my system, so I not not want
users to use it. However, I do want them to be able to shut the system down
cleanly. So the option to add these buttons needs to be separate from the option
to allow shutdown/reboot.

Comment 1 Rex Dieter 2007-06-20 15:06:56 UTC
Than, any chance of implementing this, or WONTFIX (but patches happily accepted)?

Comment 2 Bug Zapper 2008-04-04 06:16:16 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 3 Bug Zapper 2008-05-06 19:14:49 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.