On Sun, 2005-01-09 at 06:12, Carlos E. R. wrote:
The Saturday 2005-01-08 at 20:12 +0530, rada and gus wrote:
Are you sure the problem is with sux and not KDE? You can test the access to your X-server with for instance "xterm". This command shouldn't be affected by problems with KDE configuration.
xterm runs just fine. Maybe it is a KDE configuration problem. Makes sense since sux seems to work just fine for most people. Where to look for the problem since some others seem to also to have had the problem? Thanks for the feedback. Gustav Degreef.
After doing "sux -", start some graphic program, but not a kde one. Or try several, some kde, some generic, some gnome, for example. Maybe try ethereal, gkrellm, yast
Thanks for the input. When I try it on my 9.1 system now it seems to run everything fine after sux - xgnokii, kwrite, gmplayer, gtoaster, konqueror all seem to run fine. Seems I can't reproduce it. Yesterday on my friends dell laptop running 9.2 I had constant problems "can't connect to X-server", though periodically it would work - can't precisely recall how and when. The problem is not critical but also not academic. I am not a newbie, but far from an expert. I use two main programs from a root console - namely kwrite and konqueror. I use kwrite to edit config files or files owned by root and I use konqueror to navigate in folders that I do not have access or write permissions. So it is very handy to sux - from a user console, edit a file with kwrite, close kwrite and exit from root back to my user console. Same with konqueror. I am sure there are other ways of doing the same things (I've tried joe, emacs and vi but find them too complex for simple tasks), but at my level this seems the most intuitive and the quickest. I used to log in as root and simply start the graphical program from the command line in Red Hat from versions 7.1 to fedora 1 and on switching to Suse I find it really interupts my work and the flow of things not being able to consistently do it. Thanks, Gustav Degreef.