xpad critical start

Bug #591978 reported by Jason
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Xpad
Fix Released
Undecided
Siergiej Riaguzow

Bug Description

xpad has a critical start and has all grey boxes with no ability to input or manage any portion of any pad.

The error is:

(xpad:3953): GLib-GObject-WARNING **: IA__g_object_set_valist: construct property "type" for object `XpadPad' can't be set after construction

I have submitted a fix for this to FreeBSD, as that is that only OS I use and test on. This bug exists in the stable and trunk versions of xpad, and I have tested the patch on both and it works.

Here is a link to the bug I posted to FreeBSD: http://www.freebsd.org/cgi/query-pr.cgi?pr=147662

Tags: bsd freebsd
Revision history for this message
Jason (jhelfman-e-e) wrote :
Changed in xpad:
assignee: nobody → Sergei Riaguzov (riaguzov)
milestone: none → 4.1
Revision history for this message
OBATA Akio (obache) wrote :

I'm using attached patch for the NetBSD package collection.

g_object_set will abort if unsettable properties is found, then rest of property setters will be ignored.
So use GTK API to set window properties to avoid other properties will break again in the future.

Revision history for this message
Siergiej Riaguzow (riaguzov) wrote :

Applied OBATA Akio patch in revision 631

Changed in xpad:
status: New → Fix Committed
Changed in xpad:
status: Fix Committed → Fix Released
Revision history for this message
Jason (jhelfman-e-e) wrote :

Is this going to be brought back to stable trunk, and possibly in the next stable release?

Revision history for this message
Siergiej Riaguzow (riaguzov) wrote :

This is in v4.1. I'm currently working on v4.2 which has a bunch of bugs targeted to it, so it will take some time (not a year like with v4.1, no, really). About the next stable release: I didn't plan to make a stable release before v4.2.

Revision history for this message
Siergiej Riaguzow (riaguzov) wrote :

If you really wan't v4.1 to became next stable please say, at least I believe I will have to target Bugs #891308, #859824 and #834931 for it.

Revision history for this message
Siergiej Riaguzow (riaguzov) wrote :
Revision history for this message
Jason (jhelfman-e-e) wrote :

The path you choose for releasing is fine. I was just wondering if the changes you are making are going to make it into the next stable release, when you do infact have a stable release.

I am not maintaining the xpad (stable) and xpad-current (trunk) ports for FreeBSD, so I will keep an eye out for updates.

Thanks!

Revision history for this message
Jason (jhelfman-e-e) wrote :

Correction:

I am now maintaining the xpad (stable) and xpad-current (trunk) ports for FreeBSD, so I will keep an eye out for updates.

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.