Nada começa após o login, apenas o fundo é mostrado (Ubuntu 14.04) -- unity campo com gnome campo com login camp askubuntu Relacionado O problema

Nothing starts after login, only background is shown (Ubuntu 14.04)


2
vote

problema

português

(não marque como duplicado, nada ajuda de outras respostas!)

Após o Ubuntu 14.04 Fazer login na tela, se eu logar em Gnome ou Unity, apenas o plano de fundo da área de trabalho aparece. Nada começa. Eu não posso nem executar o terminal através do CTRL + ALT + T.

Eu posso, no entanto, iniciar o console através do Ctrl + Alt + 1.

De lá, tentei começar a união, e funciona apenas parcialmente. Os ícones e barra lateral aparecem quando eu voltar para a área de trabalho do console, mas é muito lento, buggy e inutilizável.

Este é o log de executar a unidade do console (eu corro com "sudo unity", então eu mudo para a área de trabalho e começa, mas é buggy, então eu paro de volta no console):

  compizconfig - Info: Backend     : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile     : unity WARN  2014-09-23 13:30:55 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... ERROR 2014-09-23 13:30:55 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory WARN  2014-09-23 13:30:55 unity <unknown>:0 Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GuO8uIKHKy: Connection refused ERROR 2014-09-23 13:30:56 unityo (appinfo2) <unknown>:0 g_file_monitor_set_rate_limit: assertion 'G_IS_FILE_MONITOR (monitor)' failed ERROR 2014-09-23 13:30:56 unity.launcher.icon.trash TrashLauncherIcon.cpp:66 Could not create file monitor for trash uri: Operation not supported WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unityn_param_values == 4 <unknown>:0 The owner of /home/stanny/.config/ibus/bus is not root! WARN  2014-09-23 13:30:56 nux.inputmethod.ibus InputMethodIBus.cpp:63 Impossible to connect to connect to ibus WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... ERROR 2014-09-23 13:30:56 unityo (appinfo2) <unknown>:0 g_dbus_proxy_new_for_bus: assertion 'g_variant_is_object_path (object_path)' failed WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Session' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.ScreenSaver' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43    

Então milhares destes:

  WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43    

Então isto:

  ERROR 2014-09-23 13:30:57 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'org.gnome.Shell' ERROR 2014-09-23 13:30:57 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'com.canonical.Unity'    

Então muitos desses, novamente:

  WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43    

Então isto:

  WARN  2014-09-23 13:30:57 unity.glib.dbus.proxy GLibDBusProxy.cpp:417 Calling method "CanShutdown" on object path: "/org/gnome/SessionManager" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43 ERROR 2014-09-23 13:30:57 unity.session.gnome GnomeSessionManager.cpp:357 Gnome Session call failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files    

Então os avisos "Falha ao cometer alterações" continuam para a totalidade de ~ 30MB de logfile. Eu finalmente tenho que pará-lo do console.

O que eu tentei até agora:

    .
  1. reinstalando o ubuntu-desktop.
  2. reinstalando o gnomo.
  3. como sugerido aqui , eu tentei habilitar Unity plugin no CCSM, mas também não ajuda. Nem o "sudo dconf reset -f / org / compiz /" de outra resposta.
  4. instalando o fluxbox.

Quando estou instalando o Ubuntu-Destkop e o GNOME, e suas dependências, recebo este erro:

  Unable to autolaunch a dbus daemon without a $DISPLAY for X11    

(eu escrevi isso, então não tenho certeza se é 100% correto.)

A partir destes, apenas instalar o Fluxbox funciona.

Estou escrevendo isso logado FluxBox e funciona sem problemas. No entanto, quando escolho o GNOME ou o Ubuntu da tela Log in, o mesmo problema de nada que começa a persiste.

english

(Don't mark as duplicate, nothing helps from other answers!)

After Ubuntu 14.04 log in screen, whether I log into Gnome or Unity, only desktop background shows up. Nothing starts. I can't even run terminal through ctrl + alt + t.

I can however start the console through ctrl + alt + 1.

From there, I tried to start unity, and it works only partially. The icons and sidebar show up when I switch back to desktop from console, but it's very slow, buggy and unusable.

This is the log from running unity from console (I run it with "sudo unity", then I switch to desktop and it starts, but it's buggy, so I stop it back in console):

compizconfig - Info: Backend     : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile     : unity WARN  2014-09-23 13:30:55 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... ERROR 2014-09-23 13:30:55 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory WARN  2014-09-23 13:30:55 unity <unknown>:0 Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GuO8uIKHKy: Connection refused ERROR 2014-09-23 13:30:56 unityo (appinfo2) <unknown>:0 g_file_monitor_set_rate_limit: assertion 'G_IS_FILE_MONITOR (monitor)' failed ERROR 2014-09-23 13:30:56 unity.launcher.icon.trash TrashLauncherIcon.cpp:66 Could not create file monitor for trash uri: Operation not supported WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unityn_param_values == 4 <unknown>:0 The owner of /home/stanny/.config/ibus/bus is not root! WARN  2014-09-23 13:30:56 nux.inputmethod.ibus InputMethodIBus.cpp:63 Impossible to connect to connect to ibus WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... ERROR 2014-09-23 13:30:56 unityo (appinfo2) <unknown>:0 g_dbus_proxy_new_for_bus: assertion 'g_variant_is_object_path (object_path)' failed WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Session' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:56 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.ScreenSaver' yet as we don't have a connection, waiting for it... WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43 

Then thousands of these:

WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43 

Then this:

ERROR 2014-09-23 13:30:57 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'org.gnome.Shell' ERROR 2014-09-23 13:30:57 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'com.canonical.Unity' 

Then a lot of these, again:

WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43 

Then this:

WARN  2014-09-23 13:30:57 unity.glib.dbus.proxy GLibDBusProxy.cpp:417 Calling method "CanShutdown" on object path: "/org/gnome/SessionManager" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files WARN  2014-09-23 13:30:57 unityinit <unknown>:0 failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=778447ddcfac03e3118fe35c53c14244 --binary-syntax --close-stderr': Child process killed by signal 43 ERROR 2014-09-23 13:30:57 unity.session.gnome GnomeSessionManager.cpp:357 Gnome Session call failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files 

Then the "failed to commit changes" warnings continue for the entirety of ~30MB logfile. I eventually have to stop it from console.

What I've tried so far:

  1. Reinstalling ubuntu-desktop.
  2. Reinstalling gnome.
  3. As suggested here, I've tried enabling unity plugin in ccsm, but it doesn't help either. Neither does the "sudo dconf reset -f /org/compiz/" from another answer.
  4. Installing fluxbox.

When I'm installing ubuntu-destkop and gnome, and their dependencies, I get this error:

Unable to autolaunch a dbus daemon without a $DISPLAY for X11 

(I wrote that down, so I'm not sure if it's 100% correct.)

From these, only installing fluxbox works.

I'm writing this logged in fluxbox and it works without any problems. However, when I choose Gnome or Ubuntu from the log in screen, the same problem of nothing starting up persists.

        
         
         

Lista de respostas


Perguntas relacionadas

1  Automaticamente é desconectado como eu tento fazer login [duplicado]  ( Automatically get logged out as i try to login ) 
. Esta pergunta já tem respostas aqui : ubuntu fica preso em um loop de login ...

1  A tela pisca cinza enquanto eu entro, posso pará-lo?  ( Screen flashes gray as i log in can i stop it ) 
Desde a instalação 11.10 Eu notei que muitas vezes quando eu fizer login na seguinte sequência: Tela de login [hit enter] tela cinza clara (0,5 - 1 seg) ...

1  preso em um loop de login após atualizar drivers  ( Stuck in a login loop after updating drivers ) 
Tudo bem, então eu atualizei meus drivers da AMD para a última versão do Catalyst, depois de quase duas horas de problemas atualizando os drivers que de algum...

0  Permissão negada (publickey) depois de toda vez sendo desconectado  ( Permission denied publickey after every time being disconnected ) 
Após ser desconectado do servidor (Ubuntu 18.04.1) eu não posso fazer login mais usando a chave pública. Eu tenho 2 contas que podem executar sudo. Uma cont...

524  Ubuntu fica preso em um loop de login  ( Ubuntu gets stuck in a login loop ) 
Meu Ubuntu está preso em um loop de login ao tentar entrar na minha área de trabalho. Quando eu fizer o login, a tela fica em preto e logo depois que a tela d...

12  Desbloquear o keyring solicita três vezes em vez de uma vez  ( Unlock keyring prompts three times instead of one time ) 
Quando eu tiver "Login automático" ativado, a caixa "Desbloquear a GNOME KINGING" pede minha senha. Mas isso acontece três vezes. Existem três caixas me pedin...

2  Senha incorreta para sudo e no bloqueio de tela, mas correto durante o login logo após a reinicialização  ( Incorrect password for sudo and on screen lock but correct while logging in rig ) 
Eu tenho essa estranha questão que ocorre depois que eu atualizei o sistema operacional de 16 a 18. No começo, não me deixaria entrar, dizendo que a senha e...

17  Por que preciso correr "/ bin / bash --login"  ( Why do i need to run bin bash login ) 
Acabei de configurar um novo servidor Ubuntu 13.10 com Ruby 2.1.1 instalado através de ABCDEFGHIJKLMNABCDEFGHIJKLMN1 . O problema é que, sempre que eu mude...

1  Tela preta e loop de login após atualizações Ubuntu 14.04 lts  ( Black screen and login loop after updates ubuntu 14 04 lts ) 
Eu tenho usado 14,04 lts por um ano agora, perfeição! Então esta semana eu tive novas atualizações, para onde uma delas tinha um erro. Não consigo me lembrar ...

3  Como escolher em que exibir a caixa de login aparecerá?  ( How to choose in which display the login box will appear ) 
Eu tenho dois monitores onde a área de trabalho é estendida. Eles estão conectados a uma placa de vídeo AMD / ATI através de cabos DVI. Quando eu inicializo o...




© 2022 pergunte.org All Rights Reserved. Casa de perguntas e respostas todos os direitos reservados


Licensed under cc by-sa 3.0 with attribution required.