| Summary: | shutdown via menu applet randomly fails to completely shut down computer | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Beard <zytemp2g> |
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | bmillett, danw, maxamillion, otaylor, samkraju, vastone, walters |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.91.93 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-08 20:40:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dan Beard
2011-03-28 12:49:38 UTC
Can you be more specific about what happens? Does it look like you're even getting logged out? Does it drop you to a tty or the Fedora logo boot screen? When you say "lock-up", does that mean that the mouse stops moving? Ctrl+Alt+F2 doesn't work to get you to a tty? Or just that the UI is still fully present, but dimmed out and non-responsive? After [ALT]+"Power off" from menu: A dialog pops up asking if you want to shut down. Clicking the OK button is immediately followed by a slight darkening of the screen, mouse can be moved, but nothing will activate from the top panel. It just sits there until I either hard power button it off, or [ctrl]+[alt]+[del] or [ctrl]+[alt]+[bkspc]. The latter will then bring GDM up and I can power off via the panel icon. Does that explain it well enough for what you need? ah, good. that was a mismatch between gnome-shell and gnome-session packages. It's fixed if you have version 2.91.93 (or later) of each Not so much. The system is showing as fully updated ... but the problem persists. Ayup. Currently shows fully updated ... but ... gnome-shell-2.91.92-3.fc15 gnome-session-2.91.91-3.fc15 I assume that grabbing the latest builds off koji and installing them will clear this up? ah, sorry, it's in updates-testing, but not updates. I didn't realize that I was pulling from updates-testing. Ok. Packagekit didn't have a clue, but Yumex located the updates this morning ... and I ran them ... but ... If you don't have an account on the fedora forums, please register as you will not be able to view the related photographs unless you do. The pertinent thread is here. http://forums.fedoraforum.org/showpost.php?p=1456821&postcount=138 And on a related note: http://forums.fedoraforum.org/showpost.php?p=1456831&postcount=141 (On a lighter note, in the interest of your continued sanity ... it may not be a good plan to post and admit being a developer in the thread. If you do, They'll likely be on you like a duck on a junebug. :-D ) I finally got back into the GUI with multiple X-kills and it's running fairly stable now, but rebooting starts the whole mess over again. Where can I look for the information you'll need to iron it all out? Might as well close this one. Updates fixed it. (In reply to comment #9) > Might as well close this one. Updates fixed it. I am not sure of that... I am fully updated and just started receiving this today. It may not be the same, if not let me know and I will start a new bug.. I installed compiz-gnome in preparation for updating to the kmod nvidia update method Now, anytime I try to shut down, it just goes to the logon screen.. And if I press the power button one time, it goes into hibernation I have to ctrl + alt + 2 to a root login to shutdown or shutdown -r For my comments above, this only started happening after I installed compiz-gnome I have another F15 install that does not have it and it is up to date and does Not have this issue Additional Info, on the 2nd up to date F15 I am also having the same issues.. So whatever was pushed today in updates is the culprit ditto |