Bug 15419 - First time changing printer properties removes printer from system-config-printer screen
Summary: First time changing printer properties removes printer from system-config-pri...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-04 10:05 CET by Herman Viaene
Modified: 2015-06-03 17:16 CEST (History)
1 user (show)

See Also:
Source RPM: system-config-printer
CVE:
Status comment:


Attachments

Description Herman Viaene 2015-03-04 10:05:34 CET
Description of problem:


Version-Release number of selected component (if applicable): Mageia 5 rc 64-bit


How reproducible: Once


Steps to Reproduce:
1.Fresh install Mageia 5 rc (second)
2.Open MCC and go to printerdrake.
3.Follow steps to install printer packages (cups e.a.)
4.Add printer, select network printer.
5. HP Officejet Pro 8100 found (wireless connection)
6. Complete steps of printer installation (search for drivers....)
7. Printer is shown in printerdrake. Right click on, it and switch off "shared".
8.Initial printerdrake screen is shown, but empty, no installed printer shown.
9. Leave printerdrake to MCC and restart printerdrake: now installed printer is shown and properties can be changed.


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-03-07 03:37:29 CET
printerdrake has been gone for years.  We now use system-config-printer from Fedora.

Summary: First time changing printer properties removes printer from printerdrake screen. => First time changing printer properties removes printer from system-config-printer screen
Source RPM: printerdrake => system-config-printer

Comment 2 Shlomi Fish 2015-06-03 17:16:46 CEST
(In reply to David Walser from comment #1)
> printerdrake has been gone for years.  We now use system-config-printer from
> Fedora.

Since this seems to be the case and since this bug received no reply, I'm going to close it. Thanks!

Status: NEW => RESOLVED
CC: (none) => shlomif
Resolution: (none) => INVALID


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