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

[leonardo2887]

Binary package hint: brother-cups-wrapper-laser

brother hl-2035 does not print

ProblemType: Crash
Architecture: i386
AssertionMessage: *** stack smashing detected ***: /usr/Brother/cupswrapper/brcupsconfig3 terminated
CrashCounter: 1
Date: Thu Oct 22 11:03:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/Brother/cupswrapper/brcupsconfig3
NonfreeKernelModules: wl
Package: brother-cups-wrapper-laser 2.0.1-2-0ubuntu5
ProcCmdline: /usr/Brother/cupswrapper/brcupsconfig3 HL2030 /etc/cups/ppd/Brother-HL-2030-series.ppd 0 BrMediaType=PLAIN\ Resolution=300dpi\ InputSlot=TRAY1\ Sleep=PrinterDefault\ number-up=1\ TonerSaveMode=Off\ PageSize=Letter\ job-uuid=urn:uuid:6d4ae0ee-9dd0-382b-565e-55d9b1b03549\ job-originating-host-name=localhost
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: brother-cups-wrapper-laser
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 __fortify_fail () from /lib/tls/i686/cmov/libc.so.6
Title: brcupsconfig3 assert failure: *** stack smashing detected ***: /usr/Brother/cupswrapper/brcupsconfig3 terminated
Uname: Linux 2.6.31-14-generic i686
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.

[Brian J. Murrell (brian-interlinx)]

This bug has been marked a duplicate of a bug I don't have access to see!!

> 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.

I'd love to, but I am not allowed.

I can't see how it's acceptable to close out a bug as duplicate of a bug that everyone is not allowed to see.

Please either fix the permissions on bug 438356 or reopen this bug so that we can work it.

Thanx.