bug ao abrir pastas do Ubuntu 12.04 [RESOLVIDO]

1. bug ao abrir pastas do Ubuntu 12.04 [RESOLVIDO]

Geidson
geidsonc

(usa Ubuntu)

Enviado em 23/06/2012 - 23:44h

Pessoal, instalei o ubuntu 12.04, depois realizei algumas configurações. Mas ao tentar abrir a pasta pessoal, ou outra pasta em Locais simplesmente não abre e os ícones da área de trabalho somem.


  


2. Log do erro

Antonio Thomacelli
tonnytg

(usa Outra)

Enviado em 23/06/2012 - 23:50h

1° Se aparecer algum erro informe ele.

Caso não apareça, por favor abra um terminal e digite:

$ nautilus

Nautilus é o navegador de pastas, ele irá abrir e dar o erro que você disse e logo que der o erro irá aparece a mensagem no terminal talvez lá esteja algo valioso, copie e cole aqui. Caso seja muito grande o log poste no paste.com


3. Re: bug ao abrir pastas do Ubuntu 12.04 [RESOLVIDO]

caroline
carolska

(usa Outra)

Enviado em 21/07/2012 - 13:23h

Estou com o mesmo problema: não consigo abrir nenhuma pasta e, quanto tento, os programas abertos dão uma travada momentânea.

O erro que aparece é "Erro no barramento (imagem do núcleo gravada)", mas não consegui encontrar informações sobre este erro.




4. Re: bug ao abrir pastas do Ubuntu 12.04 [RESOLVIDO]

Antonio Thomacelli
tonnytg

(usa Outra)

Enviado em 23/07/2012 - 21:35h

carolska escreveu:

Estou com o mesmo problema: não consigo abrir nenhuma pasta e, quanto tento, os programas abertos dão uma travada momentânea.

O erro que aparece é "Erro no barramento (imagem do núcleo gravada)", mas não consegui encontrar informações sobre este erro.



Você abriu o nautilus pelo terminal e deu esse erro de barramento ou a mensagem foi direto na tela ?
Aguardo informações para ajudar.




5. mesmo problema

Cesar Felipe Ferreira
cesarscout

(usa Ubuntu)

Enviado em 16/10/2012 - 05:08h

Estou com o mesmo problema e não consegui resolver ainda.
quando passo o comando no terminal como dito aparece o que esta abaixo.

Initializing nautilus-dropbox 0.7.1

** (nautilus:19902): WARNING **: Error calling current_status: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): CRITICAL **: syncdaemon_status_info_get_online: assertion `SYNCDAEMON_IS_STATUS_INFO (sinfo)' failed

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Error calling get_folders: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Could not get syncdaemon's root dir: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (nautilus:19902): WARNING **: Failed calling get_metadata_and_quick_tree_synced: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.







Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts