Bug 475989 - The Scanner Module Lacks Stability and Often Encounters Endless Loops
Summary: The Scanner Module Lacks Stability and Often Encounters Endless Loops
Status: RESOLVED INVALID
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-14 22:08 UTC by Scott Couston
Modified: 2010-08-24 19:49 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Couston 2009-02-14 22:08:15 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6

The Scanner Module has serious codeing error in that Addition/Editing/Driver Selection/Scanner Selection either do not function and end up in endless lops or timeout without result or until Window Manager terminates the Scanner Window.



Reproducible: Always

Steps to Reproduce:
1.Add a new USB Scanner
2.Edit the Scanner Model and Driver
3.Try to filter the model and driver
Actual Results:  
This Module require RC Candidate testing - as it is the module has little or No value

Expected Results:  
It Works!
Comment 1 Johannes Meixner 2009-02-18 14:27:04 UTC 
Interesting to see that you are so smart that you know
that it is the "Scanner Module which has serious codeing error"
and that you can judge that it "has little or No value".

I recommend that either you do a more thorough analysis
or simply post only what happened without any judgement
when you do not know anything about any underlying reason.

*** This bug has been marked as a duplicate of bug 442173 ***
Comment 2 Scott Couston 2009-02-18 21:10:00 UTC 
Any Application that does not function and or ends up in an endless loop by definition has coding problems - Environment is ruled out. If an application is designed to do something and it doesn't - it has not been tested and the fault must lye in the applications design. This fundamental in 1st year uni stuff

Bug Closed by reporter as #1 is neither helpful nor constructive