gtimer crashed with SIGSEGV in __libc_start_main()

[Susan Cragin]

I had just installed gtimer and tried to open it.
I am running Quantal with all updates.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gtimer 2.0.0-1
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic i686
ApportVersion: 2.1.1-0ubuntu2
Architecture: i386
CheckboxSubmission: 7ff03e7bc08d6fa0280a0998c43f449f
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Mon Jun 11 09:31:53 2012
ExecutablePath: /usr/bin/gtimer
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120528)
ProcCmdline: gtimer
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80521e0: mov 0x8(%eax),%ebx
 PC (0x080521e0) ok
 source "0x8(%eax)" (0x49a25408) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gtimer
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: gtimer crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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