|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
|
| 1 | |
Centos 6.3 gedit от root `a28.10.2012, 11:57. Показов 3533. Ответов 13
Метки нет (Все метки)
собственно, как запустить gedit из-под root - известно: Код
su gedit ctrl + o потом нудно рыскать по дереву каталогов... а как сделать, чтобы файлы, на которые у меня нет прав доступа, открывались из nautilus в gedit от root `a?
0
|
|
(| 28.10.2012, 11:57 | |
|
Ответы с готовыми решениями:
13
Как дать права root для gedit? CentOS 7 изменить размер root
|
|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
|||||||||||
| 30.10.2012, 12:32 [ТС] | 4 | ||||||||||
Сообщение от accept
действительно странно, как эта простая мысль не пришла мне самому в голову. однако, dolphin у меня не установлен:
а после
Кликните здесь для просмотра всего текста
(nautilus:2546): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(nautilus:2546): Eel-WARNING **: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (nautilus:2546): Eel-WARNING **: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (nautilus:2546): Eel-WARNING **: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (nautilus:2546): Eel-WARNING **: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf warning: failure listing pairs in `/apps/nautilus/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (nautilus:2546): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nautilus:2546): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting. (nautilus:2546): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nautilus:2546): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
0
|
|||||||||||
|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
|
| 31.10.2012, 09:42 [ТС] | 6 |
|
Сообщение от accept
хотя, повторюсь, dolphin у меня не установлен, ибо гном. да и незачем: в качестве двухпанельника использую mc. однако, вот незадача: nautilus, открытый с рабочего стола (на скриншоте слева) разительно отличается от открытого из консоли (справа) 
0
|
|
|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
||||||
| 01.11.2012, 20:09 [ТС] | 10 | |||||
|
даже не знаю, что там можно настроить:
если залогиниться от рута, nautilus выглядит вот так: http://storage5.static.itmages... aa308.jpeg а если запускать его:
http://storage3.static.itmages... d2dfd.jpeg даже боковую панель включить нельзя
0
|
||||||
|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
|
| 03.11.2012, 00:08 [ТС] | 12 |
|
Сообщение от accept
applications -> system tools -> file browser но залогинившись рутом если запускать через dbus результат тот же, что и через su dbus и совершенно неясно, где всё это хозяйство настраивать
0
|
|
|
43 / 7 / 0
Регистрация: 16.09.2009
Сообщений: 115
|
||||||
| 03.11.2012, 07:57 [ТС] | 14 | |||||
|
Сообщение от accept
итого правильный ответ:
0
|
||||||
| 03.11.2012, 07:57 | |
| 03.11.2012, 07:57 | |
|
Помогаю со студенческими работами здесь
14
Как лечить shown root:root -R / gEdit Кодировка в gEdit Как установить gedit? Искать еще темы с ответами Или воспользуйтесь поиском по форуму: |
Наверх