banshee aborts on horse-poo

[rjasmin]

plugging in a i(phone in this case) anything while listening to banshee causes internal failure, removal of device and banshee to abort.

iirc, banshee should pick up the device.

its a 5s.
I have force disabled pulse and am on alsa. instructions for this are elsewhere. touche for this but pulse is as busted as gnome3.

THIS SHOULD NOT HAPPEN.
hardware is internal to the motherboard and REMOVAL NOTICES are beligerent and acinine and NONSENSE.
NOTHING is REMOVED.
ALC 889 INTEL driver on CrossHairV(mind you a known SIN board but..) MUST certainly be broken.

also whist reporting this one:

Unhandled Exception:
System.ExecutionEngineException: Couldn't create thread
  at (wrapper managed-to-native) System.Threading.ThreadPool:RequestWorkerThread ()
  at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () <0x7f8adf834790 + 0x00044> in <filename unknown>:0
  at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 0x000fc> in <filename unknown>:0
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7f8adf836530 + 0x00008> in <filename unknown>:0

Unhandled Exception:
System.ExecutionEngineException: Couldn't create thread
  at (wrapper managed-to-native) System.Threading.ThreadPool:RequestWorkerThread ()
  at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () <0x7f8adf834790 + 0x00044> in <filename unknown>:0
  at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 0x000fc> in <filename unknown>:0
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7f8adf836530 + 0x00008> in <filename unknown>:0

yes I have caps (500) but if your threading over 500 we have an issue. you are trying to forkbomb the system. only fedora as native prevention and mitigation techniques that work OOBE.YOu have to force them on debian based systems.