Summary: | kded crash at login time | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | rtdvrs |
Component: | bluetooth-daemon | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | joost.van.weenen |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
rtdvrs
2012-06-17 15:31:06 UTC
I have the same issue on shutdown. Hi, can you tell me which BlueDevil versions are you using? Also, could you test this with 1.3rc2? it should be fixed. Thanks! I disabled bluetooth completely, so I cannot test this. I always found it questionable that on hardware without bluetooth a bluetooth daemon is still started. The correct behaviour should be: - check whether any bluetooth hardware exists - if it exists, run some daemon unless it has been explicitly disabled -if it doesn't exist, do not run any software which depends on bluetooth hardware being present. - if someone inputs a bluetooth USB device, i.e. hotpluggable device, detect that this is happening and then start the bluetooth daemon unless another variable in some file has been set. This is what we do, if no bluetooth hardware is detected all that we do is listen for a bt interface to be plugged. Going to close the bug since i'm quite confident that we fixed this. Please! if you are able to reproduce this with 1.3 feel free to reopen the bug. Thanks! (In reply to comment #3) > I disabled bluetooth completely, so I cannot test this. I always found it > questionable that on hardware without bluetooth a bluetooth daemon is still > started. The correct behaviour should be: > > - check whether any bluetooth hardware exists > - if it exists, run some daemon unless it has been explicitly disabled > -if it doesn't exist, do not run any software which depends on bluetooth > hardware being present. > - if someone inputs a bluetooth USB device, i.e. hotpluggable device, detect > that this is happening and then start the bluetooth daemon unless another > variable in some file has been set. |