Bug 11427 - drakconf fails to open the printer configuration dialog
Summary: drakconf fails to open the printer configuration dialog
Status: RESOLVED DUPLICATE of bug 11541
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard: 4alpha3
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-10 12:19 CEST by Juergen Harms
Modified: 2013-10-26 18:45 CEST (History)
0 users

See Also:
Source RPM: drakconf-12.42-2.mga4
CVE:
Status comment:


Attachments
Output when drakconf is launched from a root console (1.10 KB, text/plain)
2013-10-10 12:21 CEST, Juergen Harms
Details

Description Juergen Harms 2013-10-10 12:19:19 CEST
Description of problem:

Trying to configure printers in cauldron, hitting "setup the printers ..." in the hardware tab of the drakconf window fails: a popup window says "This program has exited abnormally". 


Version-Release number of selected component (if applicable):
drakconf-12.42-2.mga4


How reproducible:
100%


Steps to Reproduce:
1. Do mcc -> hardware tab
2. hit setup the printer(s), the print job queues, ...
3.

A similar result is obtained by lauching drakconf from a root console. See the attachment for the console output obtained.

Note: directly launching "system-config-printer" from a root console works and can be used as a work-around - no problem in configuring printers this way (except the system-config-printer does not display an icon for my local printer - I will file a separate bug on this)

Reproducible: 

Steps to Reproduce:
Comment 1 Juergen Harms 2013-10-10 12:21:30 CEST
Created attachment 4426 [details]
Output when drakconf is launched from a root console
Juergen Harms 2013-10-10 12:23:12 CEST

Priority: Normal => High
Whiteboard: (none) => 4alpha3

David Walser 2013-10-10 19:15:09 CEST

Assignee: bugsquad => nicolas.lecureuil

Comment 2 Manuel Hiebel 2013-10-26 18:45:09 CEST
lets keep the other one (and thanksfor seeing it)

*** This bug has been marked as a duplicate of bug 11541 ***

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


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