Description of problem: Just doing a reboot. Version-Release number of selected component: gnome-bluetooth-3.4.2-1.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 backtrace_rating: 4 cmdline: bluetooth-applet crash_function: g_variant_type_info_check kernel: 3.3.4-5.fc17.i686 truncated backtrace: :Thread no. 1 (10 frames) : #5 g_variant_type_info_check at gvarianttypeinfo.c:164 : #6 g_variant_type_info_get_type_string at gvarianttypeinfo.c:200 : #7 g_variant_get_type at gvariant.c:1999 : #8 g_variant_is_of_type at gvariant.c:2041 : #9 g_variant_lookup_value at gvariant.c:1039 : #10 bluez_appeared_cb at bluetooth-client.c:971 : #11 actually_do_call at gdbusnamewatching.c:154 : #13 do_call at gdbusnamewatching.c:216 : #14 call_appeared_handler at gdbusnamewatching.c:228 : #16 get_name_owner_cb at gdbusnamewatching.c:348
Created attachment 635250 [details] File: core_backtrace
Created attachment 635251 [details] File: environ
Created attachment 635252 [details] File: backtrace
Created attachment 635253 [details] File: limits
Created attachment 635254 [details] File: cgroup
Created attachment 635255 [details] File: smolt_data
Created attachment 635256 [details] File: maps
Created attachment 635257 [details] File: dso_list
Created attachment 635258 [details] File: proc_pid_status
Created attachment 635259 [details] File: var_log_messages
Created attachment 635260 [details] File: open_fds
This happened while starting up the system. I do not have any blue-tooth device so thats probably the start of the problem. backtrace_rating: 4 Package: gnome-bluetooth-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
A bug appeared after an update reboot. backtrace_rating: 4 cmdline: bluetooth-applet core_backtrace: crash_function: g_variant_type_info_check executable: /usr/bin/bluetooth-applet kernel: 3.8.4-102.fc17.i686 package: gnome-bluetooth-3.4.2-1.fc17 reason: Process /usr/bin/bluetooth-applet was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors:
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.