Bug 9276 - Lexmark S315 does not appear in the printer setup menu
Summary: Lexmark S315 does not appear in the printer setup menu
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks: 18367
  Show dependency treegraph
 
Reported: 2013-03-06 16:32 CET by j-c P
Modified: 2022-06-05 00:14 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description j-c P 2013-03-06 16:32:00 CET
Description of problem:I would like to have a driver to install the MFP Lexmark S315


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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-03-09 12:11:36 CET
nothing here http://www.openprinting.org/printers/manufacturer/Lexmark

some more info http://ubuntuforums.org/archive/index.php/t-1994717.html

Keywords: (none) => UPSTREAM

Comment 2 Manuel Hiebel 2013-10-11 23:25:58 CEST
Changing version to Cauldron for keeping this request.
When Mageia 2 will be in End Of Life in a little more than one month, we will close these version bugs.

If the package is present in Mageia 3 or Cauldron, you can close this bug. Thanks.

--
Mageia Bugsquad

Version: 2 => Cauldron

Marja Van Waes 2016-05-05 10:22:15 CEST

Blocks: (none) => 18367

Comment 3 Marja Van Waes 2016-08-10 19:41:24 CEST
On the 25th of July, Phillipem uploaded the following packages to 
Cauldron's core/updates_testing:

    system-config-printer-1.5.7-5.mga6.i586
    system-config-printer-applet-1.5.7-5.mga6.i586
    system-config-printer-udev-1.5.7-5.mga6.i586

    system-config-printer-libs-1.5.7-5.mga6.noarch

    system-config-printer-1.5.7-5.mga6.x86_64
    system-config-printer-applet-1.5.7-5.mga6.x86_64
    system-config-printer-udev-1.5.7-5.mga6.x86_64


@ Anyone reading this:

* If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report.

* If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.

CC: (none) => makowski.mageia, marja11

Comment 4 Samuel Verschelde 2016-10-11 20:53:49 CEST
Assigning this package request to all packagers collectively. On a voluntary basis, one of them might want to integrate it to the distribution and maintain it for bug and security fixes.

You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Assignee: bugsquad => pkg-bugs

Comment 5 Marja Van Waes 2016-11-02 09:29:24 CET
Sorry, bugs@ml and pkg-bugs@ml members, for the avalanche.

72 bugs with the "New RPM package request" component, had a severity of "normal" or more, which can lead to losing precious time when searching Bugzilla for bugs that urgently need to get fixed

Now mass-changing that to "enhancement", as it should be for package requests.

https://wiki.mageia.org/en/How_to_report_a_bug_properly#How_to_file_a_package_request

@ the reporter of this package request

Please check in http://madb.mageia.org/ whether this software did already get packaged, and close this bug report if it did.
Please do also close it if you find a package with the same purpose, that meets your needs.

Severity: normal => enhancement

Comment 6 Morgan Leijström 2018-04-18 11:09:52 CEST
Still valid on current Mageia?
Said to work perfectly here:
http://www.openprinting.org/printer/Lexmark/Lexmark-MS315dn

CC: (none) => fri

Comment 7 sturmvogel 2022-06-05 00:14:41 CEST
After 6 years that Marja asked for test of the imported packages (comment 3) and nobody answered Morgan's "ping" from comment 6, one can assume that nobody uses this printer type anymore or it works as intended (see also link in comment 6).

Closing as OLD.

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


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