Допоможіть налаштувати Evolution ?

[isydor]

Допоможіть налаштувати Evolution, якщо я правильно розумію, цей ресурс може збирати листи зі всіх скриньок користувача. Саме найбільше що мені вдавалось - запустити щоденник.

[Re.]

Які саме скриньки і що саме не виходить?

[isydor]

Які саме скриньки і що саме не виходить?

meta.ua
Щось я таки від балди налаштував, бо щоденником можу користуватись.

Вкладка Отримання пошти
Тип сервера ?
Сервер ?
Вкладка Параметри отримання Що конче потрібно активувати?
Вкладка Відправлення пошти
Тип сервера ?
Сервер ? Мабуть такі як і Вкладка Отримання пошти?

[Ign1111]

Які саме скриньки і що саме не виходить?

meta.ua
Щось я таки від балди налаштував, бо щоденником можу користуватись.

Основне питання: а ви взагалі вмієте налаштовувати поштові клієнти? А щоденник в будь якому випадку буде працювати.

[Re.]

Вам треба ввести дані про POP. У мене все на працює, однак це i.ua під thunderbird. Тут інструкція зі знімками:
http://www.help.meta.ua/ua/mail/mail_client/evol/

[isydor]

Вам треба ввести дані про POP. У мене все на працює, однак це i.ua під thunderbird. Тут інструкція зі знімками:
http://www.help.meta.ua/ua/mail/mail_client/evol/

Помилка GConf: Помилка при з'єднанні з сервером конфігурації. Можливо це пов'язано з тим, що Вам необхідно увімкнути підтримку мережі TCP/IP для ORBit, чи лишились старі блокування NFS через збій в системі. Для отримання інформації дивіться http://www.gnome.org/projects/gconf/ . (Докладніше -  1: Помилка при встановленні зв'язку з сеансом: 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.).

Як це врегулювати, щоб не наробити дурниць?

[Re.]

Який дистрибутив?
Спробуйте в консолі ввести:

Код: [Вибрати]

LANG=en_US evolutionта одержати цю помилку англійською, а потім шукати в ґуґлі.

[isydor]

Який дистрибутив?
Спробуйте в консолі ввести:

Код: [Вибрати]

LANG=en_US evolutionта одержати цю помилку англійською, а потім шукати в ґуґлі.

OpenSuse 11.3
Ввів, одержав, але мій побутовий рівень знання англійської унеможливлює цей шлях, і ваш час не хочу гаяти так непродуктивно. Декілька слів, щоб ви краще уявляли ситуацію.
1) Ще до того, як ви надали чітку зрозумілу покрокову інструкцію. я потенційно міг щось порушити.
2)Система(OpenSuse) для мене нова і малознайома. Наразі навчився лиш оновити після встановлення (правильно чи ні не знаю, але запускається кожен раз). Можливо питання не в  evolution, а початкових налаштування самої системи.
Отож спробую запакувати  evolution і знов встановити.
Якщо це не допоможе, без проблем перевстановлю систему, бо наразі вона система-адміністратор (не знаю. як грамотно назвати) і тоді можна подивитись буде така помилка чи ні.

[Re.]

Тоді просто напишіть вивід. Схоже, що щось недовстановлено.

[isydor]

Тоді просто напишіть вивід. Схоже, що щось недовстановлено.

Досить великий текст, а якою кнопкою його вставити у спойлер не знаю. Вивід? Це ж відповідь з терміналу?

[Re.]

Спойлер? Можна не для просунутих?

[isydor]

Спойлер? Можна не для просунутих?

Великий текст ховається за словом, скажімо, тут, ось.... а коли натиснути на це слово - з’являється прихований текст. У нас на Linux.org.ua точно є.

[Re.]

Читайте довідку. Або використовуйте тег code.

[isydor]

Тоді просто напишіть вивід. Схоже, що щось недовстановлено.

Код: [Вибрати]

  hcppc0:/home/nemoos # LANG=en_US evolution
** Message: couldn't connect to dbus session bus: 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.
(evolution:13612): e-data-server-DEBUG: Loading categories from "/root/.evolution/categories.xml"
(evolution:13612): e-data-server-DEBUG: Loaded 22 categories

** (evolution:13612): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed

** (evolution:13612): WARNING **: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)

** (evolution:13612): WARNING **: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
*** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): GConf-CRITICAL **: gconf_client_get_entry: assertion `err == NULL || *err == NULL' failed

(evolution:13612): e-data-server-WARNING **: Could not load account lock settings: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)

(evolution:13612): e-utils-WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)

(evolution:13612): evolution-shell-CRITICAL **: e_shell_backend_add_activity: assertion `E_IS_SHELL_BACKEND (shell_backend)' failed^A^AЯкщо швидко прочитати, то я ще зможу його видалити.

[Re.]

Спробуйте Dbus запустити, якщо він не запущений. Або спробуйте виконати це ж, але з-під адміністратора (root), якщо там буде все гаразд, то проблема з правами доступу.