Red Hat Bugzilla – Bug 201522
User cannot run Wireshark in unprivileged mode
Last modified: 2008-07-24 16:16:12 EDT
+++ This bug was initially created as a clone of Bug #159958 +++
Description of problem:
Attempting to open ethereal as an unprivilged user:
Warning window opens asking for root password. When clicking on the
'unprivilged' button, program exits with 'Unknown Error' window and a close button.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Ethereal as non-root user.
2. Select 'Unpriviliged' button
3. Program exits with 'Unknown Error'.
Actual Results: Program exits with a '0' result code.
Expected Results: Program opens with non-privilged user permissions, allowing a
user to do an ethereal analysis of a packet capture owned by the user.
Workaround: run "/usr/sbin/ethereal" directly, bypassing "consolehelper".
Thanks for your report.
I can't reproduce the crash on i386. Please:
* run wireshark,
* when the password dialog appears, switch to a virtual terminal
* attach gdb to the "userhelper" process and let it continue.
* switch to X, select the "Unprivileged" button
* switch back to a virtual terminal; if gdb reports a crash,
please generate a backtrace and attach it to this bug report.
Created attachment 150262 [details]
GDB reported a sigsegv. I'm attaching the backtrace.
Thank you, this indeed seems to be a the same bug as #159958.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Thank you for fixing this.