Перестала запускаться система когда ввожу startx, выводит:"Call to lnusertemp failed (temporary directories full?). Check your installation.". Вошел только через "sudo startx". Лог файла приложил.
* Stopping Read required files in advance[204G[ OK ] * Starting Mount filesystems on boot[204G[ OK ] * Starting Populate and link to /run filesystem[204G[ OK ] * Stopping Populate and link to /run filesystem[204G[ OK ] * Stopping Track if upstart is running in a container[204G[ OK ] * Starting Initialize or finalize resolvconf[204G[ OK ] * Starting set console keymap[204G[ OK ] * Starting Signal sysvinit that virtual filesystems are mounted[204G[ OK ] * Starting Signal sysvinit that virtual filesystems are mounted[204G[ OK ] * Starting Bridge udev events into upstart[204G[ OK ] * Starting Signal sysvinit that remote filesystems are mounted[204G[ OK ] * Stopping set console keymap[204G[ OK ] * Starting device node and kernel event manager[204G[ OK ] * Starting load modules from /etc/modules[204G[ OK ] * Starting cold plug devices[204G[ OK ] * Starting log initial device creation[204G[ OK ] * Starting load fallback graphics devices[204G[ OK ] * Stopping load fallback graphics devices[204G[ OK ] * Stopping load modules from /etc/modules[204G[ OK ] * Starting Uncomplicated firewall[204G[ OK ] * Starting configure network device security[204G[ OK ] * Starting configure network device security[204G[ OK ] * Starting configure network device[204G[ OK ] * Starting configure network device[204G[ OK ] * Starting configure network device security[204G[ OK ] * Starting Mount network filesystems[204G[ OK ] * Stopping Mount network filesystems[204G[ OK ] * Starting Bridge socket events into upstart[204G[ OK ] * Starting configure network device[204G[ OK ] * Starting Signal sysvinit that the rootfs is mounted[204G[ OK ] * Starting Clean /tmp directory[204G[ OK ] * Stopping Clean /tmp directory[204G[ OK ] * Starting Signal sysvinit that local filesystems are mounted[204G[ OK ] * Starting SMB/CIFS File Server[204G[ OK ] * Stopping Mount filesystems on boot[204G[ OK ] * Starting Flush boot log to disk[204G[ OK ] * Starting flush early job output to logs[204G[ OK ] * Stopping Failsafe Boot Delay[204G[ OK ] * Starting System V initialisation compatibility[204G[ OK ] * Stopping Flush boot log to disk[204G[ OK ] * Starting Enabling additional executable binary formats[204G[ OK ] * Stopping flush early job output to logs[204G[ OK ] * Starting Bridge file events into upstart[204G[ OK ] * Starting D-Bus system message bus[204G[ OK ] * Starting modem connection manager[204G[ OK ] * Starting configure network device security[204G[ OK ] * Starting bluetooth daemon[204G[ OK ] * Starting system logging daemon[204G[ OK ] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Setting sensors limits * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] [210G * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ]
[204G[ OK ] * Starting SystemD login management service[204G[ OK ] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Setting up X socket directories... [210G [204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Stopping System V initialisation compatibility[204G[ OK ] * Starting System V runlevel compatibility[204G[ OK ] * Starting anac(h)ronistic cron[204G[ OK ] * Starting MDM Display Manager[204G[ OK ] * Starting save kernel messages[204G[ OK ] * Starting configure network device security[204G[ OK ] * Starting ACPI daemon[204G[ OK ] * Stopping save kernel messages[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting cups-browsed - Bonjour remote printer browsing daemon[204G[ OK ] * Starting configure virtual network devices[204G[ OK ] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting CPU interrupts balancing daemon[204G[ OK ] * Starting regular background program processing daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Stopping Restore Sound Card State[204G[ OK ] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting mDNS/DNS-SD daemon[204G[ OK ] * Starting mDNS/DNS-SD daemon[204G[[31mfail[39;49m] * Stopping mDNS/DNS-SD daemon[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[204G[[31mfail[39;49m] * Starting deferred execution scheduler[204G[ OK ] * Stopping anac(h)ronistic cron[204G[ OK ] * Starting network connection manager[204G[ OK ] /sbin/start-stop-daemon: unable to open pidfile /var/run/dirmngr.pid (Permission denied) * Starting DirMngr dirmngr [210G [204G[[31mfail[39;49m] * Stopping cold plug devices[204G[ OK ] * Stopping log initial device creation[204G[ OK ] * Starting enable remaining boot-time encrypted block devices[204G[ OK ] * Starting save udev log and update rules[204G[ OK ] * Stopping save udev log and update rules[204G[ OK ] sh: 1: /etc/linuxmint/adjustments//20-mint-kde-software-properties-desktop.execute: Permission denied * speech-dispatcher disabled; edit /etc/default/speech-dispatcher Starting VirtualBox kernel modules * Stopping Send an event to indicate plymouth is up[204G[ OK ] ...done. [33m*[39;49m VirtualBox Additions disabled, not in a Virtual Machine * Starting NTP server ntpd [210G [204G[ OK ] saned disabled; edit /etc/default/saned * Restoring resolver state... [210G [204G[ OK ] * Stopping System V runlevel compatibility[204G[ OK ] * Starting Mount network filesystems[204G[ OK ] * Stopping Mount network filesystems[204G[ OK ] * Starting Samba Winbind[204G[ OK ] * Starting NetBIOS name server[204G[ OK ] * Stopping LightDM Display Manager[204G[ OK ] * Starting CUPS printing spooler/server[204G[ OK ] * Starting Samba Auto-reload Integration[204G[ OK ] * Stopping Samba Auto-reload Integration[204G[ OK ] * Starting MDM Display Manager[204G[[31mfail[39;49m] * Starting anac(h)ronistic cron[204G[ OK ] * Stopping anac(h)ronistic cron[204G[ OK ]
Редактировалось: 1 раз (Последний: 12 марта 2016 в 01:16)
Сообщений: 0
#3 - 11 марта 2016 в 21:56
bor-bos:
temporary directories full?
Код PHP:
sudo df -h
Сообщений: 0
#4 - 11 марта 2016 в 21:59
Есть ли свободное место на диске? поделайте fsck, покажите smart. Что делали перед поломкой?
Сообщений: 0
#5 - 11 марта 2016 в 22:52
bor-bos, http://poplinux.ru/node/283 -здесь пишут,что такое в KDE случается и некоторые варианты исправления Но смарт по параметрам 05, 10, 186-188 глянуть бы обязательно нужно
Места на диске хватает. Аварийно выключил пк. При запуске временами пишит еще: "Каталог авторизации сервера (daemon/ServAuthDir) установлен "/var/mdm", но такой путь не существует. Исправьте конфигурацию менеджера MDM, перезапустите его."
Сообщений: 0
#8 - 11 марта 2016 в 23:56
mastergx:
Но смарт по параметрам 05, 10, 186-188 глянуть бы обязательно нужно
Как это сделать? Обьясни пожалуйста
Сообщений: 0
#9 - 12 марта 2016 в 00:17
bor-bos, загружайся в консоль или в гуй и выполни команду:
Код BASH:
# chmod 1777 /tmp
# chmod 1777 /var/tmp
Сообщений: 0
#10 - 12 марта 2016 в 00:39
sizonov_stas, ничего не поменялось
Сообщений: 0
#11 - 12 марта 2016 в 01:10
bor-bos, ls - la /tmp
и все-таки, я не понял -- он не запускается из-за прав на /tmp или из-за менеджера MDM? попробуй восстановить mdm, для этого запусти утилиту восстановления
# ls - la /tmp ls: невозможно получить доступ к -: Нет такого файла или каталога ls: невозможно получить доступ к la: Нет такого файла или каталога /tmp: akonadi-roo# ls - la /tmp ls: невозможно получить доступ к -: Нет такого файла или каталога ls: невозможно получить доступ к la: Нет такого файла или каталога /tmp: akonadi-root.HV0AEV kde-boris kde-root ksocket-boris ksocket-root mintUpdate serverauth.7o4On4IfDn tmpA72VNy812997541.cert tmpaiD9uA812997541.keyt.HV0AEV kde-boris kde-root ksocket-boris ksocket-root mintUpdate serverauth.7o4On4IfDn tmpA72VNy812997541.cert tmpaiD9uA812997541.key
Сообщений: 0
#13 - 12 марта 2016 в 01:35
Менеджер mdm не видел папку /var/mdm, хотя она существует и в ней скрытые файлы. Установил kdm, но тут возникла вторая проблема "Call to lnusertemp failed (temporary directories full?). Check your installation.". То есть под обычным пользователем входить отказываеться
Сообщений: 0
#14 - 12 марта 2016 в 01:40
прости, там ошибка, пробел не нужен ls -la /tmp
Сообщений: 0
#15 - 12 марта 2016 в 01:42
# ls -la /tmp итого 60 drwxrwxrwt 10 root root 4096 Мар 12 00:41 . drwxr-xr-x 24 root root 4096 Мар 11 20:54 .. drwx------ 2 root root 4096 Мар 12 00:30 akonadi-root.HV0AEV drwxrwxrwt 2 root root 4096 Мар 12 00:30 .ICE-unix drwx------ 2 boris boris 4096 Мар 12 00:41 kde-boris drwx------ 2 root root 4096 Мар 12 00:30 kde-root -rw------- 1 root root 70 Мар 12 00:41 kdesudo-nn3272-xauth drwx------ 2 root root 4096 Мар 12 00:39 ksocket-boris drwx------ 2 root root 4096 Мар 12 00:30 ksocket-root drwxrwxrwx 2 root root 4096 Мар 12 00:30 mintUpdate -rw------- 1 root root 70 Мар 12 00:30 serverauth.7o4On4IfDn -rw------- 1 root root 806 Мар 12 00:31 tmpA72VNy812997541.cert -rw------- 1 root root 1281 Мар 12 00:31 tmpaiD9uA812997541.key -r--r--r-- 1 root root 11 Мар 12 00:30 .X0-lock drwxrwxrwt 2 root root 4096 Мар 12 00:30 .X11-unix