python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable() possibly after starting WftO from Steam

[Thomas A. F. Thorne]

I had finished reporting bug #1543585 so I restarted Steam and attempted to restart WftO. This time the game loaded without an issue and I was able to play it. Nothing seemed wrong with the Steam interface either. This seemed someone different to before so I chose to open a new bug and see what the traces say.

About Steam shows
Build: Feb 4 2016, at 12:25:24
Steam API: v017
Steam package versions: 1454620878

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: python2.7-minimal 2.7.6-8ubuntu0.2
ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
Uname: Linux 3.16.0-60-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Feb 9 13:48:31 2016
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2015-03-12 (333 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: python indicator-applet-skype.py
SegvAnalysis:
 Segfault happened at: 0x5b763d: mov 0x10(%rax),%rdi
 PC (0x005b763d) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 gdk_pixbuf_get_from_drawable () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libwnck-1.so.22
 ?? () from /usr/lib/libwnck-1.so.22
 ?? () from /usr/lib/libwnck-1.so.22
 ?? () from /usr/lib/libwnck-1.so.22
Title: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 IA__gdk_pixbuf_render_threshold_alpha (pixbuf=0x7f06b0f9c6c0, bitmap=0x17169a0, src_x=1, src_y=-1325807744, dest_x=1352621468, dest_y=1352621452, width=2284, height=0, alpha_threshold=0) at /build/gtk+2.0-KsZSEA/gtk+2.0-2.24.23/gdk/gdkpixbuf-render.c:61
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libltdl7
no debug symbol package found for libfreetype6
no debug symbol package found for libtiff5
no debug symbol package found for libxcb-util0
no debug symbol package found for libdbusmenu-glib4
no debug symbol package found for libstartup-notification0
no debug symbol package found for libunity-gtk2-parser0
no debug symbol package found for libselinux1
no debug symbol package found for unity-gtk2-module
no debug symbol package found for libgirepository-1.0-1
no debug symbol package found for overlay-scrollbar-gtk2
no debug symbol package found for libharfbuzz0b
no debug symbol package found for libunity-protocol-private0
no debug symbol package found for libunity9
no debug symbol package found for libjbig0

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Thomas A. F. Thorne (tafthorne)]

I am confident that I had up to date packages when this bug report was generated. Tracing took almost two weeks, which seems a rather long time to me. Is the tracing service OK?
In any case this bug is not invalid as it is not spam. It might be hard to investigate but that does not devalue its status. Setting to New for now. I might be able to reproduce this again in the next few days with the latest packages installed. If I cannot then it may be safe to assume this has been resolved.

[Thomas A. F. Thorne (tafthorne)]

I have looked through the logs and traces and cannot see anything sensitive in them. Setting this to public as I cannot see a reason to keep it private.

[Matthias Klose (doko)]

more likely an issue in some bindings

[Launchpad Janitor (janitor)]

[Expired for pygobject (Ubuntu) because there has been no activity for 60 days.]