Bug 6902

Hi Ole,

Thanks for your report. 
Sorry that we didn't reply to it before, we are short on active bugsquad members. :-(

If you still have the problems, could you then please read the following
https://wiki.mageia.org/en/Triage_guide#Printer_problems
https://wiki.mageia.org/en/Triage_guide#Scanner_problems

and attach the suggested files and outputs?

If the problem still exists, in which Mageia version(s) is that?

CC: (none) => dmorganec, marja11

Created attachment 4262 [details]
Correspondence with Marja

Hi Ole,

Thanks for all the feedback :-)

Do you mind putting it in a comment in the bug report, so that dmorgan
(the packager/developer who will hopefully fix the bug) and others who
know more than me, can see it too?

Kind regards,
Marja

On 12/08/13 17:48, Ole Madsen wrote:
>
> <bugzilla-daemon@mageia.org <mailto:bugzilla-daemon@mageia.org>>:
> unknown user: "bugzilla-daemon@mageia.org
> <mailto:bugzilla-daemon@mageia.org>"
> Thanks Marja, nice to hear from you.
>
> The problem is still there.  I can print but not scan.  I am running
> Mageia 2 on this machine.  I tried Mageia 3 on different hardware, but
> had no luck getting the Samsung scanner working there either.  I am
> connecting via the USB port.
>
>
> Here are the outputs from the terminal:
>
> [root@localhost ole]# tailf /var/log/messages 2>&1 | tee output.txt
> Aug 11 19:41:26 localhost kernel: [ 1978.648980] usb 5-4: New USB device
> found, idVendor=04e8, idProduct=3432
> Aug 11 19:41:26 localhost kernel: [ 1978.648991] usb 5-4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Aug 11 19:41:26 localhost kernel: [ 1978.648998] usb 5-4: Product:
> SCX-4x26 Series
> Aug 11 19:41:26 localhost kernel: [ 1978.649004] usb 5-4: Manufacturer:
> Samsung Electronics Co., Ltd.
> Aug 11 19:41:26 localhost kernel: [ 1978.649010] usb 5-4: SerialNumber:
> 6575BAXB300103B
> Aug 11 19:41:26 localhost mtp-probe: bus: 5, device: 4 was not an MTP device
> Aug 11 19:41:28 localhost hp[3441]: io/hpmud/pp.c 627: unable to read
> device-id ret=-1
> Aug 11 19:41:28 localhost python: io/hpmud/pp.c 627: unable to read
> device-id ret=-1
> Aug 11 19:41:28 localhost udev-configure-printer: Re-enabled printer
> ipp://localhost:631/printers/Samsung
> Aug 11 19:41:28 localhost udev-configure-printer: Re-enabled printer
> ipp://localhost:631/printers/Samsung-SCX-4x26-Series
>
>
> [root@localhost ole]# sane-find-scanner
>
>    # sane-find-scanner will now attempt to detect your scanner. If the
>    # result is different from what you expected, first make sure your
>    # scanner is powered up and properly connected to your computer.
>
>    # No SCSI scanners found. If you expected something different, make
> sure that
>    # you have loaded a kernel SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.],
> product=0x3432 [SCX-4x26 Series]) at libusb:005:004
>    # Your USB scanner was (probably) detected. It may or may not be
> supported by
>    # SANE. Try scanimage -L and read the backend's manpage.
>
>    # Not checking for parallel port scanners.
>
>    # Most Scanners connected to the parallel port or other proprietary ports
>    # can't be detected by this program.
> [root@localhost ole]#
>
>
>
> [ole@localhost ~]$ scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> [ole@localhost ~]$
>
>
> Best regards
> Ole
>
> ------------------------------------------------------------------------
> *From:* Marja van Waes <bugzilla-daemon@mageia.org>
> *To:* philimorept@yahoo.com
> *Sent:* Sunday, August 11, 2013 11:06:08 AM
> *Subject:* [Bug 6902] Samsung printer/scanner SCX 4826 FN does not work
>
> https://bugs.mageia.org/show_bug.cgi?id=6902
>
> Marja van Waes <marja11@xs4all.nl <mailto:marja11@xs4all.nl>> changed:
>
>            What    |Removed |Added
> ----------------------------------------------------------------------------
>                  CC|                            |dmorganec@gmail.com
> <mailto:dmorganec@gmail.com>,
>                    |                            |marja11@xs4all.nl
> <mailto:marja11@xs4all.nl>
>
> --- Comment #1 from Marja van Waes <marja11@xs4all.nl
> <mailto:marja11@xs4all.nl>> ---
> Hi Ole,
>
> Thanks for your report.
> Sorry that we didn't reply to it before, we are short on active bugsquad
> members. :-(
>
> If you still have the problems, could you then please read the following
> https://wiki.mageia.org/en/Triage_guide#Printer_problems
> https://wiki.mageia.org/en/Triage_guide#Scanner_problems
>
> and attach the suggested files and outputs?
>
> If the problem still exists, in which Mageia version(s) is that?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

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

The problem persists on version 3.

Status: RESOLVED => REOPENED
Version: 2 => 3
Resolution: OLD => (none)

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => OLD