It was actually the ~/.wireshark/recent_common that caused this - and when you'll look at it, it's obvious why - though I have no clue how I got to this situation. Y.
On Wed, Oct 5, 2011 at 10:23 PM, Stephen Fisher <st...@stephen-fisher.com>wrote: > On Wed, Oct 05, 2011 at 10:07:36PM +0200, Kaul wrote: > > > I'm on #39276. Something tells me that until I delete the prefs., it's > > not going to go away :( > > Do a "mv ~/.wireshark/preferences ~/.wireshark/preferences.old" and see > if it works fine after that. If so, sharing your preferences.old file > with us may allow us to repliate the problem. > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe >
recent_common.old
Description: Binary data
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
