ebtables crashed with SIGSEGV in ebt_initialize_entry()

[Jerry]

might be a duplicate,
but sending anyway to be sure...

64 bit machines and different hardware
and Ubuntu releases listed in some of what
I read on the other bug report...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ebtables 2.0.9.2-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Wed Dec 7 13:59:56 2011
ExecutablePath: /sbin/ebtables
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /sbin/ebtables -t nat -L
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0xde3ba8 <ebt_initialize_entry+104>: movl $0x1,0x4c(%eax)
 PC (0x00de3ba8) ok
 source "$0x1" ok
 destination "0x4c(%eax)" (0x0000004c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ebtables
StacktraceTop:
 ebt_initialize_entry () from /lib/ebtables/libebtc.so
 do_command () from /lib/ebtables/libebtc.so
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: ebtables crashed with SIGSEGV in ebt_initialize_entry()
UpgradeStatus: Upgraded to precise on 2011-11-25 (11 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ebt_initialize_entry (e=0x8d19008) at libebtc.c:169
 do_command (argc=4, argv=0xbf9ad684, exec_style=0, replace_=0x804a040) at ebtables.c:573
 ?? ()
 __libc_start_main (main=0x8048470, argc=4, ubp_av=0xbf9ad684, init=0x8048590 <ebt_early_init_once@plt>, fini=0x8048600 <main+64>, rtld_fini=0x3a3bc0, stack_end=0xbf9ad67c) at libc-start.c:226
 ?? ()

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 899315, so it 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.