AW: Re: Cannot suspend now?

Israel israeldahl at
Fri Jun 6 14:52:09 UTC 2014

On 06/05/2014 11:06 PM, c. marlow wrote:
> On Wed, Jun 4, 2014 at 1:11 PM, c. marlow <chris at> wrote:
>> On 06/04/2014 07:54 AM, Israel wrote:
>>> On 06/04/2014 12:33 AM, c. marlow wrote:
>>>> on 06/03/2014 10:55 PM, leszek.lesner at wrote:
>>>>> Hi,
>>>>> Check your free ram.
>>>>> If this problem only occurs after some time of work on the PC the
>>>> ram might run full and there is not enough free to suspend to ram
>>>> (hence it times out)
>>>>> Greetings
>>>>> Leszek
>>>> =====================================================================
>>>> I checked and it said it was only using 200 MB out of 2 gigs... Odd....
>>>> Christopher
>>> Hi,
>>> Did you update the kernel package recently?  If so, you might try
>>> booting into the older kernel to see if this is a bug in the current
>>> version.  The screenshots indicate a 'kernel oops'... so it would be
>>> worth trying an older kernel.  If you are unfamiliar with how to do
>>> this, when you turn on your computer (assuming you have BIOS not EFI)
>>> you will see the BIOS screen.
>>> After this hold down the 'SHIFT' key.  This will display your Grub2 menu
>>> screen.  Choose the 'Advanced options for Ubuntu' (I don't remember the
>>> entry name verbatim, sorry if I am a bit off).
>>> You will then enter a sub-menu.  Simply choose the kernel version before
>>> 3.13.0-27 (i.e. linux 3.13.0-26)
>>> Then boot normally.  If the problem is fixed, you now know where the
>>> issue is.  If it is not... there will be some digging to do.
>> =======================================================
>> Oh, I let KSPLICE do the updating for me to where I dont have to reboot so much kind of one of the reason's I got away from windows :X.
>> It works very well, no errors updates the kernel and I dont have to reboot. ^_^
> ===============================
> and things just got weirder... I have now rebooted and now using
> kernel something .24 I remember that much I was using .27 when these
> screenshots were taken:
> its funny STANDBY works in XUBUNTU perfectly, and in KDE but gnome 3,
> and LU and Unity desktops it all goes haywire I dont understand that?
> Christopher
Sometimes having multiple power management utilities can cause some
serious issues.
You may be experiencing this, if all those DE are installed in the same
And some of the issues may be related to the order in which you login to
the various DE.
This is one of the major problems I have had in using multiple DE at the
same time.
It has been this way for as long as I have tried using multiple DE.  I
don't very often install KDE, so I can't comment on it.  I usually use
Unity, LXDE or XFCE (and before Unity it was Gnome 2 that I used).  I
wonder if these issues are present in other Distros (like Fedora or even
I suppose this has something to do with the default settings for each
respin, and the way they autostart the power management.

Anyone else have any thoughts?


More information about the Lubuntu-users mailing list