Description of problem: first boot-up after large update pkg... Version-Release number of selected component: telepathy-haze-0.6.0-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-haze crash_function: yahoo_send_typing kernel: 3.6.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 yahoo_send_typing at libymsg.c:4681 : #1 purple_conversation_destroy at conversation.c:483 : #2 haze_im_channel_dispose at im-channel.c:623 : #4 g_hash_table_remove_all_nodes at ghash.c:536 : #5 g_hash_table_remove_all at ghash.c:1345 : #6 g_hash_table_destroy at ghash.c:1049 : #7 close_all at im-channel-factory.c:349 : #8 ffi_call_unix64 at ../src/x86/unix64.S:75 : #9 ffi_call at ../src/x86/ffi64.c:486 : #10 g_cclosure_marshal_generic at gclosure.c:1454 Potential duplicate bug: 794949
Created attachment 641987 [details] File: environ
Created attachment 641988 [details] File: event_log
Created attachment 641989 [details] File: limits
Created attachment 641990 [details] File: backtrace
Created attachment 641991 [details] File: cgroup
Created attachment 641992 [details] File: smolt_data
Created attachment 641993 [details] File: executable
Created attachment 641994 [details] File: maps
Created attachment 641995 [details] File: build_ids
Created attachment 641996 [details] File: proc_pid_status
Created attachment 641997 [details] File: open_fds
Not really sure ... just chatting with empathy backtrace_rating: 4 Package: telepathy-haze-0.6.0-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Was chatting while downloading huge patch set. I checked YAHOO (via empathy) today (day following + reboot). All seems well enough.
loging to my account. backtrace_rating: 4 Package: telepathy-haze-0.6.0-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.