Bug 1040632 - Non viene riconosciuto dispositivo scanner Canoscan Lide 100
Summary: Non viene riconosciuto dispositivo scanner Canoscan Lide 100
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-session
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-11 18:16 UTC by esploratore
Modified: 2015-02-18 11:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 11:00:50 UTC
Type: Bug


Attachments (Terms of Use)

Description esploratore 2013-12-11 18:16:48 UTC
Ho installato Fedora 19 con desktop XFCE. Con l'aiuto di Fedora online ho cercato di farlo riconoscere dal sistema. Nonostante tutti i tentativi, anche dopo l'installazione di Xsane, il dispositivo di scansione non veniva riconosciuto. Il problema si è risolto quando sono ritornato a lavorare in ambiente Gnome, lasciando da parte XFCE. Infatti lavorando con Fedora 19 Gnome, non appena collegato lo scanner, questo è stato riconosciuto ed ha funzionato

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dennis Gilmore 2014-02-19 13:08:40 UTC
reassigning to xsane, maybe they can help you work out why the scanner was not detected.

Comment 2 Nils Philippsen 2014-04-03 15:25:08 UTC
I don't speak Italian. Here's what Google Translate makes out of it:

> I installed Fedora 19 with XFCE desktop. With the help of online Fedora I tried to make it recognize by the
> system. Despite all attempts, even after the installation of Xsane, the scanning device was not recognized.
> The problem was resolved when I returned to work in Gnome, XFCE aside. In fact, working with Fedora 19 Gnome,
> not just connected the scanner, this has been recognized and it worked

So to me it's most likely something where the permissions aren't set up correctly in XFCE when this works in GNOME. Changing component to xfce4-session accordingly.

Comment 3 Kevin Fenzi 2014-04-03 15:33:42 UTC
xsane works fine here in Xfce. 

If you start it in a terminal does it output any errors? Or it just doesn't see the scanner?

How did you login to Xfce?

Comment 4 Fedora End Of Life 2015-01-09 22:22:40 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-18 11:00:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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