maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Development (https://talk.maemo.org/forumdisplay.php?f=13)
-   -   rtcom_el_new (https://talk.maemo.org/showthread.php?t=41431)

morusaka 2010-01-19 22:22
rtcom_el_new
 
Hi,

I'm trying to make RTCom/eventlogger working in a Python module extension written in C.

When I run this piece of code:
Code:
RTComEl* rtcomel;
rtcomel = rtcom_el_new();
I get this errors:

Code:
process 3050: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5257.
This is normally a bug in some application using the D-Bus library.
python2.5[3050]: GLIB WARNING ** default - Could not add dbus filter: (null)
process 3050: arguments to dbus_connection_unref() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2657.
This is normally a bug in some application using the D-Bus library.
I can't understand what I'm doing wrong.

Thank you,

Luca.

morusaka 2010-01-19 22:23
Re: rtcom_el_new
 
Forgot to mention that I'm doing this under ScratchBox, compile and run under X86.

Luca.

danielwilms 2010-01-20 08:56
Re: rtcom_el_new
 
Quote:
Originally Posted by morusaka (Post 483022)
Forgot to mention that I'm doing this under ScratchBox, compile and run under X86.

Luca.
I'm not sure, but it looks like you haven't started the application framework with:

Code:
af-sb-init.sh start
More information on how to start the AF you find here. If this is not the issue let me know.

Daniel

morusaka 2010-01-20 21:36
Re: rtcom_el_new
 
Thank you Daniel for your reply, I'll check the link.

I can give you more details about how I performed my test:

1) I start scratchbox

Code:
# scratchbox
Welcome to Scratchbox, the cross-compilation toolkit!
Use 'sb-menu' to change your compilation target.
See /scratchbox/doc/ for documentation.
[sbox-FREMANTLE_X86: ~] >
2) I start xephyr (otherwise my program complains that D-Bus is not running)
Code:
(I do this from another bash)
# /usr/local/bin/start_xephyr.sh
3) I run the test

Ok, I noticed that the message I receive actually isn't an error: it seems to be only a warning.
My test runs, but it complains a lot:
Code:
process 4016: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5257.
This is normally a bug in some application using the D-Bus library.
python2.5[4016]: GLIB WARNING ** default - Could not add dbus filter: (null)
process 4016: arguments to dbus_connection_unref() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2657.
This is normally a bug in some application using the D-Bus library.
python2.5[4016]: GLIB MESSAGE default - Plugin registered: CALL.
python2.5[4016]: GLIB MESSAGE default - Plugin registered: CHAT.
python2.5[4016]: GLIB MESSAGE default - Plugin registered: SMS.
process 4016: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3099.
This is normally a bug in some application using the D-Bus library.
python2.5[4016]: GLIB WARNING ** default - Could not send signal!
process 4016: arguments to dbus_connection_flush() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3390.
This is normally a bug in some application using the D-Bus library.
process 4016: arguments to dbus_connection_unref() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2657.
This is normally a bug in some application using the D-Bus library.
python2.5[4016]: GLIB WARNING ** default - rtcom_el_plugin_get_value: here: gint, gboolean
python2.5[4016]: GLIB WARNING ** default - rtcom_el_plugin_get_value: here ends
The program runs, ok, but it is annoying to see all these warnings.

I've also tried your suggestion:

Code:
(i tried this *AFTER* starting xephyr AND scratchbox)
[sbox-FREMANTLE_X86: ~/MyDocs/maemo/rtcom-eventlogger] > af-sb-init.sh start
but my program's output remains the same.

Thank you,

Luca-


All times are GMT. The time now is 18:03.

vBulletin® Version 3.8.8