colorization isn't working

0

boulder_dash
1 ●1 ●2 ●1

Guy Harris
19905 ●3 ●667 ●207

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.

Comments

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

grahamb ( Feb 12 '1 )

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 ( Feb 13 '1 )

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 ( Feb 13 '1 )

add a comment

0

answered May 2 '2

Brian Cunnie
1

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

link

add a comment

0

answered Feb 12 '1

boulder_dash
1 ●1 ●2 ●1

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.

link

Comments

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

grahamb ( Feb 13 '1 )

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 ( Feb 13 '1 )

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 ( Feb 13 '1 )

add a comment

0

answered Feb 12 '1

hugo.vanderkooij
76 ●191 ●4

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.

link

Comments

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 ( Feb 12 '1 )

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 ( Feb 13 '1 )

add a comment

colorization isn't working

Comments

3 Answers

Comments

Comments

Your Answer

Question Tools

Stats

Related questions

colorization isn't working savecancel

Comments

3 Answers

Comments

Comments

Your Answer

Question Tools

Stats

Related questions

colorization isn't working