| Summary: | After suspend/resume the whole session dies in a few minutes (back to kdm) | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Richard Homonnai <Chain> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | cfeck |
| Priority: | NOR | ||
| Version: | 4.5 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Richard Homonnai
2011-01-07 23:02:53 UTC
It could be related to video drivers causing an X crash. LXDE does not do OpenGL compositing, so you do not see the bug there. To verify, could you try disabling compositing (desktop effects) in System Settings? No, this still happens when effects are off. It seemed to take longer, but it did exactly the same way yesterday - even with compositing disabled. It still happens with 4.5.5, and I cannot entirely turn off desktop effects. The checkmark is set, but greyed out. Mostly it happens within Firefox, but not using it just extends the time until the session dies. I have tried quite everything with LXDE, I was using xcompmgr, and tried the whole thing. No crash. In KDE, mostly when using Firefox, it still happens. The only thing I can even find is the following line in /var/log/everything/current: Jan 19 21:33:07 [kdm] X server for display :0 terminated unexpectedly Nothing else. I am wondering, if I should try to return 4.4.5, because this bug is really annoying me. Intersting new results. I tried it with another GPU, an nvidia 8400M. Interestingly enough, this also happens with this one, like with the Intel one. How to disable Compositing completely in Xorg 1.9? By the way I always have this in my log: kwin(11916) KWin::Workspace::setupCompositing: KWin has detected that your OpenGL library is unsafe to use, falling back to XRender. kwin(11916): Failed to initialize compositing, compositing disabled kwin(11916): Consult http://techbase.kde.org/Projects/KWin/4.0-release-notes#Setting_up So I guess Compositing is not even active? I managed to disable Composite entirely for my system, Xorg.log tells me it is, and no effects available. Still, the behaviour is reproducible. After waking up from suspend, in a few minute KDE crashes. LXDE stays there, whatever I do, even when using xcompmgr. This is not concerning any KDE programs - I am using then with LXDE without any problems. So I guess it must be KWin, or Plasma, or something like that. I hope someone picks this up, I would be glad to help testing some patches etc. Try disabling Nepomuk and/or Strigi in System Settings > Desktop Search. (In reply to comment #8) > Try disabling Nepomuk and/or Strigi in System Settings > Desktop Search. Never had it running so far, checked it again. Was not enabled. I will try again with KDE 4.6.0, as soon as I can install it on my Gentoo. unfortunately, KDE 4.6 made it worse. It crashes even when not after suspend (but reproducibly does it still then). However, in 4.6 kded freezes and eats up 100% CPU. Also some of the services stay alive, and the only thing you can do to restore things to normal is reboot. (If you simply kill kded, services like Akonadi are going haywire - Cannot start Kopete for instance, as long as you don't reboot!) Quite the same with KDE 4.6.1. It seems the problems with the services are fixed now, but the problem itself still exists. I also tried a different machine, however this one also uses the intel driver. Completeley different kernel though. Still, the problem also happens with that machine. Is there any way to debug what's happening? This ultimately stops using KDE for me (at least the shell) because I use suspend/resume often at my studies. Thanks for the updates. Other ideas: - Software update notifiers. If you are using, for example, a KPackageKit-based update notifier, it could cause a crash when looking for updates after a resume. Try disabling any such components. - Power management. Try disabling anything that is related to power management, such as screen savers, power conserving modes etc. It could cause a crash when switching some power modes. Try to find out if the crash is always happening in the first few minutes, even if you do nothing after a resume, or if it is related to actions your are performing after the resume. Actually, this line
> Jan 19 21:33:07 [kdm] X server for display :0 terminated unexpectedly
indicates that the X server is crashing, which underlines my initial assumption that it is video driver related. You might ask the Xorg maintainers how you can debug the issue, for example, how to get a backtrace from the X crash.
I obtained a backtrace, and even found the problem with this. The bug can be found here: https://bugs.freedesktop.org/show_bug.cgi?id=35477 It's not KDE-related at all. It is caused by x11vnc triggering a bug in RECORD it seems, the only thing KDE has to do with it is that it started x11vnc by a script in .kde4/Autostart - which is only run in KDE. Sorry about the confusion and thanks for the pointers - I can now continue using KDE again! :) |