https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4308
Summary: completely unresponsive when run very first time by
root user
Product: Wireshark
Version: 1.2.4
Platform: x86
OS/Version: Fedora
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: ron.flory@xxxxxxxxxx
Build Information:
Version 1.2.4
Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 with GTK+ 2.18.3, with GLib 2.22.2, with libpcap 1.0.0, with libz
1.2.3, without POSIX capabilities, with libpcre 7.8, with SMI 0.4.8, without
c-ares, without ADNS, without Lua, with GnuTLS 2.8.5, with Gcrypt 1.4.4, with
MIT Kerberos, without GeoIP, with PortAudio V19-devel (built Jul 28 2009),
without AirPcap.
Running on Linux 2.6.31.6-162.fc12.i686.PAE, with libpcap version 1.0.0, GnuTLS
2.8.5, Gcrypt 1.4.4.
Built using gcc 4.4.2 20091027 (Red Hat 4.4.2-7).
--
Problem:
After a fresh install of FC12, ran Wireshark from root account for the very
first time.
Wireshark was complete unresponsive, would not respond to mouse clicks, and
could not be closed without resorting to command like "kill" command from
another shell.
This problem persisted upon several attempts to re-launch Wireshark. Each had
to be hard-killed from another shell because it was unresponsive to all input.
------------------------------------------
Underlying Cause:
It seems that Wireshark opens a warning dialog when it is run by the root user
for the first time BUT THIS DIALOG IS OPENED BEFORE/UNDER THE MAIN GUI, MAKING
IT INVISIBLE.
My guess is there is an oversight in the order the warning and main windows
are created. If the warning dialog was opened AFTER the main gui, it would be
visible to the user, allowing the user to dismiss the warning and continue
using Wireshark normally.
Once I fortuitously discovered and dismissed the hidden warning dialog,
Wireshark seems to operate just fine on subsequent sessions.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
