Description of problem: If I enter my password incorrectly in KDM, then enter it correctly, the X server shuts down, I'm left with a blank screen, and nothing appears to happen. To remedy this situation I need to switch to another VT by pressing CTRL+ALT+F2, login, type "su", enter the root password, and then type "killall kdm", and finally switch back to the X VT. Version-Release number of selected component (if applicable): kdm-4.2.3-5.fc11.i586 How reproducible: Always Steps to Reproduce: 1. Boot up 2. Attempt to log in to KDM with the right username but the wrong password 3. Log in with the correct username and password Actual results: Screen goes blank. Nothing happens. Expected results: KDE should start Additional info: This does not happen if I enter the correct password on the first attempt.
Based on the description, I most definitely cannot reproduce this. X server hang is usually symptomatic of video driver issues. What video hardware/driver are you using?
(In reply to comment #1) > X server hang Clarification: The X server actually shuts down (why, I do not know), and kdm just sits there. I would expect kdm to restart the X server if it dies, but no. > is usually symptomatic of video driver issues. Indeed, I do have other issues with this driver, which I am currently trying to work around. I will let you know if they affect this bug at all if I manage to work around them. > What video hardware/driver are you using? Driver is Radeon Hardware is ATI Radeon XPRESS 200M 5955 (PCIE) rev 0, according to Xorg.0.log.
Reducing my Virtual so that DRI got enabled seems to have fixed my other display issues - but unfortunately not this one.
This is a driver bug, reassigning.
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), /var/log/dmesg, 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.
Created attachment 348337 [details] Xorg.0.log
Created attachment 348338 [details] xorg.conf I could not reproduce this bug a second time with DRI enabled, so I re-disabled DRI, as shown in this config file.
Created attachment 348340 [details] dmesg > dmesg taken after crash Note the kdm segfault.
*** Bug 508615 has been marked as a duplicate of this bug. ***
*** Bug 510677 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > This is a driver bug, reassigning. I don't think so, I can trigger the bug in a machine with a intel video and a VM with vboxvideo driver, I don't think which the problem is kdm but one library pam or selinux the last crash in intel shows in /var/log/messages: Jul 10 12:23:17 snow kernel: kdm[3483]: segfault at 13dc00 ip 0013dc00 sp bfba7b2c error 7 in libselinux.so.1[13a000+1c000] Jul 10 12:23:17 snow kdm_greet[3493]: Cannot read from core Jul 10 12:23:17 snow kdm[1567]: Unknown session exit code 0 (sig 11) from manager process
Created attachment 351286 [details] dmesg from kdm crash comment #11
Created attachment 351287 [details] Xorg log from kdm crash comment #11 No xorg.conf exist in this machine
The same thing is reproduced in my environment. I personally think it is kdm's problem, and is not responsible of graphic drivers, pam, selinux, and others. I also found out that this can be reproduced by: 1. Leave "Username" blank and hit "Enter". 2. Set focus on "Username" again by hitting "Tab". 3. Try to login. But since I do know nothing specially about window managers and login managers, I don't know the reason why this problem occurs completely X( Oh yes, please note that my graphic card is neither Radeon nor Intel. Mine is GeForce. I was able to reproduce this problem with both Nvidia's proprietary driver and nv driver. Following is an abstract of my /var/log/messages: ----- Aug 27 10:26:41 localhost kernel: agpgart-via 0000:00:00.0: AGP 2.0 bridge Aug 27 10:26:41 localhost kernel: agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode Aug 27 10:26:41 localhost kernel: nvidia 0000:01:00.0: putting AGP V2 device into 4x mode Aug 27 10:26:41 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 0 Aug 27 10:26:41 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 0 Aug 27 10:26:41 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 1 Aug 27 10:26:41 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 1 Aug 27 10:26:45 localhost /sbin/mingetty[1557]: tty1: invalid character 0x1c in login name Aug 27 10:26:47 localhost kernel: kdm[1597]: segfault at 9ecc00 ip 009ecc00 sp bfe1b06c error 4 in libnsl-2.10.1.so[a71000+17000] Aug 27 10:26:47 localhost kdm[1575]: Unknown session exit code 0 (sig 11) from manager process Aug 27 10:26:48 localhost kdm_greet[1605]: Cannot read from core Aug 27 10:26:48 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 1 Aug 27 10:26:48 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 0 Aug 27 10:26:50 localhost init: tty1 main process (1557) terminated with status 1 Aug 27 10:26:50 localhost init: tty1 main process ended, respawning Aug 27 10:28:40 localhost kernel: agpgart-via 0000:00:00.0: AGP 2.0 bridge Aug 27 10:28:40 localhost kernel: agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode Aug 27 10:28:40 localhost kernel: nvidia 0000:01:00.0: putting AGP V2 device into 4x mode Aug 27 10:28:40 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 0 Aug 27 10:28:40 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 0 Aug 27 10:28:40 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 1 Aug 27 10:28:40 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 1 Aug 27 10:28:43 localhost /sbin/mingetty[1635]: tty1: invalid character 0x1c in login name Aug 27 10:28:45 localhost kernel: kdm[1722] general protection ip:4d0c03 sp:bfb672ec error:0 in libglib-2.0.so.0.2000.4[47f000+dd000] Aug 27 10:28:45 localhost kdm[1700]: Unknown session exit code 0 (sig 11) from manager process Aug 27 10:28:45 localhost kdm_greet[1729]: Cannot read from core Aug 27 10:28:45 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 1 Aug 27 10:28:46 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 0 Aug 27 10:28:48 localhost init: tty1 main process (1635) terminated with status 1 Aug 27 10:28:48 localhost init: tty1 main process ended, respawning Aug 27 10:29:47 localhost kernel: agpgart-via 0000:00:00.0: AGP 2.0 bridge Aug 27 10:29:47 localhost kernel: agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode Aug 27 10:29:47 localhost kernel: nvidia 0000:01:00.0: putting AGP V2 device into 4x mode Aug 27 10:29:47 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 0 Aug 27 10:29:47 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 0 Aug 27 10:29:48 localhost kernel: nouveau 0000:01:00.0: Allocating FIFO number 1 Aug 27 10:29:48 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_alloc: initialised FIFO 1 Aug 27 10:29:50 localhost /sbin/mingetty[1759]: tty1: invalid character 0xb2 in login name Aug 27 10:29:55 localhost init: tty1 main process (1759) terminated with status 1 Aug 27 10:29:55 localhost init: tty1 main process ended, respawning Aug 27 10:29:55 localhost /sbin/mingetty[1846]: tty1: invalid character 0xf in login name Aug 27 10:29:59 localhost kdm_greet[1833]: Cannot read from core Aug 27 10:29:59 localhost kdm[1804]: Unknown session exit code 0 (sig 4) from manager process Aug 27 10:29:59 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 1 Aug 27 10:29:59 localhost kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 0 Aug 27 10:30:00 localhost init: tty1 main process (1846) terminated with status 1 Aug 27 10:30:00 localhost init: tty1 main process ended, respawning Aug 27 10:30:00 localhost /sbin/mingetty[1848]: tty1: invalid character 0xe0 in login name Aug 27 10:30:05 localhost init: tty1 main process (1848) terminated with status 1 Aug 27 10:30:05 localhost init: tty1 main process ended, respawning Aug 27 10:30:05 localhost /sbin/mingetty[1849]: tty1: invalid character 0xbd in login name Aug 27 10:30:10 localhost init: tty1 main process (1849) terminated with status 1 Aug 27 10:30:10 localhost init: tty1 main process ended, respawning Aug 27 10:30:10 localhost /sbin/mingetty[1850]: tty1: invalid character 0xe0 in login name Aug 27 10:30:15 localhost init: tty1 main process (1850) terminated with status 1 Aug 27 10:30:15 localhost init: tty1 main process ended, respawning Aug 27 10:55:55 localhost kernel: kdm[1970]: segfault at 6afc00 ip 006afc00 sp bf9229cc error 4 in libXau.so.6.0.0[6ec000+2000] Aug 27 10:55:55 localhost kdm_greet[1977]: Cannot read from core Aug 27 10:55:55 localhost kdm[1309]: Unknown session exit code 0 (sig 11) from manager process -----
Latest updates (kdm-4.3.0) solves this issue for me.
Strange, because something very similar just got reported against 4.3.0: https://bugzilla.redhat.com/show_bug.cgi?id=520240
I tested and isn't fixed yet in Fedora 11 i586 with kdm-4.3.0-9.fc11.i586, the error in /var/log/messages: Aug 30 19:04:41 localhost kernel: kdm[1408]: segfault at 476c00 ip 00476c00 sp bffe10fc error 14 in pam_nologin.so[4a0000+1000] Aug 30 19:04:41 localhost kdm_greet[1415]: Cannot read from core Aug 30 19:04:41 localhost kdm[1329]: Unknown session exit code 0 (sig 11) from manager process and the error don't occurs in Fedora 10 i386 with kdm-4.3.0-9.fc10.i386 both are running in VMs with VirtualBox 3.0.4 in Fedora pam version is pam-1.0.91-6.fc11.i586 and if F10 is pam-1.0.4-4.fc10.i386 but I saw the bug with libX11.so.6.2.0 , pam_deny.so and libglib-2.0.so.0.2000.3 instead of pam_nologin.so as error reported in /var/lib/messages
I'm getting this now as well. Might have some additional details... 1. Happens with gdm and kdm. 2. Happens when logging in remotely (XDMCP). 3. Does not happen with xdm. 4. I'm having this occur with both the nouveau driver and the nvidia proprietary driver (flipped back and forth). 5. This started when I added an old creative pci soundcard to the system. Removing doesn't fix it (maybe there's something in /var somewhere)? 6. I can bring up the console with startx - no issues. 7. ran kdm in debug mode... everything looked ok until I entered the password. here's the debug output from that: Oct 31 14:31:45 kdm: :0[8947] debug: sending int 0 (0x0) to greeter for display :0 Oct 31 14:31:45 kdm_greet[9116] debug: -> 0 (0x0) Oct 31 14:31:45 kdm_greet[9116] debug: V_OK ==9116== ==9116== ERROR SUMMARY: 444990 errors from 965 contexts (suppressed: 9 from 3) ==9116== malloc/free: in use at exit: 963,246 bytes in 19,058 blocks. ==9116== malloc/free: 538,855 allocs, 519,797 frees, 126,956,247 bytes allocated. ==9116== For counts of detected errors, rerun with: -v ==9116== Use --track-origins=yes to see where uninitialised values come from ==9116== searching for pointers to 19,058 not-freed blocks. ==9116== checked 2,309,776 bytes. ==9116== ==9116== LEAK SUMMARY: ==9116== definitely lost: 666,141 bytes in 15,996 blocks. ==9116== possibly lost: 152 bytes in 3 blocks. ==9116== still reachable: 296,953 bytes in 3,059 blocks. ==9116== suppressed: 0 bytes in 0 blocks. ==9116== Rerun with --leak-check=full to see details of leaked memory. Oct 31 14:31:45 kdm: :0[8947] debug: closed greeter for display :0 Oct 31 14:31:45 kdm: :0[8947] debug: greeter for :0 stopped Oct 31 14:31:45 kdm: :0[8947] debug: display :0 exiting with status 30 Oct 31 14:31:45 kdm[8732] debug: select returns 2 Oct 31 14:31:46 kdm[8732] debug: receiving command from sub-daemon for display :0 ... Oct 31 14:31:46 kdm[8732] debug: -> no data Oct 31 14:31:46 kdm[8732] debug: select returns 2 Oct 31 14:31:46 kdm[8732] debug: manager wait returns pid 8947 sig 0 core 0 code 30 Oct 31 14:31:46 kdm[8732] debug: display exited with EX_NORMAL Oct 31 14:31:46 kdm[8732] debug: exitDisplay :0, endState = 0, serverCmd = 0, GoodExit = 1 Oct 31 14:31:46 kdm[8732] debug: killing X server for :0
Ok - I fixed my issue... while I did change a few to many variables to be certain, I believe the issue was actually permissions on /etc/X11. I had added write permissions "temporarily" while I was adjusting screen resolution as a non-root user. I neglected to reset permissions. Caught this on an rpm -Va. Haven't dug too deeply, but I'm guessing that something is refusing to function if /etc/X11 is world writeable.
At least for my issue I've confirmed that making /etc/X11 world writeable yields the same behaviour reported above - i.e., X server restarts after attempting log in from greeter (kdm or gdm). No issues when using startx. X server/driver independent, and with no obvious indication that this is why the X server quit. Don't know whether this is related or not to the issues raised in this thread.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This is no longer happening on my system - works for me.
Still there on both of my laptops in Fedora 12. Both use the intel graphics drivers. So it's unlikely that this is a driver problem. There exists no xorg.conf. SElinux is disabled.
Reporter, could you retest please? Thank you
(In reply to comment #24) > Reporter, could you retest please? Cannot reproduce any more on Fedora 11.
Thank you for letting us know.
I repeat. This bug STILL exists in Fedora 12! I have it on all my Fedora 12 installations - all of them done with preupgrade btw.
I think this bug is mixing several very different issues with the same or similar symptoms.
I think so to. Bjorn, could you please file a bug against xorg-x11 with all the information requested in the comment 5, please? Thank you
Just wanted to collect the information ... and now the bug has vanished. Must have been an update in the last four days?
(In reply to comment #30) > Just wanted to collect the information ... and now the bug has vanished. Must > have been an update in the last four days? Glad to hear it! Thank you for filing the bug report
This bug still appears to be present in my system - hardware details at http://www.smolts.org/client/show/pub_9855ac6b-c48a-47cc-9a72-9bcbbce87dc5 This is a fully up to date F11 system - and all drivers are default - there is no nvidia driver from rpmfusion or anywhere else - just nouveau. This is marked as closed but the problem still persists in this system
Relevant lines from /var/log/messages are: Dec 31 14:05:44 pavilion kernel: kdm[1962]: segfault at 85e4c0 ip 00155f4b sp bf96a360 error 4 in libglib-2.0.so.0.2000.5[121000+de000] Dec 31 14:05:44 pavilion kdm[1935]: Unknown session exit code 0 (sig 11) from manager process Dec 31 14:05:44 pavilion kdm_greet[1969]: Cannot read from core Dec 31 14:05:44 pavilion kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 2 Dec 31 14:05:44 pavilion kernel: nouveau 0000:01:00.0: nouveau_fifo_free: freeing fifo 1 Dec 31 14:16:53 pavilion dhclient: DHCPREQUEST on eth0 to 10.0.0.1 port 67 Dec 31 14:16:53 pavilion dhclient: DHCPACK from 10.0.0.1 Dec 31 14:16:53 pavilion dhclient: bound to 10.0.0.66 -- renewal in 11720 seconds. There is no xorg.conf on this machine. I will attach xorg log files shortly.
Created attachment 381107 [details] xorg log from kdm crash - This was the xorg before re-booting machine after x crashed
Created attachment 381108 [details] xorg log from reboot after kdm crashed This is the second xorg log when the machine started and was running correctly - no attempt to crash kdm was made - this and the previous attachment refer to comment #34
OK, sigh, this time the segfault is in glib2. So far in this report, we've seen segfaults in libnsl, libselinux, libX11 (and pam in other reports) too. Leads me to a big wtf. ?? Maybe it's in the pam stack... somewhere, somehow.
Well, I see this bug still on my netbook - but not on my main workstation. Both are running Fedora 12 upgraded from Fedora 11. The difference is that the netbook uses a 32bit system and the laptop 64bit.
I think there are several different bugs with similar symptoms here, some fixed, some not.
I had the exact same problem. But I found an empty file with name "-" in /etc/X11 directory. After deleting it this bug no longer happening on my system.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
kdm crash after fail password, it is solved for me , I don't have this issue anymore , after update fedora 13.
(In reply to comment #41) > kdm crash after fail password, it is solved for me , I don't have this issue > anymore , after update fedora 13. sorry today I got a crash again, one fail password, one good password and kdm down. I have a fully update F13, so this a F13 bug not F11 .
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Seeing this on F13 on a different machine. No strange empty files or world-writeable permissions in /etc/X11. Re-re-opened.
Relevant lines from /var/log/messages: Sep 29 07:44:52 natgreen kernel: kdm[3884]: segfault at a0b580 ip 0036c135 sp bf9fee70 error 4 in libglib-2.0.so.0.2400.1[333000+ff000] Sep 29 07:44:52 natgreen abrt[3905]: saved core dump of pid 3884 (/usr/bin/kdm) to /var/spool/abrt/ccpp-1285742692-3884.new/coredump (839680 bytes) Sep 29 07:44:52 natgreen abrtd: Directory 'ccpp-1285742692-3884' creation detected Sep 29 07:44:52 natgreen kdm_greet[3887]: Cannot read from core Sep 29 07:44:52 natgreen kdm[1599]: Unknown session exit code 0 (sig 11) from manager process Sep 29 07:44:53 natgreen abrtd: New crash /var/spool/abrt/ccpp-1285742692-3884, processing Sep 29 07:44:53 natgreen abrtd: Registered Action plugin 'RunApp' Sep 29 07:44:53 natgreen abrtd: RunApp('/var/spool/abrt/ccpp-1285742692-3884','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
Created attachment 450395 [details] abrt log
I also still have it, at least on my netbook (intel video). F13 i386 and up to date. I used to have it also on my workstation nvidia (X86_64). After reading this thread, i will re-check again all F13 instalations. 1 - Type incorrecly your password in KDM 2 - Type your password correctly in KDM (& Hit ENTER) Result: No more X I must switch to another VT and then do an init 3 and then an init 5. Sep 29 09:48:07 xxxxxxx kernel: kdm[1422]: segfault at 4f7580 ip 00d1a135 sp bfb52d30 error 4 in libglib-2.0.so.0.2400.1[ce1000+ff000] Sep 29 09:48:08 xxxxxxx abrt[1473]: saved core dump of pid 1422 (/usr/bin/kdm) to /var/spool/abrt/ccpp-1285764487-1422.new/coredump (839680 bytes) Sep 29 09:48:08 xxxxxxx abrtd: Directory 'ccpp-1285764487-1422' creation detected Sep 29 09:48:08 xxxxxxx kdm_greet[1425]: Cannot read from core Sep 29 09:48:08 xxxxxxx kdm[1376]: Unknown session exit code 0 (sig 11) from manager process Sep 29 09:48:08 xxxxxxx abrtd: New crash /var/spool/abrt/ccpp-1285764487-1422, processing Sep 29 09:48:08 xxxxxxx abrtd: Registered Action plugin 'RunApp' Sep 29 09:48:08 xxxxxxx abrtd: RunApp('/var/spool/abrt/ccpp-1285764487-1422','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .') Sep 29 09:48:53 xxxxxxx init: system-setup-keyboard main process (837) killed by TERM signal Sep 29 09:48:54 xxxxxxx init: start-ttys main process (1636) terminated with status 1 Sep 29 09:48:56 xxxxxxx kernel: usb 2-1.2: USB disconnect, address 4 Sep 29 09:48:57 xxxxxxx kernel: usb 2-1.2: new low speed USB device using uhci_hcd and address 5 Sep 29 09:48:57 xxxxxxx kernel: usb 2-1.2: New USB device found, idVendor=0458, idProduct=003a Sep 29 09:48:57 xxxxxxx kernel: usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 29 09:48:57 xxxxxxx kernel: usb 2-1.2: Product: Optical Mouse Sep 29 09:48:57 xxxxxxx kernel: usb 2-1.2: Manufacturer: Genius Sep 29 09:48:57 xxxxxxx kernel: input: Genius Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input12 Sep 29 09:48:57 xxxxxxx kernel: generic-usb 0003:0458:003A.0004: input,hidraw2: USB HID v1.11 Mouse [Genius Optical Mouse] on usb-0000:00:1d.0-1.2/input0 Sep 29 09:49:02 xxxxxxx init: start-ttys main process (1713) terminated with status 1 Sep 29 09:49:03 xxxxxxx kernel: composite sync not supported Sep 29 09:49:03 xxxxxxx kernel: composite sync not supported Sep 29 09:49:03 xxxxxxx kernel: composite sync not supported Sep 29 09:49:13 xxxxxxx kernel: kdm[1724] general protection ip:431135 sp:bf9b1cb0 error:0 in libglib-2.0.so.0.2400.1[3f8000+ff000] Sep 29 09:49:13 xxxxxxx abrt[1745]: saved core dump of pid 1724 (/usr/bin/kdm) to /var/spool/abrt/ccpp-1285764553-1724.new/coredump (839680 bytes) Sep 29 09:49:13 xxxxxxx abrtd: Directory 'ccpp-1285764553-1724' creation detected Sep 29 09:49:13 xxxxxxx kdm_greet[1727]: Cannot read from core Sep 29 09:49:13 xxxxxxx kdm[1711]: Unknown session exit code 0 (sig 11) from manager process Sep 29 09:49:13 xxxxxxx abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1285764487-1422) Sep 29 09:49:13 xxxxxxx abrtd: Deleting crash ccpp-1285764553-1724 (dup of ccpp-1285764487-1422), sending dbus signal Sep 29 09:49:30 xxxxxxx init: system-setup-keyboard main process (1651) killed by TERM signal Sep 29 09:49:30 xxxxxxx init: start-ttys main process (1841) terminated with status 1 Sep 29 09:49:34 xxxxxxx init: start-ttys main process (1907) terminated with status 1 Sep 29 09:49:35 xxxxxxx kernel: composite sync not supported [root@gxxxxx ~]# uname -a Linux xxxxx.xxxxx 2.6.34.7-56.fc13.i686 #1 SMP Wed Sep 15 03:33:58 UTC 2010 i686 i686 i386 GNU/Linux [root@xxxxxx ~]# yum list installed kdm Loaded plugins: presto, refresh-packagekit Installed Packages kdm.i686 4.4.5-1.fc13 @updates
Same for me. I still have the problem on my netbook. eeePC-1005HA-M with intel atom 270. My main laptop on intel santa rosa plattform makes no problem.
*** This bug has been marked as a duplicate of bug 605156 ***