Ouch! I missed it! at Date: Sat, 04 Mar 2000 03:28:03 +0900, I wrote:
> I checked BTS, and found this report. > > %%%%% %%%%% %%%%% %%%%% %%%%% %%%%% %%%%% %%%%% %%%%% %%%%% > > | Package: xfree86-common > | Version: 3.3.6-4 > | Severity: important > | > | While yesterdays upgrade from 3.3.6-3 (I believe to remeber) to > | 3.3.6-4, the script /etc/X11/Xsession was modified which may cause > | that no window-manager will be started after starting the session. (snip) > | told me to do). register-window-manager tells that it will "soon > | become obsolete". Obviously this is already true. I had to find out > | the syntax of update-alternatives and manually do a > | > | `update-alternatives --install /usr/bin/x-window-manager \ > | x-window-manager /usr/X11R6/bin/afterstep 10` > | > | which probably should be done by the postinst script of > | xfree86-common. "/usr/X11R6/bin/afterstep" ??? It belongs to afterstep package, not to asclassic package (which is mine). The binary in asclassic package is /usr/X11R6/bin/asclassic. $ apt-cache show afterstep Package: afterstep Version: 1.6.10-1 Priority: optional Section: x11 Maintainer: Jonathon D. Nelson <[EMAIL PROTECTED]> Rene, which do you use, afterstep or asclassic ? If it does not have proper setting in postinst/prerm (using update-alternatives), then you have to file another report on the right package (afterstep). I add cc: to J. D. Nelson for this mail. > | If I'm completely wrong and the postinst script is correct, than my > | trouble could be caused by uninstalling the packet asclassic. I'd be > | glad to provide you with information if that seems to be the cause. I think asclassic is not related to this problem, because /etc/X11/window-manager is not used now, so the remaining entry for asclassic in /etc/X11/window-manager does not have any effect. Anyway, I already have uploaded asclassic_1.1b-12 to close 59534. FYI. -- Taketoshi Sano: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
