Bug 1526166

Summary: abrt-applet thinks a crash is a duplicate of an existing bug when it probably isn't
Product: [Fedora] Fedora Reporter: kevin
Component: gnome-abrtAssignee: Jakub Filak <jakub>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: awilliam, digitalfreak, jakub, mhabrnal, mkutlak, mmarusak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-14 22:54:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description kevin 2017-12-14 21:04:12 UTC 
See comment #83 in bug #1510059. Seems the original report for 1510059 is different than my automatically reported comment #78. Do the heuristics of abrt-applet take into account the stack trace?
Comment 1 Adam Williamson 2017-12-14 22:54:44 UTC 
This and #1509086 are essentially the same - we now have *two* cases (1510059 and 1469813), but the underlying cause is the same, it's this _g_log_abort codepath.

*** This bug has been marked as a duplicate of bug 1509086 ***