Příspěvky

Dakujem za radu,
trosku som sa s tym pohral a ide to tak, ako ma ;)

Ahoj, denne pouzivam na debiane slovensku qwertz klavesnicu, ale od isteho momentu mi vzdy po starte nabehne americke qwerty rozlozenie nepriek tomu, ze gui nastaveni je jesne definovane (ako jedine a predvolene) slovenske rozlozenie. (Cez gui) je jedinym riesenim vymazat a pridat to iste rozlozenie  ??? , co je po kazdom strate naozaj otravne.
Ak poznate riesenie, popripade nastavenie rozlozenie klavesnice mimo gui budem Vam velmi vdacny.
   

Ahoj,
som slastníkom horeuvedenej graf. karty Nvidia, na graf prostredie mi ide uplne normalne, ale pri pokuse spustit ET vypise chybovu hlasku

Kód [Vybrat] Rozbalit

Using XFree86-VidModeExtension Version 2.2
XF86DGA Mouse (Version 2.0) initialized
XFree86-VidModeExtension Activated at 640x480
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Couldn't get a visual
...WARNING: could not set the given mode (3)
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
----- CL_Shutdown -----
-----------------------
Sys_Error: GLimp_Init() - could not load OpenGL subsystem


Tak som nazrel aj do glxinfo a nic:

Kód [Vybrat] Rozbalit

hahahappy@hahahappy-pc:~$ glxinfo
name of display: :0.0
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x21 24 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x22 24 dc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x71 32 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None


Pouzivan driver z repozitarov:
nvidia-glx
nvidia-kernel-common
nvidia-kernel-2.6.26-2-686 (zhodujuce sa s mojim jadrom)

Skusal som instalovat drivre aj z nvidia stranky, lenze ten instalator potreboval gcc 4.1 (pouzivat 4.3)

Dakujem za odpoved 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

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.

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?

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.

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.