Some excerpts from dmesg

Bluetooth: Core ver 2.15
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11




btusb 2-1:1.0: no reset_resume for driver btusb?
btusb 2-1:1.1: no reset_resume for driver btusb?

Shows original initialisation and problem after suspending.

Off topic: testing change of email address.

The icon is back but it still needs replugging after suspend to ram.

I think the icon must have been due to the gnome-settings-daemon bug which is now fixed.

@ Claire

Forget what I asked last week, it is silly not to touch this bug.


I do not really understand what you mean by replugging your icon.

@ manuel

Do you use BT in your Gnome stable? if so, do you have any issues

CC: (none) => dmorganec, manuel, marja11
Summary: No Bluetooth Icon / Functionality & Suspend problem => Functionality & Suspend problem witn gnome-bluetooth
Source RPM: (none) => gnome-bluetooth-2.32.0-2.mga1.src.rpm

Ok Marja no problem, it'd be good to see it fixed one day :)

It isn't replugging the icon, it is the adapter that needs removing and then plugging back in again.

(In reply to comment #5)

> It isn't replugging the icon, it is the adapter that needs removing and then
> plugging back in again.

That makes a lot more sense, thx :D

What happens when you reboot your system? Do you then need to replug the adapter, too?

No, when it's first booted the adapter is OK. It stays OK until after suspending.

Well, you're not alone, when I google "resume from suspend" bluetooth, an amazing lot of links are given about failing BT after resume :/

@ pterjan

Do you mind looking into this? Is this a pm-utils or suspend (the suspend package) issue?

CC: (none) => pterjan
Source RPM: gnome-bluetooth-2.32.0-2.mga1.src.rpm => gnome-bluetooth-2.32.0-2.mga1.src.rpm, pm-utils, suspend

@ Claire

I'm afraid we have to work it out by ourselves :)

Can you reproduce this and then run
dmesg > dmesg.txt
and attach that file here

and can you also copy the last part of /var/log/messages and attach that as well?

Thanks :)

Created attachment 1442 [details]
dmesg.txt

Created attachment 1443 [details]
messages.txt

shows end of suspend and then resume.


There is an error related to dbus and also btusb which is the kernel module so this should probably have been filed against the kernel or dbus instead of combining it with gnome-bluetooth, which is probably a red herring.

(In reply to comment #11)
> Created attachment 1443 [details]
> messages.txt
> 
> shows end of suspend and then resume.
> 
> 
> There is an error related to dbus and also btusb which is the kernel module so
> this should probably have been filed against the kernel or dbus instead of
> combining it with gnome-bluetooth, which is probably a red herring.

Yes, first this message:
Jan 27 14:12:34 localhost kernel: btusb 2-1:1.0: no reset_resume for driver btusb?

and then this one:
Jan 27 14:12:34 localhost dbus-daemon: [system] Rejected send message, 4 matched rules; type="error", sender=":1.73" (uid=500 pid=5075 comm="bluetooth-applet) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply=0 destination=":1.8" (uid=0 pid=1069 comm="/usr/sbin/bluetoothd))

I'll assign to the kernel, because we don't have a dbus maintainer, and anyway, the kernel message came first :)

Assigning to maintainer and cc'ing one more committer of dbus

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb
Source RPM: gnome-bluetooth-2.32.0-2.mga1.src.rpm, pm-utils, suspend => kernel

3-monthly ping

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 
Mageia version prior to Mageia 1'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 Mageia 1 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 Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

gnome 2 is unsupported now anyway

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX