Bug 708250

Summary: openbox crash when wireshark is launched
Product: [Fedora] Fedora Reporter: Othman Madjoudj <athmanem>
Component: openboxAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: mlichvar
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 17:25:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Strace output when wireshark is launched
none
Wireshark strace output none

Description Othman Madjoudj 2011-05-27 02:43:54 UTC
Created attachment 501227 [details]
Strace output when wireshark is launched

Description of problem:

When I try launch wireshark fron LXDE (Fedora Security Lab Spin), openbox crash, I've attached strace to openbox process and straced wireshark.

Version-Release number of selected component (if applicable):
openbox-3.4.11.2-8.fc15.i686
wireshark-1.4.6-2.fc15.i686

How reproducible:
100% both in LXDE and standalone Openbox

Steps to Reproduce:
1. start wireshark
  
Actual results:
Openbox crash and desktop become unsuable

Expected results:
Works

Additional info:
See strace output.

Comment 1 Othman Madjoudj 2011-05-27 02:46:03 UTC
Created attachment 501228 [details]
Wireshark strace output

Comment 2 Othman Madjoudj 2011-05-27 02:51:10 UTC
And sorry for the typos, there's no dictionaries in Security Lab Spin :-(

Comment 3 Othman Madjoudj 2011-05-27 03:16:53 UTC
Same issue after update:

openbox-3.4.11.2-8.fc15.i686
openbox-libs-3.4.11.2-8.fc15.i686
wireshark-1.4.6-3.fc15.i686
wireshark-gnome-1.4.6-3.fc15.i686

Comment 4 Othman Madjoudj 2011-05-27 05:00:33 UTC
wireshark works just fine under KDE, so I assume it's an openbox issue.

Comment 5 Miroslav Lichvar 2012-01-05 16:28:40 UTC
Can you get a backtrace for the openbox crash? abrt should be able to catch it.

Comment 6 Othman Madjoudj 2012-01-05 16:53:08 UTC
I can't reproducible it with f16 and openbox-3.5.0-3.fc16, I guess we can close this bug unless f15 is still affected.

Comment 7 Fedora End Of Life 2012-08-07 17:25:21 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping