Comment # 13
on bug 9516
from [email protected]
(In reply to comment #12)
> (In reply to comment #11)
> > Actually I always did the same thing and earlier also NFS was there but this
> > error never came.
>
> Were you using the same version of Wireshark earlier, when you didn't get
> the error? (I assume from "I always did the same thing" that, when you
> didn't get the error, you made an RPM and tried to install it, just as you
> did when you *did* get the error, and that, from "earlier also NFS was
> there", you tried to install it in your home directory and that your home
> directory was mounted over NFS.)
>
> > Can you please paste the actual ./configure flags which I need to give.
> > Is this ok?
> >
> > ./configure --enable-setuid-install --disable-setcap-install
>
> Yes.
Earlier I was using wireshark version 1.8.6(when it was working with NFS) but
now for the first time I am using wireshark version 1.10.3 and getting the
error. Has any change been done in 1.10.3(not working with NFS) regarding this?
Also I tried using ./configure --enable-setuid-install
--disable-setcap-install, but that too didn't help.
Then I thought of disabling dumpcap(./configure --enable-dumpcap=no) and after
make rpm-package it was not there in ~vishnu.bhatt/install/bin but after rpm
-ivhf wireshark.rpm
I got the same error and dumpcap was present in ~vishnu.bhatt/install/bin
How is dumpcap getting created after running rpm -ivhf wireshark.rpm?
You are receiving this mail because:
- You are watching all bug changes.
