O sistema totalmente criptografado inicializa com o login do Terminal em vez da GUI

1

Quando eu ligo o computador, porque eu o tenho criptografado, ele sempre pergunta primeiro pela minha senha na GUI. Eu entro na frase, então ainda na GUI normalmente pede minha senha, e vou para a área de trabalho da GUI.

Agora, por algum motivo, ele começou a ir direto para o Terminal depois que eu digitei a frase secreta, com o prompt:

Ubuntu 14.04.3 LTS thomas-All-Series tty1
thomas-All-series login:

Eu não sei porque isso começou.

Após o login como usuário (não raiz), as seguintes informações são exibidas:

Last login: Sat Jan 9 18:23:13 CST 2016 on tty1
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-74-generic x86_64)

*Documentation: https://helpubuntu.com
find: '/var/lib/apt//lists/': No such file or directory
/usr/lib/update-notifier/update-motd-updates-available: 39: /usr/lib/update-notifier/update-motd-updates-available: cannot create /var/lib/update-notifier/updates available: Directory nonexistent
cat: /var/lib/update-notifier/updates available: No such file or directory
run-parts: /etc/update-motd.d/90-updates-available exited with return code 1
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd: 39: /usr/lib/ubuntu-release-upgrader/release-upgrade-motd: cannot create /var/lib/ubuntu-release-upgrader/release-upgrade-available: Directory nonexistent
/usr/lib/update-notifier/fsck-at-reboot: 33: /usr/lib/update-notifier/update-motd-fsck-at-reboot: cannot create /var/lib/update-notifier/fsck-at-reboot: Directory nonexistent
cat: /var/lib/update-notifier/fsck-at-reboot: No such file or directory
run-parts: /etc/update-motd.d/98-fsck-at-reboot exited with return code 1
thomas@thomas-All-Series:~$ _  

Eu tentei startx $(which unity) no meu nome de usuário e no root para ver se havia uma diferença, e esta é a leitura que eu tenho em ambos:

(compiz:1347): dconf-WARNING **: failed to commit changes to dconf:
Cannot spawn a message bus without a machine-id:
Unable to load /var/lib/dbus/machine-id or /etc/machine-id:
Failed to open file '/var/lib/dbus/machine-id': No such file or directory

A mensagem acima é repetida três vezes, seguida por:

WARN 2016-01-13 20:06:08 unity.glib.dbus.server GlibDBusServer.cpp:579 Can't registe
r object 'org.gnome.Shell' yet as we don't have a connection, waiting for it...
ERROR 2016-01-13 20:06:09 unity.debug.interface DebugBusInterface.ccp:216 Unable to
load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object
file: No such file or directory
process 1347: D-Bus library appears to be incorrectly set up: failed to read machine
uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
ERROR 2016-01-13 20:06:09 unity.launcher.entry.remote.mode1 LauncherEntryRemoteMode1
.cpp:50 Unable to connect to session bus: Cannot spawn a message bus without a machi
ne-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open fi
le '/var/lib/dbus/machine-id': No such file or directory
CRIT 2016-01-13 20:06:09 unity <unknown>:0 Unable to get org.ayatana.bamf matcher: 
Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machin
e-id or /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such fil
e or directory
Trace/breakpoint trap (core dumped)
xinit: connection to X server lost

waiting for X server to shut down (EE) Server terminated successfully (0). Closing l
og file.
    
por Push 08.01.2016 / 17:53

0 respostas