Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1063347 - Problem with IBM Global Printer Installer module
Summary: Problem with IBM Global Printer Installer module
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firstboot
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Vratislav Podzimek
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-10 14:40 UTC by Nick Bronn
Modified: 2014-02-11 12:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-11 12:20:33 UTC


Attachments (Terms of Use)
debug output (deleted)
2014-02-10 14:40 UTC, Nick Bronn
no flags Details

Description Nick Bronn 2014-02-10 14:40:01 UTC
Created attachment 861426 [details]
debug output

Description of problem:

After launching IBM Global Printer Installer, afterboot.py reports "An error has occured in the IBM Global Printer Installer module" with a traceback. Last few lines indicate how to file bug report.
 
Version-Release number of selected component (if applicable):
N/A

How reproducible:
Recently, every time it is launched.

Steps to Reproduce:
1. After having problems printing, I was advised to delete printers and add them again. This worked the first time.
2. Delete printers via CUPS
3. Trying and failing to run IBM Global Printer Installer

Actual results:
Error from afterboot.py and debug output (attached)

Expected results:
Ability to add network printers

Additional info:

Comment 2 Vratislav Podzimek 2014-02-11 12:20:33 UTC
The afterboot.py module is not a part of the firstboot package, it is a part of the third-party module. Thus I cannot fix this issue.


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