while implementing the "fast user switching" stuff in kdm/kde, i stumbled over an annoyance: the server always switching to some vt at exit sucks. if the active vt is not the one the server runs on, it should not touch it. that way kdm could manage its own switching stack without annoying intermediate switches (that additionally make my crt's sucky firmware run amok). a patch for tinyx was sent to keithp already. related problem: before alt-ctrl-fx-ing to another vt, the server should check whether this vt is used, like the linux kernel does. otherwise we might allocate a vt for no purpose ... tinyx has this fixed already.
yeah, I'm implementing a -novtswitch for Ubuntu (well, implemented), which doesn't do an initial switch, and also doesn't switch away when it's done the only problem with this approach is that people type 'startx' and expect it to function as a program does -> start the program and show itself (switch VTs to the new one), and then stop the program and hide itself (switch VTs back to textmode) this is why I've implemented it as a flag there's also -sharevts, if you want multiple servers sharing the same VT, but that's total crack
-novtswitch and -sharevts are in HEAD now, closing.
urgs. somehow i missed stoned's ;) mail ... :( -novtswitch is too aggressive - suppressing the initial vt switch is counterproductive in my case. i need to add additional code to compensate it. -sharevts is severely underdocumented, and i must admit that after a quick skim over the code i don't really understand how it works.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.