Bug 820095
Summary: | RFE: add detail to the 'Oh no! Something has gone wrong' error message | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | collura |
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> |
Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | antonio.montagnani, collura, emcnabb, fschwarz, jprajzne, maxamillion, otaylor, redhat, rjones, samkraju, urilabob, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | noarch | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 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: |
Description
collura
2012-05-09 07:06:54 UTC
I'd like to add my support to collura in requesting this (I found this RFE because I was planning to make my own RFE on exactly the same issue, but collura has put it so much better than I would have). Better information would help most users (with the risk that it might confuse some). However I'd like to ask whether there could be a slightly different design for a solution. I gather (don't have time to check) that by the time this screen appears, gnome is unreliable so that there's not much available to do interaction; the error screen seems to be just a splash screen that is thrown up. Would it at that point be possible to listen for keystrokes? In that case, the interaction could provide an interaction something like "Oh no! Something has gone wrong and the system can't recover. You have two choices: 1. Use the hardware buttons to restart your machine (it might restart successfully next time). 2. Hit any key, which will take you to more information." In this proposal, detecting a keystroke would lead to init 3, throwing up on the screen before or after login something like: " Something has gone wrong with $package at $function. This error is shown by gnome-session when any critical component of the GNOME session respawns more than once within a minute. The offending component is always mentioned in ~/.xsession-errors . Taking you to a console session. Please log in, and take note of the contents of ~/.xsession-errors Please report this to your administrator so they can see what's crashing. " This error message might need some modification if the crash occurs before login, because presumably the error logging can't go to ~/.xsession-errors at that point. I'm guessing /root/.xsession-errors? fwiw I'm on F18 and I'm getting this message before I login. I logout and it keeps happening over and over :-( So the issue occurs for other reasons besides an app within a logged in session respawning over and over. I probably need to open a new bug. (In reply to comment #2) > fwiw I'm on F18 and I'm getting this message before I login. I logout and it > keeps happening over and over :-( So the issue occurs for other reasons > besides an app within a logged in session respawning over and over. I > probably need to open a new bug. that got me thinking, since a regular user wasn't logged in, X was running, but under gdm. In /var/log/gdm/:0-greeter.log I see stuff like so: gnome-session[1070]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. I had modified my pam configuration (system-auth file) for SSSD per http://docs.fedoraproject.org/en-US/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html reverting those changes got me back in, albeit w/o network logon. now i'm having issues with my i915 graphics driver :-( Non-actionable error messages like this are bad news all round. We're not writing a Windows clone. Can we make this higher priority please? THe fact that the session might be still running, it can save the user some unsaved work and then take some corrective actions. The current solution is really a poor alternative to what it may become. |