Не запускается KDE4 и firefox от доменного пользователя. Проблема с DBus

[Yamah]

Обновился в пятницу. В понедельник было все нормально.
Обновился в понедельник. ПК не перезагружал. Во вторник, кроме звука и монтирование флэшек тоже нормально было.

Сегодня перезагружаю ПК, пытаюсь зайти от доменного пользователя ка обычно. После бутсплеша KDE на 1-15 секунда появляется меню SimpleWelcom на весь экран. После этого мигает какое-то окно и я остаюсь черным экраном. Помогает только Ctrl+Alt+Backspace.

Логинюсь в консоли под тем же доменным пользователем. Все ОК. Запускаю

Код: Выделить всё

xinit -- :1

и уже в терминале в X-ах запускаю Firefox, получаю.

Код: Выделить всё

firefox
process 22804: arguments to dbus_connection_set_exit_on_disconnect() were incorrect, assertion "connection != NULL" failed in file /builddir/build/BUILD/dbus-1.8.4/dbus/dbus-connection.c line 3121.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Redirecting call to abort() to mozalloc_abort

Segmentation fault (core dumped)

Со startkde результат такой же. (Из заметного Вижу, что Akonady не может стартовать). После прерывания всего процесса с зависшим startkde, в консоль начинает циклически выводиться

Код: Выделить всё

Network

Выхожу из иксов. Логинюсь от локального пользователя. В терминале переключаю пользователя на доменного и получаю.

Код: Выделить всё

su - MyDomenUser
Пароль: 
Error connecting: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS)

В домене авторизация проходит через Керберос.
Так как авторизоваться от доменного пользователя я могу, пользователи и группы из домена отображаются нормально, а не численно, то проблема где-то уже после авторизации.

Как это исправить?

Обновлялся только из Update.
В syslog:

Код: Выделить всё

Jul 20 12:12:42 admin-pc acpid: 1 client rule loaded
Jul 20 12:12:54 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:54 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:55 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] main.c: Module load failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:12:55 admin-pc pulseaudio[6599]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:12:56 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:56 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:57 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:57 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:57 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:57 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:12:58 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:12:58 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:02 admin-pc systemd-coredump[6637]: Coredump of 6614 (plasma-desktop) is larger than configured processing limit, refusing.
Jul 20 12:13:04 admin-pc systemd-coredump[6637]: Process 6614 (plasma-desktop) of user 65549 dumped core.
Jul 20 12:13:05 admin-pc kernel: [ 7691.565482] plasma-desktop[6636]: segfault at 48 ip 00007efc51cbde71 sp 00007ffd0a8bfe90 error 4 in libQtDBus.so.4.8.7[7efc51c91000+70000]
Jul 20 12:13:07 admin-pc mdkapplet[6707]: ### Program is starting ###
Jul 20 12:13:07 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:08 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:08 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:08 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:08 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc /hp-systray: hp-systray[6692]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc mdkapplet[6707]: running: ionice -p 6707 -n7
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6713]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: failed to bind to LDAP server ldap://mydomen.ru: Can't contact LDAP server
Jul 20 12:13:11 admin-pc dbus[4088]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6896]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6896]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6887]: [pulseaudio] main.c: Не удалось запустить демон.

В User.Log падает:

Код: Выделить всё

Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] main.c: Module load failed.
Jul 20 12:12:55 admin-pc pulseaudio[6602]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:12:55 admin-pc pulseaudio[6599]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:08 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.                                                                                                              
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.                                                                                                              
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.                                                                                                              
Jul 20 12:13:11 admin-pc /hp-systray: hp-systray[6692]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.                                                                                                              
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6727]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6713]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6746]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6736]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6748]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6715]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:11 admin-pc pulseaudio[6784]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:11 admin-pc pulseaudio[6764]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:14 admin-pc pulseaudio[6892]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:14 admin-pc pulseaudio[6888]: [pulseaudio] main.c: Не удалось запустить демон.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] core-util.c: Failed to connect to system 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] module.c: Failed to load module "module-bluez5-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: 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.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] module.c: Failed to load module "module-bluez4-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] main.c: Module load failed.
Jul 20 12:13:14 admin-pc pulseaudio[6896]: [pulseaudio] main.c: Не удалось инициализировать демон.
Jul 20 12:13:14 admin-pc pulseaudio[6887]: [pulseaudio] main.c: Не удалось запустить демон.

[keleg]

Настройки KDE удалить?

[Yamah]

Настройки KDE удалить?

Первое, что попробовал сделать.
Вычистил все конфиги.
Бесполезно.

Обновил первый пост. Добавил логи.

[keleg]

А что прилетало в обновлениях не помните? Я совсем ничего серьезного не помню в районе понедельника, разве что samba с исправлением безопасности.

[Yamah]

А что прилетало в обновлениях не помните? Я совсем ничего серьезного не помню в районе понедельника, разве что samba с исправлением безопасности.

Разница в установленных пакетах на пятницу и сегодня.

Код: Выделить всё

ls -l /var/log | grep rpmpkgs | grep -v "gz"
-rw-r--r--  1 root    root              284551 июл 20 09:51 rpmpkgs
-rw-r--r--  1 root    root              279709 июл 15 04:02 rpmpkgs.1
diff rpmpkgs.1 rpmpkgs
104c104
< chromium-browser-pepper-flash-22.0.0.192-1-rosa2014.1.x86_64
---
> chromium-browser-pepper-flash-22.0.0.209-1-rosa2014.1.x86_64
107c107
< chromium-widevinecdm-plugin-22.0.0.192-1-rosa2014.1.x86_64
---
> chromium-widevinecdm-plugin-22.0.0.209-1-rosa2014.1.x86_64
155a156
> cyrus-sasl-2.1.25-9-rosa2014.1.x86_64
229a231
> f2fs-tools-1.4.0-2-rosa2014.1.x86_64
235c237
< file-5.27-1-rosa2014.1.x86_64
---
> file-5.28-1-rosa2014.1.x86_64
244c246
< flash-player-plugin-11.2.202.626-1-rosa2014.1.x86_64
---
> flash-player-plugin-11.2.202.632-1-rosa2014.1.x86_64
305a308
> gio2.0-32-2.44.1-1-rosa2014.1.i586
341c344
< gparted-0.26.0-1-rosa2014.1.x86_64
---
> gparted-0.26.1-1-rosa2014.1.x86_64
347c350
< granite-0.2.3-1-rosa2014.1.x86_64
---
> granite-0.3.1-1-rosa2014.1.x86_64
353,354c356,357
< grub2-2.00-78-rosa2014.1.x86_64
< grub2-efi-2.00-78-rosa2014.1.x86_64
---
> grub2-2.00-79-rosa2014.1.x86_64
> grub2-efi-2.00-79-rosa2014.1.x86_64
452a456
> heimdal-libs-1.5.3-9-rosa2014.1.x86_64
513c517
< kamoso-2.0.2-7.20140902.4-rosa2014.1.x86_64
---
> kamoso-2.0.2-7.20140902.5-rosa2014.1.x86_64
561c565
< kde5-l10n-ru-16.04.2-2-rosa2014.1.noarch
---
> kde5-l10n-ru-16.04.3-1-rosa2014.1.noarch
953c957
< lib64dcerpc0-4.3.10-1-rosa2014.1.x86_64
---
> lib64dcerpc0-4.3.11-1-rosa2014.1.x86_64
1014a1019
> lib64f2fs0-1.4.0-2-rosa2014.1.x86_64
1088c1093
< lib64gensec0-4.3.10-1-rosa2014.1.x86_64
---
> lib64gensec0-4.3.11-1-rosa2014.1.x86_64
1156d1160
< lib64granite1-0.2.3-1-rosa2014.1.x86_64
1584,1585c1588,1589
< lib64magic1-5.27-1-rosa2014.1.x86_64
< lib64magic-devel-5.27-1-rosa2014.1.x86_64
---
> lib64magic1-5.28-1-rosa2014.1.x86_64
> lib64magic-devel-5.28-1-rosa2014.1.x86_64
1588c1592
< lib64MagickWand6.Q16_2-6.9.3.7-1-rosa2014.1.x86_64
---
> lib64MagickWand6.Q16_2-6.9.4.9-1-rosa2014.1.x86_64
1621c1625
< lib64molletnetwork5_5-16.04.2-1-rosa2014.1.x86_64
---
> lib64molletnetwork5_5-16.04.3-1-rosa2014.1.x86_64
1654c1658
< lib64ndr0-4.3.10-1-rosa2014.1.x86_64
---
> lib64ndr0-4.3.11-1-rosa2014.1.x86_64
1662c1666
< lib64netapi0-4.3.10-1-rosa2014.1.x86_64
---
> lib64netapi0-4.3.11-1-rosa2014.1.x86_64
1675c1679
< lib64nm0-1.2.2-3-rosa2014.1.x86_64
---
> lib64nm0-1.2.2-5-rosa2014.1.x86_64
1677,1678c1681,1682
< lib64nm-glib4-1.2.2-3-rosa2014.1.x86_64
< lib64nm-glib-vpn1-1.2.2-3-rosa2014.1.x86_64
---
> lib64nm-glib4-1.2.2-5-rosa2014.1.x86_64
> lib64nm-glib-vpn1-1.2.2-5-rosa2014.1.x86_64
1680c1684
< lib64nm-util2-1.2.2-3-rosa2014.1.x86_64
---
> lib64nm-util2-1.2.2-5-rosa2014.1.x86_64
1693c1697
< lib64nsswins2-4.3.10-1-rosa2014.1.x86_64
---
> lib64nsswins2-4.3.11-1-rosa2014.1.x86_64
1759,1767c1763,1771
< lib64pango1.0_0-1.36.8-1-rosa2014.1.x86_64
< lib64pango1.0-devel-1.36.8-1-rosa2014.1.x86_64
< lib64pangocairo1.0_0-1.36.8-1-rosa2014.1.x86_64
< lib64pangocairo1.0-devel-1.36.8-1-rosa2014.1.x86_64
< lib64pangocairo-gir1.0-1.36.8-1-rosa2014.1.x86_64
< lib64pangoft2_1.0_0-1.36.8-1-rosa2014.1.x86_64
< lib64pangoft2_1.0-devel-1.36.8-1-rosa2014.1.x86_64
< lib64pangoft2-gir1.0-1.36.8-1-rosa2014.1.x86_64
< lib64pango-gir1.0-1.36.8-1-rosa2014.1.x86_64
---
> lib64pango1.0_0-1.36.8-2-rosa2014.1.x86_64
> lib64pango1.0-devel-1.36.8-2-rosa2014.1.x86_64
> lib64pangocairo1.0_0-1.36.8-2-rosa2014.1.x86_64
> lib64pangocairo1.0-devel-1.36.8-2-rosa2014.1.x86_64
> lib64pangocairo-gir1.0-1.36.8-2-rosa2014.1.x86_64
> lib64pangoft2_1.0_0-1.36.8-2-rosa2014.1.x86_64
> lib64pangoft2_1.0-devel-1.36.8-2-rosa2014.1.x86_64
> lib64pangoft2-gir1.0-1.36.8-2-rosa2014.1.x86_64
> lib64pango-gir1.0-1.36.8-2-rosa2014.1.x86_64
1769c1773
< lib64pango-modules1.0-1.36.8-1-rosa2014.1.x86_64
---
> lib64pango-modules1.0-1.36.8-2-rosa2014.1.x86_64
1771c1775
< lib64pangoxft1.0_0-1.36.8-1-rosa2014.1.x86_64
---
> lib64pangoxft1.0_0-1.36.8-2-rosa2014.1.x86_64
2066c2070
< lib64registry0-4.3.10-1-rosa2014.1.x86_64
---
> lib64registry0-4.3.11-1-rosa2014.1.x86_64
2077,2083c2081,2087
< lib64samba-credentials0-4.3.10-1-rosa2014.1.x86_64
< lib64samba-hostconfig0-4.3.10-1-rosa2014.1.x86_64
< lib64samba-passdb0-4.3.10-1-rosa2014.1.x86_64
< lib64samba-policy0-4.3.10-1-rosa2014.1.x86_64
< lib64samba-server0-4.3.10-1-rosa2014.1.x86_64
< lib64samba-util0-4.3.10-1-rosa2014.1.x86_64
< lib64samdb0-4.3.10-1-rosa2014.1.x86_64
---
> lib64samba-credentials0-4.3.11-1-rosa2014.1.x86_64
> lib64samba-hostconfig0-4.3.11-1-rosa2014.1.x86_64
> lib64samba-passdb0-4.3.11-1-rosa2014.1.x86_64
> lib64samba-policy0-4.3.11-1-rosa2014.1.x86_64
> lib64samba-server0-4.3.11-1-rosa2014.1.x86_64
> lib64samba-util0-4.3.11-1-rosa2014.1.x86_64
> lib64samdb0-4.3.11-1-rosa2014.1.x86_64
2113,2115c2117,2119
< lib64smbclient0-4.3.10-1-rosa2014.1.x86_64
< lib64smbconf0-4.3.10-1-rosa2014.1.x86_64
< lib64smbldap0-4.3.10-1-rosa2014.1.x86_64
---
> lib64smbclient0-4.3.11-1-rosa2014.1.x86_64
> lib64smbconf0-4.3.11-1-rosa2014.1.x86_64
> lib64smbldap0-4.3.11-1-rosa2014.1.x86_64
2185c2189
< lib64tevent-util0-4.3.10-1-rosa2014.1.x86_64
---
> lib64tevent-util0-4.3.11-1-rosa2014.1.x86_64
2216a2221,2223
> lib64usb1.0_0-1.0.18-3-rosa2014.1.x86_64
> lib64usb1.0-devel-1.0.18-3-rosa2014.1.x86_64
> lib64usb1.0-static-devel-1.0.18-3-rosa2014.1.x86_64
2221,2223d2227
< lib64usbx1.0_0-1.0.18-1-rosa2014.1.x86_64
< lib64usbx1.0-devel-1.0.18-1-rosa2014.1.x86_64
< lib64usbx1.0-static-devel-1.0.18-1-rosa2014.1.x86_64
2260c2264
< lib64wbclient0-4.3.10-1-rosa2014.1.x86_64
---
> lib64wbclient0-4.3.11-1-rosa2014.1.x86_64
2268c2272
< lib64winbind2-4.3.10-1-rosa2014.1.x86_64
---
> lib64winbind2-4.3.11-1-rosa2014.1.x86_64
2423a2428
> libacl1-2.2.51-9-rosa2014.1.i586
2424a2430
> libalsa-plugins-jack-1.1.1-1-rosa2014.1.i586
2425a2432
> libappindicator1-12.10.0-5-rosa2014.1.i586
2429a2437,2438
> libatk1.0_0-2.16.0-1-rosa2014.1.i586
> libattr1-2.4.47-2-rosa2014.1.i586
2430a2440,2441
> libavahi-client3-0.6.31-16-rosa2014.1.i586
> libavahi-common3-0.6.31-16-rosa2014.1.i586
2431a2443,2444
> libavformat56-2.8.7-1plf-plf2014.1.i586
> libavutil52-2.3.3-1plf-plf2014.1.i586
2434a2448
> libbluray1-0.9.2-1-rosa2014.1.i586
2437a2452,2454
> libcairo2-1.14.2-1-rosa2014.1.i586
> libcanberra0-0.30-2-rosa2014.1.i586
> libcanberra-gtk0-0.30-2-rosa2014.1.i586
2441a2459
> libcg0-3.1.0013-1-rosa2014.1.i586
2442a2461
> libcups2-1.7.5-17-rosa2014.1.i586
2444a2464,2465
> libdatrie1-0.2.4-4-rosa2014.1.i586
> libdb5.2-5.2.42-2-rosa2014.1.i586
2446a2468,2470
> libdbusmenu-glib4-0.6.2-5-rosa2014.1.i586
> libdbusmenu-gtk4-0.6.2-5-rosa2014.1.i586
> libdconf1-0.24.0-2-rosa2014.1.i586
2473a2498,2499
> libfreebl3-3.23-1-rosa2014.1.i586
> libfreeglut3-2.8.1-2-rosa2014.1.i586
2475a2502,2503
> libgail18-2.24.30-1-rosa2014.1.i586
> libgamin-1_0-0.1.10-9-rosa2014.1.i586
2478a2507,2508
> libGConf2_4-3.2.6-2-rosa2014.1.i586
> libgcrypt11-1.5.3-3-rosa2014.1.i586
2479a2510,2511
> libgdk_pixbuf2.0_0-2.31.4-2-rosa2014.1.i586
> libgdk_pixbuf_xlib2.0_0-2.31.4-2-rosa2014.1.i586
2488a2521
> libgmp10-6.0.0a-2-rosa2014.1.i586
2490a2524
> libgnutls28-3.2.21-1-rosa2014.1.i586
2492a2527
> libgomp1-4.9.2_2014.08-2-rosa2014.1.x86_64
2502a2538,2543
> libgstbase0.10_0-0.10.36-6-rosa2014.1.i586
> libgstcheck0.10_0-0.10.36-6-rosa2014.1.i586
> libgstcontroller0.10_0-0.10.36-6-rosa2014.1.i586
> libgstdataprocol0.10_0-0.10.36-6-rosa2014.1.i586
> libgstnet0.10_0-0.10.36-6-rosa2014.1.i586
> libgstreamer0.10_0-0.10.36-6-rosa2014.1.i586
2503a2545
> libgstreamer-plugins-base0.10-0.10.36-7-rosa2014.1.i586
2505a2548,2551
> libgtk+2.0_0-2.24.30-1-rosa2014.1.i586
> libgtk-aurora-engine-1.5.1-3-rosa2014.1.i586
> libgtk-engines2-2.20.2-8-rosa2014.1.i586
> libgtk-modules2.0-2.24.30-1-rosa2014.1.i586
2506a2553
> libgudev1.0_0-219-1.20150505.21-rosa2014.1.i586
2507a2555
> libhogweed2-2.7.1-7-rosa2014.1.i586
2509a2558,2562
> libindicator7-12.10.1-4-rosa2014.1.i586
> libjack0-1.9.10-2-rosa2014.1.i586
> libjacknet0-1.9.10-2-rosa2014.1.i586
> libjasper1-1.900.1-19-rosa2014.1.i586
> libjbig1-2.0-10-rosa2014.1.i586
2511a2565
> libjson0-0.9-4-rosa2014.1.i586
2539a2594
> liblua5.2-5.2.3-5-rosa2014.1.i586
2540a2596
> libmikmod3-3.3.8-1-rosa2014.1.i586
2541a2598
> libmodplug1-0.8.8.4-4-rosa2014.1.i586
2543a2601
> libmurrine-0.98.2-2-rosa2014.1.i586
2546a2605,2611
> libnettle4-2.7.1-7-rosa2014.1.i586
> libnm-glib4-1.2.2-5-rosa2014.1.i586
> libnm-util2-1.2.2-5-rosa2014.1.i586
> libnotify4-0.7.6-1-rosa2014.1.i586
> libnspr4-4.12-1-rosa2014.1.i586
> libnss3-3.23-1-rosa2014.1.i586
> libnut0-0.0.675-2-rosa2014.1.i586
2551a2617
> libopenssl-engines1.0.0-1.0.1t-1-rosa2014.1.i586
2553a2620,2627
> liborc-test0.4_0-0.4.23-1-rosa2014.1.i586
> libp11-kit0-0.20.2-3-rosa2014.1.i586
> libpango1.0_0-1.36.8-2-rosa2014.1.i586
> libpangocairo1.0_0-1.36.8-2-rosa2014.1.i586
> libpangoft2_1.0_0-1.36.8-2-rosa2014.1.i586
> libpango-modules1.0-1.36.8-2-rosa2014.1.i586
> libpangox1.0_0-1.30.1.0.0.2-2-rosa2014.1.i586
> libpangoxft1.0_0-1.36.8-2-rosa2014.1.i586
2554a2629
> libpci3-3.2.0-6-rosa2014.1.i586
2556a2632,2633
> libpcrecpp0-8.35-2-rosa2014.1.i586
> libpixman1_0-0.32.8-1-rosa2014.1.i586
2574a2652
> libreadline6-6.3-4-rosa2014.1.i586
2607a2686
> librtmp0-2.3-5-rosa2014.1.i586
2609a2689
> libsasl2-plug-sasldb-2.1.25-9-rosa2014.1.i586
2611a2692,2700
> libSDL2_2.0_0-2.0.4-1-rosa2014.1.i586
> libSDL2_image2.0_0-2.0.1-1-rosa2014.1.i586
> libSDL2_mixer2.0_0-2.0.1-1-rosa2014.1.i586
> libSDL2_net2.0_0-2.0.1-1-rosa2014.1.i586
> libSDL2_ttf2.0_0-2.0.14-1-rosa2014.1.i586
> libSDL_image1.2_0-1.2.12-4-rosa2014.1.i586
> libSDL_mixer1.2_0-1.2.12-4-rosa2014.1.i586
> libSDL_ttf2.0_0-2.0.11-3-rosa2014.1.i586
> libselinux1-2.3-31-rosa2014.1.i586
2615a2705
> libsmpeg0.4-0.4.4-45-rosa2014.1.i586
2623a2714,2715
> libswscaler2-2.3.3-1plf-plf2014.1.i586
> libswscaler3-2.8.7-1plf-plf2014.1.i586
2624a2717,2720
> libtasn1_6-4.5-1-rosa2014.1.i586
> libtdb1-1.3.8-1-rosa2014.1.i586
> libthai0-0.1.18-2-rosa2014.1.i586
> libtheora0-1.1.1-12-rosa2014.1.i586
2626a2723,2724
> libtiff5-4.0.6-1-rosa2014.1.i586
> libtinfo5-5-3-rosa2014.1.i586
2631c2729,2731
< libusbx-devel-doc-1.0.18-1-rosa2014.1.noarch
---
> libudev1-219-1.20150505.21-rosa2014.1.i586
> libusb1.0_0-1.0.18-3-rosa2014.1.i586
> libusbx-devel-doc-1.0.18-3-rosa2014.1.noarch
2637a2738,2739
> libvdpau1-1.1.1-2-rosa2014.1.i586
> libvdpau-trace-1.1.1-2-rosa2014.1.i586
2642a2745
> libvorbisfile3-1.3.4-4-rosa2014.1.i586
2654a2758,2760
> libxcb-composite0-1.11.1-2-rosa2014.1.i586
> libxcb-damage0-1.11.1-2-rosa2014.1.i586
> libxcb-dpms0-1.11.1-2-rosa2014.1.i586
2658a2765,2771
> libxcb-randr0-1.11.1-2-rosa2014.1.i586
> libxcb-record0-1.11.1-2-rosa2014.1.i586
> libxcb-render0-1.11.1-2-rosa2014.1.i586
> libxcb-res0-1.11.1-2-rosa2014.1.i586
> libxcb-screensaver0-1.11.1-2-rosa2014.1.i586
> libxcb-shape0-1.11.1-2-rosa2014.1.i586
> libxcb-shm0-1.11.1-2-rosa2014.1.i586
2659a2773,2774
> libxcb-xevie0-1.11.1-2-rosa2014.1.i586
> libxcb-xf86dri0-1.11.1-2-rosa2014.1.i586
2660a2776,2782
> libxcb-xinerama0-1.11.1-2-rosa2014.1.i586
> libxcb-xkb1-1.11.1-2-rosa2014.1.i586
> libxcb-xprint0-1.11.1-2-rosa2014.1.i586
> libxcb-xtest0-1.11.1-2-rosa2014.1.i586
> libxcb-xv0-1.11.1-2-rosa2014.1.i586
> libxcb-xvmc0-1.11.1-2-rosa2014.1.i586
> libxcomposite1-0.4.4-1-rosa2014.1.i586
2665a2788
> libxft2-2.3.2-5-rosa2014.1.i586
2669a2793,2794
> libxmu6-1.1.2-1-rosa2014.1.i586
> libxpm4-3.5.11-1-rosa2014.1.i586
2673a2799
> libxt6-1.1.5-1-rosa2014.1.i586
2772c2898
< networkmanager-1.2.2-3-rosa2014.1.x86_64
---
> networkmanager-1.2.2-5-rosa2014.1.x86_64
2838c2964
< p7zip-15.14.1-2-rosa2014.1.x86_64
---
> p7zip-15.14.1-4-rosa2014.1.x86_64
3028c3154
< plasma5-kio-extras-16.04.2-1-rosa2014.1.x86_64
---
> plasma5-kio-extras-16.04.3-1-rosa2014.1.x86_64
3232c3358
< python-magic-5.27-1-rosa2014.1.noarch
---
> python-magic-5.28-1-rosa2014.1.noarch
3247c3373
< python-pyasn1-0.1.9-2-rosa2014.1.noarch
---
> python-pyasn1-0.1.9-3-rosa2014.1.noarch
3448c3574
< quick-usb-formatter-0.5-0.preview.2-rosa2014.1.x86_64
---
> quick-usb-formatter-0.6-2-rosa2014.1.x86_64
3466c3592
< rosa-imagewriter-2.6.1.1-1-rosa2014.1.x86_64
---
> rosa-imagewriter-2.6.2.0-1-rosa2014.1.x86_64
3468c3594
< rosa-media-player-1.6.11-6-rosa2014.1.x86_64
---
> rosa-media-player-1.6.11-8-rosa2014.1.x86_64
3477c3603
< rpmdrake-5.26.12-54-rosa2014.1.noarch
---
> rpmdrake-5.26.12-55-rosa2014.1.noarch
3493,3497c3619,3623
< samba-client-4.3.10-1-rosa2014.1.x86_64
< samba-common-4.3.10-1-rosa2014.1.x86_64
< samba-python-4.3.10-1-rosa2014.1.x86_64
< samba-server-4.3.10-1-rosa2014.1.x86_64
< samba-winbind-4.3.10-1-rosa2014.1.x86_64
---
> samba-client-4.3.11-1-rosa2014.1.x86_64
> samba-common-4.3.11-1-rosa2014.1.x86_64
> samba-python-4.3.11-1-rosa2014.1.x86_64
> samba-server-4.3.11-1-rosa2014.1.x86_64
> samba-winbind-4.3.11-1-rosa2014.1.x86_64
3548c3674
< steam-1.0.0.51-6-rosa2014.1.i586
---
> steam-1.0.0.52-3-rosa2014.1.i586
6341c6467
< wget-1.17.1-2-rosa2014.1.x86_64
---
> wget-1.18-1-rosa2014.1.x86_64
6346,6347c6472,6473
< wine32-1.9.12-1-rosa2014.1.i586
< wine64-1.9.12-1-rosa2014.1.x86_64
---
> wine32-1.9.12-2-rosa2014.1.i586
> wine64-1.9.12-2-rosa2014.1.x86_64

Не уверен на счет lib64dcerpc0-4.3.11-1-rosa2014.1.x86_64, но подозрения идут на:
lib64nsswins2-4.3.11-1-rosa2014.1.x86_64
lib64wbclient0-4.3.11-1-rosa2014.1.x86_64
lib64winbind2-4.3.11-1-rosa2014.1.x86_64
Так же напрягает, что в системе нет 64-хбитной версии пакета libdbusmenu-glib4

Код: Выделить всё

rpm -qa | grep dbusmen
lib64dbusmenu-qt5_2-0.9.3-0.20140604.1-rosa2014.1.x86_64
lib64dbusmenu-qt2-0.9.2-2-rosa2014.1.x86_64
libdbusmenu-glib4-0.6.2-5-rosa2014.1.i586
libdbusmenu-gtk4-0.6.2-5-rosa2014.1.i586

[keleg]

Наверное, быстрее всего будет не гадать, а поставить в виртуалку образ с прошлой недели (например https://abf.rosalinux.ru/platforms/rosa ... ists/15648), ввести в ваш домен, сделать снапшот и ставить подозрительные обновления по одному. Скорее всего это самба и связанные библиотеки, хотя там вроде минорное секьюрное изменение только.

[keleg]

еще можно попробовать удалить heimdal-libs

[Yamah]

Наверное, быстрее всего будет не гадать, а поставить в виртуалку образ с прошлой недели (например https://abf.rosalinux.ru/platforms/rosa ... ists/15648), ввести в ваш домен, сделать снапшот и ставить подозрительные обновления по одному. Скорее всего это самба и связанные библиотеки, хотя там вроде минорное секьюрное изменение только.

Странно! В этом образе те же симптомы.

[keleg]

Можно тогда подревнее взять образ, например https://abf.rosalinux.ru/platforms/rosa ... ists/15570

[keleg]

попробуйте обновиться до конца. У нас заработало, пересобрали еще кой-что с новой самбой и NM.
правки уже на http://abf-downloads.rosalinux.ru/rosa2 ... epository/ , скоро дойдут до зеркал.

[Yamah]

попробуйте обновиться до конца. У нас заработало, пересобрали еще кой-что с новой самбой и NM.
правки уже на http://abf-downloads.rosalinux.ru/rosa2 ... epository/ , скоро дойдут до зеркал.

Похоже, что у меня стоят все обновления на 5:00 по Москве.

Код: Выделить всё

urpmi --auto-update
источник «Main» уже обновлён
источник «Main Updates» уже обновлён
источник «Main32» уже обновлён
источник «Main32 Updates» уже обновлён
источник «Contrib» уже обновлён
источник «Contrib Updates» уже обновлён
источник «Non-free» уже обновлён
источник «Non-free Updates» уже обновлён
источник «Non-free32» уже обновлён
источник «Non-free32 Updates» уже обновлён
источник «Restricted» уже обновлён
источник «Restricted Updates» уже обновлён
источник «Restricted32» уже обновлён
источник «Restricted32 Updates» уже обновлён
источник «Kernel 4.4» уже обновлён
источник «Kernek 4.5» уже обновлён
источник «Main (ABF1)» уже обновлён
источник «Main Updates (ABF2)» уже обновлён
источник «Main Testing (ABF3)» уже обновлён
источник «Main32 (ABF4)» уже обновлён
источник «Main32 Updates (ABF5)» уже обновлён
источник «Main32 Testing (ABF6)» уже обновлён
источник «Contrib (ABF7)» уже обновлён
источник «Contrib Updates (ABF8)» уже обновлён
источник «Contrib Testing (ABF9)» уже обновлён
Для удовлетворения зависимостей будут установлены следующие пакеты:
 Пакет                          Версия       Релиз         Dist  DEpoch Платформа 
(источник «Main Testing (ABF3)»)
 firefox                        47.0         1             rosa  2014.1 x86_64 
 firefox-ru                     47.0         1             rosa  2014.1 noarch 
Будет использовано 1МБ дополнительного дискового пространства.
Будет загружено 43МБ пакетов.
Установить 2 пакетов? (Y/n) 

Забыл сказать, что перед обновлениям 15-го, я последний раз обновлялся в начале июня.

[Yamah]

Можно тогда подревнее взять образ, например https://abf.rosalinux.ru/platforms/rosa ... ists/15570

Странно. И тут эта же проблема.

Проверил на чистой R7. Про DBus в консоли пишет то же самое, но все работает.
Все ставил в VirtualBox на чистый жесткий диск.

[Yamah]

Откатился на созданный ранее снапшот. Обновлял все постепенно.
После обновления самбы, KDE перестает запускаться.

Код: Выделить всё

urpmi --auto-update
источник «Main» уже обновлён
источник «Main Updates» уже обновлён
источник «Main32» уже обновлён
источник «Main32 Updates» уже обновлён
источник «Contrib» уже обновлён
источник «Contrib Updates» уже обновлён
источник «Non-free» уже обновлён
источник «Non-free Updates» уже обновлён
источник «Non-free32» уже обновлён
источник «Non-free32 Updates» уже обновлён
источник «Restricted» уже обновлён
источник «Restricted Updates» уже обновлён
источник «Restricted32» уже обновлён
источник «Restricted32 Updates» уже обновлён
источник «Kernel 4.4» уже обновлён
источник «Kernel 4.5» уже обновлён
Следующий пакет будет удалён для обновления остальных:
lib64granite1-0.2.3-1-rosa2014.1.x86_64                                                                                                                                                 
 (из-за неудовлетворённости granite == 0.2.3-1:2014.1) (y/N) y                                                                                                                          
Для удовлетворения зависимостей будут установлены следующие пакеты:                                                                                                                     
 Пакет                          Версия       Релиз         Dist  DEpoch Платформа                                                                                                       
(источник «Main Updates»)                                                                                                                                                               
 lib64dcerpc0                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64gensec0                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64ndr0                      4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64netapi0                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64nsswins2                  4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64registry0                 4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-credentials0        4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-hostconfig0         4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-passdb0             4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-policy0             4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-server0             4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samba-util0               4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64samdb0                    4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64smbclient0                4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64smbconf0                  4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64smbldap0                  4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64tevent-util0              4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64wbclient0                 4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 lib64winbind2                  4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 samba-client                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 samba-common                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 samba-python                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 samba-server                   4.3.11       1             rosa  2014.1 x86_64                                                                                                          
 samba-winbind                  4.3.11       1             rosa  2014.1 x86_64                                                                                                          
(источник «Contrib Updates»)                                                                                                                                                            
 granite                        0.3.1        1             rosa  2014.1 x86_64                                                                                                          
Будет освобождено 256КБ дискового пространства.                                                                                                                                         
Будет загружено 8.7МБ пакетов.                                                                                                                                                          
Установить 25 пакетов? (Y/n) n 

[keleg]

А домен классический или на IPA?

[keleg]

Я протестировал домен в эти выходные. Сначала была ошибка, но она ушла после того, как сервак win2008R2 обновил "до упора", возможно фикс безопасности самбы соответствует какому-то фиксу винсервака и они не работают раздельно.
Перед выходом R8 KDE мы будем править работу с доменами по замечаниям из http://bugs.rosalinux.ru/show_bug.cgi?id=7235
Очень хотелось бы проверить это не только на тестовых доменах, присоединяйтесь!

[Yamah]

А домен классический или на IPA?

На RDS. Текущая версия на RELS 6.5. (Остальное в ЛС.)

[Yamah]

Странность заметил. При использовании ядра 4.5.7 не запускается logbind (или bindlog). На одной машине.

[Yamah]

Обновил все кроме NetWorkManager и его либ, и SAMBA и ее либ.
Сделал снаапшот. Перезагрузился. Все работает. Перезагрузился еще раз. Все работает.
Установил NM. Перезагрузился. Все работает. Перезагрузился второй раз - KDE не может запустится.
Откатываюсь обратно.
Обновил Samba. Перезагрузился. Все работает. Перезагрузился второй раз. Все работает.
Сделал снапшот. Перезагрузился. Все работает.
Обновляю NM. Перезагрузился. Все работает. Перезагрузился второй раз. KDE не может запустится.

Что за фигня твориться?

[keleg]

Может, порядок сервисов меняется случайно. А попробуй остановить сервисы systemd-networkd и systemd-resolved

[Yamah]

Может, порядок сервисов меняется случайно. А попробуй остановить сервисы systemd-networkd и systemd-resolved

Это перед тем как запустить KDE?

[keleg]

в состоянии "все работает".

[Yamah]

Выполнил

Код: Выделить всё

# service systemd-networkd stop
service systemd-resolved stop

В состоянии, когда все работает.

Код: Выделить всё

service systemd-networkd status
Redirecting to /bin/systemctl status  systemd-networkd.service
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2016-09-22 17:38:05 KRAT; 9min ago
     Docs: man:systemd-networkd.service(8)
  Process: 4123 ExecStart=/lib/systemd/systemd-networkd (code=exited, status=0/SUCCESS)
 Main PID: 4123 (code=exited, status=0/SUCCESS)
   Status: "Shutting down..."

Sep 22 16:05:50 admin-pc.domen.com systemd-networkd[4123]: Enumeration completed
Sep 22 16:05:50 admin-pc.domen.com systemd-networkd[4123]: enp3s0          : renamed to eth0
Sep 22 16:05:50 admin-pc.domen.com systemd-networkd[4123]: eth0            : renamed to enp3s0
Sep 22 16:05:50 admin-pc.domen.com systemd[1]: Started Network Service.
Sep 22 16:05:52 admin-pc.domen.com systemd-networkd[4123]: enp3s0          : gained carrier
Sep 22 16:05:52 admin-pc.domen.com systemd-networkd[4123]: enp3s0          : DHCPv4 address 192.168.0.51/24 via 192.168.0.5
Sep 22 16:05:52 admin-pc.domen.com systemd-networkd[4123]: enp3s0          : link configured
Sep 22 16:05:54 admin-pc.domen.com systemd-networkd[4123]: enp3s0          : Could not set hostname: Permission denied
Sep 22 17:38:05 admin-pc.domen.com systemd[1]: Stopping Network Service...
Sep 22 17:38:05 admin-pc.domen.com systemd[1]: Stopped Network Service.

# service systemd-resolved status
Redirecting to /bin/systemctl status  systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2016-09-22 17:38:17 KRAT; 10min ago
     Docs: man:systemd-resolved.service(8)
  Process: 4269 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=0/SUCCESS)
 Main PID: 4269 (code=exited, status=0/SUCCESS)
   Status: "Shutting down..."

Sep 22 16:05:50 admin-pc.domen.com systemd[1]: Starting Network Name Resolution...
Sep 22 16:05:51 admin-pc.domen.com systemd-resolved[4269]: Using system hostname 'admin-pc.domen.com'.
Sep 22 16:05:51 admin-pc.domen.com systemd-resolved[4269]: Switching to system DNS server 192.168.0.2.
Sep 22 16:05:51 admin-pc.domen.com systemd[1]: Started Network Name Resolution.
Sep 22 17:38:17 admin-pc.domen.com systemd[1]: Stopping Network Name Resolution...
Sep 22 17:38:17 admin-pc.domen.com systemd[1]: Stopped Network Name Resolution.
Sep 22 17:39:11 admin-pc.domen.com systemd[1]: Stopped Network Name Resolution.

Загрузился в KDE от доменного пользователя нормально.

[keleg]

не, не просто остановить, выключить. Это сервисы автонастройки сети, они дублируют NM.
А потом обновиться попробовать.

[Yamah]

не, не просто остановить, выключить. Это сервисы автонастройки сети, они дублируют NM.
А потом обновиться попробовать.

Выключил указанные службы. Перезагрузился. Обновился с консоли. Перезагрузился. Первый раз зашел нормально. Еще одна перезагрузка, и опять KDE вылетел.

[keleg]

а что в логах-то? С чего KDE вылетел?

[Yamah]

Так в первом сообщении есть все.
LXQt стартует.
KDE5 вроде тоже, но у меня он похоже криво встал - не было иконок совсем.

[Yamah]

NSCD не стартует от доменного пользователя. Запускаешь от рута - проблема уходит.

[keleg]

Так это ж вроде сервис, он должен от рута пускаться? Или что-то нужно подправить?

[Yamah]

На домашнем ПК он запускается от своего юзера
nscd 4257 0.0 0.1 922188 10432 ? Ssl 18:40 0:00 /usr/sbin/nscd --foreground
На рабочем ПК, запущенный от рута процесс
nscd 7227 0.0 0.0 927164 7108 ? Ssl 16:18 0:00 nscd

Я понятия не имею где и когда он запускается. Сам факт, что он не запускается на ПК с доменной авторизацией. Причем в R8 и R9

[keleg]

systemctl enable nscd.service решит проблему?

[Yamah]

Ну теперь я смогу проверить только завтра.

[Yamah]

Если запускать через systemd, то загрузка вообще стопорится. Вход в иксах не работает, в других консолях приглашения авторизоваться нет.

[keleg]

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

[Yamah]

Запускал его от рута, когда смог попасть во вторую консоль.
Одна команда nscd без параметров.

PS: Сочувствую с кмопом. Я полтора месяца без основного ПК дома был. Сгорела материнская плата, прихватив процессор. Сейчас вот с компом дочери вожусь.