Created attachment 6693 [details]
trimmed .xsession-errors .tar.gz

Same 306 thousand lines. This time i looked at an (old) wall clock, and it seems it took almost 3 minutes.  Strange time.  Here is a downtrimmed .xsession-errors.

I note the many lines ends with a message about negative time.
Right before that there start to frequently coming many lines of

Error response:  "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." 

...between other messages, and some programs (dolphin, kwrite) take a minute or so to respond to a mouse click.  No CPU load.

This is probably another issue than the bluedevil one, but which that actually delays the screen from wakening i can not tell.  .xsession-errors really sould use timestamps...

Upgrading kernel from 3.19.8-desktop-1.mga5 to 3.19.8-desktop-2.mga5 the messages about bluedevil are still there, but for the resumes i did this fare i have not seen the messages "Did not receive a reply." etc , and no black screen.
However with this kernel i see bug 15727 .

So maybe this bug (about bluedevil) have nothing to to with black screen, and instead it is whatever cause the "Did not receive a reply." messages. Whatever they were.  I will tell if i see them again in latest mageia 5 kernel. 

But the massive bluedevil messages are stil not good to have so i leave the bug open for that.

I plan an update to bluedevil 2.1.1 (2.1 -> 2.1.1) after Mageia 5 release.

bluedevil 2.1.1 is available in cauldron and mga 5 core/updates_testing.

Suggested advisory:
Updated libbluedevil and bluedevil packages fix errors on resume from suspend

The KDE's bluetooth stack, bluedevil, sometimes has problems on resume from suspend, and can flood .xsession-errors with many consecutive lines of 'Error response:  "The name org.kde.bluedevilmonolithic was not provided by any .service files" ' .

These issues are fixed with this update.


References:
https://bugs.mageia.org/show_bug.cgi?id=16072
https://bugs.kde.org/show_bug.cgi?id=343682
https://bugs.kde.org/show_bug.cgi?id=346329

src.rpm:
libbluedevil-2.1-1.1.mga5.src.rpm
bluedevil-2.1.1-1.mga5.src.rpm

packages i586:
libbluedevil2-2.1-1.1.mga5.i586.rpm
libbluedevil-devel-2.1-1.1.mga5.i586.rpm
bluedevil-2.1.1-1.mga5.i586.rpm

packages x86_64:
lib64bluedevil2-2.1-1.1.mga5.x86_64.rpm
libbluedevil-devel-2.1-1.1.mga5.x86_64.rpm
bluedevil-2.1.1-1.mga5.x86_64.rpm

CC: (none) => lmenut
Version: Cauldron => 5
Assignee: lmenut => qa-bugs
Whiteboard: MGA5TOO => (none)

Updated my x86_64 mga5 machine that had sometimes problems resuming.

* Problem seem to be fixed * 
- i only get one line of that message 
 "The name org.kde.bluedevilmonolithic was not provided by any .service files" 

I also updated an i586 machine but it did not have a problem before.
Both machines seem to work without hassles.
But i have never used bluetooth for anything before or now.
Tested Bluetooth now like this:

$ bluetoothctl
[NEW] Controller 00:1E:4C:F9:DF:04 bamse.tribun [default]
[NEW] Device 64:6C:B2:B0:D2:28 Kajsa Leijström (SM-G3
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# 

It is visible from an android phone but i do not know how to use it.

Advisory committed to svn.

Morgan, are you saying it's ok, or not ok? I don't have any bluetooth devices
to test with.

CC: (none) => davidwhodgins
Whiteboard: (none) => advisory

I also dont have any bluetooth devices to test bluetooth with.

But now the system resumes from suspend properly.

So the *reported bug is fixed*
BUT *i can not say anything on functionality or if there is any regression*

From the sidelines to Morgan.

Comment 5
> Updated my x86_64 mga5 machine that had sometimes problems resuming.
> * Problem seem to be fixed *

> I also updated an i586 machine but it did not have a problem before.
> Both machines seem to work without hassles.
One imagines that the i586 machine is also Mageia 5 (the bug/update only applies to that).

Comment 7
> But now the system resumes from suspend properly.
> So the *reported bug is fixed*
It looks as if you can certainly MGA5-64-OK this on the whiteboard; and probably  MGA5-32-OK unless someone else who had the problem on x32 can confirm better.

CC: (none) => lewyssmith

Yes the machines tested are mga5 - sorry for not being clear - and are still working good.
So the bug is fixed, but IMO we need someone who are using bluetooth to confirm there is no regression on the functionality it provides.

I will have a look at this tomorrow.  I have an old Dell XPS laptop with built-in Bluetooth which currently runs mga4 64bit.  It was intended as an updates testing platform for mga4 but can be upgraded to mga5 temporarily for testing.  No install before tomorrow.  And shall try to get it working either with my Bose Soundlink or my hearing aid adapter.

CC: (none) => tarazed25

Mageia 5 : x86_64 laptop : kernel 3.19.8-desktop-3.mga5
nvidia 8700M GT : nvidia 340.76
Sound device : Bose Soundlink Mini

Sound not working with mplayer but was able to play Handel with xine or vlc.
Before the update I could not reproduce the fault with Bluedevil installed and bluetooth enabled.  Installed the updated files and ran the test from comment 5.

[root@canopus ~]# bluetoothctl
[NEW] Controller 00:1F:3A:E2:A5:C4 canopus [default]
[NEW] Device 00:0C:8A:9D:21:C3 Bose Mini SoundLink
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1F:3A:E2:A5:C4 Discovering: yes
[bluetooth]# exit
[DEL] Controller 00:1F:3A:E2:A5:C4 canopus [default]

Wireless speaker available immediately on switch on and was able to play a music track through it so it looks like there is no regression.

Although I could not reproduce the original fault the fixed package seems to work so I shall OK this for 64-bit.  Morgan's test should justify has_procedure.

Whiteboard: advisory => advisory MGA5-64-OK has_procedure

Validating. Please push to 5 updates

Thanks

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0114.html

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