Bug 194573

Summary: Random X.org freezing in KDE4 across multiple distros, using Intel 965GM chipset on 64-bit linux
Product: unknown Reporter: kawk256
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andresbajotierra, finex
Priority: NOR Keywords: investigated, triaged
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kawk256 2009-05-29 18:13:13 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Unlisted Binary Package

Recently, I switched to using KDE 4.2.3, from using a completely different window manager (awesome, for those who care). I'd heard good things about KDE4, so I decided to try it.

I am currently using Arch Linux (www.archlinux.org), updated on the 29th of May (today), with the xorg X server, version 1.6.1.901-1. The problem is not unique to Arch linux, as it propagates on Debian Sid and Squeeze as well, using a similar X server version.

My computer is an Acer Aspire laptop, using an Intel T5450 1.67GHz dual-core processor, with 2.5GB of RAM, and using an Intel X3100 graphics card (965GM chipset), and I use the intel X.org driver. The computer is just over a year old.

Onto the problem itself: About once every half hour or so, the display freezes. All keyboard input is disabled (CTRL-ALT-F1, CTRL-ALT-BACKSPACE do not do anything, and of course regular typing does not do anything), the display stops updating (the clock freezes), but it is still possible to move the mouse. Connecting to the computer via SSH reveals that the computer is still operational, it has not frozen, but that the display is not operational. The kernel, daemons, etc. are all still fine, only X has crashed. Killing X and KDM (requires a -9 signal, a SIGKILL) does work, but restarting them remotely does not do anything other than disable the ability to move the mouse around the screen. I cannot reproduce the problem, as it occurs spontaenously. I believe it may be my video driver, although I am not certain.

The problem does not propagate on other window managers, it only occurs during the usage of KDE 4 or any KDE 4 applications. GNOME appears to work perfectly.

This may be a X bug, not a KDE bug, but since KDE appears to be the trigger, I assume that this would be the place to report it. If I am mistaken, I apologize ahead of time.

Thank you for your time.
Comment 1 Dario Andres 2009-06-04 22:10:21 UTC
What is your intel drivers version? What is your kernel version ? 
I remember this issue when using the 2.7.x versions. (They are a bit buggy if the user is using a kernel < 2.6.30.)
BTW: there are some related forum threads on archlinux about this:

http://bbs.archlinux.org/viewtopic.php?id=71703
http://bugs.archlinux.org/task/14594

Actually, I reverted to the intel-legacy drivers (2.4.x) and things are working properly now

Regards
Comment 2 kawk256 2009-06-04 23:32:12 UTC
I believe I am using the 2.7.1-1 version of the Intel video driver, a 2.6.29-3 kernel, and mesa 7.4.2-1, if that helps at all.

Someone on the #archlinux IRC channel suggested I try a newer kernel and driver version that is available in the testing repositories for Arch.

Thank you for those links, by the way. I am glad to see that it's not just me. I will simply wait, then, for Intel to fix this issue, or for someone else to come up with a solution.

Thanks.
Comment 3 Dario Andres 2009-06-04 23:39:00 UTC
Quick workaround: install the "xf86-video-intel-legacy" (it will remove "xf86-video-intel"). If I remember correctly you don't need to change anything else. 
Thanks
Comment 4 FiNeX 2009-08-17 14:42:12 UTC
I've had that exact freeze for some months until one/two years ago (with nvidia gpu). Does some keyboard led blinks too? It was an xorg/kernel related problem and it were widely discussed on ubuntu launchpad for example.

Anyway, did you solved followin the hint from Dario?
Comment 5 kawk256 2009-08-27 04:48:17 UTC
Yes, sorry. Using the legacy drivers does indeed solve this problem, but it also introduces other problems that have since been fixed in the newer versions of the driver. So, it's a bit of a trade-off between stablity and usefulness.

The keyboard LEDs do not blink, by the way.

The Arch Linux bug tracker entry for this bug: http://bugs.archlinux.org/task/14594.

Thanks again.
Comment 6 Dario Andres 2009-09-04 22:56:20 UTC
Can you check this against the last intel drivers on Arch ? They have been working good for me. Thanks
Comment 7 kawk256 2009-09-08 16:40:17 UTC
I have not yet tested with the new 2.8.1 driver. I will give it a try, and report the results in a few days.
Comment 8 Andrew Crouthamel 2018-09-20 03:05:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-21 04:44:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!