Created attachment 372861 [details]
output of 'top -s 1 | tee toptest' during hang, KDE menu was clicked at ~23:05:30
Description of problem:
X hangs for approximately 90 seconds both on initial login and anytime the KDE menu is accessed (click the KDE menu to access apps, right click a plasmoid). The mouse moves, but no other input is taken and the clock and all other video is frozen during that time.
Version-Release number of selected component (if applicable): F12 using the proprietary NVIDIA driver (kmod-nvidia) from rpmfusion-nonfree-updates-testing, kernel kernel-220.127.116.11-127.fc12.x86_64
Steps to Reproduce:
1. Log in to a KDE Session
2. Click the KDE start menu
Hangs 90 seconds before showing the menu
Show the menu immediately
This system was just upgraded from F11 to F12 via preupgrade. Problem did not occur under F11
Created attachment 372862 [details]
strace of /usr/bin/X during hang, KDE menu was clicked at ~23:09:48
You can see a a lot of waiting for SIGALRM during the hang, control returned ~23:11:17
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I have the same setup and see the same behavior. However for me it's just 3-5 seconds but still annoying :)
Exactly the same problem here with x86_64 and i686. KDE hangs for about 20 seconds after several actions like clicking on KDE menu button, ALT+F2 or ALT+CRTL+Fn. The mouse cursor still works but nothing else. I tried kmod-nvidia / akmod-nvidia for x86_64 and kmod-nvidia-PAE / akmod-nvidia for i686. The opensource drivers work (within their limited specifications). I was using F10 for about a year with nvidia drivers and experienced no such problems.
I want to provide useful debug information, but I don't know how to generate "strace of /usr/bin/X". Is this really needed and if yes can you please give me advice how to produce it?
Created attachment 374764 [details]
Output of strace of /usr/bin/X
[root@mimic patrick]# ps ax | grep X
1469 tty1 Ss+ 3:35 /usr/bin/X -br -nolisten tcp :0 vt1 -auth /var/run/kdm/A:0-mtrHix
[root@mimic patrick]# strace -p 1469 -o strace_out.txt
// then click on KDE Kickoff Application Launcher
// result: Desktop freeze, except mouse, for about 23 seconds
Created attachment 374765 [details]
Output of top during freeze
[root@mimic patrick]# top -S > top_out.txt
// X has nearly 100% CPU time during freeze
Created attachment 374767 [details]
Output of dmesg
[root@mimic patrick]# dmesg > dmesg_out.txt
Created attachment 374768 [details]
Output of uname
[root@mimic patrick]# uname -a > uname_out.txt
Created attachment 374769 [details]
Created attachment 374770 [details]
Created attachment 374771 [details]
Created attachment 374772 [details]
Created attachment 374773 [details]
Output of yum info kmod-nvidia (excerpt)
Created attachment 374776 [details]
Output of nvidia-bug-report
[root@mimic patrick]# nvidia-bug-report.sh
Created attachment 374782 [details]
xorg.conf created by nvidia-settings
xorg.conf generated by GUI application 'nvidia-settings'. After reboot the problem is still the same.
In /etc/X11/xorg.conf setting "Composite" to "Disable" solves the problem:
Option "Composite" "Disable"
But now KDE desktop effects can not be enabled, of course.
I think this is a duplicate of bug 533620.
This is definitely a duplicate of bug 533620. I followed the advice given there and updated packaged to xorg-x11-server-*-1.7.1-12.fc12.x86_64.rpm from the Fedora build system (binaries can be found here: http://koji.fedoraproject.org/koji/buildinfo?buildID=142860 ) and now everything works fine. :-)
Closing per comment #18 and comment #19.
*** This bug has been marked as a duplicate of bug 533620 ***