Will this be fixed any time soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025
Title:
Fails running In chroot with "ENGINE_by_id failed (crypto failure)"
To manage notifications about
I can confirm that the following debian packages resolve the issue:
bind9_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
bind9utils_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libbind9-140_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libdns162_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libgssapi-krb5-2_1.15-1+deb9u1_amd64.deb
Per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820974#86 , Debian
has fixed this. Can we please import this package to get this resolved?
While this may be thought of as a non-standard configuration this is a
critical security issue that is now solved upstream. Could we please get
this
Here's my package listing
** Attachment added: DPKG output
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1390628/+attachment/4448761/+files/dpkg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I purged gnome-settings-daemon, which also purged gnome-control-center.
This is how I get my mouse back now:
1. Log in
2. Open terminal
3. sleep 85 gsettings set org.gnome.settings-daemon.plugins.cursor active
false
4. Log out
5. Verify mouse appears now (movement on login page)
6. Log in
7.
I'm running on an Intel NUC NUC5i7RYH with boot disk as SM-951 NVMe
(MZVPV512HDGL) and secondary disk Samsung Evo 850.
I fresh installed 14.04.3 LTS and experience this problem.
Solutions, such as the following, don't predictably work for me:
* exec unity-settings-daemon
* sudo gsettings set
