Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1203208

Summary: [abrt] system-config-printer-1.4.2-1.fc19: newprinter.py:2995:on_entNPTNetworkHostname_changed:TypeError: set_cursor() got an unexpected keyword argument 'cell'
Product: Red Hat Enterprise Linux 7 Reporter: Tim Waugh <twaugh>
Component: system-config-printerAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jpopelka
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:020cde2ae495588e712b1d9139a31540189ebe90
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1006692 Environment:
Last Closed: 2015-03-23 13:39:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1006692    
Bug Blocks:    
Attachments:
Description Flags
system-config-printer-set-cursor-cell.patch none

Description Tim Waugh 2015-03-18 11:56:52 UTC
Created attachment 1003183 [details]
system-config-printer-set-cursor-cell.patch

This also affects Red Hat Enterprise Linux 7, and has been hit a few times on e.g. CentOS 7:
https://retrace.fedoraproject.org/faf/problems/277684/

Reproduced with system-config-printer-1.4.1-19.el7.

+++ This bug was initially created as a clone of Bug #1006692 +++

Description of problem:
Trying to add a network printer.  Put in ipp:// network location and the app crashed

Version-Release number of selected component:
system-config-printer-1.4.2-1.fc19

Additional info:
reporter:       libreport-2.1.6
cmdline:        /usr/bin/python /usr/share/system-config-printer/system-config-printer.py
dso_list:       system-config-printer-libs-1.4.2-1.fc19.noarch
executable:     /usr/share/system-config-printer/system-config-printer.py
kernel:         3.10.10-200.fc19.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
newprinter.py:2995:on_entNPTNetworkHostname_changed:TypeError: set_cursor() got an unexpected keyword argument 'cell'

Traceback (most recent call last):
  File "/usr/share/system-config-printer/newprinter.py", line 2995, in on_entNPTNetworkHostname_changed
    start_editing=False)
TypeError: set_cursor() got an unexpected keyword argument 'cell'

Local variables in innermost frame:
path: <GtkTreePath at 0x200d3b0>
model: <TreeStore object at 0x246a870 (GtkTreeStore at 0x1f16a30)>
ent: <Entry object at 0x1c03320 (GtkEntry at 0x1cf31c0)>
self: <NewPrinterGUI object at 0x19775a0 (newprinter+NewPrinterGUI at 0x19fd560)>
text: 'ipp:192.168.1.4'

--- Additional comment from Matt McAdoo on 2013-09-11 02:24:39 EDT ---



--- Additional comment from Matt McAdoo on 2013-09-11 02:24:47 EDT ---



--- Additional comment from Tim Waugh on 2013-09-11 07:00:44 EDT ---

Should be fixed upstream in commit ce23926.

--- Additional comment from Fedora Update System on 2013-10-22 12:55:27 EDT ---

system-config-printer-1.4.3-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/system-config-printer-1.4.3-1.fc20

--- Additional comment from Fedora Update System on 2013-10-22 12:57:44 EDT ---

system-config-printer-1.4.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/system-config-printer-1.4.3-1.fc19

--- Additional comment from Fedora Update System on 2013-10-22 23:30:27 EDT ---

Package system-config-printer-1.4.3-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing system-config-printer-1.4.3-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-19726/system-config-printer-1.4.3-1.fc19
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-11-06 02:38:58 EST ---

system-config-printer-1.4.3-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from Fedora Update System on 2013-11-10 02:43:57 EST ---

system-config-printer-1.4.3-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 1 Tim Waugh 2015-03-23 13:39:05 UTC

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