Bug 605749

Description of problem:

I am not sure if pulseaudio is the problem but these were the last messages in the log file before the freeze occurred. If this should be multiple bugs please let me know which packages to file it for and how to split up the log file messages.

Jun 18 10:00:18 localhost pulseaudio[2007]: module-alsa-card.c: Failed to find a working profile.
Jun 18 10:00:18 localhost pulseaudio[2007]: module.c: Failed to load  module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=no ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.

During the freeze... I have the system monitor applet installed in the panel which I can see functioning properly. I can move the mouse but clicks are unresponsive. Changing to a different virtual terminal worked, and I was able restart the X server. There were error messages (including the one above) in the log file after the restart as well:

Jun 18 10:03:39 localhost gnome-keyring-daemon[1883]: dbus failure unregistering from session: Connection is closed
Jun 18 10:03:39 localhost gnome-keyring-daemon[1883]: dbus failure unregistering from session: Connection is closed
Jun 18 10:03:39 localhost bonobo-activation-server (akshay-3255): could not associate with desktop session: Failed to connect to socket /tmp/dbus-oDQBJNWGNo: Connection refused
Jun 18 10:03:39 localhost console-kit-daemon[1744]: WARNING: Couldn't read /proc/1855/environ: Failed to open file '/proc/1855/environ': No such file or directory
Jun 18 10:03:40 localhost pulseaudio[3288]: pid.c: Stale PID file, overwriting.
Jun 18 10:03:40 localhost pulseaudio[3288]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-oDQBJNWGNo: Connection refused
Jun 18 10:03:43 localhost rtkit-daemon[1868]: Sucessfully made thread 3339 of process 3339 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Jun 18 10:03:43 localhost rtkit-daemon[1868]: Sucessfully made thread 3341 of process 3339 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Jun 18 10:03:43 localhost rtkit-daemon[1868]: Sucessfully made thread 3342 of process 3339 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Jun 18 10:03:43 localhost pulseaudio[3339]: module-alsa-card.c: Failed to find a working profile.
Jun 18 10:03:43 localhost pulseaudio[3339]: module.c: Failed to load  module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jun 18 10:03:43 localhost gdm-simple-greeter[3329]: Gtk-WARNING: gtkwidget.c:5643: widget not within a GtkWindow
Jun 18 10:03:43 localhost gdm-simple-greeter[3329]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width 264 and height -1
Jun 18 10:03:43 localhost gdm-simple-greeter[3329]: WARNING: Unable to parse history: (null)   2#012
Jun 18 10:03:49 localhost gdm-simple-greeter[3329]: WARNING: Failed to send buffer
Jun 18 10:03:49 localhost pulseaudio[3288]: module-alsa-card.c: Failed to find a working profile.
Jun 18 10:03:49 localhost pulseaudio[3288]: module.c: Failed to load  module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=no ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Jun 18 10:03:52 localhost rtkit-daemon[1868]: Sucessfully made thread 3487 of process 3487 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 18 10:03:52 localhost pulseaudio[3487]: pid.c: Daemon already running.

Version-Release number of selected component (if applicable):

How reproducible:
Can't reproduce yet. Happens every so often, but not sure what the conditions are. The last time it happened, I was doing the following:

1. Entered search term in Google Chrome search bar
2. That hangs Google Chrome but not the rest of the desktop
3. Then, I right click on the task button for Google Chrome, and click "Close"
4. This does not close Google Chrome, but makes it operational (yes, crazy)
5. Then, I click on the "Wrench menu" in Google Chrome which brings up the menu partially: just one transparent box with an outline and a shadow.
6. The whole desktop freezes.