Comment # 4
on bug 10405
from [email protected]
> > This happens systematically 100% of the times, but has started recently.
> I.e., it wasn't happening at all until recently, and recently it's
> started happening every time you run Wireshark?
That's exactly what I meant, but that was not completely correct, and now I've
figured out better:
- if I run wireshark as root (with sudo from a terminal), then the issue never
happens
- if I run it as normal user (either from Ubuntu's Dash or from a terminal but
without sudo), then it happens 100% of the times (or close enough so that I
haven't been able to run it once without observing the issue)
I usually run wireshark as root (with sudo), because otherwise it doesn't allow
me to capture from any network interface (except bluetooth). So I had always,
or 99.9% of the times, run it as root. Now I ran it as normal user a few times
(once to see if it still wouldn't allow me to capture, and then a few more
times just to see if this hangs-when-closing bug was systematic)
So I guess this has always been the same and probably nothing has changed
recently.
You are receiving this mail because:
- You are watching all bug changes.