Testing procedure:
https://wiki.mageia.org/en/QA_procedure:Wireshark

Whiteboard: (none) => has_procedure

I have some bad news: on my Mageia v5 x86-64 VM simply typing "wireshark" in the command line - either as root or as a normal user after "sg wireshark" causes it to just hang there and not start the GUI. strace shows it does a lot of stuff. I can start an "xterm" fine from that command line and "wireshark" works fine on my Cauldron system.

CC: (none) => shlomif

(In reply to Shlomi Fish from comment #2)
> I have some bad news: on my Mageia v5 x86-64 VM simply typing "wireshark" in
> the command line - either as root or as a normal user after "sg wireshark"
> causes it to just hang there and not start the GUI. strace shows it does a
> lot of stuff. I can start an "xterm" fine from that command line and
> "wireshark" works fine on my Cauldron system.

I am aware of this issue.  I believe it is a missing dependency, but I don't know what it is.  I saw this issue on my pre-mga5 development VM which was a very minimal install.  More full-featured installations don't show this issue.

(In reply to David Walser from comment #3)
> (In reply to Shlomi Fish from comment #2)
> > I have some bad news: on my Mageia v5 x86-64 VM simply typing "wireshark" in
> > the command line - either as root or as a normal user after "sg wireshark"
> > causes it to just hang there and not start the GUI. strace shows it does a
> > lot of stuff. I can start an "xterm" fine from that command line and
> > "wireshark" works fine on my Cauldron system.
> 
> I am aware of this issue.  I believe it is a missing dependency, but I don't
> know what it is.  I saw this issue on my pre-mga5 development VM which was a
> very minimal install.  More full-featured installations don't show this
> issue.

I see - thanks for the heads up.

Also, it only affected Qt5 builds, not Gtk+, so it may be a packaging issue in our Qt5 libraries.

(In reply to David Walser from comment #3)
> (In reply to Shlomi Fish from comment #2)
> > I have some bad news: on my Mageia v5 x86-64 VM simply typing "wireshark" in
> > the command line - either as root or as a normal user after "sg wireshark"
> > causes it to just hang there and not start the GUI. strace shows it does a
> > lot of stuff. I can start an "xterm" fine from that command line and
> > "wireshark" works fine on my Cauldron system.
> 
> I am aware of this issue.  I believe it is a missing dependency, but I don't
> know what it is.  I saw this issue on my pre-mga5 development VM which was a
> very minimal install.  More full-featured installations don't show this
> issue.

after a long amount of investigation, I found out that the problem appears to be that I cannot start wireshark on IceWM but can on JWM or KDE4 or other desktops. ð¡ - I am angry. Perhaps there were also some missing packages becasue I also installed libpcap-devel, all lib64qt* (minus the devel ones) and lib64xcb* packages and some other packages.

Ahh, interesting.  IceWM is what I was using in the VM where I saw the issue as well.

MGA5-32 on Acer D620 Xfce
No installation issues
Used procedure as per comment 1:
wireshark -n wiresharktest : creates wiresharktest file with data
tshark -nr wiresharktest : gives feedback at CLI + file like
1 0.000000000  192.168.2.6 -> 192.168.2.1  DNS 73 Standard query 0xdf42 A www.google.be
  2 0.000037645  192.168.2.6 -> 192.168.2.1  DNS 73 Standard query 0xd483 AAAA www.google.be
  3 0.000278670  192.168.2.6 -> 192.168.2.1  DNS 73 Standard query 0xa41c A www.google.be

editcap -r wiresharktest wiresharktest50 1-50 : no feedback at CLI but file created OK
mergecap -v -w wiresharkmerged wiresharktest wiresharktest50 : creates file  + CLI feedback:
mergecap: wiresharktest is type Wireshark/... - pcapng.
mergecap: wiresharktest50 is type Wireshark/... - pcapng.
mergecap: selected frame_type Ethernet (ether)
mergecap: ready to merge records
Record: 1
Record: 2
Record: 3
etc .....

capinfos wiresharktest50
File name:           wiresharktest50
File type:           Wireshark/... - pcapng
File encapsulation:  Ethernet
File timestamp precision:  nanoseconds (9)
Packet size limit:   file hdr: (not set)
Number of packets:   50
File size:           10 kB
and some more

As far as I am concerned OK

CC: (none) => herman.viaene
Whiteboard: has_procedure => has_procedure MGA5-32-OK

(In reply to Herman Viaene from comment #8)
> MGA5-32 on Acer D620 Xfce
> No installation issues
> Used procedure as per comment 1:

Thanks Herman! Should I still test it on my x86-64 VM? Or can this update be validated as is?

(In reply to Shlomi Fish from comment #9)
> (In reply to Herman Viaene from comment #8)
> > MGA5-32 on Acer D620 Xfce
> > No installation issues
> > Used procedure as per comment 1:
> 
> Thanks Herman! Should I still test it on my x86-64 VM? Or can this update be
> validated as is?

tested fine on an x86-64 vbox VM. marking as MGA5-64-OK.

Whiteboard: has_procedure MGA5-32-OK => has_procedure MGA5-32-OK

(In reply to Shlomi Fish from comment #9)
> (In reply to Herman Viaene from comment #8)
> > MGA5-32 on Acer D620 Xfce
> > No installation issues
> > Used procedure as per comment 1:
> 
> Thanks Herman! Should I still test it on my x86-64 VM? Or can this update be
> validated as is?

tested fine on an x86-64 vbox VM. marking as MGA5-64-OK.

Whiteboard: has_procedure MGA5-32-OK => has_procedure MGA5-32-OK MGA5-64-OK

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0120.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED