<SOLVED> 2010 KDE on again, off again "sleep" support and other gripes.....

[kaptain_zero]

I've mentioned this before and there is beginning to be a distinct pattern to this issue. Every "second" time I do a system update with Synaptic, starting with the Beta releases, sleep becomes broken and I cannot log back in when the system wakes up from a sleep session because my keyboard input isn't recognized (mouse still works though). I CAN select to start a new session, at which point the keyboard IS recognized and I can type in my user name a log in password.  The original login from the pre-sleep session is still there, so when I shut down, I have to shut down 2 sessions with the same user/password.  It's downright weird as it seems to break every second time there's updates to install and the other half of the time, the updates fix the issue and I can once again suspend to "sleep" when I'm leaving the computer.

Fortunately, booting is much faster now, and so I can live with this issue, but gosh darn..... the next time this is fixed....I'm going to hesitate to do any further updating as I just plain prefer to put the confuser to sleep rather than shut down and have to do a full boot the next time I sit down at the keyboard.

I'm also still unable to get "keytouch" to work as it used to in the past... I don't really understand why. During shutdown, I get a bunch of "Loop detected" warnings, one refers to a config file for keytouch but there's a bunch more as well... and they are sort of scrambled and hard to actually read... but once past the loop warning, I get and orderly flow of reports as the system shuts down.

This, by the way, occurs on two entirely different computers (hardware wise), running two different desktops (one KDE, one LXDE)  and the scrambled "loop" warnings are normally hidden behind the shutdown bot splash (I've set my system to "verbose", without the bootsplash so I can see some of the issues as they happen.

Ultimately, I'm super happy with the 2010 PClos, been running PClos since the 2007 release and have not found anything I like better. Still, these quirks are irritating, and the On again, Off again "Sleep" problem bugs me the most! Well.... that and not being able to get Keytouch to work!

Regards

Christian, aka

Kaptain "Why didn't I become a computer programmer so I could figure this out on my own?" Zero

[Riki]

I've mentioned this before and there is beginning to be a distinct pattern to this issue. Every "second" time I do a system update with Synaptic, starting with the Beta releases, sleep becomes broken and I cannot log back in when the system wakes up from a sleep session because my keyboard input isn't recognized (mouse still works though). I CAN select to start a new session, at which point the keyboard IS recognized and I can type in my user name a log in password.  The original login from the pre-sleep session is still there, so when I shut down, I have to shut down 2 sessions with the same user/password.  It's downright weird as it seems to break every second time there's updates to install and the other half of the time, the updates fix the issue and I can once again suspend to "sleep" when I'm leaving the computer.

Fortunately, booting is much faster now, and so I can live with this issue, but gosh darn..... the next time this is fixed....I'm going to hesitate to do any further updating as I just plain prefer to put the confuser to sleep rather than shut down and have to do a full boot the next time I sit down at the keyboard.

I'm also still unable to get "keytouch" to work as it used to in the past... I don't really understand why. During shutdown, I get a bunch of "Loop detected" warnings, one refers to a config file for keytouch but there's a bunch more as well... and they are sort of scrambled and hard to actually read... but once past the loop warning, I get and orderly flow of reports as the system shuts down.

This, by the way, occurs on two entirely different computers (hardware wise), running two different desktops (one KDE, one LXDE)  and the scrambled "loop" warnings are normally hidden behind the shutdown bot splash (I've set my system to "verbose", without the bootsplash so I can see some of the issues as they happen.

Ultimately, I'm super happy with the 2010 PClos, been running PClos since the 2007 release and have not found anything I like better. Still, these quirks are irritating, and the On again, Off again "Sleep" problem bugs me the most! Well.... that and not being able to get Keytouch to work!

Regards

Christian, aka

Kaptain "Why didn't I become a computer programmer so I could figure this out on my own?" Zero

I share your irritation Christian. A buggy system is annoying/time consuming and bugs me as well. 

[kaptain_zero]

Update: After a second fresh install.... everything is working fine and things have returned to the rock solid performance I got so used to with the earlier versions of PClos. I'd almost forgotten about this post but felt I should revisit and mark it solved..... It must have been the gremlins!

Keytouch remains none functional, but that is a Keytouch issue rather than a PClos issue.  Instead, I've set power management to allow the use of the power button on the computer case to make the computer suspend to ram and it works a treat!

Regards

Christian