Some stuff broke today when I upgraded my Ubuntu Jaunty machine to Karmic. Here's what fixed the problems that I've run into so far:
The version of GDM in Karmic no longer runs ~/.xsession at login. To add an xsession option to GDM, create an /etc/X11/sessions/Xsessions.desktop file containing:
[Desktop Entry]
Name=Xsession
Comment=This runs ~/.xsession
Exec=/etc/X11/Xsession
(from this bug report)
I also ended up with a long delay between entering my password and seeing the window manager start. This page suggested that xsplash may be to blame. Sure enough, /var/log/gdm/xsplash-user.log showed the same 15-second delay and sudo dpkg --purge xsplash ubuntu-desktop fixed it.
GDM's "ready to log in" sound came back even though I'd previously disabled it in /etc/gdm/custom.conf. While I haven't confirmed that it's fixed yet, this page suggests that sudo -u gdm gconftool-2 --set /desktop/gnome/sound/event_sounds --type bool false will take care of it (yes, it does).
I'm using Nvidia's TwinView stuff to stretch the display over two monitors, and GDM's login prompt now ends up on the right-most monitor instead of the left one. I haven't tried to track this down yet.
I've noticed a few pops over my speakers when booting up / logging in / starting apps, so presumably something weird is going on between PulseAudio and ALSA.
A script that was using ruby's xosd bindings suddenly stopped being able to find the Trebuchet MS font; the upgrade process uninstalled the msttcorefonts package, but it looks like the font is still installed, and the XLFD that I was using looks like it works in xfontsel. I switched the script to use liberation.sans instead and it seems fine.
Everything else seems okay so far. I was expecting encfs problems, but it worked after manually porting over a change to /etc/pam.d/common-auth.
Edit: I was a bit hasty; sound playback is hosed after a reboot. I was expecting it to be the same issue that Jaunty had with everything getting muted at boot, but I still get nothing after adjusting levels with alsamixer. On a brighter note, I was sure that my laptop would be rendered unbootable due to initrd vs. full-disk-encryption issues as happened after going from Intrepid to Jaunty, but this upgrade seems fine on that front.
Edit again: Sound seems to be working after running gnome-volume-control once. Beware, the levels are kind of wonky (~30% in gnome-volume-control seems to equal 77% in alsamixer), so don't almost blow out your speakers and ears like I just did. I ran into problems with MPD hanging after seeking a few times until I switched it to use PulseAudio instead of ALSA by replacing my old audio_output section with:
audio_output {
type "pulse"
name "PulseAudio output"
}and adding
mixer_type "disabled". Who knows if it'll still work after a reboot? I miss the days when everything was controlled by easy-to-edit config files. :-(One more edit: To make sound not muted at startup, I had to do the same thing as in Jaunty, namely comment out the mute_and_zero_levels call in the stop handler near the end of /etc/init.d/alsa-utils. I'm happy to see that cpufreqd works correctly now — there appeared to be a kernel bug in Jaunty that erroneously rejected some frequency changes as invalid, which resulted in my 1.835 Ghz laptop being always stuck at 1 Ghz, even when plugged in to AC.