Re: X busted after 2.0 - 2.1 upgrade
On Thu, Apr 08, 1999 at 09:59:31AM -0400, Raymond A. Ingles wrote: I knew that XF86Setup would overwrite XF86Config, so I saved a copy. I don't know what *other* file XF86Setup created/restored/modified, but it wasn't XF86Config. There have been some brains hacked into both XF86Setup and the xserver-configure wrapper script that goes to lengths to avoid clobbering an existing XF86Config file. XF86Setup also puts its fingers into /etc/X11/Xserver. I'm pretty sure these two files are the only things it touches. -- G. Branden Robinson | I just wanted to see what it looked like Debian GNU/Linux | in a spotlight. [EMAIL PROTECTED] | -- Jim Morrison cartoon.ecn.purdue.edu/~branden/ | pgpNmt79iwc17.pgp Description: PGP signature
Re: X busted after 2.0 - 2.1 upgrade
On Thu, Apr 08, 1999 at 09:47:49AM -0400, Bob Hilliard wrote: When I updated a hamm partition to slink (using apt-get dist-upgrade) the upgrade was easy and painless. I purged xbase (and a lot of other x stuff I don't use). My XF86Config was not disturbed by the installation or purging. I doubt if you need that dire warning. Yes; as this thread has developed it looks like XF86Config itself is not the problem. I'd appreciate more info from anyone having a problem, so we can track this down. PS: After reading Brian Mays' message commenting on this, I checked the ownership of XF86Config on my system. dpks -S reports /usr/X11R6/lib/X11/XF86Config is owned by xserver-common in slink and xbase in /hamm. In both cases it is a symlink to /etc/X11/XF86Config. dpkg -S doesn't find /etc/X11/XF86Config. Per the packaging manual, XF86Config is not a conffile, because there is no reasonable default for it. /etc/X11/XF86Config does not ship with any package; it is created by hand or with the xf86config or XF86Setup tools. -- G. Branden Robinson | The key to being a Southern Baptist: Debian GNU/Linux | It ain't a sin if you don't get caught. [EMAIL PROTECTED] | -- Anthony Davidson cartoon.ecn.purdue.edu/~branden/ | pgpdiq9C5n3GL.pgp Description: PGP signature
Re: X busted after 2.0 - 2.1 upgrade
On Wed, Apr 07, 1999 at 12:14:33PM -0400, Raymond A. Ingles wrote: On Wed, 7 Apr 1999, Richard Harran wrote: I'm not sure about this, but perhaps you should remove, rather than purge, the xbase package. This is what I did, and I did not get this problem. The difference between purging and removing is that removing leaves configuration files alone, so perhaps purging xbase removes config files necessary to run startx?? This appears to be the case. I saved my old XF86Config, reran XF86Setup, and then replaced the auto-generated XF86Config with my old one. Now startx works just fine. GACK! I hadn't run across this problem in the versions of XFree86 that were released in the course of stabilizing it after the Great X Reorganization. Yes, this is a serious problem. I am not sure what I can do to fix it; my pre- and post- removal scripts in the current xbase package don't delete those conffiles, dpkg does. It's not easy to change dpkg's mind about such things. I have checked, and the slink xbase package: 1) does not have a prerm script 2) does not have a postrm script 3) does not have a conffiles list In English, this means that when you remove or purge xbase, what SHOULD happen is simply that all the files and directories listed by the dpkg -L xbase command are removed. Is it the case that somehow the old /var/lib/dpkg/info/xbase.conffiles file is being left around? On my system, I even still have xbase installed and it is not there. Is there perhaps some scenario in which the old conffiles file is not removed? If so, this is probably a bug in dpkg, and not in X. In the meantime, I will update the appropriate README files with a dire warning to not purge xbase, but to simply remove it instead. All of xbase's conffiles have migrated to other packages; an enumeration is in the existing xbase/README.Debian. I guess I'll take a very close look at the docs and see if this needs to be reported as a bug. I need to examine more closely how I can preserve those conffiles, even in the face of a purge of xbase, which is not an unreasonable thing to do except for this very bad behavior. -- G. Branden Robinson | Debian GNU/Linux | Mob rule isn't any prettier just because [EMAIL PROTECTED] | you call your mob a government. cartoon.ecn.purdue.edu/~branden/ | pgpy3AU3smfIB.pgp Description: PGP signature
Re: X busted after 2.0 - 2.1 upgrade
In article [EMAIL PROTECTED] you write: I'm not sure about this, but perhaps you should remove, rather than purge, the xbase package. This is what I did, and I did not get this problem. The difference between purging and removing is that removing leaves configuration files alone, so perhaps purging xbase removes config files necessary to run startx?? =20 This appears to be the case. I saved my old XF86Config, reran XF86Setup, and then replaced the auto-generated XF86Config with my old one. Now startx works just fine. GACK! I hadn't run across this problem in the versions of XFree86 that were released in the course of stabilizing it after the Great X Reorganization. Yes, this is a serious problem. I am not sure what I can do to fix it; my pre- and post- removal scripts in the current xbase package don't delete those conffiles, dpkg does. It's not easy to change dpkg's mind about such things. This sound like the exact same problem (at least it sounds the same) I had when I upgraded from dhcpd to dhcpd-beta. dhcpd wasn't purged, so I purged it, and it broke dhcpd-beta because purging dhcpd deleted /var/dhcpd and /var/dhcpd.leases which are used by both packages. AFAIK, the bug report is still open. dhcpd is a slightly different situation though - I think the postrm script deletes it. However, it is possible that the solution may be similar for both cases, hence my reason for mentioning it here. Is it the case that somehow the old /var/lib/dpkg/info/xbase.conffiles file is being left around? On my system, I even still have xbase installed and it is not there. Is there perhaps some scenario in which the old conffiles file is not removed? If so, this is probably a bug in dpkg, and not in X. With my very limited knowledge of dpkg. Suggestions: - what package owned the config file in question? On my slink system /etc/X11/XF86Config isn't owned by any package. That might be significant. - I assume that XF86Config once was be owned by xbase?? - In this case, it might be worth installing an older version of XF86Config, and then reinstalling the new version, checking that everything looks Ok at every step. I don't know if this is possible on slink. - If the above step is not possible, it should be possible to create a dummy package that contains a config file, install it, and then install a newer version that doesn't contain the config file, and see what happens. I think this should reproduce the same situation as with xbase.
Re: X busted after 2.0 - 2.1 upgrade
On Thu, 8 Apr 1999, Brian May wrote: In article [EMAIL PROTECTED] you write: This appears to be the case. I saved my old XF86Config, reran XF86Setup, and then replaced the auto-generated XF86Config with my old one. Now startx works just fine. [...] Yes, this is a serious problem. I am not sure what I can do to fix it; my pre- and post- removal scripts in the current xbase package don't delete those conffiles, dpkg does. It's not easy to change dpkg's mind about such things. [...] - what package owned the config file in question? On my slink system /etc/X11/XF86Config isn't owned by any package. That might be significant. I should clarify - my old XF86Config file was still there in /etc/X11/. It wasn't deleted when I purged xbase. But even so, startx failed. I knew that XF86Setup would overwrite XF86Config, so I saved a copy. I don't know what *other* file XF86Setup created/restored/modified, but it wasn't XF86Config. Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] If all the muscles in your body pulled in the same direction, you could lift over twenty tons. But you'd walk funny. - L. M. Boyd
Re: X busted after 2.0 - 2.1 upgrade
Branden Robinson [EMAIL PROTECTED] writes: In the meantime, I will update the appropriate README files with a dire warning to not purge xbase, but to simply remove it instead. When I updated a hamm partition to slink (using apt-get dist-upgrade) the upgrade was easy and painless. I purged xbase (and a lot of other x stuff I don't use). My XF86Config was not disturbed by the installation or purging. I doubt if you need that dire warning. BTW, I had tended to side (silently) with Santiago during your warm discussions about how to treat the Great X Reorganization. However, my experience in upgrading vindicated your position. Of course, I had read the Upgrade-notes. :-) PS: After reading Brian Mays' message commenting on this, I checked the ownership of XF86Config on my system. dpks -S reports /usr/X11R6/lib/X11/XF86Config is owned by xserver-common in slink and xbase in /hamm. In both cases it is a symlink to /etc/X11/XF86Config. dpkg -S doesn't find /etc/X11/XF86Config. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Re: X busted after 2.0 - 2.1 upgrade
On 06 Apr 1999q, Raymond A. Ingles wrote: I upgraded (at least, with CD 1) from 2.0 - 2.1 last night, and everything seemed to be fine. I quit dselect, fired up X, and while running X, looked at some notes I had made preparing for the upgrade. I purged xbase, since it's been claimed that it's no longer needed. Everything still ran fine. I powered things off for the night and went to bed. I got up this morning, powered up, logged on, and then: --- $ startx _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. --- What the heck? Did I jump the gun on removing xbase? Any idea what's up, or how to find what's up? Now that you say this, I realize I had just the same experience (twice, in fact, on different machines). Something wrong with the install advice, I think. Anthony -- Anthony Campbell - running Linux Debian 2.1 Book Reviews: www.achc.demon.co.uk/bookreviews/ The Moving Finger writes; and, having writ, Moves on... - Edward Fitzgerald (Rubaiat of Omar Khayyam)
Re: X busted after 2.0 - 2.1 upgrade
I'm not sure about this, but perhaps you should remove, rather than purge, the xbase package. This is what I did, and I did not get this problem. The difference between purging and removing is that removing leaves configuration files alone, so perhaps purging xbase removes config files necessary to run startx?? This is just a guess. Rich Anthony Campbell wrote: On 06 Apr 1999q, Raymond A. Ingles wrote: I upgraded (at least, with CD 1) from 2.0 - 2.1 last night, and everything seemed to be fine. I quit dselect, fired up X, and while running X, looked at some notes I had made preparing for the upgrade. I purged xbase, since it's been claimed that it's no longer needed. Everything still ran fine. I powered things off for the night and went to bed. I got up this morning, powered up, logged on, and then: --- $ startx _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. --- What the heck? Did I jump the gun on removing xbase? Any idea what's up, or how to find what's up? Now that you say this, I realize I had just the same experience (twice, in fact, on different machines). Something wrong with the install advice, I think. Anthony -- Anthony Campbell - running Linux Debian 2.1 Book Reviews: www.achc.demon.co.uk/bookreviews/ The Moving Finger writes; and, having writ, Moves on... - Edward Fitzgerald (Rubaiat of Omar Khayyam) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: X busted after 2.0 - 2.1 upgrade
On Wed, 7 Apr 1999, Richard Harran wrote: I'm not sure about this, but perhaps you should remove, rather than purge, the xbase package. This is what I did, and I did not get this problem. The difference between purging and removing is that removing leaves configuration files alone, so perhaps purging xbase removes config files necessary to run startx?? This appears to be the case. I saved my old XF86Config, reran XF86Setup, and then replaced the auto-generated XF86Config with my old one. Now startx works just fine. I guess I'll take a very close look at the docs and see if this needs to be reported as a bug. Sincerely, Ray Ingles (248) 377-7735[EMAIL PROTECTED] Every question has a simple, easy-to-understand wrong answer. -H. L. Mencken
Re: X busted after 2.0 - 2.1 upgrade
Richard Harran wrote: Isn't the X packages in cd 2? I'm not sure about this, but perhaps you should remove, rather than purge, the xbase package. This is what I did, and I did not get this problem. The difference between purging and removing is that removing leaves configuration files alone, so perhaps purging xbase removes config files necessary to run startx?? This is just a guess. Rich Anthony Campbell wrote: On 06 Apr 1999q, Raymond A. Ingles wrote: I upgraded (at least, with CD 1) from 2.0 - 2.1 last night, and everything seemed to be fine. I quit dselect, fired up X, and while running X, looked at some notes I had made preparing for the upgrade. I purged xbase, since it's been claimed that it's no longer needed. Everything still ran fine. I powered things off for the night and went to bed. I got up this morning, powered up, logged on, and then: --- $ startx _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. --- What the heck? Did I jump the gun on removing xbase? Any idea what's up, or how to find what's up? Now that you say this, I realize I had just the same experience (twice, in fact, on different machines). Something wrong with the install advice, I think. Anthony -- Anthony Campbell - running Linux Debian 2.1 Book Reviews: www.achc.demon.co.uk/bookreviews/ The Moving Finger writes; and, having writ, Moves on... - Edward Fitzgerald (Rubaiat of Omar Khayyam) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- * Window users: Move up to Linux * * Linux users: Move up to Debian *
X busted after 2.0 - 2.1 upgrade
I upgraded (at least, with CD 1) from 2.0 - 2.1 last night, and everything seemed to be fine. I quit dselect, fired up X, and while running X, looked at some notes I had made preparing for the upgrade. I purged xbase, since it's been claimed that it's no longer needed. Everything still ran fine. I powered things off for the night and went to bed. I got up this morning, powered up, logged on, and then: --- $ startx _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. --- What the heck? Did I jump the gun on removing xbase? Any idea what's up, or how to find what's up? Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] Two rules for success in life: 1. Don't tell people everything you know.
Re: X busted after 2.0 - 2.1 upgrade
After I installed Slink I read that you were suppose to delete xbase, so I did and X wouldn't load. I got an error that said I needed some font. I just reinstalled xbase and it works now. I haven't been worrying about it but now that you bring it up I thought I would throw in my two cents. kent Raymond A. Ingles wrote: I upgraded (at least, with CD 1) from 2.0 - 2.1 last night, and everything seemed to be fine. I quit dselect, fired up X, and while running X, looked at some notes I had made preparing for the upgrade. I purged xbase, since it's been claimed that it's no longer needed. Everything still ran fine. I powered things off for the night and went to bed. I got up this morning, powered up, logged on, and then: --- $ startx _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. --- What the heck? Did I jump the gun on removing xbase? Any idea what's up, or how to find what's up? Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] Two rules for success in life: 1. Don't tell people everything you know. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
