empathy crashed with SIGSEGV in gtk_tree_view_get_cursor()

[Gavin Panella]

I was resizing the contact's window using Ctrl-Alt-NumPad6 in Unity and getting frustrated that repeated presses were not cycling through narrower sizes as before. I then tried to use a shortcut I half-remembered to maximize vertically. I tried Alt-v to no effect, then Super-v, which did something weird to the contact list. Empathy crashed within a few seconds.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Mon Jan 16 17:29:27 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb209936207: mov 0x20(%rax),%r12d
 PC (0x7fb209936207) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_tree_view_get_cursor () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in gtk_tree_view_get_cursor()
UpgradeStatus: Upgraded to precise on 2012-01-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #914927, 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.