Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

====================================================================

UPDATE

I've still got Gnome/Metacity installed so I logged into that (still used KDM) and the problems listed below seem to not exist. I could go into Suspend and it will resume with no problems. Switching from my X session to a TTY session doesn't break anything... so I'm going to rule out Xorg, unless it's an Xorg issue caused by Kwin/Plasma/KDE (any variety still not sure).

====================================================================

This is going to be an evolutionary question so bare with me. Hopefully at the end it will be a great resource for this problem. If that turns out to be unnecessary then I'll edit accordingly. I'm just not sure all the right questions to ask (that's why I'm here).

I'm running Kubuntu with Kwin (latest) as my window manager. I'm loving it, I'm ready to remove all things Gnome. I've updated to the latest Kernel (2.6.30) for the updates to the latest Intel graphics drivers since I have an integrated Intel (950?) graphics device.

After having resolved similar issues in plain-old-Ubuntu I'm having some regressions it seems with my display and can't seem to figure it out.

Everything boots fine, runs fine until I switch away from my desktop session. If I suspend to RAM or switch to a TTY session once I resume or switch back to my active desktop session my window manager doesn't come back properly. The bottom panel is gone however my background and widgets (Plasmoids?) appear. No windows are viewable, I can execute Krunner with Alt+F2 but it doens't show, however if I type anything and execute it seems to not mind running things, they just aren't viewable.

Question #1
Where do I even start to look to find what is causing this? Which log will be the most helpful?

share|improve this question

1 Answer 1

Where to look for the logs?
Check the /var/log/Xorg.0.log and /var/log/syslog files first for error messages. Also, take a snapshot of ps -ef output for the before and after scenarios to rule out any processes crashing when you switch back to the desktop session.

Suspend to RAM has been problematic, but the issue with switching to TTY should be easier to tackle.

share|improve this answer
    
I'm still going to do more looking into this, just haven't had a lot of personal computing time this week to hash it out.. plus Oblivion calls! –  codeLes Aug 28 '09 at 14:13

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.