debian (bullseye) client crashes on connection to Xming

[prs247au]

Details of the issue

Running sqlitebrowser on debian bullseye (Release 11) crashes after a very brief appearance (flicker?) of a window. The X11 server is Xming (v 6.9.0.31) on Windows 10. Output is;

$ sqlitebrowser

qt.qpa.xcb: X server does not support XInput 2
failed to get the current screen resources
QXcbConnection: XCB error: 1 (BadRequest), sequence: 165, resource id: 90, major code: 130 (Unknown), minor code: 47
QXcbConnection: XCB error: 170 (Unknown), sequence: 180, resource id: 90, major code: 146 (Unknown), minor code: 20
The X11 connection broke (error 1). Did the X11 server die?

The X11 server didn't die (at least not permanently), it still accepts connections from other clients.

Version info

$ sqlitebrowser --version
qt.qpa.xcb: X server does not support XInput 2
failed to get the current screen resources
DB Browser for SQLite Version 3.12.1

Built for arm-little_endian-ilp32-eabi-hardfloat, running on arm
Qt Version 5.15.1
SQLite Version 3.33.0.

Other apps work ok with Xming in this debian release. For example `glxgears' demo or running ipython and then doing some matplotlib plots render the plot windows with no problem.

Previous version (working)

This was working on the previous debian (buster) release, output looked like;

$ sqlitebrowser
failed to get the current screen resources
qt.qpa.xcb: QXcbConnection: XCB error: 170 (Unknown), sequence: 174, resource id: 90, major code: 146 (Unknown), minor code: 20

and then the sqlitebrowser window opened.

$ sqlitebrowser --version
failed to get the current screen resources
This is DB Browser for SQLite version 3.10.1.

Useful extra information

Windows: 10 (Xming server)

Linux: bullseye (sqlitebrowser)

 $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

What is your DB4S version?

• 3.12.1

[chrisjlocke]

The error is coming from Qt (doesn't it always?) 5.15. This seems newer than my version for Windows, but we use a plethora of different versions to cater for different OSs and weather patterns, so that isn't too odd. Working in the older version would also indicate a different Qt version though (3.10.1 is quite old). I don't have a list of Qt versions against DB4S versions, or whether you can try an alternative version on Raspbian... and it's only a guess as to what's causing the error.