Description of problem: I have the "Mustek BearPaw 2448TA Pro" scanner and it is not detected by the Mageia 2. From what I checked the cause may be the lack of library "libsane-mustek_usb2". In the source "ftp://ftp2.sane-project.org/pub/sane/sane-backends-1.0.22/" this file is present, as in other distributions such as Fedora. Version-Release number of selected component (if applicable): sane-backends-1.0.22-7.mga2.x86_64.rpm How reproducible: No file "libsane-mustek_usb2.so*" in "/usr/lib64/sane/". Steps to Reproduce: 1. 2. 3.
Keywords: (none) => Junior_jobSource RPM: sane-backends-1.0.22-7.mga2.x86_64.rpm => sane
(In reply to comment #0) > Description of problem: > I have the "Mustek BearPaw 2448TA Pro" scanner and it is not detected by the > Mageia 2. From what I checked the cause may be the lack of library > "libsane-mustek_usb2". > In the source "ftp://ftp2.sane-project.org/pub/sane/sane-backends-1.0.22/" this > file is present, as in other distributions such as Fedora. > > Version-Release number of selected component (if applicable): > sane-backends-1.0.22-7.mga2.x86_64.rpm > > How reproducible: > No file "libsane-mustek_usb2.so*" in "/usr/lib64/sane/". > > > Steps to Reproduce: > 1. > 2. > 3. Probably I found solution of the problem: http://lists.opensuse.org/opensuse-bugs/2010-08/msg04418.html But I do not know how to create the correct rpm file with this solution. Can someone help me with this?
The lack of any response from half of the year. Maybe something will change after the change of the priority?
Target Milestone: --- => Mageia 3Priority: Normal => release_blockerCC: (none) => nexus9Severity: normal => critical
not necessarily
Changing the priority doesn't help a bit, but nagging sometimes helps. BTW there are several other bugs about scanners not working (mostly epson so probably not related to this issue). The problem here is that enabling the 2 missing backends requires flipping a global switch that also modifies some of the other backends. This is generally not acceptable for a stable release. Instead, I changed the configure script to just build those 2 backends with pthreads (AFAICT all the other backends do not use pthreads at all). This is of course not supported by upstream so still quite risky. This updated package is now in mga2 updates_testing. Getting it released as an update will require some (1 or 2) people to verify if the existing backends still work. I have no idea if/how we are going to do this - I do not have a scanner so could not test this package at all. Please test with sane packages 1.0.22-7.1.mga2 .
Priority: release_blocker => NormalCC: (none) => cjwTarget Milestone: Mageia 3 => ---Severity: critical => normal
With "Mustek BearPaw 2448TA Pro" scanner work excellent!!! Thank you very much. I hope that this change does not broke handle other scanners and will go to the stable version of Mageia 2 (also 3).
Can you arrange one in mga3 updates testing please? I have an Epson perfection 1660 photo that worked on mga1 but not mga3. (i skipped mga2 here in my office) BTW there are some posts on [discuss] ml today about general epson problems.
CC: (none) => fri
*** Bug 7018 has been marked as a duplicate of this bug. ***
CC: (none) => jcm
CC: (none) => hhielscher
So, if I'm correct, there's an update candidate for Mageia 2, but it wasn't pushed to updates, and there's a request for the same fix in Mageia 3. What about cauldron? Assigning to the maintainer by the way.
Keywords: (none) => PATCH, TriagedCC: (none) => stormiAssignee: bugsquad => dmorganec
IIUC, Christiaan provided a patch to sane (sane-backends-1.0.23-have-pthread.patch) which fixes this bug. An updated package was pushed to 2/core_updates-testing (see http://mageia.madb.org/package/show/release/2/application/0/name/sane-backends), and the patch was also included in Cauldron at that time (thus making it in 3/core_release, and it is still present in 4/core_release). AFAIC, this bug should be assigned to QA for validation on Mageia 2 only. @Morgan: It seems to me that bug 7018 is not a duplicate of this bug. The Mageia 3 package also contains the fix from comment 4, so you are likely hit by another bug (which should be discussed in another bug report).
CC: (none) => remi
Reopened 7018, asking reporter for input
Assigning to QA for testing on Mageia 2. sane should be tested against all types of scanners, to see if everything still works as intended (it's worth noting that the patch is also used in Mageia 3 and cauldron). nexus confirmed in comment 5 that the update candidate works on Mageia 2 64bit. SRPM: sane-1.0.22-7.1.mga2.i586.rpm
Assignee: dmorganec => qa-bugs
Source RPM: sane => sane-1.0.22-7.1.mga2.i586.rpm
Small mistake in last comment, the SRPM should be: sane-1.0.22-7.1.mga2.src.rpm
Source RPM: sane-1.0.22-7.1.mga2.i586.rpm => sane-1.0.22-7.1.mga2.src.rpm
With "Mustek BearPaw 2448TA Pro" and Mageia 3 also works perfectly.
Which two backends were changed? We need an advisory, before this can be validated.
CC: (none) => davidwhodgins
Before ------ # urpmf libsane1 | grep libsane-mustek_usb libsane1-devel:/usr/lib/sane/libsane-mustek_usb.so libsane1:/usr/lib/sane/libsane-mustek_usb.so.1 libsane1:/usr/lib/sane/libsane-mustek_usb.so.1.0.22 libsane1:/usr/lib/sane/libsane-mustek_usb.so.1 libsane1:/usr/lib/sane/libsane-mustek_usb.so.1.0.22 After ----- # urpmf libsane1 --media Testing | grep libsane-mustek_usb libsane1-devel:/usr/lib/sane/libsane-mustek_usb.so libsane1-devel:/usr/lib/sane/libsane-mustek_usb2.so libsane1:/usr/lib/sane/libsane-mustek_usb.so.1 libsane1:/usr/lib/sane/libsane-mustek_usb.so.1.0.22 libsane1:/usr/lib/sane/libsane-mustek_usb2.so.1 libsane1:/usr/lib/sane/libsane-mustek_usb2.so.1.0.22 Canon scanner works as well after the update as it did before in vbox.
Mageia 2 exact match *** Arch: i586 *** RPMs from 'core-updates_testing' ======================== libsane1-1.0.22-7.1.mga2.i586.rpm libsane1-devel-1.0.22-7.1.mga2.i586.rpm sane-backends-1.0.22-7.1.mga2.i586.rpm sane-backends-doc-1.0.22-7.1.mga2.i586.rpm sane-backends-iscan-1.0.22-7.1.mga2.i586.rpm saned-1.0.22-7.1.mga2.i586.rpm SRPMs from 'core-updates_testing' ======================== sane-1.0.22-7.1.mga2.src.rpm *** Arch: x86_64 *** RPMs from 'core-updates_testing' ======================== lib64sane1-1.0.22-7.1.mga2.x86_64.rpm lib64sane1-devel-1.0.22-7.1.mga2.x86_64.rpm sane-backends-1.0.22-7.1.mga2.x86_64.rpm sane-backends-doc-1.0.22-7.1.mga2.x86_64.rpm sane-backends-iscan-1.0.22-7.1.mga2.x86_64.rpm saned-1.0.22-7.1.mga2.x86_64.rpm SRPMs from 'core-updates_testing' ======================== sane-1.0.22-7.1.mga2.src.rpm
Whiteboard: (none) => mga2-32-ok?
$ urpmf lib64sane1 | grep libsane-mustek_usb lib64sane1-devel:/usr/lib64/sane/libsane-mustek_usb.so lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1 lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1.0.22 lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1 lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1.0.22 $ urpmf lib64sane1 --media Testing | grep libsane-mustek_usb lib64sane1-devel:/usr/lib64/sane/libsane-mustek_usb.so lib64sane1-devel:/usr/lib64/sane/libsane-mustek_usb2.so lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1 lib64sane1:/usr/lib64/sane/libsane-mustek_usb.so.1.0.22 lib64sane1:/usr/lib64/sane/libsane-mustek_usb2.so.1 lib64sane1:/usr/lib64/sane/libsane-mustek_usb2.so.1.0.22 Testing with canon scanner mga2 64 Anybody else have scanners to test with?
Whiteboard: mga2-32-ok? => mga2-32-ok? mga2-64-ok?
Downloaded updates for mga2-32, as that's my only machine with a SCSI card. tested with HP ScanJet 5p SCSI, all OK, no regressions.
CC: (none) => wrw105
(In reply to claire robinson from comment #17) > Anybody else have scanners to test with? The only thing I can add here is that I have an HP scanner and XSane on M2 & M3 have always worked just fine for me.
CC: (none) => wilcal.int
I've tested with a cannon pixma mp150 all in one. We still need an advisory before the update can be validated.
Advisory 6120.adv committed to svn. Validating the update. Someone from the sysadmin team please push 6120.adv to updates.
Keywords: (none) => validated_updateWhiteboard: mga2-32-ok? mga2-64-ok? => mga2-32-ok mga2-64-okCC: (none) => sysadmin-bugs
Update pushed: http://advisories.mageia.org/MGAA-2013-0109.html
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED