On Thu, 9 Sep 2004, Erik Steffl wrote: > problem 1 (that's just something to be careful about): if you just > have the default x-window-manager it can be replaced during update and > when you restart WM the X session will crash/end. > > problem 2 (IMO serious alternative issue): even if you set up the > x-window-manager to whatever you want manually and alternatives promises > to not touch it (see the docs) it actually does change it (it switches > the x-window-manager to another WM), I am not sure why because I always > found out about it too late. You restart your WM and the X session is gone.
Well, I don't administrate the boxes that I'm using. I'm just an end user. If the window manager is changed, that's fine. I just want my programs to load on login without having to duplicate the X startup scripts. I'm surpised that the X startup scripts take this all or nothing approach. You can either take the system config or short circuit it with .Xsession or .xinitrc. There really should be a user file that can be sourced even if the two other files do not exist and the system startup is used. This would allow users such as myself to move a X startup script from one machine to another without modification and without worrying about which window manager is installed on the machine. > I filed the bug, there was a discussion on mailing list (iirc > debian-devel) etc. no result (other than nothing:-). not sure if the > problem still persists (I am not using x-window-manager anymore). Can an end user such as myself file a bug report or do I have to email a developer or maintainer? I'd really like to see the feature that I described above added to Debian. I'd be glad to do it myself as it just looks like shell scripts for the X startup. How does one get involved with Debian to contribute such changes? -- Matt Perry | matt at primefactor dot com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]