|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-printer terse "Assign driver" string leads to confusion | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Martin Schlander <martin.schlander> |
| Component: | YaST2 | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | jnelson-suse, jsmeix |
| Version: | Beta 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast logs
Screenshot of yast saying no suitable driver is found for my printer - hope the Danish translations doesn't throw you off too much yast logs for rc1 printer setup failure |
||
|
Description
Martin Schlander
2008-11-18 17:34:10 UTC
Please provide y2logs. More info on http://en.opensuse.org/Bugs/YaST Created attachment 253475 [details]
yast logs
When I enter at "Assing Driver" "Okipage 6ex" and then click [Show matching drivers] I get several drivers for it. Same problem in RC1. x86_64 DVD installation with KDE4, YaST Qt. When I start the printer module it searches for printers, it finds my okipage, but it says no suitable driver found. Clicking "Show suitable drivers" doesn't help. I then think: "Ok, not the end of the world, it's an ancient parallel printer from the last millenium, needing a PPD from a completely different manufacturer to work properly (HP LaserJet 4, HP != Oki), I'll just assign the proper ppd-file manually" So I click "Add driver" -> "Browse" -> After some fiddling around I manage to navigate the annoying Qt3 filedialog to /usr/share/cups/model/manufacturer-PPDs/hp/HP_LaserJet_4_Plus.ppd.gz -> Click "Open" -> Ok I'm then returned to the maindialog and I'm told again that no suitable driver has been found. The automation obviously doesn't work for this printer - and for the life of me I can't figure out how to make the automation stfu and let me assign the PPD file that I need manually. I'll attach a screenshot of the yast module telling me there's no a driver. And I'll attach my yast logs again. Created attachment 256996 [details]
Screenshot of yast saying no suitable driver is found for my printer - hope the Danish translations doesn't throw you off too much
Created attachment 256997 [details]
yast logs for rc1 printer setup failure
When I enter at "Assing Driver" (which is translated to "Tildel driver" in your case) "Okipage 6ex" and then click [Show matching drivers] I get several drivers for it. The search string at "Assing Driver"/"Tildel driver" is preset with the model autodetection string from the table of autodetected printers above. When there is no driver description which mathes to the model autodetection string, it cannot find a matching driver. Therefore you must manually enter an appropriate search string and then clicking "Show Matching drivers" (which is translated to "Vis passende drivere" in your case) to display the driver descriptions which match to the search string. I don't know your language but perhaps the translations are misleading in your language? Martin, see the above description. It seems I was perfectly right to show longer descriptive texts like "Find and assign a suitable driver" because now (and of course in the past) those current terse snippets like "Assign driver" are too easy to be misunderstood. See https://bugzilla.novell.com/show_bug.cgi?id=446432#c11 and https://bugzilla.novell.com/show_bug.cgi?id=446432#c12 It seems too many users simply do not understand that the stuff is a about to enter a search string and then click "Show Matching drivers" to display the results which match to the current search string. Finally I get it. I would definitely support changing the "Assign driver" string to "Search for driver by keyword" or "Search for drivers", "Enter search term here", "Driver search term" or something like that. It would never in a million years have occured to me that a field titled "Assign driver", and already populated with my printer name, was actually a search field, intended to be edited. I understood it to be a static field, with the sole purpose of informing me that my printer had been detected and identified under that name. Reopen to get a decission from usability team if I should - either rename it to something more descriptive and break all translations for this label - or leave it as is. If I should rename it to something more descriptive, please provide the exact text which I should use. Martin, see comment #10 and decide what you like. *** Bug 418186 has been marked as a duplicate of this bug. *** FYI: Bug #418186 is not a duplicate of this bug. Mhm. What about "Search for drivers" as a label and change the label now. I know that this would mean a break of translation but this might be better than confusing users. Fixed in yast2-printer version 2.17.51. |