|
Bugzilla – Full Text Bug Listing |
| Summary: | Better error message instead of "the ncurses frontend is installed but does not work" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andreas Hanke <andreas.hanke> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | casualprogrammer, kkaempf, snwint |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Demonstration patch
Maybe nicer yast2-ui.diff |
||
|
Description
Andreas Hanke
2006-10-10 17:58:16 UTC
To reproduce:
% rm /usr/lib*/libyui.so.2
% yast2
warning: the qt frontend is installed but does not work
warning: the ncurses frontend is installed but does not work
You need to install yast2-ncurses to use the YaST2 text mode interface
I would prefer a message like:
% rm /usr/lib*/libyui.so.2
% yast2
warning: the qt frontend is installed but does not work
libyui.so.2 => not found
warning: the ncurses frontend is installed but does not work
libyui.so.2 => not found
You need to install yast2-ncurses to use the YaST2 text mode interface
The attached patch implements that - in a ruther ugly way, it is meant to demonstrate what I mean.
The reason is, with the current implementation, the user never reaches a point where he can see what's wrong.
Created attachment 101167 [details]
Demonstration patch
Created attachment 101183 [details]
Maybe nicer
The other part is the message in /sbin/yast2, line 189. The current message "You need to install yast2-ncurses to use the YaST2 text mode interface" is appropriate under the assumption that the user can only reach this point if he is in text mode and yast2-ncurses does not work. But that assumption is not correct, the user can as well reach this point if he is in graphical mode and none of either yast2-ncurses or yast2-qt works. rpm -qf /usr/lib/YaST2/bin/yast2-funcs -> yast2 mvidner did the very last entry there :) Comment 3: good idea, applied. Comment 4: I'd like to redirect the output of the entire script to xmessage in such situations, but I haven't found out how exactly OK, the key is "exec &> >(xmessage)", but it doesnt seem to work with kdesu/gnomesu. Anyway, submitted in yast2-2.15.27. *** Bug 265263 has been marked as a duplicate of this bug. *** Apparently, its not completely fixed since xmessage popups are shown too often (see bug 265263 for the full thread) Nice try, Klaus. :-) Adjusting severity to match bug 265263. This bug is not a dup of bug 265263. That bug is much more broad and there are other issues with it that need to be discussed separately (on that bug). Created attachment 161388 [details] yast2-ui.diff Even though Klaus reopened this bug for a wrong reason... (In reply to comment #0 from Andreas Hanke) > - Change the message "You need to install yast2-ncurses" to something like "You > need to install yast2-ncurses and its dependencies" or "You need to verify > yast2-ncurses" or give a hint about "rpm -V yast2-ncurses" I overlooked that originally. This patch should be better. Submitted in yast2-2.15.52. |