This was a culmination of that info gathering. HTH - There was tons of info out there using Google. The VNC session should be successful and you should be able to launch wireshark from the LXDE desktop. Note we are using port 5900 as displayed when you ran the x11vnc command on the remote computer. On the computer you want to VNC from, open the VNC client. sudo x11vnc -xkb -noxrecord -noxfixes -noxdamage -display :0 -auth /var/run/lightdm/root/:0 -usepw -scale 1920x1080 -forever Use the directory ~/.vnc to store the password file in. You will get output like the following: root 546 6.4 3.1 614984 122828 ? Sl 06:14 1:52 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitchįirst create a VNC password. As you can see, this is a much shorter command, and it performs the same recursive search as the longer command, specifically: The -r option says do a recursive search. Modeline '1920x1080_60.00' 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync Solution 2: grep-r.However, I was just reminded that a much easier way to perform the same recursive search is with the -r flag of the grep command: grep-rl alvin. sudo apt install xserver-xorg-video-dummyĬreate nf file in /etc/X11/ and /usr/share/X11/ with the following contents for 1920x1080 resolution: Section 'Monitor' Dummy monitor: xserver-xorg-video-dummy.

Desktop: LXDE (lightweight X11 Desktop Environment).

In this case, you can set the setuid bit for dumpcap so that it always runs as root.Ok - after TONS of troubleshooting, I managed to successfully launch a new wireshark GUI.įor the benefit of others experiencing the same issue, here's my steps.

Finally, if the problem is still not resolved, it may be that dumpcap was not correctly configured, or there is something else preventing it from operating correctly. Then log out and log back in (or reboot), and Wireshark should work correctly without needing additional privileges. In summary, after installing Wireshark, execute the following commands: sudo dpkg-reconfigure wireshark-common Since you are running Ubuntu, this can be resolved by following the instructions given in this answer on the Wireshark Q&A site. This sometimes results from an incomplete or partially successful installation of Wireshark. with sudo), it should generally be avoided (see here, specifically here).

While you can avoid this issue by running Wireshark with elevated privileges (e.g. This is usually caused by incorrectly setting up permissions related to running Wireshark correctly.

Wireshark command line not found