synaptic crashed with SIGSEGV in g_closure_invoke()

[Markus Naeher]

1)
lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2)
apt-cache policy synaptic
synaptic:
  Installiert: 0.75.9
  Kandidat: 0.75.9
  Versionstabelle:
 *** 0.75.9 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

3)
I was searching for a package in the Quick filter

4)
It crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.9
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 11 20:53:19 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330)
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
 LANGUAGE=de:en
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x44c2f8: mov (%rdx),%rdx
 PC (0x0044c2f8) ok
 source "(%rdx)" (0x00000041) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: synaptic crashed with SIGSEGV in g_closure_invoke()
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 this software better. This particular crash has already been reported and is a duplicate of bug #927501, 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.