Pype segfault on new file/open file

Bug #3028 reported by Wouter Stomp
22
Affects Status Importance Assigned to Milestone
pype (Ubuntu)
Fix Released
High
MOTU Reviewers Team

Bug Description

Pype gives a segmentation fault when trying to create a new document or opening a file:

[ Mon Oct 10 18:45:42 2005 ] Loading history from /home/wouter/.pype/history.txt
[ Mon Oct 10 18:45:45 2005 ] found filetype-specific defaults python

(python:15111): Gtk-CRITICAL **: gtk_pixmap_new: assertion `val != NULL' failed

(python:15111): Gtk-CRITICAL **: gtk_box_pack_start: assertion `GTK_IS_WIDGET (child)' failed
Segmentation fault

Changed in pype:
assignee: nobody → motu
Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

There is a new upstream to upload when dapper is open. Anyway, pype is very young, promising but young.

Revision history for this message
Yann Rouillard (yann-pleiades) wrote :

This bug is still present on dapper, version is 2.2.1-1

Changed in pype:
status: Unconfirmed → Confirmed
Revision history for this message
Yann Rouillard (yann-pleiades) wrote : Pype last upstream debdiff

I tested last upstream version (2.2.2), and this version solves this bug.
I will notice the debian developper so we can sync the package.

I attach a debdiff from the previous package in case the debian developper doesn't react.

Revision history for this message
Yann Rouillard (yann-pleiades) wrote :

No response from debian maintainer, I think we can upload this version.

Changed in pype:
assignee: motu → motureviewers
status: Confirmed → Fix Committed
Revision history for this message
Yann Rouillard (yann-pleiades) wrote :

I just saw last version was uploaded by doko.
Dunno if my debdiff was used.

Changed in pype:
status: Fix Committed → Fix Released
Revision history for this message
Andy Price (andy-price) wrote :

Reopening this bug as the segfault still occurs in PyPE 2.2.2 (on up-to-date ubuntu 6.06 i386).

Changed in pype:
status: Fix Released → Confirmed
Revision history for this message
Vassilis Pandis (pandisv) wrote :

This bug has apparently been fixed in Edgy, with Pype 2.5-1.

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Closing as it is fixed in edgy - possibly a candidate for backports.

Changed in pype:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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