gnokii 0.6.28.1 does't compile

[Dev Mohanty]

Binary package hint: gnokii

The default gnokii v0.6.26 from the Jaunty rep seems to work fine with AT driver. Though needed to upgrade to the lastest to support S40 3rd mobile, but the source doesn't seem to compile completely. Only gnokii compile but not xgnokii or the driver files.

Connecting to mobile through series40 or 6510 and bluetooth addr port doesn't register, but limited features are available through AT and rfcomm0.

Mobile: Nokia 5200

Besides the wiki page on 'supported mobile' says series40 for non-symbian phones. But aren't series40 also symbian phones?

[Dev Mohanty (devm-nepalwireless)]

Partially Resolved:

I was able to reconfigure makefie and compile again after installing a couple of missing dev files such as libglib2.0 and gmodule which is a shared library object from the same packageas needed by smsd.

Gnokii now detects my mobile with the following configuration:

port = aa:bb:cc:dd:ee (bluetooth address)
connection = bluetooth
model = series40

Though gnokii-smsd works without a glitch for both sending and receiving, I do get an error with gnokii --sendsms from the terminal but other generic commands seem to work without the error.

"*** glibc detected *** gnokii: double free or corruption" (!prev)

And also once smsd reads and updates mysql database with the texts in the inbox, am unable to open my inbox on the mobile. Says system error and requires me to switch it on again to get to the inbox.

Would attach log in a bit.

[Pawel Kot (gnokii)]

First, it's better to report upstream problems directly upstream (either gnokii-users mailing list or http://savannah.nongnu.org/projects/gnokii).

As for your concerns: as you already noticed you need devel libraries (-dev packages) to compile from the sources. Compile-time requirements are usually higher than run-time.

"Besides the wiki page on 'supported mobile' says series40 for non-symbian phones. But aren't series40 also symbian phones?" Well, commonly as Symbian are described just series60. I think series40 have completely different kernel and is referred as NokiaOS.

As for double free/corruption. We would need at least debug log and command given to solve the issue.

As for smsd issue. I haven't seen this before. Can you do more testing? Does it help when you close smsd? And when you do --getsms ME 1 end? And when you delete a message (--deletesms)? Do you need to restart the phone (ie. with PIN entering and stuff)?

[Dev Mohanty (devm-nepalwireless)]

>First, it's better to report upstream problems directly upstream (either gnokii-users mailing list or
> http://savannah.nongnu.org/projects/gnokii).

Will do.

The glibc double free corruption error log is attached.

Its basically called by a perl script which logs in to my gmail account periodically and parses all unread mails (one at a time) and sends it over to my other mobile as a text. and the gnokii part of the command is:

open(GNOKII, "| gnokii --sendsms $sms_to") || die "Error starting gnokii failed: $!\n";
#Start gnokii and wait for the SMS body
    print GNOKII $sms_body;
# Print the SMS body in 160 Char chunks
    close(GNOKII);

This had been working without an issie on 0.6.26

outut for --getsms ME 1 end:
GetSMS ME 1 failed! (Invalid type of memory.)

I guess for my mobile N5200 only IN OU AR and DR work including parsing all of the text correctly, which smsd fails to do, wrt to time, sent number and smsc ..

Yup everytime smsd has deleted a message. am having to restart the phone to get to the inbox.

Find my conf settings:

[global]

# port = /dev/rfcomm0
# model = AT
# connection = serial
port = 00:1D:3B:32:30:AB
model = series40
connection = bluetooth
initlength = default
use_locking = no
serial_baudrate = 38400
rfcomm_channel = 14
smsc_timeout = 10
#sm_retry = 1
#disconnect_script =

[xgnokii]
allow_breakage = 0

[gnokiid]
bindir = /usr/sbin/

[connect_script]
TELEPHONE = 12345678
[disconnect_script]

[logging]

# where to log the debug output (on: stderr, off: /dev/null)
debug = on

# where to log the rlp debug output (on: stderr, off: /dev/null)
rlpdebug = off

# where to log X debug output (on: stderr, off: /dev/null)
xdebug = off

I haven't used a PIN though.. is it essential? My sim's never asked me for one that is.

[Pawel Kot (gnokii)]

I need in fact gnokii debug log. That is probably the part that was printed before the output you provided. It will give me the clue where something goes wrong. This glibc dump is black magic for me.
For SMSD problem -- the same story.

[Ilya Barygin (randomaction)]

As you seem to have problems with upstream sources and not Ubuntu package, I'm reassigning this bug to the upstream project.