Created attachment 571544 [details]
Backtrace copied form the ABRT window.

Description of problem:
Bibus Reference Editor crashes with an X Window System error when selecting "Bibliography Type".

Version-Release number of selected component (if applicable):
bibus-1.5.1-5.fc15.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Start bibus, e.g.:
	$ bibus &
2. In left panel, right-click on "References", select "New reference". (Reference Editor window opens.)
3. In Reference Editor, left-click in "Bibliography Type" field, select "TECHREPORT" (or any other option), left-click.
  
Actual results:
Bibus crashes & window disappears with following message:

Gdk-ERROR **: The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 69421 error_code 3 request_code 151 minor_code 3)
  (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.)


Expected results:
Continued entry of the bibliographic information.

Additional info:
This behaviour started within the last 2 weeks; first noticed after the KDE packages update on 3/18, but I had not used bibus within a week or so before that.  Suspecting an incompatibility with updated pykde package. Problem occurs whether or not there is a LibreOffice document open.

ABRT reports "Process /usr/bin/python was killed by signal 5 (SIGTRAP)", but ABRT refuses to report, saying "Reporting disabled because the backtrace is unusable.  I've attached the backtrace text copied from the ABRT window, just in case it is partly useful.