Bug 17623 - wireshark File->Print crashes
Summary: wireshark File->Print crashes
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-26 03:52 CET by Pierre Fortin
Modified: 2016-05-01 19:42 CEST (History)
1 user (show)

See Also:
Source RPM: wireshark-2.0.1-1.mga5
CVE:
Status comment:


Attachments
crash log (14.00 KB, text/plain)
2016-01-26 03:53 CET, Pierre Fortin
Details
crash log (34.61 KB, text/plain)
2016-01-26 03:59 CET, Pierre Fortin
Details

Description Pierre Fortin 2016-01-26 03:52:16 CET
Description of problem:  File->Print.. and wireshark crashes.

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. capture some packets (or load a capture file)
2. File->Print... (capture active or stopped)
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Pierre Fortin 2016-01-26 03:53:03 CET
Created attachment 7377 [details]
crash log
Comment 2 Pierre Fortin 2016-01-26 03:59:37 CET
Created attachment 7378 [details]
crash log

First crash log was while trying to print marked packets on an active capture.
This crash log was after opening a previously saved capture file and trying to access printing (no marked packets).
Comment 3 Samuel Verschelde 2016-02-02 14:50:24 CET
Assigning to packagers collectively as nobody is registered as this package's maintainer.

Do you manage to reproduce this bug? There's a chance it's an UPSTREAM bug, if you can, please look for similar bugs in wireshark's bug tracker.
Comment 4 Samuel Verschelde 2016-02-02 14:50:40 CET
Really assigning to packagers collectively.

Assignee: bugsquad => pkg-bugs

Comment 5 Pierre Fortin 2016-02-02 15:34:41 CET
Added pointer to this bug at:
 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12040
Comment 6 David Walser 2016-05-01 19:42:24 CEST
Marked fixed upstream two months ago and we just shipped an update for wireshark.

Status: NEW => RESOLVED
CC: (none) => luigiwalser
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.