Bug 717678 - gnokii-smsd-mysql: incoming SMS with non-ascii chars are wrong in MySQL database
Summary: gnokii-smsd-mysql: incoming SMS with non-ascii chars are wrong in MySQL database
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnokii
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Linus Walleij
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-29 14:46 UTC by Patrick Monnerat
Modified: 2012-08-16 16:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 16:33:23 UTC
Type: ---


Attachments (Terms of Use)
Patch as described in the comment (1.14 KB, patch)
2011-06-29 14:46 UTC, Patrick Monnerat
no flags Details | Diff

Description Patrick Monnerat 2011-06-29 14:46:11 UTC
Created attachment 510479 [details]
Patch as described in the comment

Description of problem:
When an incoming SMS contains non-ascii characters, the stored version in the MySQL Inbox table shows garbage instead of these characters.

Version-Release number of selected component (if applicable):
0.6.28-1

How reproducible:
Always

Steps to Reproduce:
1. Setup an SMS gateway with inbound SMS written to a mysql database.
2. Make sure /etc/my.cnf contains "default-character-set=utf8" in the [client] group.
3. From a mobile phone (i.e.), send an SMS with accentuated characters to your gateway
4. Examine the corresponding message in the Inbox table.
  
Actual results:
UTF8 2-byte characters are understood as if they were "latin1": thus they are stored on 4-bytes in the database.

Expected results:
Proper UTF8-only handling, and correct UTF8 encoding in the DB.

Additional info:
This is a "mysql client default character set" problem: although my /etc/my.cnf contains "default-character-set=utf8" in the [client] group, this file is not read by default.
The attached patch fixes this problem by forcing the read of the [client] option group in the default mysql option file (/etc/my.cnf). In addition, it also fixes an FTBFS problem (yet undetected by the Fedora build system).

Comment 1 Patrick Monnerat 2011-08-04 12:00:54 UTC
Ping !
Since this report proposes a patch, a fix or at least an acknowledgement would have been welcome...

Comment 2 Robert Scheck 2012-01-15 13:10:58 UTC
I'm not the package maintainer, but I think, this issue has been solved also
upstream with gnokii-0.6.31 when reading the code.

Comment 3 Fedora End Of Life 2012-08-16 16:33:26 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.