@ssuominen, are you running KDE on ~x86? The problem only seems to affect that arch, and backleveling doesn't fix it. All of my ~amd64 machines are running just fine. There is most definitely a problem, and it cropped up only a week or so ago. I can assure you that there are no misconfigurations on ...

Interesting. Porthole shows dev-libs/glib-2.38.2 available for all ~arch's, not hard masked at all. All my systems run ~arch and so have 2.38.2. Back leveling to 2.36.4-r1 had no effect here.

I solved the Pulseaudio problem by making sure that my user was a member of the audio group.

It's beginning to look like a change was made that affected the x86 side of the house. I'll bet that none of the devs run such systems so such was never tested.

I had a similar problem. My ConsoleKit and emerge.log in /var/log indicated that dev-libs/gobject-introspection-common, dev-libs/glib, and dev-libs/gobject-introspection packages were updated shortly before the problem appeared. All were included as test packages in /etc/portage/package.keywords ...

None at all. I've made sure that all appropriate kernel configs are set. What's curious is that this installation was working just fine before the reboot. No updates or other changes were made immediately before. The kernel has been in use for almost a week before this started.

When logging in to KDM I get the following:

"Warning: Cannot open ConsoleKit session: Unable to open session: Unable to get information about the calling process"

This started spontaneously. Worked just fine on the first login of the day, and after a reboot, there it was.

"ck-list-sessions ...