apport-kde crashed with SIGSEGV in ~QX11WindowSurface()

[jajaX]

Binary package hint: apport

hi (sorry for my bad english)

after last update today and after reboot, apport-kde crash after startup kde load.

ProblemType: Crash
Architecture: i386
CrashReports:
 600:1000:1000:3674238:2009-10-23 09:58:35.000000000 +0200:2009-10-23 09:58:36.000000000 +0200:/var/crash/_usr_bin_vlc.1000.crash
 600:1000:1000:9007158:2009-10-23 10:25:35.000000000 +0200:2009-10-23 10:29:12.000000000 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash
Date: Fri Oct 23 10:25:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-kde
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.9.3-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x4a8df32 <~QX11WindowSurface+82>: mov 0x8(%eax),%eax
 PC (0x04a8df32) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ~QX11WindowSurface (this=0xa315e40,
 ~QWidgetBackingStore (this=0xa22ff80,
 QWidgetPrivate::deleteExtra (this=0xa327be0)
 ~QWidgetPrivate (this=0xa327be0,
 ~QDialogPrivate (this=0xa327be0,
Title: apport-kde crashed with SIGSEGV in ~QX11WindowSurface()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip disk floppy fuse lpadmin mysql plugdev sambashare scanner video
XsessionErrors: (polkit-gnome-authentication-agent-1:3055): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

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