Bug 1117553
Summary: | bitlbee crashes often | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lokesh Mandvekar <lsm5> |
Component: | bitlbee | Assignee: | Robert Scheck <redhat-bugzilla> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | lsm5, mcepl, mcepl, redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | bitlbee-3.2.2-3.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-30 21:56:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lokesh Mandvekar
2014-07-08 23:46:39 UTC
Do you have any backtrace or debugging information? There are many of this sort: Jul 08 19:57:44 nagato.amegakure.ch bitlbee[16334]: ** (process:16334): CRITICAL **: purple_core_init: assertion 'purple_get_core() == NULL' failed Jul 08 19:57:44 nagato.amegakure.ch bitlbee[16334]: libpurple initialization failed. Jul 08 19:58:34 nagato.amegakure.ch bitlbee[16338]: ** (process:16338): CRITICAL **: purple_core_init: assertion 'purple_get_core() == NULL' failed Jul 08 19:58:34 nagato.amegakure.ch bitlbee[16338]: libpurple initialization failed. Jul 08 20:01:53 nagato.amegakure.ch bitlbee[16345]: ** (process:16345): CRITICAL **: purple_core_init: assertion 'purple_get_core() == NULL' failed Jul 08 20:01:53 nagato.amegakure.ch bitlbee[16345]: libpurple initialization failed. Does this help? Do you use any libpurple based functionality? Note that oscar, jabber, yahoo, msn and twitter protocols are still from BitlBee itself not via libpurple. Okay, this is caused due to non-forkdaemon and libpurple. I will build the package again without libpurple because we can not (yet) switch to bitlbee forkdaemon mode. bitlbee-3.2.2-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2014-8126/bitlbee-3.2.2-1.fc19 bitlbee-3.2.2-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2014-8129/bitlbee-3.2.2-2.fc20 Package bitlbee-3.2.2-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bitlbee-3.2.2-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-8126/bitlbee-3.2.2-2.fc19 then log in and leave karma (feedback). Robert, thanks for the update, things seem to be working well for me :) bitlbee-3.2.2-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2.2-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |