No shutdown/restart/standby after hibernate

[mwesten]

On 10/26/2010 10:01 AM, James Laska wrote:
> On Mon, 2010-10-25 at 21:37 -0400, mwesten wrote:
>    
>> On 10/25/2010 08:47 PM, Adam Williamson wrote:
>>      
>>> On Mon, 2010-10-25 at 20:39 -0400, mwesten wrote:
>>>
>>>        
>>>>>> Had another thought about this. There's a forum poster reporting similar
>>>>>> issue:
>>>>>>
>>>>>> http://forums.fedoraforum.org/showthread.php?t=253221
>>>>>>
>>>>>> (is that you, Steven?) and it made me think of this bug jlaska reported:
>>>>>>
>>>>>>              
>>>>> Nah - not me... Interestingly enough though, I can't reproduce this
>>>>> right this second. I'll do some more testing after having a bit of food.
>>>>>
>>>>>
>>>>>            
>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=643367
>>>>>>
>>>>>> can you check the ck-list-sessions output?
>>>>>>
>>>>>>              
>>>>> James reported in his bug he can't reproduce reliably either. If you all
>>>>> have the same bug, it seems to me like this isn't a bug you hit every
>>>>> time, but we haven't identified the trigger for it yet...
>>>>> -- 
>>>>> Adam Williamson
>>>>>
>>>>>            
>>>> I'm the forum poster.  In my case, the trigger is a reboot.  Like so,
>>>>
>>>> Boot - login - suspend/resume - see problem - logout/in - suspend/resume as desired with no further trouble.
>>>> Shutdown&   reboot - login - suspend/resume - see problem again...
>>>>
>>>>          
>>> That's interesting, thanks for the information. Did you check the output
>>> of ck-list-sessions in each 'problem' and 'non-problem' case? Thanks!
>>>
>>>        
>> Actually, it may be more accurate to say the trigger is a
>> suspend/resume, a logout/login is a fix, and the reboot is a reset...
>>
>> If I boot and login, everything is fine until I suspend/resume.  Then
>> there are problems until I either logout and login again, or reboot.
>>
>> If I boot, login, then logout and login again at any time before
>> suspending, everything works right.
>>
>> I'll check out the sessions output in both cases and let you know.
>>      
> Instead of logging out, and back in ... the ConsoleKit maintainer
> suggested another workaround of changing tty's to force ck-list-sessions
> to re-active the current login.
>
> I haven't tested this yet ... but plan to shortly.
>
> Thanks,
> James
>    
Yes, a quick CTRL-ALT-F2/CTRL-ALT-F1 does appear to take care of it too.