Hide Forgot
Description of problem: Sometimes, when I open a flv video file (I don't know about other formats), the entire video portion of the desktop freezes up and no keyboard commands are possible, yet the mouse cursor still moves (cannot right-click the desktop, though). I don't know if this happens only in kde or in gnome et al., too. It has happened with vlc and kaffeine so far. Version-Release number of selected component (if applicable): kernel-2.6.38.2-9.fc15.x86_64 xorg-x11-server-common-1.10.0-7.fc15.x86_64 xorg-x11-drv-intel-2.14.0-4.fc15.x86_64 vlc-1.1.8-1.fc15.x86_64 kaffeine-1.1-2.fc15.x86_64 How reproducible: Right-click a flv video file (other formats, too?) in dolpin and select open with and select a video player. Usually I select vlc but have also experienced the problem with kaffeine. The window opens maximized (haven't tried when not maximized) and usually the sound plays, but the video screen remains black (sometimes video plays for a bit before freezing). The entire display freezes, despite sound continuing, and it is not possible to close the program or execute any other commands, although the mouse pointer moves. I have moved to another virtual terminal and tried killing vlc (or kaffeine), killing plasma-desktop, killing X, etc., but nothing helps, and despite killing, switching back to vt1 still shows the locked display. The only option I have found is to reboot the computer. This has been a problem for at least 3 months, but I thought it had disappeared a few weeks ago, when all of a sudden it occurred again twice yesterday. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I am not sure if x686 is also affected (have not tried playing video on the laptop lately).
Correction: when I kill the X server and switch back to vt1, the screen is black (It just happened again). When I ctrl-alt-backspace to kill the X server, something happens, as I see some of the bootup error messages that displayed during plymouth's run, but kdm fails to reappear to allow me to log back in. I am unable to get any kind of responsive system, neither graphical nor text, on vt1 and am forced to reboot the system.
I should also add that I think this only (usually?) happens when I right-click a video file and select open with and select a video player. When I open the video player from the menu or other means and use the video player's open file dialogue, I think that the error does not occur (or at least not usually).
I am beginning to suspect that this is a kde, perhaps kwin, problem. I am using gnome3 right now and have opened nautilus and have right-clicked various video files and selected open with vlc, kaffeine and gnome-mplayer and I have had no screen lockups.
reassigning to KDE for further investigation. Of course, feel free to send it back if you find out it is our issue.
It's almost certainly X getting wedged, but let's see if some further details will help. What particular (intel) video chipset are you using? (my oldish i945 has largely been rock-solid). Do you have desktop effects enabled when this occurs? (if so, tried turning it off?)
(In reply to comment #5) I used gnome for a few hours last night, watched dozens of videos and not one lock-up. This is certainly a kde problem. Kinfocentre reports Intel 4 Series Integrated Graphics Controller. Gee, that sure seems lacking in specificity. Isn't there a way to get the system to print out what it really is? The handbook says INTEL X3000 (Chipset 965G). I really should try the laptop, which has INTEL (Mobile 915GM/GMS/910GML Express), just to see. Yes, I always have desktop effects enabled. I thought about giving it a try with them off, as gnome doesn't appear to use desktop effects yet. I haven't gotten around to trying without yet, but will give it a go later and will report the results here.
X crashing is an X bug. It may be KDE triggering it, but it's not a KDE bug.
Yep, turning off desktop effects appears to cure the problem. Click and play, no freezes.
(In reply to comment #7) > X crashing is an X bug. It may be KDE triggering it, but it's not a KDE bug. I didn't want for a second argue that X crashing is OK. I just hoped that KDE maintainers would be better able to tell us what exactly is going on which could cause the crash. For reporter, aside from the information requested by KDE maintainer, please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. Thanks in advance.
OK, I have all of the requested files. Unfortunately, kde desktop effects were disabled when I booted, but I enabled them before making a snapshot of the files. It probably doesn't make any difference, though there might be some pertinent addition to messages. And no, I didn't forget the drm.debug=0x04 kernel boot parameter in grub.
Created attachment 490992 [details] an xorg.conf snippet from /etc/X11/xorg.conf.d
Created attachment 490993 [details] xorg log file from currently running session
Created attachment 490994 [details] output of dmesg for current session
Created attachment 490995 [details] a clean /var/log/messages for only this session
I should add that the problem persists in kde-4.6.2.
I am using kde-4.6.3 and kernel-2.6.38.6-27. I have not noticed this problem for a number of weeks and I have expressly clicked directly on files from within dolphin, which used to be the #1 trigger for the problem.