problem resuming from suspend when gnome-do is running

Bug #230908 reported by Barak
4
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-do

gmone-do seems to work well on my laptop, until i suspend.

when trying to resume from suspend, it takes a LOT of time to resume, if at all.

when gnome-do is not running, resume from suspend works quickly and well.

i'm running Ubuntu 8.04 on Compaq tc4200.

gnome-do version: 0.4.0.1-0ubuntu2 (hardy)

any idea?

Revision history for this message
Richard Seguin (sectech) wrote :

Thank you for reporting this issue,

Could you please attach the output of dmesg after you resume the laptop with gnome-do installed? It might shed some light on the problem.

Thanks,

Richard Seguin

Revision history for this message
Richard Seguin (sectech) wrote :

* Marked as incomplete pending enough information to complete triage

Changed in gnome-do:
status: New → Incomplete
Revision history for this message
Barak (barak-naveh) wrote :

attached is the output of dmesg after resuming from suspend when gnome-do is running.

here is some more (weird) info for the case it gives someone a hint. i know it may sound like a hoax, but it's real.
when my laptop hangs upon resume from suspend, it seems to do something but nothing is displayed. i tried to disconnect it from AC power and reconnect it. i was surprised to find that upon doing that my laptop quickly resumed from suspend, as it was supposed to.

Revision history for this message
Barak (barak-naveh) wrote :

added the requested additional info.

Changed in gnome-do:
status: Incomplete → New
Revision history for this message
Richard Seguin (sectech) wrote :

Note: Marking a bug to new indicates that the bug hasn't been looked at by a triager yet.
* Returning to incomplete as I am currently attempting to triage bug

Changed in gnome-do:
status: New → Incomplete
Revision history for this message
Barak (barak-naveh) wrote :

oh sorry, i'm not familiar with the process.
thought it was set to "incomplete" because it took me time to send the info.

Revision history for this message
Richard Seguin (sectech) wrote :

I looked over the information that you provided, but was unable to see a problem... I also tried to reproduce this on my own system but was unable to recreate the bug... I think at this point marking the bug back to "new" might be appropriate so another triager who has more experience with suspend/resume bugs can look at it...

I'll stay subscribed to the bug to see what happens with it though,

Thanks,

Richard Seguin

Revision history for this message
Richard Seguin (sectech) wrote :

* Returning status to "new"... Triager is unable to complete triage.

Changed in gnome-do:
status: Incomplete → New
Revision history for this message
Richard Seguin (sectech) wrote :

It looks like this issue wasn't solved while I was gone... Changing the status back to incomplete as more information (such as an error message or a fail in a log) is required to confirm this issue.

Changed in gnome-do:
status: New → Incomplete
Revision history for this message
Richard Seguin (sectech) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-do:
status: Incomplete → Invalid
Revision history for this message
Barak (barak-naveh) wrote :

I didn't understand you are waiting for more information.
What information do you want me to provide? I already attached the dmesg in one of the earlier posts. do you need anything else?

Revision history for this message
Richard Seguin (sectech) wrote :

The bug went inactive for more then 30 days, which is why it was closed out... I guess in order to move forward I'll have to get you to look over the ACPI trouble shooting guide and provide any information based upon that...

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Changed in gnome-do:
status: Invalid → Incomplete
Revision history for this message
Richard Seguin (sectech) wrote :

This bug hasn't been updated in quite some time... If this issue still is occurring please change the status back to new.

Thanks,

Richard Seguin

Revision history for this message
Richard Seguin (sectech) wrote :

* Closing out issue due to inactivity

Changed in gnome-do:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.