abrt version: 2.0.1 executable: /usr/libexec/at-spi-bus-launcher cmdline: /usr/libexec/at-spi-bus-launcher component: at-spi2-core crash_function: XFlush kernel: 2.6.38.3-18.fc15.x86_64 package: at-spi2-core-2.0.0-1.fc15 reason: Process /usr/libexec/at-spi-bus-launcher was killed by signal 11 (SIGSEGV) uid: 500 architecture: x86_64 username: wetab rating: 4 time: 1303826257 os_release: Fedora release 15 (Lovelock) Binary file: coredump, 26099712 bytes Text file: dsos, 4841 bytes Text file: backtrace, 6813 bytes Text file: maps, 7742 bytes environ ----- SHELL=/bin/bash DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-X1LFUo7q4D,guid=31911b961bfc6aca722796b000000010 XDG_SESSION_COOKIE=2aeb5ba1ff15f02072c8a25800000014-1303825322.271473-1572207733 XDG_RUNTIME_DIR=/run/user/wetab DISPLAY=:0 DESKTOP_SESSION=gnome SSH_AUTH_SOCK=/tmp/keyring-4uQNyq/ssh SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1104,unix/unix:/tmp/.ICE-unix/1104 WINDOWPATH=1 PATH=/usr/local/bin:/usr/bin:/bin GNOME_DESKTOP_SESSION_ID=this-is-deprecated USERNAME=wetab GDMSESSION=gnome XDG_SESSION_ID=1 GPG_AGENT_INFO=/tmp/keyring-4uQNyq/gpg:0:1 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-X1LFUo7q4D,guid=31911b961bfc6aca722796b000000010 XAUTHORITY=/var/run/gdm/auth-for-wetab-XFPODE/database USER=wetab DBUS_STARTER_BUS_TYPE=session PWD=/home/wetab GDM_LANG=de_DE.utf8 SHLVL=1 GNOME_KEYRING_CONTROL=/tmp/keyring-4uQNyq LANG=de_DE.utf8 _=/usr/bin/dbus-launch LOGNAME=wetab HOME=/home/wetab event_log ----- 2011-04-26-17:25:23> (exited with 0) 2011-04-26-17:25:23> Analyzing coredump '/home/wetab/.abrt/spool/ccpp-2011-04-26-15:57:37-1522/coredump' 2011-04-26-17:25:24 All 19 debuginfo files are available 2011-04-26-17:25:24> Lock file './.lock' is locked by process 2206 2011-04-26-17:25:25 Backtrace is generated and saved, 6813 bytes 2011-04-26-17:25:25> (exited with 0) build_ids ----- 9fd7f9c1f8b41211bd210e10f915ef69cea6a2ee 2c35820baaea8571d8a8dc977f23cc7f629ddcb4 1c6a95451ee19617be5abea3d121f0226d21ddda 8f67031b50aa96f0a6ae7c89efed129297831c5d 9ef41f9ca0eabaf3a03dd77eb180e202ab4fe956 21ad5b8ca30ad4dbb2190cfd19b03c69958ad013 4c842320387ff7f6f91b7842b223c16518be909f 1055ac8cb851ad0f25c1533682ed949a1d85c826 a7158bee1dfaecfbd81d16bc6b31b082b0d5244a 5d363f921f4545ef2e76fa9405d096745d4177fd d54647ce3fe0f70c8d886886d69b0fb5038371fa 8b86e05e174366cfcab602f40f851b804e605b1c 2f709c0d80b7741b678d35892b3ffacecc03d50c e5f626726497a81807681ed0088dbce6d6a1f17b 6ffe5717bdc04650a6023fe5933cd729feab53ee 5cc111ce758441128d08b5bc105a37addbc28a93 5c94d34eef463a380dece1eac0811d6cb2dea2f9 415dd94df0672c555dd4b2a4ef9dbf530694c82c b3900bee00b584ef0bfe2adc2f9b9aed93870bc0
Created attachment 494955 [details] File: dsos
Created attachment 494956 [details] File: backtrace
Created attachment 494957 [details] File: maps
Created attachment 495557 [details] abrt.log This is still occurring with at-spi2-core-2.0.1-1.fc15.
*** Bug 692554 has been marked as a duplicate of this bug. ***
Proposed fix reported here: https://bugzilla.gnome.org/show_bug.cgi?id=648942
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- dfgsdgsgsdfg
abrt testing, please disregard new comments
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I do not know how to reproduce this problem.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Don't know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Happened while logging in.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I was logging in after reboot. May be related to https://bugzilla.redhat.com/show_bug.cgi?id=717705 since these happen in pairs.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I was logging in after rebooting
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I was simply logging in after rebooting my laptop
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Log in to XFCE.
This happens *all the time*. It's easy to reproduce by logging to XFCE with "Launch GNOME services on startup".
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I have no idea what this does nor what happened.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I dont know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know!
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Loging to XFCE.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Login to XFCE.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I just loged in XFCE and this problem appeared
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I was logging in.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- i don't know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I try to connect wia Firewire to wireless network
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- restart error
WONTFIX?
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- no clue what happened
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- at start up
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- when working on folder etc
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Process /usr/libexec/at-spi-bus-launcher was killed by signal 11 (SIGSEGV)
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- DVD+RW active on read of DVD
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I was just working on some other stuffs
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Started KDE through XMing by command startkde
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Removed an admininstrator user using system settings that has never actually been used.
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- don't know
Package: at-spi2-core-2.0.1-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- pfffffffff
Package: at-spi2-core-2.0.1-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Running system
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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