Tomas, can you help on this one ?

CC: (none) => stormi, supp

(In reply to comment #0)
> Description of problem:
> Looking for new scanner ends with a segfault form a terminal but doesn't create
> a message error when used from the MCC.
> scanimage -L ends with a segfault 
> 
> SANE_DEBUG_DLL=128 scanimage -L ends with libsane-canon.so.1
> 
> Version-Release number of selected component (if applicable):
> 1.0.22-1.mga1
> 
> How reproducible:
> every time scanimage -L is launched
> 

> 
> The Segfault is happening when scanimage looks for a canon scanner, so removing
> âall the related libs solved the problem :
> 
> /usr/lib64/sane/libsane-canon.so.1
> /usr/lib64/sane/libsane-canon.so.1.0.22
> /usr/lib64/sane/libsane-canon630u.so.1
> /usr/lib64/sane/libsane-canon630u.so.1.0.22
> /usr/lib64/sane/libsane-canon_dr.so.1
> /usr/lib64/sane/libsane-canon_dr.so.1.0.22
> /usr/lib64/sane/libsane-canon_pp.so.1
> /usr/lib64/sane/libsane-canon_pp.so.1.0.22
> 
> scanimage -L now detects correctly my scanner :
> 
> device `v4l:/dev/video0' is a Noname Logitech QuickCam Zoom virtual device
> device
> `net:192.168.2.2:hpaio:/usb/Officejet_J4500_series?serial=CN97TC92RM052T' is a
> Hewlett-Packard Officejet_J4500_series all-in-one

@ Florian

cc'ing you because this report might contain useful information and because I don't know what to do with this bug: The reporter found a workaround.
So I'll leave that to you to decice :D

CC: (none) => doktor5000, marja11

(In reply to comment #0)
> Description of problem:
> Looking for new scanner ends with a segfault form a terminal but doesn't create
> a message error when used from the MCC.
> scanimage -L ends with a segfault

Please check https://wiki.mageia.org/en/Debugging_software_crashes 
You need to provide a backtrace for the segfault, so in short you need to move the removed files back and then follow the instructions given in the wiki page.

Created attachment 1322 [details]
backtrace of scanimage -L scanner FS4000 off

Created attachment 1323 [details]
backtrace scanimage -L scanner FS4000 powered

I noticed that the problem occurs only when my SCSI scanner Canon FS4000US is connected and powered. Attached the results of the backtrace with an without the scanner powered.

@ JeanMarc

Thanks for providing the backtrace

assigning to maintainer

Assignee: bugsquad => dmorganec

@ JeanMarc

Sorry, our maintainer was too busy 

I hope Mageia 2 solved the issue for you.... did it?

(In reply to comment #8)
> @ JeanMarc
> 
> Sorry, our maintainer was too busy 
> 
> I hope Mageia 2 solved the issue for you.... did it?

The problem is still there but a "solution" is to remove /usr/lib64/libsane-canon.so.1.0.22. There is some sort of conflict when using this scanner maybe because its a scsi scanner or because it is not properly recognized. Once the lib is removed evrything works well as I use Vuescan to scan my films and slides.
Regards

Jean-Marc

Per last comment i'd say closing it as the reporter has a workaround and nobody else reported this.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED