Bug 853961
| Summary: | power-off/reboot results in log out after a long timeout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||
| Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | awilliam, collura, jmccann, lmacken, mclasen, robatino, rstrode | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-10-03 08:02:30 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752660 | ||||||
| Attachments: |
|
||||||
|
Description
Kamil Páral
2012-09-03 12:28:13 UTC
Created attachment 609368 [details]
messages after attempt to power off
" All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work " https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria Just to be clear, this is a bug about the power menu on the login screen ? Or about the power off menu item in the user menu in the session ? User menu in the session. There was a similar bug caused by selinux, I should re-test this whether it is still broken or not. Discussed at 2012-09-26 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-09-26/f18-beta-blocker-review-1.2012-09-26-16.03.log.txt . As reported it would be a blocker, but Kamil says he hasn't seen it lately, and other testers running F18 (myself and viking-ice) reported that we had not seen this issue, so it doesn't seem to be that straightforward. We agreed to delay the decision on this bug while Kamil re-tests it and others see if they can trigger it. This seems to work well now: selinux-policy-3.11.1-25.fc18.noarch systemd-188-3.fc18.x86_64 gdm-3.6.0-1.fc18.x86_64 gnome-session-3.6.0-1.fc18.x86_64 |