Bug 6413

Summary:	Window position error on applying stored "geometry"
Product:	Mageia	Reporter:	Matteo Pasotti <matteo.pasotti>
Component:	RPM Packages	Assignee:	Matteo Pasotti <matteo.pasotti>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	richard.j.walker
Version:	2
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	gambas3-3.1.1-1.mga2.src.rpm	CVE:
Status comment:
Bug Depends on:	6443
Bug Blocks:

Description Matteo Pasotti 2012-06-11 10:18:07 CEST

Description of problem:
gb.gtk has a wrong implementation of the algorithm to compute screen size (as the author said) causing crashes while using two screens.

Version-Release number of selected component (if applicable):
gb.gtk component belonging to gambas3-3.1.1

How reproducible:
A way to reproduce this bug is available at http://sourceforge.net/mailarchive/message.php?msg_id=29355415

Moreover gambas test project from Richard Walker is available at http://sourceforge.net/mailarchive/attachment.php?list_name=gambas-user&message_id=CAJWAV%2BHEzGy%2BpypViiZoMC5u-wNhKR%3DYShpkUbkXrdQD-17C8w%40mail.gmail.com&counter=1

Comment 1 Matteo Pasotti 2012-06-11 10:27:18 CEST

work in progress

Status: NEW => ASSIGNED

Comment 2 Matteo Pasotti 2012-06-13 13:31:03 CEST

This bug should be fixed in gambas3-3.1.1-1.1.mga2

http://svnweb.mageia.org/packages?view=revision&revision=260284

The new package is now in core/updates_testing waiting for validation.

Status: ASSIGNED => NEW

Manuel Hiebel 2012-06-13 13:55:52 CEST

Depends on: (none) => 6443

Comment 3 Richard Walker 2012-06-16 20:43:11 CEST

I have just installed gambas3-3.1.1-1.1.mga2 and I can confirm that Gambas programs no longer crash when saving the screen coordinate settings from a location on the second screen of a two-monitor desktop.

Is there a specific suite of validation tests to be run against a Mageia update? I would be happy to contribute some test time if that is what is required to get this update validated.

Richard

CC: (none) => richard.j.walker

Comment 4 Manuel Hiebel 2012-06-16 22:27:10 CEST

richard, this bug is not assigned to the QA but only the bug 6443, so they will not see your request
anyway thanks for the testing

Comment 5 Matteo Pasotti 2012-06-25 12:43:48 CEST

Marking this bug as resolved fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED