Bug 649986
| Summary: | Gajim consumes 100% CPU | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Johan Vromans <jvromans> |
| Component: | gajim | Assignee: | Michal Schmidt <mschmidt> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | mschmidt |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gajim-0.14.1-3.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-11-19 22:33:27 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
Johan Vromans
2010-11-04 22:33:28 UTC
I am not seeing this problem on my F14 systems. Apart from the high CPU usage, is the program otherwise usable? I wonder if the bug is triggered by something specific in your Jabber account. Could you test it with another Jabber account? Also try running Gajim from a terminal window with debugging output: gajim --verbose Hopefully it will show a hint. I tried this on another F14 system and it shows the same behaviour. I ran gajim --verbose on F13 and F14. The main difference is that after setting up, F13 sits waiting quietly for messages while F14 starts looping: 16:27:10 (I) gajim.c.x.idlequeue read timeout removed for fd 30 (the fd may vary between sessions). This loop consumes the CPU time. When I set the account Offline, and then Available, gajim behaves like it should (and did on F13). So the looping only occurs when gajim is started and automatically connects the account. I can send you the F13 and F14 logs but I'm hesitant to upload them here since they may contain sensitive information. This may be the same bug: http://trac.gajim.org/ticket/5991 Can you check with the XML console what the server tells you in the "<streamhost ...>" data? I made a scratch build of Gajim with the patch from the upstream bug applied: http://koji.fedoraproject.org/koji/taskinfo?taskID=2580521 Let me know if it fixes the bug for you. The streamhost info from my jabber server is, indeed: <streamhost jid="proxy.jabber.xs4all.nl" host="127.0.1.1" port="7777"/> Gajim with the patch from the upstream bug applies behaves normally. Thanks a lot! Should I inform the jabber server people that they send the wrong info? gajim-0.14.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gajim-0.14.1-2.fc14 (In reply to comment #4) > Should I inform the jabber server people that they send the wrong info? Yes, please. gajim-0.14.1-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gajim'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gajim-0.14.1-2.fc14 The original fix in gajim-0.14.1-2.fc14 caused a regression for a gmail.com user. I applied another patch in 0.14.1-3. Could you please verify that gajim-0.14.1-3.fc14 still works fine for you? https://admin.fedoraproject.org/updates/gajim-0.14.1-3.fc14 Confirmed. Thanks. gajim-0.14.1-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gajim'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gajim-0.14.1-3.fc14 gajim-0.14.1-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |