Description of problem: Opened Blueman Device Manager 1.23 paired with Smart Phone Xperia P and tried to send binary file. Click accept on the phone screen. I think the crash alarm appeared even before I click accept. Version-Release number of selected component: obex-data-server-0.4.6-4.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/obex-data-server --no-daemon '' crash_function: obex_client executable: /usr/bin/obex-data-server kernel: 3.7.4-204.fc18.i686.PAE remote_result: 820522 uid: 1000 var_log_messages: Jan 28 11:26:25 mdimitr-laptop abrt[13269]: Saved core dump of pid 2025 (/usr/bin/obex-data-server) to /var/spool/abrt/ccpp-2013-01-28-11:26:25-2025 (765952 bytes) Truncated backtrace: Thread no. 1 (6 frames) #0 obex_client at obex_client.c:178 #1 obex_data_indication at obex_main.c:314 #2 obex_transport_handle_input at obex_transport.c:113 #3 OBEX_HandleInput at obex.c:467 #4 obex_io_callback at src/ods-session.c:247 #5 g_io_unix_dispatch at giounix.c:167 Potential duplicate: bug 820522
Created attachment 688814 [details] File: backtrace
Created attachment 688815 [details] File: cgroup
Created attachment 688816 [details] File: core_backtrace
Created attachment 688817 [details] File: dso_list
Created attachment 688818 [details] File: environ
Created attachment 688819 [details] File: limits
Created attachment 688820 [details] File: maps
Created attachment 688821 [details] File: open_fds
Created attachment 688822 [details] File: proc_pid_status
send file by bluetooth reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/obex-data-server --no-daemon '' crash_function: obex_client executable: /usr/bin/obex-data-server kernel: 3.10.10-100.fc18.x86_64 package: obex-data-server-0.4.6-4.fc18 reason: Process /usr/bin/obex-data-server was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.