Bug 11693 – Scanning a MeCard results in Signal 11

Bug 11693 - Scanning a MeCard results in Signal 11


Summary:	Scanning a MeCard results in Signal 11

Status:	RESOLVED FIXED

Product:	mbarcode
Component:	Plugins-General
Version:	unspecified
Platform:	N900 Maemo

Importance:	Unspecified major (vote)
Target Milestone:	---
Assigned To:	Simon Pickering
QA Contact:	general

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-12-15 13:39 UTC by Philipp Tölke
Modified:	2010-12-20 11:54 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
QR-Code that produces the crash (14.85 KB, image/jpeg) 2010-12-15 13:39 UTC, Philipp Tölke	Details
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 Philipp Tölke (reporter) 2010-12-15 13:39:41 UTC

Created an attachment (id=3248) [details]
QR-Code that produces the crash

SOFTWARE VERSION: 
0.2.6-1

EXACT STEPS LEADING TO PROBLEM: 
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Scan QR-Code containing the string
"MECARD:N:Hans
Efghijk;TEL:+491771234567;EMAIL:hans.efghijk@lmno.de;URL:lmno.de;ORG:lmnO
GmbH;ADR:Theresienstr. 50 N5.1, 80333 Mnchen;;" as generated by
<http://www.quickmark.com.tw/en/diy/?qrText>
2. Select the MeCard-Plugin
3. Receive a signal 11

EXPECTED OUTCOME: 

The information on the Card is added to the contacts

ACTUAL OUTCOME: 

Crash.

REPRODUCIBILITY: 
always

Comment 1 Simon Pickering maemo.org

2010-12-15 13:56:43 UTC

I'll have a look at this today

Comment 2 Simon Pickering maemo.org

2010-12-15 16:46:06 UTC

I've just committed a fix and pushed a new version of the qrcode plugin to
Extras-devel (0.0.6-2).

This was caused by the barcode generator not following the MECARD spec
(unfortunately that's life) and the parser expecting there to be 6 address
fields, even if some were empty (my fault). I've made the parsing more robust,
but you will probably find that the fields are not placed in the correct
locations.

This could be improved somewhat by looking at how different countries arrange
their addresses by default, and guessing which field to insert the data in.

Patches welcome, otherwise we'll get round to improving this aspect in the
fullness of time.

Comment 3 Philipp Tölke (reporter) 2010-12-20 11:54:31 UTC

Works now, thanks!