Hello all. In a previous context, I mentioned that --perhaps associated with a locking screen-saver becoming active in the middle of a BIG apt-get update (my first big one, ever) -- the system had locked beyond my ability to get X going again. So I had performed a shutdown from console. When I re-started, I no longer had KDE3 or GNOME... I was dumped into WindowManager, with no kdm or gdm opportunity to select another desktop mangler. Anyway, I ran SuSEconfig, and everything seemed to go ok except the following section: Executing /sbin/conf.d/SuSEconfig.susewm... unable to copy /opt/kde3/share/applnk/Settings//.directory to /etc/opt/kde3/share/applnk/SuSE//Settings/.directory unable to read /opt/kde3/share/applnk/Settings//.directory SuSEwm: ERROR: gnome: no "name" defined ! Executing /sbin/conf.d/SuSEconfig.tetex... /sbin/conf.d/SuSEconfig.tetex: Unknown default printer, use texconfig to setup dvips manually. So, I looked at SuSEconfig.susewm, and this is what it *wanted* to do: if [ -d "$r/opt/kde2/share/applnk/" ]; then kde2_links="$(find $r/opt/kde2/share/applnk/ -name \*.desktop)" fi Is it obvious to anybody what is broken? Where to start fixing (so as not to break anything even worse)? Is this one of those situations where one just modifies a line in one config file and it works again? Or is this where I re-install X and KDE and maybe GNOME, to make it all happy again? I don't miss the KDE candy as much as I thought I would, but I miss being able to run many KDE or GNOME apps. Regards, /kevin
On Thu, 24 Oct 2002 23:27:56 +0100
KMcLauchlan
Hello all.
In a previous context, I mentioned that --perhaps associated with a locking screen-saver becoming active in the middle of a BIG apt-get update (my first big one, ever) -- the system had locked beyond my ability to get X going again. So I had performed a shutdown from console. When I re-started, I no longer had KDE3 or GNOME... I was dumped into WindowManager, with no kdm or gdm opportunity to select another desktop mangler.
Anyway, I ran SuSEconfig, and everything seemed to go ok except the following section:
[...] I tried running Synaptic just now, but I get the following result: schmoo@linux:~> sux - Password: linux:~ # synaptic Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server Gtk-WARNING **: cannot open display: :0.0 If I get this while staring at a WindowMaker screen, am I not already using X and the first device controlled by X?? I thought that's what display: :0.0 was all about. So, what do these errors really mean? I tried looking at the X config files again, but I don't understand why (when I have only one video adapter and a single screen) the :0.0 display would NOT be the one that I, and X, and WindowManager were already using. Explain, in small words, for the dummy, please. /kevin
On Friday 25 October 2002 03:02, KMcLauchlan wrote:
I tried running Synaptic just now, but I get the following result:
schmoo@linux:~> sux - Password: linux:~ # synaptic Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Gtk-WARNING **: cannot open display: :0.0
If I get this while staring at a WindowMaker screen, am I not already using X and the first device controlled by X?? I thought that's what display: :0.0 was all about.
So, what do these errors really mean?
X has its own authorization system separate from the *nix concept of "root" and "users". Put simply, only the user who started X may connect, unless that user gives authorization to others. In this case, root is just another user. SuSE has written the script "sux" to automate the authorization, but in certain circumstances, the script fails. Usually when a user who normally logs in through kdm/xdm suddenly logs in through "startx" or vice versa. The solution is simple. As root, do rm /root/.Xauthority exit and then go to root with "sux" again. regards Anders
I tried running Synaptic just now, but I get the following result:
schmoo@linux:~> sux - Password: linux:~ # synaptic Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Gtk-WARNING **: cannot open display: :0.0
In a terminal window, xhost localhost + then become root then launch synaptic fxf -- ______________________ Courtesy of SuSE Linux nibz.org
Op vrijdag 25 oktober 2002 21:50, schreef FX Fraipont:
I tried running Synaptic just now, but I get the following result:
schmoo@linux:~> sux - Password: linux:~ # synaptic Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Gtk-WARNING **: cannot open display: :0.0
In a terminal window, xhost localhost + then become root then launch synaptic
First bullit at: http://linux01.gwdg.de/apt4rpm/home.html#hints -- Richard Bos Without a home the journey is endless
On Friday 25 October 2002 21.50, FX Fraipont wrote:
I tried running Synaptic just now, but I get the following result:
schmoo@linux:~> sux - Password: linux:~ # synaptic Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Gtk-WARNING **: cannot open display: :0.0
In a terminal window, xhost localhost +
This turns off the security checking. If you break the key to your door, isn't it better to fix the key instead of keeping the door unlocked?
participants (4)
-
Anders Johansson -
FX Fraipont -
KMcLauchlan -
Richard Bos