[Bug 16226] New: evince crash while highlighting certain text

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16226
Ubuntu | evince

           Summary: evince crash while highlighting certain text
           Product: Ubuntu
           Version: unspecified
          Platform: All
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: evince
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: john.dong at gmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


Evince has trouble with highlighting text in certain PDF's. At first, I thought
this was #14032, but the symptoms are completely different.


REPRODUCE:
1. Download ftp://people.redhat.com/jakub/prelink/prelink.pdf and open with
Evince (better if from a terminal)
2. On the first page, start highlighting some text, and keep on dragging down to
highlight more.

WHAT HAPPENS:

Evince suddenly shuts down, at the console, an X Windows error is reported:
jdong at ubuntu:~$ evince prelink.pdf
The program 'evince' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 4549 error_code 8 request_code 59 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

jdong at ubuntu:~$ evince prelink.pdf  --sync
The program 'evince' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 12341 error_code 8 request_code 59 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.