brcupsconfig3 assert failure: *** stack smashing detected ***: /usr/Brother/cupswrapper/brcupsconfig3 terminated

[Robin.He]

Binary package hint: brother-cups-wrapper-laser

The printer was not power on, and I try to print a document via my LAN, then the error happend.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brother-cups-wrapper-laser 2.0.1-2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
AssertionMessage: *** stack smashing detected ***: /usr/Brother/cupswrapper/brcupsconfig3 terminated
Date: Tue Jun 7 02:44:46 2011
ExecutablePath: /usr/Brother/cupswrapper/brcupsconfig3
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/Brother/cupswrapper/brcupsconfig3 HL2070N /etc/cups/ppd/Brother_HL-2070N_series.ppd 0 InputSlot=TRAY1\ Sleep=PrinterDefault\ number-up=1\ PageSize=A4\ TonerSaveMode=Off\ Resolution=600dpi\ BrMediaType=PLAIN\ job-uuid=urn:uuid:345c2c39-d1e6-3904-6515-88756ad61e8a\ job-originating-host-name=localhost\ time-at-creation=1307385885\ time-at-processing=1307385885
ProcEnviron:
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
Signal: 6
SourcePackage: brother-cups-wrapper-laser
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __fortify_fail () from /lib/i386-linux-gnu/libc.so.6
Title: brcupsconfig3 assert failure: *** stack smashing detected ***: /usr/Brother/cupswrapper/brcupsconfig3 terminated
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #438356, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.