TDM/kdm is running and lets me log in, but then I only get an xterm entitled "Failsafe"

High again, that was a short trip into paradise... After playing around a bit in TDE, and additionally installing some other handy software (xmms, geeqie, povray, and some others), I just wanted to start copying some files from the old to the new box. But I had chosen a default disk partitioning at install-time, and my /home was only 25GB, which I then wanted to resize. Not knowing what it is all about (first-timer), I followed the recommen- dation to do the resizing when the FS is not mounted, so I logged out, set off `umount /home`, which failed, because some trinity processes did not exit and held files open. Such things happens even with the best software around, so I didn't find it suspicious enough to jot down the files and processes (and I'm still not sure whether they are (one of) the reason(s) for what has happened then. I resized the volume for the /home FS, which was done in a second, rebooted, logged on in TDM as before, but was presented only with one single xterm. No window manager, no kicker, nothing from the previous session... nothing at all... Meanwhile I found my way to the freenode#trinity-desktop channel, where SlavekB tried to help me out with this already. No error output in .xsession-errors; I ran /opt/trinity/bin/kdm manually, redirecting it's stdout and stderr to some files... no output... sure, it writes to a "custom file", namely /var/log/kdm.log, which was already beyond 100MB when I checked. This is, however, full of some lines that say (II) AIGLX: Suspending AIGLX clients for VT switch which happens far too often, but either before or after the TDE session doesn't come up. I just moved all the old log out of my way, to see what it is actually printing when things go wrong. The startup merely copied the X servers log, and it was 68 lines long when the SAK screen appeared, (fortunately) only one of which was such an (II) line as mentioned. After logging in, the log file grew by only two lines, the following ones: QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible what's that? I can't imagine that these lines are a description of the reason for the malfunction. Even before I asked for help on freenode, I tried some possibly curative actions on my own. I moved ~/.trinity to ~/.trinity.old, in the hope there was just something wrong with my config... I also moved other files out of the way of a new session, of which I thought they might have to do with the desktop environment, as there are: ~/.dbus ~/.kderc ~/.qt ~/.xcompmgrrc In the older kdm.log I also found the following message: kdm_config [935] info: Cannot open master configuration file /opt/trinity/share/config/kdm/kdmdistrc That file does indeed not exist, and after I looked into that dir, and read the README file, I used /opt/trinity/bin/genkdmconf --no-old to create a new config, but it was actually the same as the old one, except it had SAK enabled, which SlavekB suggested to deactivate, to see if that may be the reason... there were/are no other trinity processes running before the login and after the failure to ignite the session, just kdm is happily running with nothing to do, and some SAK processes if enabled... Any further suggestions? Thanks in advance, best regards, Jagged -- valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error