Re: Invalid byte sequence when accepting event

Michael J Rubinsky <[email protected]> Thu, 27 Jul 2017 12:29:38 +0000
Newsgroups gmane.comp.horde.kronolith
Message-ID <20170727122938.Horde.Cf3jvuCIBEPLNCyask-3UyT@h4.theupstairsroom.com>
Quoting [email protected]:

> Zitat von Jan Schneider <[email protected]>:
>
>> Zitat von [email protected]:
>>
>>> Hello,
>>>
>>> today we got the following error when trying to accept a invite  
>>> from one Horde user to another :
>>>
>>> Jul 26 16:31:47 webmail HORDE: [kronolith] SQL QUERY FAILED:  
>>> SQLSTATE[22021]: Character not in repertoire: 7 ERROR:  invalid  
>>> byte sequence fo                                                    
>>>                                              r encoding "UTF8":  
>>> 0xf6 0x72 0x67 0x20
>>>       INSERT INTO kronolith_events (event_id, event_uid, event_creator_id,
>>>         event_title, event_description, event_location, event_timezone,
>>>         event_url, event_private, event_status, event_attendees,
>>>         event_resources, event_modified, event_start, event_end,  
>>> event_allday,
>>>         event_alarm, event_alarm_methods, event_recurtype,  
>>> calendar_id) VALUES
>>>         ('m3S_DfjWK-KhdFuqJQHNyCH',
>>>          
>>> '040000008200E00074C5B7101A82E00800000000170A59505D5FCE41AA27C7A904474
>>>         D1B100000009378262B6DF6AC4ABEF0A516E6103476', 'xxxx',
>>>         'Führungsrunde', '', '', NULL, '', 0, 2,
>>>          
>>> 'a:3:{s:16:"[email protected]";a:3:{s:10:"attendance";i:1;s:8:"response
>>>         ";i:1;s:4:"name";s:16:"[email protected]";}s:21:"[email protected]"
>>>          
>>> ;a:3:{s:10:"attendance";i:1;s:8:"response";i:1;s:4:"name";s:16:"J▒rg
>>>         xxxx";}s:17:"[email protected]";a:3:{s:10:"attendance";i:1;s:8:
>>>         "response";i:1;s:4:"name";s:14:"xxxx xxxx";}}', 'a:0:{}',
>>>         1501079507, '2017-11-23 08:00:00', '2017-11-23 16:00:00',  
>>> 0, 15, 'N;',
>>>         0, 'xxxx') [pid 32203 on line 236 of  
>>> "/usr/share/php/Horde/Db/Adapter/Pdo/Base.php"]
>>>
>>>
>>> For sure it looks like the display name is not properly encoded,  
>>> but can soemone explain how to avoid this Problem. All the  
>>> Horde/Kronolith are at latest versions and the database used ist  
>>> PostgreSQL. Browser used from the failing Client is Chrome on  
>>> Windows OS.
>>>
>>> Thanks for any hints
>>>
>>> Andreas
>>
>> We would probably have to normalize any external data to UTF-8  
>> before storing to the backend.
>
> Hm, yes. Further investigation showed that the invite was created by  
> Windows 10 Mail App tied with ActiveSync to the horde installation.  
> It looks like the display name of the attendee is not properly  
> encoded. I can send the raw E-Mail invite to some developer if this  
> would help?


Can you please create a ticket on bugs.horde.org as well? I will look at this.

>
> Regards
>
> Andreas
>
>
> -- 
> kronolith mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
(unnamed) (application/pgp-keys, 9.1 KB) - not displayed
signature.asc (application/pgp-signature, 821 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4

iQIcBAABAgAGBQJZedyzAAoJEJGSgkbRsxbbA7sP/j0RlVmbUIV5HwucZ0zG9IHn
A0iNw75e0JlmWjcyjt78S7h83AiM0k3P0JbpPC6zi2j2akw//ij4CoT5tN28Nt1D
Nya1zePmiTOnLMUr2TTYGpqhtTySAmmNmFPecV64NO57S3xdTKRnfdpftbF2nUTr
Tw1f6bbW+BaIzjKQvocFyB1d/FhkLkXCftP0nI4bF+QwPX6c/w7q296FTjD9/Jef
OPOyX3QenDGShnauKm9fOIwtmvWWJco78ouLtcs761kq1meMrJVC4DcTkDIhwda+
tCR+b2GhbXrBswATnLzqtfW2fMF23f0JDmdkUkdxAvoDyAhIbgP7G6E3ccu4JAwt
ODmg5Zr2aZ2/4JxhZNeO2KXUOQbaMfqlBR2xyFJIOTG2dCXyeCCuRfjIIycLeUc/
CmO27pMBMXx8Ph1xh5WdfbPzxACNcplFhkZaQo/Ohas0AbdbKlhUlXJ4Qx/Ab7i4
5t07h3eDwdxFIK6w0d821JuTX+6WNdW9m62q77SBd+o/tThXn2hOjtIsa9JyZSsK
uh94aCEuD8DjMWnkBtgV56UOhefjbaiayBPzLI5l7Rcyq2Y/UcpekluVwy8hDJrW
X7Ml0wh2jA9GKMeNE3rzrLCz1hqG0OOH9LUC861dLxpxXmKUAryhCCNNbGy4vn3j
MArHi9gH8jKjcyILV0Bq
=P7+S
-----END PGP SIGNATURE-----