Bug 588074 - Cannot reboot from LXDE logout window
Summary: Cannot reboot from LXDE logout window
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: lxsession
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 14:27 UTC by Michael Monreal
Modified: 2010-05-02 16:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-02 16:58:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Monreal 2010-05-02 14:27:21 UTC
I can shut down but not reboot the system from rge LXDE logout window. I can reboot using LXDM just fine.

Comment 1 Christoph Wickert 2010-05-02 15:16:19 UTC
I can shutdown and reboot just fine from LXDE and your description is too sparse to understand your problem. When you report a bug, please be so kind as to fill out all necessary fields, e.g.

Description of problem:
I can shut down but not reboot the system from rge LXDE logout window. I can
reboot using LXDM just fine.    

Version-Release number of selected component (if applicable):
should be lxsession-0.4.4-1.fc13 I guess, run rpm -q lxsession to verify.

How reproducible:
sometimes/often/always

Steps to Reproduce:
1. what exactly
2. did you
3. do?
  
Actual results:
What happens instead of rebooting?

Expected results:
System should reboot

Additional info:
Is SELinux turned on or off? Please give me the output of "getenforce".
Are there any more users logged in? Note that lxsession will not allow you to shutdown or reboot when you are not the only user. Please give me the output of ck-list-sessions before you reboot.

Comment 2 Michael Monreal 2010-05-02 16:58:07 UTC
Running lxsession-0.4.4-1.fc13, right.

It used to happen every time I tried but now I tried again and it worked perfectly... I am not aware of any changes I did to the system which would cause this, so closing for now...


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