Good to hear that you can confirm the next kernel release can fix the suspend/resume problem.
And for the "leave active bluetooth connection while putting computer into suspend" problem, I think it's a different problem and different bt chip with this issue, so it's better to file a new bug for it to have a further and better discussion.
BTW, you can just copy/paste the following script and put it in /etc/pm/sleep.d and give it executable permission if you don't want to start the bluetooth daemon every time you resume from suspend.
--------- 8< --------------------------
#!/bin/sh
PATH=/sbin:/usr/sbin:/bin:/usr/bin
case "${1}" in suspend|hibernate)
;; resume|thaw) (sleep 3 ; /usr/sbin/service bluetooth stop ; sleep 3 ; /usr/sbin/service bluetooth start)&
;;
esac
--------- >8 --------------------------
Tomasz,
Good to hear that you can confirm the next kernel release can fix the suspend/resume problem.
And for the "leave active bluetooth connection while putting computer into suspend" problem, I think it's a different problem and different bt chip with this issue, so it's better to file a new bug for it to have a further and better discussion.
BTW, you can just copy/paste the following script and put it in /etc/pm/sleep.d and give it executable permission if you don't want to start the bluetooth daemon every time you resume from suspend.
--------- 8< ------- ------- ------- -----
#!/bin/sh
PATH=/sbin: /usr/sbin: /bin:/usr/ bin
case "${1}" in
suspend| hibernate)
resume| thaw)
(sleep 3 ; /usr/sbin/service bluetooth stop ; sleep 3 ; /usr/sbin/service bluetooth start)& ------- ------- -----
;;
;;
esac
--------- >8 -------