[Bug 265263] New: Corrupted message box issued by YaST on finishing Software Update
https://bugzilla.novell.com/show_bug.cgi?id=265263 Summary: Corrupted message box issued by YaST on finishing Software Update Product: openSUSE 10.3 Version: Alpha 3 Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: jsrain@novell.com After the current update to openSuSE 10.3 alpha3plus YaST 2.15.28-2 issues a corrupted message box on completing software updates, offering OK as only option, text is unreadable. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #1 from casualprogrammer@yahoo.com 2007-04-17 04:53 MST ------- Created an attachment (id=131698) --> (https://bugzilla.novell.com/attachment.cgi?id=131698&action=view) Screenshot of message box To create: Start yast, then chose "Software Management", filter "Installation Summary", check "Keep", from the context menu of a random entry chose "All in this list/update if newer version available" then "Accept" -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #2 from casualprogrammer@yahoo.com 2007-04-17 09:02 MST ------- To create: Start yast, then chose "Software Management", then "Accept" -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #3 from casualprogrammer@yahoo.com 2007-04-17 09:07 MST ------- Created an attachment (id=131828) --> (https://bugzilla.novell.com/attachment.cgi?id=131828&action=view) resized xmessage window This actually also happens when starting YaST and closing it. The window can be resized, then the window dressing becomes visible. It's called "xmessage" and contains just some vertical lines on the left edge. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #4 from casualprogrammer@yahoo.com 2007-04-17 09:09 MST ------- Addenda: when calling yast as root from a terminal, this does not happen. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #5 from mhorvath@novell.com 2007-04-20 06:35 MST ------- Please attach your yast logs. http://en.opensuse.org/Bugs/YaST -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #6 from casualprogrammer@yahoo.com 2007-04-20 08:44 MST ------- Created an attachment (id=132881) --> (https://bugzilla.novell.com/attachment.cgi?id=132881&action=view) yast2logs -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | ------- Comment #7 from casualprogrammer@yahoo.com 2007-04-20 10:59 MST ------- Actually it is an empty xmessage ( x-window echo ) window. This must be initiated in some YaST related script, probably for debugging ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 mvidner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lslezak@novell.com |mvidner@novell.com Status|NEW |ASSIGNED ------- Comment #8 from mvidner@novell.com 2007-04-23 06:19 MST ------- Yes, xmessage, see also bug 211392. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Corrupted message box issued|xmessage issued by YaST on finishing Software |by YaST on finishing |Update |Software Update | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #9 from casualprogrammer@yahoo.com 2007-04-28 03:05 MST ------- This is actually caused by /sbin/yast2
From line 20 it has:
# #211392 # if we are in X and do not have _input_ from terminal, # make it output to xmessage redirect() { XMESSAGE=`type -p xmessage` if $REDIRECT && [ -n "$DISPLAY" -a ! -t 0 -a -n "$XMESSAGE" ]; then exec &> >($XMESSAGE -buttons OK:0 -default OK -center -file -) fi } This does not seem to meet normal requirements. Starting YaST from the menu surely requires to be in X, and just as sure does not give input from terminal. So an xmessage is raised anytime YaST feels like talking to us. Might be nice as debugging feature, otherwise it's just confusing. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #10 from casualprogrammer@yahoo.com 2007-04-28 03:08 MST ------- Fixed it for me: Commenting out /sbin/yast2 line 32: # redirect -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 gp@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gp@novell.com Platform|x86 |All ------- Comment #11 from gp@novell.com 2007-04-30 04:15 MST ------- I have also been seeing this for some time, on STABLE x86-64. Changing architecture to "All". -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stbinner@novell.com ------- Comment #12 from locilka@novell.com 2007-05-09 02:09 MST ------- *** Bug 271245 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #14 from casualprogrammer@yahoo.com 2007-05-14 05:11 MST ------- This obviously is caused by the "Solution" to Bug 211392, not sure whether this would not be possible without throwing xmessages at everybody. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 zajec5@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |silviu_marin-caea@otpbank.ro ------- Comment #15 from zajec5@gmail.com 2007-05-17 16:01 MST ------- *** Bug 275198 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Version|Alpha 3 |Alpha 4 ------- Comment #16 from stbinner@novell.com 2007-05-18 08:09 MST ------- Still happening and annyoing/very visible. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #17 from jt@newmarket.k12.nh.us 2007-05-18 11:09 MST ------- Hello, I just installed alpha4 w\gnome and let it update, I am also getting a lot of "xmesage" screens referring to /usr/share/themes/Gilouche/gtk-2.0/gtkrc:42:Clearlooks configuration option "xxxx" is not supported and will be ignore. James -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|xmessage issued by YaST on |xmessage issued by YaST on finishing every |finishing Software Update |module -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ra100@atlas.cz ------- Comment #18 from stbinner@novell.com 2007-05-21 00:37 MST ------- *** Bug 276479 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #19 from kmachalkova@novell.com 2007-05-21 08:39 MST ------- Fixed in svn, for the next build (yast2-2.15.34) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgroneman@gmail.com ------- Comment #20 from mhorvath@novell.com 2007-06-01 11:13 MST ------- *** Bug 280068 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #21 from casualprogrammer@yahoo.com 2007-06-01 14:51 MST ------- Katarina: what exactly did you fix ? I still experience it with 2.15.34-4, only solution for me see comment #10 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #22 from casualprogrammer@yahoo.com 2007-06-01 14:52 MST ------- just to change to reopened -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #23 from casualprogrammer@yahoo.com 2007-06-02 10:15 MST ------- Seems to be OK now with 2.15.35-2 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #24 from casualprogrammer@yahoo.com 2007-06-02 10:18 MST ------- Not really :-( -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #25 from silviu_marin-caea@otpbank.ro 2007-06-04 23:48 MST ------- I have yast2-2.15.35-4 from Factory and it works for me. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #26 from casualprogrammer@yahoo.com 2007-06-05 00:52 MST ------- So then there must be a difference between your ( comment #25 ) and my setup: I am using openSuSE 10.3 alpha4plus kernel 2.6.22-rc2-git7-2-default with Gnome and YaST QT, yast2 is at 2.15.35-3 i586. Not sure how you can have yast2-2.15.35-4, as yast2 is at 2.15.35-3 i586 is the latest version offered from factory ( according to my /sbin/yast2 sw_single ) When I call yast2 from a terminal, then obviously, the x-message is not issued, as explained in comment # 9. If I start YaST from the GUI however, ( Computer / More Applications... / System / YaST ), and start any module, the x-message is issued on closing YaST ( Not closing the module, only when YaSt is closed completely ) As I pointed out in comment #9: "Starting YaST from the menu surely requires to be in X, and just as sure does not give input from terminal. So an x-message is raised anytime YaST feels like talking to us. Might be nice as debugging feature, otherwise it's just confusing." And as pointed out in comment #10: Commenting out /sbin/yast2 line 32: # redirect Only change so far is, that it's now in line 43 instead of 32 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263 ------- Comment #27 from silviu_marin-caea@otpbank.ro 2007-06-05 01:40 MST ------- I have x86_64. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c28
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c29
--- Comment #29 from Chad Groneman
https://bugzilla.novell.com/show_bug.cgi?id=265263#c30
--- Comment #30 from Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c31
James Tremblay
https://bugzilla.novell.com/show_bug.cgi?id=265263#c32
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c33
--- Comment #33 from James Tremblay
https://bugzilla.novell.com/show_bug.cgi?id=265263#c34
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c35
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=265263#c36
--- Comment #36 from Romain Pelissier
https://bugzilla.novell.com/show_bug.cgi?id=265263#c37
--- Comment #37 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=265263#c38
Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=265263#c39
--- Comment #39 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=265263
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=265263#c40
--- Comment #40 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=265263#c41
Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=265263#c42
Aaron Bockover
https://bugzilla.novell.com/show_bug.cgi?id=265263#c43
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c44
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=265263#c45
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=265263#c47
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c48
--- Comment #48 from Aaron Bockover
https://bugzilla.novell.com/show_bug.cgi?id=265263#c49
--- Comment #49 from Stefan Hundhammer
For one, I would _never_ want to see xmessage in any shape or form.
Nobody wants that. But then, nobody ever wants bad news. But should that mean that bad news simply always gets suppressed?
If YaST segfaults, well, we have bug buddy on GNOME, etc. Maybe the GTK front end should integrate with 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.
Also, all of the cryptic messages that are being debated here for showing to users should be logged in ~/.xession-errors anyway - if a user advanced enough to understand the error really cares about said error - they will probably know where to find it.
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". We didn't add that "xmessage" just for the fun of it. If there was no reason for it, we'd have kept the start script simple. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c50
--- Comment #50 from Aaron Bockover
(In reply to comment #48 from Aaron Bockover)
For one, I would _never_ want to see xmessage in any shape or form.
Nobody wants that. But then, nobody ever wants bad news. But should that mean that bad news simply always gets suppressed?
I'm not saying the messages should be suppressed. (speaking as average joe user) I just don't want to know about it. Why would I really care that yast segfaulted? I can't do anything about it. I'm going to file a bug, if I care that much, but I don't care about the details of the crash. This is why I suggested integrating the front ends with the crash handlers (i.e. Bug Buddy in GNOME). If the GTK front end were integrated with Bug Buddy, the crash handling UI would be consistent for 1, handle the ugly details of capturing crash information for 2, and make the bug reporting process simple and mostly transparent for 3.
If YaST segfaults, well, we have bug buddy on GNOME, etc. Maybe the GTK front end should integrate with 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?
It makes a lot of sense to me. You're talking about maybe 15 lines of bash here. I did just this in the opensuse-codecs-installer, and the use case is more complicated than what is required here. It should ideally be an xdg script.
I vote strictly against this. This would just be code bloat and a maintenance nightmare.
I think you are exaggerating, but I respect your strong convictions.
Also, all of the cryptic messages that are being debated here for showing to users should be logged in ~/.xession-errors anyway - if a user advanced enough to understand the error really cares about said error - they will probably know where to find it.
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".
I fear you don't understand the average user by advocating that communicating with users in any way via xmessage in the year 2007 is acceptable at all. The first question as a response to that bug would be "attach your ~/.xsession-errors" - again, this issue goes away entirely if the front ends just integrate with the desktop/platform crash handlers. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c51
--- Comment #51 from Aaron Bockover
https://bugzilla.novell.com/show_bug.cgi?id=265263
Aaron Bockover
https://bugzilla.novell.com/show_bug.cgi?id=265263#c52
Garrett LeSage
https://bugzilla.novell.com/show_bug.cgi?id=265263#c53
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=265263#c54
--- Comment #54 from Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=265263#c55
Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=265263#c56
--- Comment #56 from Stefan Hundhammer
Created an attachment (id=160793) --> (https://bugzilla.novell.com/attachment.cgi?id=160793) [details] A theoretical cross desktop message display
Just a thought...
Unfortunately, things are never as easy as this. This simplistic snippet misses the error handling that is crucial for code like this. For example, while normal KDE installations do indeed include "kdialog", we need to have a fallback in case it's not available after all. And the same for GNOME. And so on. I've been in this business long enough to see quick hacks like this fail at the worst possible of moments, usually out there at a customer's machine. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c57
Aaron Bockover
I think this xmessage is a really good debugging aid and therefore helps us to find bugs during alpha/beta phase. But can we disable it directly after RC3? What about a sysconfig variable?
I tend to agree, these xmessages can be good for beta testing, but they absolutely should be turned off before the GM release. That's the bottom line. After the RCs are over, this becomes an issue of usability and design and at that point, engineers shouldn't have the final word. (In reply to comment #56 from Stefan Hundhammer)
Unfortunately, things are never as easy as this. This simplistic snippet misses the error handling that is crucial for code like this...
Stefan, I'm not sure if you noticed, but for one, I called that snippet "theoretical" and it was written in 2 minutes to give you a basic idea. And second, if zenity or kdialog can't be run, then it falls back to ... xmessage! That's what the || means in bash. I wasn't saying the code was 100% accurate, but I can tell you a real solution is not as complicated as you would like to think it is. Anyway, displaying of these overly technical and pointless messages (to users) is something that should be completely turned off when the RCs are over. https://bugzilla.novell.com/show_bug.cgi?id=211392 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c58
--- Comment #58 from Martin Vidner
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.
https://bugzilla.novell.com/show_bug.cgi?id=265263#c60
--- Comment #60 from Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c61
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c62
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c63
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=265263#c64
Mark Gordon
participants (1)
-
bugzilla_noreply@novell.com