I see you've made progress elsewhere in this thread, so just a couple of points below...
On Mon, Nov 23, 2009 at 12:36:42PM -0800, John Jason Jordan wrote: > On Mon, 23 Nov 2009 11:30:08 -0800 > Andrew Sackville-West <and...@farwestbilliards.com> dijo: [...] > > > I'm wondering if you're somehow changing the default selection to be a > > .xsession session and consequently getting an empty session. > > Now we might be getting somewhere. I am not very familiar with what's > under the hood in Linux. What is an .xsession session? users can specify an .xsession or .xinitrc (not sure if gdm uses .xinitrc or not) file to control how their X session is created. Typically this is used when one wants a highly customized configuration using a non-standard windowmanager (if a WM is used at all...) or when starting the X session from a console via startx (what I do). Basically, it is a shell script that is run by X after it sets up the graphics display and in it the user specifies various things they want such as environment variables, starting special services, a window manager etc. When that script exits, then the X session closes and returns the user to the console. But this doesn't sound like your problem, so that's just for your education ;) [...] > Looking at the aptitude logs didn't help - no error messages. I wasn't looking for error messages, but rather information about what packages were being installed or removed that might have provided a clue. REgardless, I know you've got it narrowed down to a local user configuration issue, so good luck with that. A
signature.asc
Description: Digital signature
