Wireshark-bugs: [Wireshark-bugs] [Bug 4569] New: Trying to Run Wireshark as "root" causes system
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 10 Mar 2010 18:43:26 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4569

           Summary: Trying to Run Wireshark as "root" causes system to
                    completely lockup (requires hard reset)
           Product: Wireshark
           Version: 1.2.6
          Platform: x86-64
        OS/Version: Ubuntu
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: gajimmy@xxxxxxxxxxx


Build Information:
Version 1.2.6

Copyright 1998-2010 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.3, with libpcap 1.0.0, with libz
1.2.3.3, without POSIX capabilities, without libpcre, without SMI, without
c-ares, without ADNS, without Lua, without GnuTLS, without Gcrypt, without
Kerberos, without GeoIP, without PortAudio, without AirPcap.

Running on Linux 2.6.31-20-generic, with libpcap version 1.0.0.

Built using gcc 4.4.1.

--
Running Wireshark on an AMD64 Quad Core Phenom II with 8 GB of DDR3 memory
using Ubuntu Karmic Koala (9.10).  I've installed Wireshark both from the
repositories (1.2.2) and from source (the current version 1.2.4).  In both
cases, no matter what, if I try to run it as "root", as soon as I try to start
it up, it locks up my system so badly that the only way I can get out of it is
to perform a hard restart of my system (hold down the power button on the box
until it turns off).

I've searched to see if there is an answer anywhere on the Internet.  Plus,
I've searched to see if this bug has been reported.  I've not seen it. 
However, I have found at least two people on the Ubuntu Forums who are having
the same problem.  Of interest is that one of them lists the exact, same CPU
and motherboard as I have (AMD64 Quad Core Phenom II).  I do not know what the
other person is using.  They did not provide that information.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.