First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

Why new wireshark GUI compiled from git does not connect to Xserver?

I have clone the git repository of wireshark on the Centos7 remote workstation and compile current version, but I'm not able to run wireshark application because:

$ ./wireshark

failed to get the current screen resources

The X11 connection broke: I/O error (code 1) XIO: fatal IO error 2 (No such file or directory) on X server "localhost:16.0" after 363 requests (363 known processed) with 0 events remaining.

I use Xming via PUTTY for connection from MS Windows to Centos7 workstation. Other X application, including Qtcreator work fine on this configuration.

Repository: https://code.wireshark.org/review/wir...

wborkowsk's avatar
1
wborkowsk
asked 2019-04-18 09:15:36 +0000, updated 2019-05-15 15:52:58 +0000
edit flag offensive 0 remove flag close merge delete

Comments

People had similar problems , but only solution I found in Internet was to install wireshark-gtk :-)

wborkowsk's avatar wborkowsk (2019-04-18 09:23:15 +0000) edit

This may be similar to this, also unsolved issue: https://bugs.wireshark.org/bugzilla/s...

wborkowsk's avatar wborkowsk (2019-04-18 09:53:37 +0000) edit

At work we had similar problem some one suggested https://sourceforge.net/projects/vcxsrv/

Anders's avatar Anders (2019-04-18 12:44:53 +0000) edit

Thank you Anders. I have to ask administrator to install anything on my Windows, so it take some time to test, but I will leave info after checking this.

wborkowsk's avatar wborkowsk (2019-04-18 14:00:05 +0000) edit

Can't you use tshark on the remote system to make the capture or capture over ssh, rather than trying to run the GUI over ssh?

grahamb's avatar grahamb (2019-04-18 15:31:46 +0000) edit
add a comment see more comments

1 Answer

0

So you're logged into a remote machine running Centos 7, from a machine running an X server, and, on the command line on the remote machine, you run ./wireshark?

If so, then you need to make sure that the DISPLAY environment variable is set to refer to the machine with the X server; the message

I/O error (code 1) XIO: fatal IO error 2 (No such file or directory) on X server "localhost:16.0" after 363 requests (363 known processed) with 0 events remaining.

means that it's trying to connect to "localhost" - i.e., it's trying to connect to an X server running on the remote machine.

But still I suggest better diagnostic when GUI starting

Please send your suggestion to the developers of the X11 client library - we don't print that message, the X11 client library does. Wireshark calls Qt routines to display the GUI, and versions of Qt that use X11 as the window system call the X11 client library to do display operations.

Guy Harris's avatar
19.9k
Guy Harris
answered 2019-05-14 06:21:59 +0000
edit flag offensive 0 remove flag delete link

Comments

This is ssh connection made by PUTTY, so DISPLAY is set automatically, as "localhost:n.m". All other applications work properly with that.

wborkowsk's avatar wborkowsk (2019-05-15 15:46:52 +0000) edit

"failed to get the current screen resources" is a warning not from Xlib but from Qt lib, and it appears also for QtCreator and some other Qt applications. But those applications work with Xming, when Wireshark not.

wborkowsk's avatar wborkowsk (2019-05-15 15:56:49 +0000) edit

All applications work on different Xserwer for Windows: VcXsrv But Xming is still much more popular.

wborkowsk's avatar wborkowsk (2019-05-15 16:00:17 +0000) edit

I have made the thread on Qt forum, (https://forum.qt.io/topic/102617/wire...) but this issue is "in betwen" of Qt library calls - QtApplication construction (it print this "failed to get the current screen resources" messages) and main_window->show() which stop Wireshark with message from Xlib.

wborkowsk's avatar wborkowsk (2019-05-15 16:21:13 +0000) edit
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer