https://bugzilla.novell.com/show_bug.cgi?id=265263#c59
Martin Vidner
I don't know if this is feasible, but maybe we can somehow change this so the xmessage window only appears if there is a serious error condition, like - y2base segfaults or terminates via other signal - y2base returns with non-zero exit status
Yes, that is my fix (patch follows), and the existing code even makes it easy. I wonder why I didn't think of it sooner. (In reply to comment #49 from Stefan Hundhammer)
(In reply to comment #48 from Aaron Bockover)
For one, I would _never_ want to see xmessage in any shape or form. If YaST segfaults, well, we have bug buddy on GNOME, etc. Maybe the GTK front end should integrate with that.
Ah, good idea, let's try adding that.
If you absolutely have to show the user a cryptic error message, at least do so in a native UI - use zenity if on GNOME or XFCE, kdialog on KDE, and xmessage as a complete last resort fallback.
That would be beautifying the display of error messages and, a lot worse, maintaining a zillion error message beautifiers in all shapes of sizes. Does that really make any sense to you?
I vote strictly against this. This would just be code bloat and a maintenance nightmare.
While we could use zenity/kdialog and xmessage as fallback, I also think that the benefits would not justify the effort. Feel free to submit a patch handling all the corner cases.
[...] the cryptic messages [...] should be logged in ~/.xession-errors anyway
I fear you overestimate even advanced users. I have yet to receive the first bug report where a user looked in ~/.xsession-errors. All we ever get in such cases is "it doesn't start".
Right. And even myself or other bug sorters don't know this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.