This is actually a big problem for two reasons:
(1) The user does not get the correct feedback to the problem: Instead of a
notice that the certificate not trusted, he/she is just asked again and again
and again for the correct username and password.
(2) Encouraging people to trust in central ce
just coming in: Google found french office spying with CA signed
intermediate certificate:
https://code.google.com/p/chromium/issues/detail?id=326787 and
http://www.heise.de/newsticker/meldung/Google-erwischt-franzoesische-
Behoerde-beim-Schnueffeln-2062479.html
So please stop requesting CA signed
The same always happens to me when the system does not register key-
strokes from my Apple bluetooth keyboard after a system restart.
Keyboard appears as connected in the bluetooth setting, but no
keystrokes come through. syslog fills with these errors.
Setup: MS bluetooth mouse and Apple Wireless
Since yesterday I am also massively affected by this issue (Ubuntu
19.04, Dell Latitude 7280). The mouse buttons 'stop working' every few
minutes, making working for me very tiresome.
The only gnome extensions I have active are the frippery move clock,
system monitor and desktop icons.
Shortly be
Ok, I solved the problem in my case. Given it seemed to be a
communication problem I go the idea it could be ownership of sockets. I
found various folders in my home directory were not owned by my local
user and/or were not readable. Root owned .dbus and .gvfs, below .local
were files/folders owned
5 matches
Mail list logo
