Wireshark-bugs: [Wireshark-bugs] [Bug 10735] wireshark fails to start when run with setuid/setgi

Date: Tue, 20 Jan 2015 02:52:23 +0000

changed bug 10735


What Removed Added
Status UNCONFIRMED INCOMPLETE
Ever confirmed   1

Comment # 9 on bug 10735 from
(In reply to yuri from comment #0)
> BSD), it is natural to be running it with setuid/setgid.
> 
> However, when any of these flags is set, wireshark fails after the splash
> screen:
> 
> Error creating proxy: Timeout was reached (g-io-error-quark, 24)
> Error creating proxy: Timeout was reached (g-io-error-quark, 24)

A little Google research suggests a few possibilities (out of many, many hits
for this type of error message):

1) you're using overlay-scrollbars which could cause some problems (
http://askubuntu.com/questions/362889/error-calling-startservicebyname-for-org-gtk-vfs-daemon-timeout-was-reached-g
).  Try running Wireshark like: "LIBOVERLAY_SCROLLBAR=0 wireshark"

2) http://sourceforge.net/p/passwordsafe/bugs/1112/ says Gtk doesn't like to be
run as a forked orphan child.  I don't think we do that though...

You might also try running some other Gtk program as root to see if it
experiences the same problem.


You are receiving this mail because:
  • You are watching all bug changes.