Xmpp broken with 79.0b2

Hello
I test 79.0b2 but xmpp does not work anymore ( on Centos8 )

I receive the messages but the zone is not visible
I changed the general theme dark/light/default and also the style and nothing displays it
Same for history messages

log :

console.error: Lightning: 
  [calStorageCalendar] Message: Error setting metadata for id calendar-properties!
Connection Ready: true
Last DB Error Number: 6
Last DB Error Message: database table is locked
Database File: /home/wvincent/.thunderbird/zzwxiyv2.default/calendar-data/cache.sqlite
Last DB Statement: [object StatementJSHelper]
Last Statement param [0]: undefined
Last Statement param [1]: undefined
Last Statement param [2]: undefined
Last Statement param [cal_id]: undefined
Last Statement param [item_id]: undefined
Last Statement param [value]: undefined
Last Statement param [length]: 3
Exception: [Exception... "Component returned failure code: 0x8052000e (NS_ERROR_FILE_IS_LOCKED) [mozIStorageStatement.executeStep]"  nsresult: "0x8052000e (NS_ERROR_FILE_IS_LOCKED)"  location: "JS frame :: resource:///modules/CalStorageCalendar.jsm :: setMetaData :: line 2484"  data: no]
1: [resource:///modules/CalStorageCalendar.jsm:2591] logError
2: [resource:///modules/CalStorageCalendar.jsm:2492] setMetaData
3: [resource:///modules/CalDavCalendar.jsm:213] saveCalendarProperties
4: [resource:///modules/caldav/CalDavRequestHandlers.jsm:513] endDocument
5: [resource:///modules/caldav/CalDavRequestHandlers.jsm:437] onStopRequest
6: [resource:///modules/caldav/CalDavRequest.jsm:545] get listener/get/<

JavaScript error: resource:///modules/CalStorageCalendar.jsm, line 241: NS_ERROR_FILE_IS_LOCKED: Component returned failure code: 0x8052000e (NS_ERROR_FILE_IS_LOCKED) [mozIStorageStatement.executeStep]
JavaScript error: resource:///modules/CalStorageCalendar.jsm, line 241: NS_ERROR_FILE_IS_LOCKED: Component returned failure code: 0x8052000e (NS_ERROR_FILE_IS_LOCKED) [mozIStorageStatement.executeStep]
JavaScript error: chrome://chat/content/conversation-browser.js, line 860: NotSupportedError: CustomElementRegistry.define: 'conversation-browser' has already been defined as a custom element

Thanks
Will

That’s Bug 1646611- Stop using raw HTML strings in chat (chat broken)

Yeah. Unfortunately they are still working on a fix.