Re: potato broke X :(

1999-10-11 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: Okay, I sent in a bug report. I followed the instructions at bugs.debian.org, so I hope I did it right... The bug report number is 47105. Looks good to me; but you should, technically, have included the versions of the packages that xserver-svga depends

Re: potato broke X :(

1999-10-10 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: David Coe ([EMAIL PROTECTED]) wrote: Still getting that X: undefined symbol: __syscall ? Yep. Hmmm, let's see what packages you have on hold --- just a shot in the dark. Please do: sgrep -e '(DEB_PKG containing (DEB_STATUS containing

Re: potato broke X :(

1999-10-10 Thread Ron Farrer
David Coe ([EMAIL PROTECTED]) wrote: Easiset way is to download reportbug and run it, follow the prompts; go to http://bugs.debian.org/ if you're unsure about what to say, or if you want to do it manually (by sending a mail message). Okay, I sent in a bug report. I followed the instructions

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: [...] The only thing in '/root/.xsession-errors' is: X connection to :0.0 broken (explicit kill or server shutdown). [...] # dpkg --print-avail xserver* Package 'xserver' is not available. WTF? Did I do something wrong in the command? Yeah there is

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: I've attached a file named log_x11.txt which is the output of the command you gave me (it was too long to try and type). OK, I'm going to digest that for a while... to see if there are any obvious problems (missing pieces, bad versions). Meanwhile, please

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: [...] in your user directory: .xinitrc .xserverrc .xsession I could not find any of these files in my users home or /root!?! Is this part of the problem? No! They could be contributing to the problem if they were there, but their absence is

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: David Coe ([EMAIL PROTECTED]) wrote: [...] And, if you really feel like it, try manually performing each piece of startx at the bash prompt ('which startx' will tell you where startx is), and see if you can find the point of failure. I am not

Re: potato broke X :(

1999-10-09 Thread Ron Farrer
David Coe ([EMAIL PROTECTED]) wrote: Well, as a starting point, try just this: 1) exit to be sure we start clean 2) login (as root or a normal user, doesn't really matter for this test, maybe even try both to see if there are differences). 3) at the shell prompt just type 'xinit' and watch

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: [...] Okay, I logged in as root and typed 'xinit' and it went to vt7 and just sits there with a blank screen. Switching back to the vt that I started with, it has the error I previously posted about connection broken. OK, that error, X: error in loading

Re: potato broke X :(

1999-10-09 Thread Art Lemasters
...not sure, because I began running xdm for potato, but did you copy and config an .xinitrc to the user home directory X is running in? You might check the X docs on this. Art On Fri, Oct 08, 1999 at 07:56:47PM -0700, Ron Farrer wrote: David Coe ([EMAIL PROTECTED]) wrote: Well, as a

Re: potato broke X :(

1999-10-09 Thread Art Lemasters
Sorry, but I did not know Xinit would work globally, and I stand corrected on that, but you do need to put your window manager entry into the Xinit or .xinitrc before it will start your window manager, unless something has changed on this recently (with slink or potato, if so?). Art On Sat,

Re: potato broke X :(

1999-10-09 Thread David Coe
Art Lemasters [EMAIL PROTECTED] writes: ...not sure, because I began running xdm for potato, but did you copy and config an .xinitrc to the user home directory X is running in? You might check the X docs on this. Art, Actually, xinit doesn't need an .xinitrc; it defaults to using

Re: Re: potato broke X :(

1999-10-09 Thread mittalr
The Message has been received, you should get a response shortly

Re: potato broke X :(

1999-10-09 Thread Ron Farrer
David Coe ([EMAIL PROTECTED]) wrote: Your version of xserver-common is Version: 3.3.2.3a-11 while current potato is Version: 3.3.5-1 You *might* want to try upgrading that (and any dependencies it has), if you can afford to play with this system. Be sure you have a way to get back (I

Re: potato broke X :(

1999-10-09 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: I ran apt-get update;apt-get -f dist-upgrade last night. It only took 12 hours at 26.4K... Anyway, I've attached an updated listing of installed x11 packages. Ohh, and it still doesn't work... Still getting that X: undefined symbol: __syscall ? Hmmm,

Re: potato broke X :(

1999-10-09 Thread Ron Farrer
David Coe ([EMAIL PROTECTED]) wrote: Still getting that X: undefined symbol: __syscall ? Yep. Hmmm, let's see what packages you have on hold --- just a shot in the dark. Please do: sgrep -e '(DEB_PKG containing (DEB_STATUS containing hold))' /var/lib/dpkg/status | grep '^Package:

potato broke X :(

1999-10-08 Thread Ron Farrer
Hello, After upgrading to potato X dies with this error: X: error in loading shared libraries: X: undefined symbol: __syscall X connection to :0.0 broken (explicit kill or server shutdown). Any ideas on how to fix this? TIA, Ron -- = = Ronald Burnett Farrer =

Re: potato broke X :(

1999-10-08 Thread David Coe
Ron Farrer [EMAIL PROTECTED] writes: After upgrading to potato X dies with this error: X: error in loading shared libraries: X: undefined symbol: __syscall X connection to :0.0 broken (explicit kill or server shutdown). Any ideas on how to fix this? are you starting X with 'startx' or

Re: potato broke X :(

1999-10-08 Thread Ron Farrer
David Coe ([EMAIL PROTECTED]) wrote: are you starting X with 'startx' or xdm (or have you tried both)? I use xdm, but I've tried 'startx'. That's how I got to see the error message. is there anything in .xsession.errors? The only thing in '/root/.xsession-errors' is: X connection to :0.0