Balint Reczey
changed
bug 12325
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
INCOMPLETE
|
| Ever confirmed |
|
1
|
Comment # 2
on bug 12325
from Balint Reczey
Hi,
I have just tried to reproduce the issue on a clean Vagrant VM
('ubuntu/trusty64' (v20160323.1.0)).
Both wireshark-qt and wireshark-gtk installed fine:
...
vagrant@vagrant-ubuntu-trusty-64:~$ history
1 sudo apt-get update
2 sudo add-apt-repository ppa:wireshark-dev/stable
3 sudo apt-get update
4 sudo apt-get install wireshark-qt
5 history
6 sudo apt-get install wireshark-gtk
7 history
vagrant@vagrant-ubuntu-trusty-64:~$ wireshark --version
Wireshark 2.0.2 (SVN Rev Unknown from unknown)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.2.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.8, with GLib 2.40.2, with SMI 0.4.8, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT
Kerberos,
with GeoIP, with QtMultimedia, without AirPcap.
Running on Linux 3.13.0-85-generic, with locale C, with libpcap version 1.5.3,
with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt 1.5.3.
Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (with SSE4.2)
Built using gcc 4.8.4.
---
I suspect the problem is caused by something specific to the system you tried
installing wireshark on.
The output of:
sudo apt-get update
sudo apt-get -f install
may help in diagnosing the problem if the commands above don't fix it already.
You are receiving this mail because:
- You are watching all bug changes.