crash on suspend

Bug #254903 reported by James Troup on 2008-08-05
Affects Status Importance Assigned to Milestone

Bug Description

Ever since the latest PPA update, gnome-do has become very unstable for me. The most reproducable pattern I've found is that running suspend via gnome-do inevitably seems to ensure gnome-do won't be running when I resume (i.e. it crashed).

Chris Halse Rogers (raof) wrote :

Is this the same as bug 226816? In particular: is Do still running after suspend, just not responsive? Do you have the Google Calendar or Rhythmbox plugins enabled?

I haven't managed to reproduce this yet, but I don't have either Google Calendar or Rhythmbox enabled. I find it easy to deadlock Do by suspending with GCal enabled, and less-often with Rhythmbox.

Changed in do:
importance: Undecided → Medium
status: New → Incomplete
Bret Kuhns (bkuhns) wrote :

I'm having a very similar problem. After hibernating, gnome-do will work for a while, then eventually stop responding to super+space. I pull up the system monitor and gnome-do is sitting there chugging the majority of my CPU. Some times I can end the process successfully and restart Do, but most of the time ending the process will dead-lock my computer. I had the Google calendar plugin enabled, but have disabled it after reading this bug. We'll see if disabling the plugin fixes this problem...

Alex Launi (alexlauni) wrote :

This bug has expired, and does not seem to happen with the latest release. I use suspend extensively and Do has never crashed on suspend.

Changed in do:
status: Incomplete → Invalid
milestone: none → 0.8.1
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers