Problémy s nautilusom pod root

[hahahappy]

Ahoj,
neviem cim to je, ale ked spustim nautilus pod rootom (su), vypise mi takuto pomerne dlhu hlasku (prepacte za spamovanie), inak normalne pod uzivatelom mi nautilus bezproblemov slape. Vopred dakujem za rady.

Kód [Vybrat] Rozbalit


(nautilus:3563): EggSMClient-WARNING **: Failed to connect to the session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed


(nautilus:3563): Eel-WARNING **: Chyba GConf:
  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:3563): Eel-WARNING **: Chyba GConf:
  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.)
Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)
(nautilus:3563): 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:3563): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(nautilus:3563): 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:3563): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
simon-pc:/home/simon# gksu nautilus
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

(nautilus:3583): EggSMClient-WARNING **: Failed to connect to the session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed


(nautilus:3583): Eel-WARNING **: Chyba GConf:
  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:3583): Eel-WARNING **: Chyba GConf:
  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.)
Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)Varovanie GConf: zlyhanie v zozname párov v `/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.)
(nautilus:3583): 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:3583): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(nautilus:3583): 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:3583): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.


[asfethan]

Skus spustit nasledovne:

Kód [Vybrat] Rozbalit

$ gksu nautilus

Myslim ze "spustit" v gnome ma skratku ALT+F2, tak tam napis vyssie uvedene. Alebo do terminalu (ale vsimni si ze ako norm. user, to znaci znak '$')

[hahahappy]

Zaujimave, ked to spustim

Kód [Vybrat] Rozbalit

gksu nautilus pod normalnym terminalom ide mi to, ale ked pod su terminalom vyhodi error, doteraz som nautilus vzdy spustaval len cez su terminal.

[asfethan]

pouzil si aj gksu?

Problem je totiz v tom ze session pod ktorou sa nachadzas je uzivatelska, ked pouzijes su tak automaticky vykonavas prikazy pod inym UID ktoremu session nepatri. Preto tie chyby. Presne pre toto vznikli programy gksu a gksudo.

[Ahmul]

To bude tím, že pokud se přihlasíte jako root, tak ten nemá spuštěnou Xkovou relaci, takže spuštění programu pro Xka pochopitelně zhavaruje.

• 1. pokud můžete nedělejte nic pod rootem
• 2. pokud už musíte něco udělat pod rootem, použijte gksu
• 3. nejhorší ze všeho je mít permanentně otevřený terminál na root konzoli. To vám pravděpodobně ten systém moc dlouho nevydrží

[hahahappy]

Dakujem za odpoved
Hej, vyhodi mi to aj ked pouzijem

Kód [Vybrat] Rozbalit

gksu pod su terminalom
, ale pod uzivatelskym nie, dokonca ani ked cez uzivatelsky spustim bez gksu, nautilus normalne ide.
--
Nejde to nejak ostranit, aby sa dal spustat ako predtym pod su terminalom?

[asfethan]

To bude tím, že pokud se přihlasíte jako root, tak ten nemá spuštěnou Xkovou relaci, takže spuštění programu pro Xka pochopitelně zhavaruje.

• 1. pokud můžete nedělejte nic pod rootem
• 2. pokud už musíte něco udělat pod rootem, použijte gksu
• 3. nejhorší ze všeho je mít permanentně otevřený terminál na root konzoli. To vám pravděpodobně ten systém moc dlouho nevydrží

Pre zaciatocnika velmi dobre rady :) Aj ked podla mna pre pokrocilych je tiez pohodlnejsie pouzit sudo. Ako root sa prihlasujem iba do VT ked padnu X, v emulatore (unicode-rxvt) nepouzivam su skoro vobec, iba ked potrebujem poslat nejaky integer value do rozhrania /sys :)

[hahahappy]

Dakujem za odpoved
Hej, vyhodi mi to aj ked pouzijem

Kód [Vybrat] Rozbalit

gksu pod su terminalom
, ale pod uzivatelskym nie, dokonca ani ked cez uzivatelsky spustim bez gksu, nautilus normalne ide.
--
Nejde to nejak ostranit, aby sa dal spustat ako predtym pod su terminalom?

Mate pravdu, prave som si uvedomil ze v druhom "uzivatelskom" terminali stahujem subor, snad preto vyhadzuje tu hlasku. Ked dostahuje, vyskusam ci ten nautilus ide ked je zapnuty len jeden root terminal.

[asfethan]

Dakujem za odpoved
Hej, vyhodi mi to aj ked pouzijem

Kód [Vybrat] Rozbalit

gksu pod su terminalom
, ale pod uzivatelskym nie, dokonca ani ked cez uzivatelsky spustim bez gksu, nautilus normalne ide.
--
Nejde to nejak ostranit, aby sa dal spustat ako predtym pod su terminalom?

To co potrebujes zariadi pre Teba program gksu!
Spustat kombinaciu su + gksu je absolutne nelogicke :)
Tym padom Ti to ale ulahci pracu, kedze nebudes musiet pisat su a heslo (iba gksu nautilus a heslo). Dokonca si mozes pridat aj spustac do menu a nemusis pisat uz vonkoncom nic.

[asfethan]

Vysvetlenie situacie:
gksu - zariadi aby program (zadany ako parameter) bol spusteny s privilegiami uzivatela root (UID=0).

[hahahappy]

Ahoj,
mám ešte jeden problém s nautilusom, najnovšie sa mi automaticky spúšťa pri štarte s otvoreným /home priečinkom. V "Relácie" som nič nenastavoval, položka "Správca súborov" ja zaškrtnutá ako predtým.
Ďakujem za pomoc hahahappy

[asfethan]

Hmm to je zvlastne, obavam sa ale ze s tymto Ti moc neporadim, nepouzivam GNOME, iba nautilus samostatne.

Skus ale dokladne pozriet ci si ho nenechal niekde nahodou otvoreny (minimalizovany) a ci nie je nastavene aby sa spustal po starte. To su iba take vseobecne rady, viac pomoct zial neviem.

Po pripade skus vymazat vsetky ulozene relacie a relognut.

[Jakub Lucký]

To bude tím, že pokud se přihlasíte jako root, tak ten nemá spuštěnou Xkovou relaci, takže spuštění programu pro Xka pochopitelně zhavaruje.

• 1. pokud můžete nedělejte nic pod rootem
• 2. pokud už musíte něco udělat pod rootem, použijte gksu
• 3. nejhorší ze všeho je mít permanentně otevřený terminál na root konzoli. To vám pravděpodobně ten systém moc dlouho nevydrží

S prvními dvěmi body souhlasím, třetí bod podle mého platí pouze pro začátečníky... Já třeba už rok a půl mám na ploše 4 rootovskou screen a nemohu říct, že by můj systém nedržel... Naopak, prosperuje... Jen není slušné tímto způsobem spouštět grafické aplikace, ale já stejně používám cp, mv, rm, ln, apt, mount, ... a pak je rootovská screen požehnáním...

[Erich Stark]

To bude tím, že pokud se přihlasíte jako root, tak ten nemá spuštěnou Xkovou relaci, takže spuštění programu pro Xka pochopitelně zhavaruje.

• 1. pokud můžete nedělejte nic pod rootem
• 2. pokud už musíte něco udělat pod rootem, použijte gksu
• 3. nejhorší ze všeho je mít permanentně otevřený terminál na root konzoli. To vám pravděpodobně ten systém moc dlouho nevydrží

Tak je mozne ze som mal podobnu chybu ked som pod user terminalom siel upravovat nejaky subor ako root napr kate /var/xxx/hmm.conf tak mi ukazalo nieco typu "unable to connect X server" ?

[Jakub Lucký]

To je vysoce pravděpodobné