 | 1 | initial version |
It is probably a combination of settings in your "configuration profile". Are you working under a custom profile or did you stick to the "Default" profile?
Quickest test (with temporarily losing all your changed settings) is to close all Wireshark instances and then rename the folder <HOMEDIR>/.config/wireshark to <HOMEDIR>/.config/wireshark.BAK (in a terminal window). Then open WIreshark and see if the problem is still there? If not, it was something in your settings (and specifically in the "Configuration Profile" that was active).
Can you first check this? Then we'll take it from there :-)
