crashed with SIGSEGV in _IO_file_xsputn()

Bug #863123 reported by Seinfeld on 2011-09-30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-defaults (Ubuntu)
system-config-printer (Ubuntu)

Bug Description

Attempting to add a printer using the following URI resulted in the application crashing:


Steps to Reproduce
- System Settings | Printing | Add
- When presented with the Enter URI enter parallel:/dev/usblp0

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-config-printer-gnome 1.3.6+20110831-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Sep 30 02:57:50 2011
ExecutablePath: /usr/share/system-config-printer/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110928)
InterpreterPath: /usr/bin/python2.7
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Apple Inc. MacBookPro8,2
PackageArchitecture: all
Papersize: letter
ProcCmdline: /usr/bin/python /usr/share/system-config-printer/
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=43debe9c-6ffd-4a6d-a4d7-8a64c3f551db ro quiet splash vt.handoff=7
 Segfault happened at: 0x7fed7dd06bb3: mov %al,(%rdi)
 PC (0x7fed7dd06bb3) ok
 source "%al" ok
 destination "(%rdi)" (0x7fed7f1130c3) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: system-config-printer
 ?? () from /lib/x86_64-linux-gnu/
 _IO_file_xsputn () from /lib/x86_64-linux-gnu/
 fwrite () from /lib/x86_64-linux-gnu/
 ?? ()
 ?? ()
Title: crashed with SIGSEGV in _IO_file_xsputn()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare 09/09/11
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B1E.1109091244
dmi.board.asset.tag: Base Board Asset Tag# Mac-94245A3940C91C80
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245A3940C91C80
dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B1E.1109091244:bd09/09/11:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: MacBookPro8,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Seinfeld (seinfeld-zealot) wrote :

 __mempcpy_sse2 () at ../sysdeps/x86_64/memcpy.S:162
 _IO_new_file_xsputn (n=44, data=<optimized out>, f=0x7fed7e0198e0) at fileops.c:1337
 _IO_new_file_xsputn (f=0x7fed7e0198e0, data=<optimized out>, n=44) at fileops.c:1292
 _IO_fwrite (buf=<optimized out>, size=1, count=44, fp=0x7fed7e0198e0) at iofwrite.c:45
 string_print (op=<optimized out>, fp=0x7fed7e0198e0, flags=<optimized out>) at ../Objects/stringobject.c:883

Changed in system-config-printer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in system-config-printer (Ubuntu):
status: New → Confirmed
visibility: private → public
Till Kamppeter (till-kamppeter) wrote :

Probably a problem somewhere in the Python interpreter, a problem of system-config-printer should have given a Python traceback.

I cannot reproduce the problem on up-to-date Oneiric, both on 64 bit and 32 bit.

Does the problem also appear if you enter another URI, like for example


You are probably using a USB-to-parallel adapter. Does nothing appear in the list of auto-detected printers, even nothing without your printer's model name, like "Unknown Printer"? Can you follow the instructions in the section "USB printer" on

Changed in python-defaults (Ubuntu):
status: New → Incomplete
Changed in system-config-printer (Ubuntu):
status: Confirmed → Incomplete
Changed in python-defaults (Ubuntu):
importance: Undecided → Medium

I have not been able to reproduce the crash since originally opening the bug. It only crashed the first time I tried to setup the printer using the URI like the behavior described in the duplicate of this bug (Bug #865967).

Launchpad Janitor (janitor) wrote :

[Expired for python-defaults (Ubuntu) because there has been no activity for 60 days.]

Changed in python-defaults (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.]

Changed in system-config-printer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers