abrt version: 2.0.0 comment: trying to start at-spi from XFCE Autostart to handle another error report uid: 503 cmdline: /usr/libexec/at-spi-bus-launcher --launch-immediately component: at-spi2-core kernel: 2.6.38.2-8.fc15.x86_64 executable: /usr/libexec/at-spi-bus-launcher crash_function: XFlush reason: Process /usr/libexec/at-spi-bus-launcher was killed by signal 11 (SIGSEGV) package: at-spi2-core-1.91.93-1.fc15 username: xfgw architecture: x86_64 os_release: Fedora release 15 (Lovelock) time: 1301580065 rating: 0 Text file: maps, 7742 bytes Text file: smaps, 39774 bytes Binary file: coredump, 26099712 bytes Text file: dsos, 4854 bytes Text file: backtrace, 7737 bytes event_log ----- 2011-03-31-10:30:11> (exited with 0) 2011-03-31-10:30:12> Analyzing coredump '/home/xfgw/.abrt/spool/ccpp-2011-03-31-10:01:05-3440/coredump' 2011-03-31-10:30:12 Coredump references 19 debuginfo files, 1 of them are not installed 2011-03-31-10:30:14 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f15&arch=x86_64 error was 2011-03-31-10:30:14 No repomd file 2011-03-31-10:30:44 Looking for needed packages in repositories 2011-03-31-10:31:14 Can't find packages for 1 debuginfo files 2011-03-31-10:31:14 Missing debuginfo file: /usr/lib/debug/.build-id/84/774d8261a3cb85d73063e2ef2899c64ba87015.debug 2011-03-31-10:31:15> Backtrace is generated and saved, 7737 bytes 2011-03-31-10:31:15> (exited with 0)
Created attachment 489102 [details] File: maps
Created attachment 489103 [details] File: smaps
Created attachment 489104 [details] File: dsos
Created attachment 489105 [details] File: backtrace
*** Bug 696295 has been marked as a duplicate of this bug. ***
Created attachment 492980 [details] gdb backtrace I believe I am seeing this too. A reproducer seems to be: 1. logout 2. from a console: $ sudo systemctl restart prefdm.service 3. switch back to the console there is segfault message at-spi2-core-2.0.0-1.fc15.i686 gdm-3.0.0-2.fc15.i686
*** This bug has been marked as a duplicate of bug 494956 ***
*** This bug has been marked as a duplicate of bug 699776 ***