Created attachment 695549 [details]
File: backtrace

Created attachment 695550 [details]
File: core_backtrace

Created attachment 695551 [details]
File: environ

Description of problem:
I am not totally sure what caused this BUT it happened while:

was doing updates with yum extender, and it found 61 updates today in  testing repo -kernel PAE was last successful update and only #3 of 61 total to update3. yum extender froze while or after this particular update. I closed yum extender and  opened it again, it recognized failed but still running process "yum_childtask.p" which I was then giving up and goint to reboot.  

THEN:
I got this crash report for blueman before I restarted. 

 also: my usb mouse was not working and had to be unplugged and re-plugged about 20 min ago. I think this is a motherboard problem because it also happens on occasion with Win XP.

 ;-) Thanks Guys! I know my crash reports are convoluted and annoying haha

Version-Release number of selected component:
blueman-1.23-5.fc18

Additional info:
reporter:       libreport-2.1.4
cmdline:        /usr/bin/python /bin/blueman-applet
executable:     /bin/blueman-applet
kernel:         3.8.7-201.fc18.i686
runlevel:       N 5
uid:            0

Truncated backtrace:
PulseAudioUtils.py:602:__event_callback:TypeError: sighandler() takes no arguments (2 given)

Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 314, in 'calling callback function'
  File "/usr/lib/python2.7/site-packages/blueman/main/PulseAudioUtils.py", line 602, in __event_callback
    def __event_callback(self, context, event_type, idx, userdata):
TypeError: sighandler() takes no arguments (2 given)

Local variables in innermost frame:
userdata: None
self: <PulseAudioUtils object at 0x8c04b6c (blueman+main+PulseAudioUtils+PulseAudioUtils at 0x8c3b110)>
context: 147428944
event_type: 36L
idx: 21L

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.