Bug 602572
Summary: | [abrt] crash in python-nltk-1:0.9.9-2.fc13: Tkinter.py:1193:_configure:TclError: bad screen distance "80.0" | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Milos Jakubicek <xjakub> | ||||
Component: | python-nltk | Assignee: | Michel Lind <michel> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 13 | CC: | michel, robinlee.sysu | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:caa97df4 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-11-12 14:13:55 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: | |||||||
Attachments: |
|
Description
Milos Jakubicek
2010-06-10 08:30:23 UTC
Created attachment 422822 [details]
File: backtrace
Hi Milos, Thanks for the report. Could you describe a sequence of steps that would reproduce this problem? http://code.google.com/p/nltk/issues/detail?id=592 Upstream response: "I believe this is a Tkinter issue, and nothing we can resolve from within NLTK." And the forwarded issue is marked "won't fix" upstream. I recently reported a similar bug against Miro -- it was passing dimensions that are floating points and that is not permitted by GTK (but apparently valid on some other platforms). The same issue might be the case here. I'll take a look -- but again, Milos, if you could let me know precisely what you were doing with nltk that would really help testing the fix. I could not obtain non-integral values for "height" in testing, so I deliberately modified height by adding 0.5 to it, and still could not reproduce the problem. so: 1) looks like nltk's chartparser_app generally produce integral heights anyway 2) and that Tkinter is perfectly happy with float values If there was a Tkinter bug it must have been fixed. |