Opened 9 years ago

Last modified 5 years ago

#12637 closed defect

Pdgin crash when accepting a sametime chatroom invitation — at Initial Version

Reported by: angejudor Owned by: siege
Milestone: 2.10.7 Component: Sametime
Version: 2.7.3 Keywords: sametime chatroom crash windows
Cc:

Description

Hello,

I have a crash of the pidgin application when I accept a chatroom invitation (sametime protocol). It's occuring since our company upgraded the sametime server to the 8.5.1 level.

I'm using 2.7.3 pidgin release on windows.

pidgin.RPT attached to this message.

Thanks for the help,

Ange.

PS : on the debug info file I have the following lines :

(14:15:05) meanwhile: place PLC$51027737236915A8 state: pending
(14:15:05) meanwhile: channel accepted with encrypt policy 0x2000
(14:15:05) meanwhile: channel 0x00000006 selected cipher RC2/128 Cipher
(14:15:05) meanwhile: channel 0x00000006 state: open
(14:15:05) meanwhile: place PLC$51027737236915A8 state: joining
(14:15:05) meanwhile: place PLC$51027737236915A8 state: joined
(14:15:05) meanwhile: mwString_get: assertion `check_buffer(b, (gsize) len)' failed
(14:15:05) meanwhile: place PLC$51027737236915A8 state: open
(14:15:05) meanwhile: collected member 2: CN=Laurent XX/OU=YYY/O=ZZZ, (null)
(14:15:05) meanwhile: collected member 1028415861: (null), (null)
(14:15:05) sametime: place PLC$51027737236915A8 opened, 2 initial members
(14:15:05) g_log: purple_normalize: assertion `str != NULL' failed
(14:15:05) g_log: purple_find_buddy: assertion `(name != NULL) && (*name != '\0')' failed
(14:15:05) g_log: purple_conv_chat_is_user_ignored: assertion `user != NULL' failed
(14:15:05) g_log: purple_conv_chat_cb_new: assertion `name != NULL' failed
(14:15:05) g_log: purple_find_buddy: assertion `(name != NULL) && (*name != '\0')' failed

Change History (1)

Changed 9 years ago by angejudor

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!