Wireshark "failed to get the current screen resources" using Xming/ssh
-
@jsulm - No. I just used ready to use CMakeLists.txt supplied with the code. But is'nt Qt creator a Qt application? It work fine.
I think, that some error handling may be missing in Wireshark GUI code. Is it posible to check about what resources this message "failed to get..." talking? I saw similar with openGL application, but there is no openGL on the library list.
-
@borkowsk I think of 3 things here, as you mentioned you need to develop under Windows:
- What about trying with another X server in Windows? i.e. VcXsrv
- What about using CentOS development environment from a virtual machine?
- What about building Wireshark directly on Windows?
-
@borkowsk said in Wireshark "failed to get the current screen resources" using Xming/ssh:
But is'nt Qt creator a Qt application? It work fine.
Yes, but you did not build it by yourself, right?
-
@jsulm - Qt creator have the same message but it work almust perfectly:
$qtcreator
failed to get the current screen resources
QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20
WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported! This is an application bug! -
@Pablo-J.-Rogina - Off course these are other options.
However, Ultimately I need Wireshark also on Centos and on Windows, but my developing enviroment is mostly on Centos7, and hopefully also remotely.Maybe I have to check VcXsrv. Is it real difference? Do you have own expierience about that?
-
@Pablo-J.-Rogina - (y)
Yes, using VcXsrv it work!
But I would suggest better diagnostic messages when QtApplication starting, and any workaround for Xming which is still the most popular MS Windows Xserwer!It looks like Qt programmers use a solution which work on Xming (most of "standard" applications work properly), but it is practice existing somewhere outside the code of Qt libraries, which is not known for other Qt libraries users.
-
@Pablo-J.-Rogina - I'm not sure the workaround means this is "solved" :-)
Especially, if this required change of such basic application as Xserwer!For me solution should be at least a piece of code able to test and solve such situation in MyApp (derived from QtApplication) class constructor.
It is possible because other Qt applications work well on Xming.
