Bug 657 – Signal emission inside QtMobility isn't working properly

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 657 - Signal emission inside QtMobility isn't working properly

Summary:

Signal emission inside QtMobility isn't working properly

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	HEAD
Platform:	All All

Importance:	P2 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-01-31 17:10 EET by Luciano Wolf
Modified:	2011-02-17 19:18 EET (History)
CC List:	9 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Luciano Wolf 2011-01-31 17:10:44 EET

I was trying to convert an example from C++ to Python and the signal emission
causes a segfault in Python. The example uses QtMobility.Location. During the
emission of new GPS coordinates it crashes. In that example it uses a
QGeoPositionInfo that takes a QGeoCoordinate in its constructor. Talking to
Hugo he noticed that the signal manager isn't reading the right data type:
QGeoCoordinate isn't detected properly (due to namespace issues).

Comment 1 Hugo Parente Lima 2011-01-31 17:26:42 EET

It doesn't crash anymore, now it throws a Python exception and doesn't emit the
signal.

Comment 2 Matti Airas 2011-02-01 06:54:59 EET

So, the issue is still there? I'm prioritizing this P2 because this would
appear to be a generic issue and it's blocking the PyMaemo team, anyway.

Comment 3 Hugo Parente Lima 2011-02-03 18:27:31 EET

*** Bug 664 has been marked as a duplicate of this bug. ***

Comment 4 renato filho 2011-02-07 17:35:55 EET

fixed on shiboken commit:
commit 61035b494dd0b5d13ea8cd7f4af7e62b36bb27b8
Author: Renato Araujo Oliveira Filho <renato.filho@openbossa.org>
Date:   Fri Feb 4 19:08:43 2011 -0300

Comment 5 renato filho 2011-02-08 13:30:51 EET

*** Bug 672 has been marked as a duplicate of this bug. ***

Comment 6 Hugo Parente Lima 2011-02-17 19:18:19 EET

Released in 1.0.0~rc1