I also have notice this quite often as well. It looks like dbus-daemon
is hogging the CPU system. It must be something to do with wifi or
connectivity. as toogling the wifi on and off will sort out the
problem. You will have to wait that all the wifi list disappears
before you can trigger the wifi on again. This occurs quite often when
you r leaving your wifi.
Thibaut
On Friday, 19 June 2015 07:37:49 BST, Johan Velthuizen wrote:
I have noticed the same problem, but noticed that the whole phone is
responding very slow when this happens.
I have to hard reset the phone to come back to a normal operation again.
Sometimes there is also a delay when pushing the right upper button
to activate the phone, it will take 20 seconds before the phone will
respond.
Met vriendelijke groet,
Johan Velthuizen
Op 19-06-15 om 08:26 schreef Marcin Wójcik:
Hi,
I don't know if this has been reported before, but after installing
OTA-4 to vivid 15.04 r23, I noticed that the keypad to unlock my
phone is unresponsive sometimes. I would press a number, getting no
feedback, thus assuming it didn't register the key press, and I
would try pressing again until the UI would finally respond with a
delay, registering all my inputs and then proceeding to give me an
error that I have entered the incorrect passcode.
At first, it was happening all the time, but later, I noticed that
sometimes it would respond normally without issue. It's not a
massive bug, and I enter my code even though there's no response and
then I wait for the phone to unlock after a delay.
It would be appreciated if time could be found to look into this
issue once other, more pressing bugs are addressed, such as the
alarm issue which was mentioned earlier.
Many thanks, and keep pup the great work. (I am loving the new
browser features)
Regards,
Marcin
