Bug#852396: wireshark: GUI using wrong capture interface

2017-01-24 Thread Bálint Réczey
Control: fixed -1 2.2.4+gcc3dc1b-1 2017-01-24 17:59 GMT+01:00 Philipp Marek : >> > I have also uploaded 2.2.4 to unstable, could you please give it a try? >> Hmmm, I don't see it yet. Please stand by, perhaps I can test tomorrow. > 2.2.4+gcc3dc1b-1 solves both issues. >

Bug#852396: wireshark: GUI using wrong capture interface

2017-01-24 Thread Philipp Marek
> I could not reproduce the issue on a fresh sid system. > > Could you please provide the output of "tshark -D" to see the > interfaces on your system? $ tshark -D 1. eth0 2. vnet0 3. virbr1 4. vnet1 5. virbr2 6. any 7. lo (Loopback) 8. virbr0 9. wlan0 10. bluetooth0 11. nflog 12. nfqueue 13.

Bug#852396: wireshark: GUI using wrong capture interface

2017-01-24 Thread Bálint Réczey
Control: tags -1 moreinfo Hi Philipp, 2017-01-24 8:20 GMT+01:00 Philipp Marek : > Package: wireshark > Version: 2.2.3+g57531cd-1 > Severity: normal > > Clicking on the "lo" interface (with or without a capture filter) results > in this process tree: > > 5985 ?

Bug#852396: wireshark: GUI using wrong capture interface

2017-01-23 Thread Philipp Marek
Package: wireshark Version: 2.2.3+g57531cd-1 Severity: normal Clicking on the "lo" interface (with or without a capture filter) results in this process tree: 5985 ?Sl 0:21 /usr/bin/wireshark 6787 ?Sl 0:00 \_ /usr/bin/dumpcap -t -n -i eth0 ... and that doesn't work,