Bug 512115

Summary: Pybliographic crashes when launching a medline query with an existing database.
Product: [Fedora] Fedora Reporter: jonathan.stott
Component: pybliographerAssignee: Zoltan Kota <zoltank>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: james.antill, pawsa, zoltank
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-06 09:57:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jonathan.stott 2009-07-16 12:41:19 UTC 
Description of problem:

Pybliographic, the GTK frontend for pybliographer, crashes when a medline query is launched, after importing an existing bibtex database.  


Version-Release number of selected component (if applicable):
Name       : pybliographer
Version    : 1.2.12
Release    : 3.fc11

How reproducible:

Exceedingly so.  It appears to be after importing any bibtex database.


Steps to Reproduce:
1. Open pybliographic
2. Open the medline query window (File -> Medline Query)
3. Search for a random topic (e.g 'Cheese')
4. Copy a reference from the list given in the new window to the first window
5. Save the database in the first window
6. Exit pybliographic
7. Open pybliographic
8. Import the database saved in step 5.
9. Open the medline query window (File -> Medline Query)
  
Actual results:

Program crashes.


Expected results:

Program lets you query medline and add more references to the database.


Additional info:

Running pybligraphic in a console to perform steps 7-9 results in the following being output in the console:

$ pybliographic 
This is Pybliographic 1.2.12 [Python 2.6.0, Gtk 2.16.2, PyGTK 2.14.1]
/usr/share/pybliographer/Pyblio/GnomeUI/FileSelector.py:118: GtkWarning: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
  ret = gtk.FileSelection.run (self)
/usr/share/pybliographer/Pyblio/GnomeUI/Utils.py:89: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
  self.xml = gtk.glade.XML (gp, window, domain = "pybliographer")

Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
aborting...
Comment 1 Zoltan Kota 2009-08-11 08:17:41 UTC 
Checked. For me it crashes as well. Investigating...
Comment 2 Zoltan Kota 2009-08-12 13:05:56 UTC 
Could you please test with the latest fc11 gtk2 update!? Gtk 2.16.5.
Comment 3 James Antill 2009-08-12 16:49:56 UTC 
 I just tried with:

gtk2.x86_64                          2.16.5-1.fc11                      @updates

...and it "worked" in that the application doesn't crash, but the Gdk-CRITICAL is still there.
Comment 4 Zoltan Kota 2009-08-25 13:40:49 UTC 
Hm, it does crash for me with 2.16.5-1. More exactly, as stated in the original bugreport, usually there is a GtkWarning first and then a Gdk-CRITICAL.
Comment 5 Zoltan Kota 2009-12-09 22:36:01 UTC 
Now I've tested again with the new gtk2 updates in f11. It doesn't crash for me now.
gtk2-2.16.6-2
Could you make some tests to check/confirm if the problem solved?!
Comment 6 jonathan.stott 2009-12-09 23:18:55 UTC 
My apologies, since submitting this bug I've moved on from Fedora and no longer have a Fedora system to test on.

So I can't help much with the testing.
Comment 7 Zoltan Kota 2010-01-06 09:57:15 UTC 
Most probably it was a gtk2 issue. So I close this bug.