Ask Your Question

colorization isn't working

asked 2021-02-12 15:01:55 +0000

boulder_dash gravatar image

updated 2021-02-13 07:10:45 +0000

Guy Harris gravatar image

MacOS 11.2.1 On WS version 3.4.3 (v3.4.3-0-g6ae6cd335aa9) colorization of any packets isn't working. I've uninstalled, reinstalled, deselected all colorization rules, created new rules, modifications of preferences-->font-and-colors, gone to github to download other colorization rules (which don't get recognized). I'm going to delete all things WS, go in and manually cleanup any remnants, and attempt a reinstallation. For clarity, I've rebooted after each install/uninstall outlined above. Welcome any and all thoughts.

edit retag flag offensive close merge delete


Maybe try creating a new Wireshark profile? I'm not sure if profiles remain on macOS when Wireshark is uninstalled.

grahamb gravatar imagegrahamb ( 2021-02-12 15:08:43 +0000 )edit

So all packets have the default color?

I tried it on my 11.2.1 VM, with a default installation of 3.4.3, and it does color packets.

Are you running in dark mode?

Guy Harris gravatar imageGuy Harris ( 2021-02-13 07:26:03 +0000 )edit

I'm not running in dark mode (or wasn't at the time of the original woes). Upon RE-installation with v3.2.11, the new profile I created during my troubleshooting with v3.4.3 persisted with the new version, so there is a config file that is being retained after uninstallation - even so, color is back on (in their default color, or colour) with v3.2.11.

boulder_dash gravatar imageboulder_dash ( 2021-02-13 20:39:19 +0000 )edit

3 Answers

Sort by ยป oldest newest most voted

answered 2022-05-02 23:55:20 +0000

Try the following (on macOS) to reset your Wireshark configuration to the default colors (it'll also remove your other customizations as well): rm -r ~/.config/wireshark

edit flag offensive delete link more

answered 2021-02-12 22:19:51 +0000

boulder_dash gravatar image

CIRCLING BACK FOR CLOSURE: Complete UNinstall and reinstallation of Version 3.2.11 (v3.2.11-0-gbfbc7825bf9b) worked like a champ. All set now. Thanks for the responses that I received to attempt to help me resolve the issue!! Mercy buckets.

edit flag offensive delete link more


So the current stable version, 3.4.3, doesn't work for you?

grahamb gravatar imagegrahamb ( 2021-02-13 09:13:29 +0000 )edit

You triggered a great thought, grahamb...what if, now that I have colorization working with v3.2.11, I upgrade to v3.4.3 and see if the colorization works. I originally went from WS v3.0.x -->v3.4.3 when I experienced my colorzation woes. Perhaps that was too large a gap and I should have done a more incremental upgrade in my process?

boulder_dash gravatar imageboulder_dash ( 2021-02-13 20:45:16 +0000 )edit

YEP. v3.4.3 is now solid and colorful in upgrading from v3.2.11 --> v3.4.3-0-g6ae6cd335aa9. Seemingly stable and up to date with default colorization coming in strong.

boulder_dash gravatar imageboulder_dash ( 2021-02-13 21:32:20 +0000 )edit

answered 2021-02-12 15:30:20 +0000

hugo.vanderkooij gravatar image

There is a tricky thnig. As coloring rules are art of a profile. If you chnage them for Prfile A and are working in Profile B then those changes will not affect you.

edit flag offensive delete link more


Preference changes affect the current profile, the only way to make changes that don't show up in the current profile is by manually modifying the files belonging to other profiles.

grahamb gravatar imagegrahamb ( 2021-02-12 15:33:24 +0000 )edit

yeah, I made no [deliberate] changes to the default color scheme from within any profile, as I think they're great and don't see the need to modify them. I did create a new profile with defaults to be inherited, but still no joy at that time with v3.4.3.

boulder_dash gravatar imageboulder_dash ( 2021-02-13 20:42:28 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2021-02-12 15:01:55 +0000

Seen: 1,098 times

Last updated: Feb 13 '21