Bug 558286
Summary: | bip crashes when ubuntu xchat connects | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> |
Component: | bip | Assignee: | Brian Lane <bcl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | dpierce, lorenzo, mmahut |
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-10-29 17:25:30 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
Kevin Fenzi
2010-01-24 17:56:56 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Could you try v0.8.6 when it hits updates-testing and let me know if you still have problems? Also, leaving feedback on bodhi would help: https://admin.fedoraproject.org/updates/bip-0.8.6-1.fc12 To install the test version run: yum --enablerepo=updates-testing update bip I've updated here and asked my friend with the weird client to test. Will let you know what I find out. Well, it no longer crashes. ;) Now the client can't connect and I see in the logs: 27-10-2010 12:24:28 ERROR: [X] Invalid credentials (user: X) but the password is correct. Puzzling. Progress! Are you sure the password is being sent as un:pw:connection? Maybe try generating a new one with bipmkpw? I'm sure the format didn't change from 0.8.4, I didn't need to change anything when I upgraded my system to 0.8.6 Yeah, the password is right. They can connect from several other machines just fine with that pass. So, its sounding to me like the client on that machine is just broken and doing the wrong thing somehow. ;( Time to fire up wireshark and sniff the connection :) Sounds like this bug is fixed though, so I'm going to close it. |