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

Bug #1543585 reported by Thomas A. F. Thorne
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pygobject (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was starting up War For The Overworld from the Steam application. The game said that Steam had had some sort of error and the game could not continue to load. The game then sat there, seemingly frozen. After a short while I exited it and found a report about a Python 2.7 error waiting to be reported.

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
CurrentDesktop: Unity
Date: Tue Feb 9 13:43:49 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

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I experienced another problem after I restarted Steam and ran up WftO again. This time both Steam and the game seemed fine so I wondered if it was a differnt bug and chose to create Bug #1543591 which may be a duplicate of this one.

Just in case it is related to Steam the About Steam menu shows
Build: Feb 4 2016, at 12:25:24
Steam API: v017
Steam package versions: 1454620878

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IA__gdk_pixbuf_render_threshold_alpha (pixbuf=0x7fb73c8215d0, bitmap=0x1e569a0, src_x=1, src_y=1015158400, dest_x=-975986996, dest_y=-975987012, width=12722, height=0, alpha_threshold=0) at /build/gtk+2.0-KsZSEA/gtk+2.0-2.24.23/gdk/gdkpixbuf-render.c:61
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in python2.7 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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!

tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I have had a look through the logs and re-traced items. Nothing looks that sensitive so I am setting this to public on the belief that there is no need for it to remain private.

information type: Private → Public
Changed in python2.7 (Ubuntu):
status: Invalid → New
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

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.

Revision history for this message
Matthias Klose (doko) wrote :

Most likely an issue with one of the gobject/gtk bindings

affects: python2.7 (Ubuntu) → pygobject (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.