Fun to see that Kexi supports web browser in a form just like what Microsoft Office Access can do while Libre Base doesn't. But Kexi is having trouble with loading image using the browser widget. When an image is loaded in the web browser widget and then I switch to the next record, the GUI sticks and crashes in a few seconds. There is no trouble if I am solely switching from real web URLs (not including image URL), but when an image URL is blended into the website URLs and I pass by this image URL, Kexi crashes again.

The issue persists in version 3.2.0 under both Windows 10 and Manjaro Linux operating systems.

Here's the message I can get from the console. Looks like web image is not supported in the browser. But I definitely need to load some images from web URL instead of from local locations. Why does the first image succeed while others don't? What can I do? Can an image widget achieve this (I would like to load some animating gif images)?

Code: Select all

gui updated 31 min. ago, next auto-update in 29 min.
Original format version:  "3.2"
kf.i18n.kuit: "Markup error in message {<__kuit_internal_top__>Click to show actions for <interface>\u0000</interface> image ...}: Unexpected ''.. Last tag parsed: interface. Complete message follows:\n<__kuit_internal_top__>Click to show actions for <interface>\u0000</interface> image box</__kuit_internal_top__>"
kf.i18n.kuit: "Markup error in message {<__kuit_internal_top__>Click to show actions for <interface>\u0000</interface> image ...}: Unexpected ''.. Last tag parsed: interface. Complete message follows:\n<__kuit_internal_top__>Click to show actions for <interface>\u0000</interface> image box</__kuit_internal_top__>"
QWidget::setMinimumSize: (/WebBrowserWidget) Negative sizes (0,-1) are not possible
"webBrowser" :  480    |  "textBox2" :  60
"textBox" :  150    |  "textBox2" :  60
"webBrowser" :  480    |  "textBox" :  150
"textBox2" :  60    |  "textBox" :  150
"image" :  110    |  "textBox" :  150
"webBrowser" :  480    |  "textBox" :  150
"image" :  110    |  "textBox2" :  60
# 0 :  "id"  ( "textBox2" )
tab order:  "textBox2" -> "image"
also adding ' KexiImageContextMenu   "" ' child to filtered widgets
also adding ' KexiDropDownButton   "" ' child to filtered widgets
# 1 :  "url"  ( "image" )
tab order:  "image" -> "textBox"
# 2 :  "url"  ( "textBox" )
tab order:  "textBox" -> "webBrowser"
also adding ' QWebView   "" ' child to filtered widgets
also adding ' QPushButton   "" ' child to filtered widgets
also adding ' QPushButton   "" ' child to filtered widgets
also adding ' QPushButton   "" ' child to filtered widgets
also adding ' QPushButton   "" ' child to filtered widgets
also adding ' QProgressBar   "" ' child to filtered widgets
# 3 :  "url"  ( "webBrowser" )
No data assigned!
No data assigned!
No data assigned!
No data assigned!
"QUERY PARAMETERS (0):"
QBuffer::seek: Invalid pos: -2736896
Jasper library can't decode Jpeg2000 image data
DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

QTgaHandler::canRead(): Image type not supported
QBuffer::seek: Invalid pos: -2736896
Jasper library can't decode Jpeg2000 image data
DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

QTgaHandler::canRead(): Image type not supported
QBuffer::seek: Invalid pos: -2736896
Jasper library can't decode Jpeg2000 image data
DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

QTgaHandler::canRead(): Image type not supported
QBuffer::seek: Invalid pos: -2736896
Jasper library can't decode Jpeg2000 image data
DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

DSvgRenderer::load: XML parse error: Error domain 1 code 4 on line 1 column 1 of data: Start tag expected, '<' not found

QTgaHandler::canRead(): Image type not supported
Segmentation fault (core dumped)


Hi Baytars
Thanks for the extensive report. From the error output we can see that the browser engine tries to decode several image types such as Jpeg2000, TGA, SVG. No plugins wer found. Because KEXI uses the web browser form widget (QtWebKit) at high level (as a "black box") I think it's not KEXI's level. Deeper investigation would be needed. Question is whether that would pay off because the deprecated QtWebKit for shall be replaced in KEXI anyway by Qt WebEngine based on more modern Chromium (that unlike WebKit receives all modern feature and security updates). When it happens - as long as KEXI is Qt 5 based it can happen, when KEXI depends on Qt 6, it must happen. Sorry for being unclear on deadlines though.

Regarding the image widget alone, for now it supports embedded image data (coming from the database) only. But you're right, it shall support local and remote images (URLs in general) if the user agrees for possible security and performance consequences. Similar idea applies to KEXI image report element.

Best regards!

PS: The image widget is in no way related to the Web widget's image handling.

Thanks, Jarosław. Good to hear that. At least I can expect it to happen.

jstaniek wrote:Hi Baytars
Thanks for the extensive report. From the error output we can see that the browser engine tries to decode several image types such as Jpeg2000, TGA, SVG. No plugins wer found. Because KEXI uses the web browser form widget (QtWebKit) at high level (as a "black box") I think it's not KEXI's level. Deeper investigation would be needed. Question is whether that would pay off because the deprecated QtWebKit for shall be replaced in KEXI anyway by Qt WebEngine based on more modern Chromium (that unlike WebKit receives all modern feature and security updates). When it happens - as long as KEXI is Qt 5 based it can happen, when KEXI depends on Qt 6, it must happen. Sorry for being unclear on deadlines though.

Regarding the image widget alone, for now it supports embedded image data (coming from the database) only. But you're right, it shall support local and remote images (URLs in general) if the user agrees for possible security and performance consequences. Similar idea applies to KEXI image report element.

Best regards!

PS: The image widget is in no way related to the Web widget's image handling.