Ubuntu
system-config-printer package

print configuration crashed while adding printer

Bug #361629 reported by ACKiX on 2009-04-15

This bug report is a duplicate of: Bug #329974: SIGSEGV in _nss_dns_gethostbyname2_r() browsing Samba printers, i386 only. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	system-config-printer (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: system-config-printer

I was adding a Windows Network printer and the printer configuration window crashed while searching for Windows Network printers.

ProblemType: Crash
Architecture: i386
CupsErrorLog:

DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
InterpreterPath: /usr/bin/python2.6
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: ASUSTeK Computer INC. 1000H
Package: system-config-printer-gnome 1.1.3+git20090218-0ubuntu19
PackageArchitecture: all
Papersize: a4
ProcCmdLine: root=UUID=eed41f03-54d2-47f7-b668-1e31edcaadce ro quiet splash
ProcCmdline: python /usr/share/system-config-printer/system-config-printer.py
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-8.24array1-netbook-eeepc
Signal: 11
SourcePackage: system-config-printer
StacktraceTop:
_nss_dns_gethostbyname2_r ()
?? () from /lib/tls/i686/cmov/libc.so.6
getaddrinfo () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libsmbclient.so.0
?? () from /usr/lib/libsmbclient.so.0
Title: system-config-printer.py crashed with SIGSEGV in _nss_dns_gethostbyname2_r()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

ACKiX (ackix) wrote on 2009-04-15:

BootDmesg.txt Edit (36.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1023 bytes, text/plain; charset="utf-8")
HalComputerInfo.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Locale.txt Edit (329 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (10.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (626 bytes, text/plain; charset="utf-8")
PrintingPackages.txt Edit (773 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (42.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (757 bytes, text/plain; charset="utf-8")
Registers.txt Edit (537 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-15: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (15.9 KiB, text/plain)

StacktraceTop:_nss_dns_gethostbyname2_r (name=0xb5235970 "XCOMP", af=10,
gaih_inet (name=0xb5235970 "XCOMP", service=0x0,
*__GI_getaddrinfo (name=0xb5235970 "XCOMP", service=0x0,
internal_resolve_name (name=0xb5235970 "XCOMP",
resolve_name (name=0xb5235970 "XCOMP",

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-15: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (15.9 KiB, text/plain)

Changed in system-config-printer (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

ACKiX (ackix) on 2009-04-15

visibility:

private → public

Revision history for this message

Ed Comer (celem) wrote on 2009-05-06:

Screenshot-Application problem.png Edit (29.8 KiB, image/png)

I previously submitted bug 368273 but the auto bug report via apport produced a list that included this bug as well as the related 329974, 344218, 359088, 360524 and this bug, 361629. Of interest, I had successfully built a windows shared printer using the workaround that I described in bug report 368273 but attempted adding a second Windows shared printer while apport was running. The printer correctly appeared in the dialogue. When I deleted the printer and tried again, the bug reappeared, this time captured by apport.