El 2/09/05, jose maria
* Hay aplicaciones que no tienen soporte en 64 bits, que si tienen incompatibilidades cuando se ejecuta el S.O. de 64 bits, en cambio no presentan incompatibilidad si se ejecuta sobre el S.O. de 32, aunque el procesador sea de 64 amd.
De momento optaré por pensar que sea eso.
* Lo de la exportacion de Xauthority, basicamente es lo que hace kdesu y varias otras lo tienes en los apuntes.
Echaré una ojeada a ver si encuentro algo de kdesu...
* otra forma, supon que estas en las x en el usuario josan , pasas a una consola control+alt+F1 te logueas como usuario pepe y tecleas startx -- :1
tendras al usuario pepe en control+alt+F8 y a josan en la F7
No, así tampoco funciona. resultado: ================================================ X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: SuSE Linux [ELF] SuSE Current Operating System: Linux linux 2.6.11.4-21.8-default #1 Tue Jul 19 12:42:37 UTC 2005 x86_64 Build Date: 22 March 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Sun Sep 4 22:21:01 2005 (==) Using config file: "/etc/X11/xorg.conf" (EE) Failed to load module "rfbkeyb" (module does not exist, 0) (EE) Failed to load module "rfbmouse" (module does not exist, 0) (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x8000000) (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. ListenOnTCPPort: Address already in use Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 7. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.1.log" for additional information. XIO: fatal IO error 104 (Connection reset by peer) on X server ":1.0" after 0 requests (0 known processed) with 0 events remaining. ================================================= En fin, ya investigaré con paciencia cuando tenga tiempo, a ver de qué se trata.