Description of problem: After logging in from KDM, I'm left with a black screen and a blinking cursor in the upper left corner. Version-Release number of selected component (if applicable): kdebase-workspace 4.4.5-1.fc13 How reproducible: pseudo-random, sometimes it happens 2 or 3 times, or nothing hapens for weeks. Steps to Reproduce: 1. boot 2. type your username and a fake/false/wrong password 3. re-type your correct password Actual results: blank screen. ALT+F1, login and reboot the system. (or change runlevels 5->3->5) Expected results: load kde after login. Additional info: kernel 2.6.34.7-61.fc13.i686 xorg-x11-drv-intel.i686 2.11.0-5.fc13 It is an annoying issue to report. No pattern. I have experienced this issue in different machines (all f13 32/64 bit, intel/nvidia) at least once per machine in the past. abrt: component: kdebase-workspace reason: Process /usr/bin/kdm was killed by singnal 11 (SIGSEV) messages: Oct 31 19:17:10 xxxx kernel: kdm[1386]: segfault at 459580 ip 0079e135 sp bfeb7c20 error 4 in libglib-2.0.so.0.2400.1[765000+ff000] Oct 31 19:17:11 xxxx abrt[1407]: saved core dump of pid 1386 (/usr/bin/kdm) to /var/spool/abrt/ccpp-1288563430-1386.new/coredump (839680 bytes) Oct 31 19:17:11 xxxx abrtd: Directory 'ccpp-1288563430-1386' creation detected Oct 31 19:17:11 xxxx kdm[1342]: Unknown session exit code 0 (sig 11) from manager process Oct 31 19:17:11 xxxx kdm_greet[1389]: Cannot read from core Oct 31 19:17:11 xxxx abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1288563337-1353) Oct 31 19:17:11 xxxx abrtd: Deleting crash ccpp-1288563430-1386 (dup of ccpp-1288563337-1353), sending dbus signal Oct 31 19:17:36 xxxx init: system-setup-keyboard main process (855) killed by TERM signal Oct 31 19:17:36 xxxx init: tty (/dev/tty3) main process (1349) killed by TERM signal Oct 31 19:17:36 xxxx init: tty (/dev/tty4) main process (1351) killed by TERM signal Oct 31 19:17:36 xxxx init: tty (/dev/tty5) main process (1357) killed by TERM signal Oct 31 19:17:36 xxxx init: tty (/dev/tty6) main process (1360) killed by TERM signal Oct 31 19:17:36 xxxx avahi-daemon[1015]: Got SIGTERM, quitting. Oct 31 19:17:36 xxxx avahi-daemon[1015]: Leaving mDNS multicast group on interface virbr1.IPv4 with address 172.16.40.1. Oct 31 19:17:37 xxxx kernel: composite sync not supported Oct 31 19:17:37 xxxx libvirtd: 19:17:37.106: warning : qemudDispatchSignalEvent:396 : Shutting down on signal 15 Oct 31 19:17:37 xxxx abrtd: UnRegistered Reporter plugin Bugzilla Oct 31 19:17:37 xxxx abrtd: UnRegistered Analyzer plugin CCpp Oct 31 19:17:37 xxxx abrtd: UnRegistered Analyzer plugin Kerneloops Oct 31 19:17:37 xxxx abrtd: UnRegistered Reporter plugin KerneloopsReporter Oct 31 19:17:37 xxxx abrtd: UnRegistered Action plugin KerneloopsScanner Oct 31 19:17:37 xxxx abrtd: UnRegistered Reporter plugin Logger Oct 31 19:17:37 xxxx abrtd: UnRegistered Analyzer plugin Python Oct 31 19:17:37 xxxx abrtd: UnRegistered Database plugin SQLite3 Oct 31 19:17:37 xxxx abrtd: Got signal 15, exiting Oct 31 19:17:42 xxxx acpid: exiting Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> caught signal 15, shutting down normally. Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (wlan0): now unmanaged Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (wlan0): device state change: 3 -> 1 (reason 36) Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (wlan0): cleaning up... Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (wlan0): taking down device. Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (eth0): now unmanaged Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (eth0): device state change: 2 -> 1 (reason 36) Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (eth0): cleaning up... Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> (eth0): taking down device. Oct 31 19:17:43 xxxx NetworkManager[1003]: <info> exiting (success) Oct 31 19:17:43 xxxx init: Disconnected from system bus Oct 31 19:17:43 xxxx console-kit-daemon[1416]: WARNING: no sender#012 Oct 31 19:17:43 xxxx rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" Oct 31 19:17:43 xxxx auditd[923]: The audit daemon is exiting. Oct 31 19:17:43 xxxx kernel: type=1305 audit(1288563463.530:20): audit_pid=0 old=923 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 Oct 31 19:17:44 xxxx cpuspeed: Disabling ondemand cpu frequency scaling governor Oct 31 19:17:44 xxxx kernel: Kernel logging (proc) stopped. Oct 31 19:17:44 xxxx rsyslogd: [origin software="rsyslogd" swVersion="4.4.2" x-pid="950" x-info="http://www.rsyslog.com"] exiting on signal 15. Oct 31 19:18:14 xxxx kernel: imklog 4.4.2, log source = /proc/kmsg started. Oct 31 19:18:14 xxxx rsyslogd: [origin software="rsyslogd" swVersion="4.4.2" x-pid="941" x-info="http://www.rsyslog.com"] (re)start Oct 31 19:18:14 xxxx kernel: Initializing cgroup subsys cpuset Oct 31 19:18:14 xxxx kernel: Initializing cgroup subsys cpu Oct 31 19:18:14 xxxx kernel: Linux version 2.6.34.7-61.fc13.i686 (mockbuild.fedoraproject.org) (gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) #1 SMP Tue Oct 19 04:42:47 UTC 2010 Oct 31 19:18:14 xxxx kernel: BIOS-provided physical RAM map: Oct 31 19:18:14 xxxx kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Oct 31 19:18:14 xxxx kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Oct 31 19:18:14 xxxx kernel: BIOS-e820: 00000000000e2000 - 0000000000100000 (reserved) Oct 31 19:18:14 xxxx kernel: BIOS-e820: 0000000000100000 - 000000007f7a0000 (usable) Oct 31 19:18:14 xxxx kernel: BIOS-e820: 000000007f7a0000 - 000000007f7ae000 (ACPI data) Oct 31 19:18:14 xxxx kernel: BIOS-e820: 000000007f7ae000 - 000000007f7f0000 (ACPI NVS)
It happened again. These are the new versions of the packages: kdebase-workspace.i686 4.5.3-3.fc13 Additional info: kernel 2.6.34.7-61.fc13.i686 xorg-x11-drv-intel.i686 2.11.0-5.fc13 abrt: component: kdebase-workspace reason: Process /usr/bin/kdm was killed by singnal 11 (SIGSEV)
------------------ EXAMPLE: User: root Password: root01 ------------------ Fedora 13 (i686): user: root password: root00 user: root password: root01 Result: <BANG!> user: root password: root00 user: root password: root00 Result: <BANG!> user: root password: root00 user: root password: <null>, just press enter. Result: <BANG!> user: root password: root00 user: root password: root01 Result: <BANG!> YES! IT IS THE CORRECT PASSWORD !!!! Affected Packages: kdm 4.5.3-3.fc13 kdebase-workspace 4.5.3-3.fc13 kernel 2.6.34.7-61.fc13 xorg-x11-drv-intel 2.11.0-5.fc13 BANG!= componet: kde-workspace reason: Process /usr/bin/kdm was killed by signal 11 (SIGSEGV) package: kdm-4.5.3-3.fc13 This is now very easy to reproduce.
Created attachment 461686 [details] Messages
I discovered that Fedora 14 is also affected (Using another netbook) and opened the bug 655270.
The issue is fixed for F14 in bug 605156. F13 still crashes (fprintd 0.2.0-1.fc13) on a fully updated system.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
It was fixed for F14 but not for F13. Additionally, the netbook which used F13 was updated to F14 and now i don't have it any more. Probably it is not fixed.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.