Bug 420091
Summary: | Deluge crashes when trying to open | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Keith <krhansford> | ||||
Component: | deluge | Assignee: | Peter Gordon <peter> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 8 | CC: | jar884, martin.sourada | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-03-07 22:15:49 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
Keith
2007-12-11 17:06:41 UTC
Created attachment 284351 [details]
bug report
First, thanks for the bug report. Second, it would be good if you provide more info, like affected package versions, etc. Third, I tried it and it indeed crashes... But I tried switching theme to Clearlooks and it crashes as well, so changing component to deluge. I don't know if this will make a difference but Deluge released 0.5.7.1, a bug fix release. This might help fix the crashing. Hi, I've just tried deluge-0.5.7.1-2.fc8 with gtk-nodoka-engine-0.6.90.1-0.80.fc8 (my private build, almost identical to gtk-nodoka-engine-0.6.90.1-1.fc9 which is now in koji). Seems to work. Can you try the new deluge version? I can verify that deluge-0.5.7.1-2.fc8 works fine with Clearlooks. I'm pretty sure the problem was with the 0.5.7 release of deluge that was fixed in 0.5.7.1, not with Nodoka. I found this bug while searching through all of those reported against Deluge. Is this still an issue for the reporter(s); or can we closed this as fixed as of the 0.5.7.1 release? Thanks. This has been in the NEEDINFO state for nearly two months now. I believe it safe to assume that this is fixed, then. |