Bug 85016 - RFE: scanner verification applet for KDE & Gnome desktops OR panels
RFE: scanner verification applet for KDE & Gnome desktops OR panels
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-02-24 16:41 EST by Elton Woo
Modified: 2014-03-16 22:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-02 13:43:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Elton Woo 2003-02-24 16:41:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030215

Description of problem:
First time login to KDE / Gnome, a scanner icon is created on desktop (similar to
printer icon) AND /OR created in the panel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. First time login to KDE or Gnome desktop
2. Desktop / panel default icons INCLUDE a scanner applet
3. Click on applet to verify that peripheral is correctly identified and configured.
IF NOT, run editor (as su) to correct /etc/sane.d/*.conf file

Actual Results:  No such applet available (RH

Expected Results:  Applet should be availalble for first-time installation of

Additional info:

Make things "EASIER" for users migrating from MS Windows, Macintosh systems, and
Comment 1 Alexander Larsson 2003-08-06 06:04:18 EDT
This really isn't a redhat-artwork bug, i'm reassigning it to distribution.
Comment 2 Bill Nottingham 2005-03-02 13:43:48 EST
Closing bugs on older, no longer supported, releases. Apologies for
any lack of response.

I don't think internal RH resources will be expended on this in the
near future.

Note You need to log in before you can comment on or make changes to this bug.