[OGo-Bugs][Bug 1960] WebUI crash when using search in jobs on amd64

[bugs@opengroupware.org]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1960


sebastia@l00-bugdead-prods.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From alex@ghisoli.ch  2008-03-11 23:20 -------
More details after a debugging session. Thanks a lot to whooha on IRC.

My OGo installation is quite old, starting with 1.1.3 then upgraded at 1.1.7.

This bug was present only in 1.1.7, all other versions didn't throw that exception.

Related to the backtrace log attached to this bug, here is the details :

(gdb) frame 3
#3  0x00002ada404d1ebd in -[NSString rangeOfString:options:] (self=0x1742198,
_cmd=0x2ada45f23730,
    string=0x16ac738, mask=1) at NSString.m:466
466         return [self rangeOfString:string options:mask range:range];
(gdb) print string
$1 = (class NSString *) 0x16ac738

(gdb) print *string
$3 = {{isa = 0x2ada406a9ca0}}

(gdb) po self
pbx t�l�phone raccordement voIP


We was suspecting something with special chars (should be téléphone).

The database is UTF-8 encoded, and I've managed to find this record in job
table, keywords column.

Replacing the 'é' with 'e' and OGo didnt crash anymore !

I've multiple other keywords with special chars, no problem so far.

------- Additional Comments From sebastia@l00-bugdead-prods.de  2008-03-12 13:54 -------
its me, whooha,

when you upgraded between 1.1.3 and now have 1.1.7, On IRC I thought you only
upgraded from 1.1.6 to 1.1.7, but that obviously was only your latest upgrade ;)
I think the database encoding changed from latin-1 to utf-8. have you dumped
your database, and recoded it from latin-1 to utf-8 ? If not, then I assume this
seems to be your problem.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.