Description of problem:
See bug 955617 as my main example

I think it's over merging any X seg into that bug - see below for more details.

Version-Release number of selected component (if applicable):
F20 libreport-2.1.10-1.fc20.x86_64


How reproducible:
Reasonably - there seem to be a lot of people on that bug and I know my bug was quite different to the original reporters, and I suspect most of the others are.

Steps to Reproduce:
1. Get X to crash
2. Attempt to report bug

Actual results:
It claims it's a dupe of 955617

Expected results:
Most probably aren't a dupe of 955617 - it needs to look further up the stack

Additional info:

Looking at the bottom of the original backtrace on that bug we have:

#0  0xb7792424 in __kernel_vsyscall ()
#1  0x4be11756 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv#2  0x4be12f93 in __GI_abort () at abort.c:90
#3  0x080b8daa in OsAbort () at utils.c:1299
#4  0x080d2147 in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1075
#5  0x080d21eb in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1119
#6  0x080b4662 in AbortServer () at log.c:670
#7  0x080b4ccf in FatalError (f=f@entry=0x81f6d38 "Caught signal %d (%s). Server aborting\n") at log.c:811
#8  0x080b6136 in OsSigHandler (signo=11, sip=0xbfaad08c, unused=0xbfaad10c) at osinit.c:147
        unused = 0xbfaad10c
        sip = 0xbfaad08c
        signo = 11
#9  <signal handler called>
No symbol table info available.
#10 0x08117ca2 in xf86CursorSetCursor (pDev=pDev@entry=0x8f20e48, pScreen=0x8e63948, pCurs=0x9117410, x=747, y=515) at xf86Cursor.c:333
        infoPtr = 0x8e7ecc8

So I say that #0..#8 are probably irrelevant to comparing the backtraces; #8 is just 'we got a seg' and it's all down hill from there.  #10 onwards is what we need here to distinguish different causes of the seg.