bleachbit.py crashed with TypeError: type 'gio.MemoryOutputStream' is not dynamically allocated but its base type '__main__.GPollableOutputStream' is dynamically allocated

Bug #1426218 reported by dino99 on 2015-02-27
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bleachbit (Ubuntu)
Undecided
Unassigned

Bug Description

Get that crash on this vivid i386 system booted with systemd-sysv on a gnome-shell session

checking the upgraded packages list recently applied, maybe it could be related to python 2.7.8-3 upgrade

http://www.pygtk.org/docs/pygobject/class-giomemoryoutputstream.html
https://people.gnome.org/~gcampagna/docs/Gio-2.0/Gio.MemoryOutputStream.get_size.html
http://bugs.python.org/issue22079

Similar report: lp:1426017

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: bleachbit 1.6-1
ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0
Uname: Linux 3.19.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Thu Feb 26 17:35:06 2015
ExecutablePath: /usr/share/bleachbit/bleachbit.py
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/bleachbit
PythonArgs: ['/usr/bin/bleachbit']
SourcePackage: bleachbit
Title: bleachbit.py crashed with TypeError: type 'gio.MemoryOutputStream' is not dynamically allocated but its base type '__main__.GPollableOutputStream' is dynamically allocated
Traceback: TypeError: type 'gio.MemoryOutputStream' is not dynamically allocated but its base type '__main__.GPollableOutputStream' is dynamically allocated
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dino99 (9d9) wrote :
information type: Private → Public
dino99 (9d9) on 2015-02-27
description: updated
description: updated
description: updated
dino99 (9d9) on 2015-02-27
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bleachbit (Ubuntu):
status: New → Confirmed
James Page (james-page) wrote :

Probably this:

    - Issue #22079: PyType_Ready() now checks that statically allocated type has
      no dynamically allocated bases.

dino99 (9d9) wrote :

Looks like many apps are/will be affected by that new function check.

dino99 (9d9) on 2015-02-27
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers