Just applied this fix to my laptop, which was having the shutdown,
suspend, and hibernate issues. This is the update that went into the
update repo within the last 24 hours.
I’m happy to report that my limited initial testing shows that all three
functions now work properly again.
Am 04.07.2012 00:51, schrieb Jim Henderson:
> Just applied this fix to my laptop, which was having the shutdown,
> suspend, and hibernate issues. This is the update that went into the
> update repo within the last 24 hours.
>
> I’m happy to report that my limited initial testing shows that all three
> functions now work properly again.
>
> Jim
>
The suspend, shutdown problem I initially had with the newer kernel
*1.13 went away by downgrading it some time ago, today for me also the
*1.16 patch came in and I am glad to see that the problem did not
reappear after that update.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
On Tue, 03 Jul 2012 23:08:58 +0000, Martin Helm wrote:
> The suspend, shutdown problem I initially had with the newer kernel
> *1.13 went away by downgrading it some time ago, today for me also the
> *1.16 patch came in and I am glad to see that the problem did not
> reappear after that update.
Yeah, many people reported the older kernel fixed it (which makes sense)
but for me the older kernel didn’t work because it didn’t have the fix
for the touchpad issue on my laptop.
This version has the fixes for shutdown/suspend/hibernate and my
touchpad.
On 07/04/2012 12:51 AM, Jim Henderson wrote:
> I’m happy to report that my limited initial testing shows that all three
> functions now work properly again.
just saying: shouldn’t someone (not me) ask the question of the developers:
How did such a troublesome kernel get signed off and into the update repo?
(and/or)
How much testing was performed on actual hardware (seems like it hit a
LOT of “normal users”), or maybe was all testing done in the OBS
environment?
(and/or)
If tested only or mostly in OBS, what needs to be changed in the testing
regime to avoid repeating a similar widespread problem?