[Bug]: Failed to load petrel 3 ccr XML dive log

[alon-dotan-fhenix]

Description

Im trying to load a dive log from my petrel 3 CCR (kiss sidewinder) computer, the application stuck and I got the following messages on the console:

QSocketNotifier: Can only be used with threads started with QThread
QObject::connect(QQuickWindow, QDeclarativeGeoMap_QML_6): invalid nullptr parameter
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
ERROR: Dive: 6, dive computer: Petrel 3: CCR dive, but no diluent cylinder found. Please add or select the correct cylinder use.
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : Blank needed here
㸿㰊楤敶砠汭獮砺摳∽瑨灴⼺眯睷眮⸳牯⽧〲㄰堯䱍捓敨慭
^
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : parsing XML declaration: '?>' expected
㸿㰊楤敶砠汭獮砺摳∽瑨灴⼺眯睷眮⸳牯⽧〲㄰堯䱍捓敨慭
^
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : Start tag expected, '<' not found
潌剧捥牯㹤 †㰠搯癩䱥杯敒潣摲㹳 㰠搯癩䱥杯ਾ⼼楤敶
                                                                              ^
INFO: Unable to parse date '--'
Polygon too complex for filling.
...

See attached XML file
Petrel 3[BAA0611A]#6 2025-9-15 10-19-51.xml.txt

Subsurface Version

6.0.55.11

Platform(s)

Linux

Platform Version

Fedora 43

Divecomputer Model

Petrel 3

Steps to Reproduce

1. Open subsurface
2. go to Import -> Import log fIles -> select the exported xml file

Logs

QSocketNotifier: Can only be used with threads started with QThread
QObject::connect(QQuickWindow, QDeclarativeGeoMap_QML_6): invalid nullptr parameter
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
Wayland does not support QWindow::requestActivate()
ERROR: Dive: 6, dive computer: Petrel 3: CCR dive, but no diluent cylinder found. Please add or select the correct cylinder use.
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : Blank needed here
㸿㰊楤敶砠汭獮砺摳∽瑨灴⼺眯睷眮⸳牯⽧〲㄰堯䱍捓敨慭
^
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : parsing XML declaration: '?>' expected
㸿㰊楤敶砠汭獮砺摳∽瑨灴⼺眯睷眮⸳牯⽧〲㄰堯䱍捓敨慭
^
/home/alond/Downloads/Petrel 3[BAA0611A]#6 2025-9-15 10-19-51 (2).xml:1: parser error : Start tag expected, '<' not found
潌剧捥牯㹤 †㰠搯癩䱥杯敒潣摲㹳 㰠搯癩䱥杯ਾ⼼楤敶
                                                                              ^
INFO: Unable to parse date '--'
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.
Polygon too complex for filling.

Mentions

No response

[mikeller]

Looks like Shearwater broke their exporter and are exporting invalid XML - they claim UTF16 encoding when the file is effectively UTF8 encoded. And it looks like this results in the XML parser used in the Fedora build throwing an error (it seems to work fine on other OS).

~/tmp/Petrel.3.BAA0611A.6.2025-9-15.10-19-51.xml:1: parser error : Document labelled UTF-16 but has UTF-8 content
<?xml version="1.0" encoding="utf-16"?>
                                     ^

<?xml version="1.0" encoding="utf-16"?>

@alon-dotan-fhenix: If you change the utf-16 in the first line of the XML file to utf-8 the import should work on Fedora. But in order to get this fixed you will need to open a support case with Shearwater Research.

Unfortunately it also looks like Shearwater also changed how they are encoding dates, time and possibly other values in their files - all of this while keeping the 'version' field at '3':

<dive xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3">

This results in incorrect dive date, and an unrealistically long dive. But instead of adding a hack trying to detect these variants it's probably best to ask Shearwater to fix this by either reverting to the established 'version 3' format, or increment the version to make it easy to identify the new format.

[alon-dotan-fhenix]

@mikeller Thanks,
Ill try to forward the issue to Shearwater support