abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 10024 bytes cmdline: /usr/libexec/gnome-user-share component: gnome-user-share Attached file: coredump, 1318912 bytes crash_function: check_mixed_deps executable: /usr/libexec/gnome-user-share kernel: 2.6.38-0.rc4.git0.2.fc15.x86_64 package: gnome-user-share-2.30.2-4.fc15 rating: 4 reason: Process /usr/libexec/gnome-user-share was killed by signal 6 (SIGABRT) release: Fedora release 15 (Rawhide) time: 1297759426 uid: 500 How to reproduce ----- 1. Installed F15 Alpha TC2 2. Started in init 3, and logged in as root and do a start x and create a user (Kickstart was not working) 3. Reboot and logged in as normal user (No users shown in gdm)
Created attachment 478797 [details] File: backtrace
Package: gnome-user-share-2.30.2-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Login 2. 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Rawhide) How to reproduce ----- 1. Log into Gnome (classic) 2. 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.boot 2.login 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. booted system into gnome desktop, fallback 2. 3. Comment ----- as above
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Login 2. 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Logged in from GDM.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Rawhide) How to reproduce ----- 1. Booted, logged into a Gnome session 2. 3. Comment ----- This has happened each time I log in
Package: gnome-user-share-2.30.2-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.install F15 alpha TC2 2.boot 3. log into gnome
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Log in into Fedora 15 TC2 2. See abrt notification that a crash occured
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. just log into GNOME Shell F15 Alpha.TC2 2. crash logged in ABRT 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Login to console as root (sorry, fresh install ;) 2. startx 3. crash
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Login into Fedora15 2. 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Right after login, error popped up. Not sure what was the reason. 2. 3.
*** Bug 678193 has been marked as a duplicate of this bug. ***
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. this bug occurs at system startup. 2. every time 3.
Package: gnome-user-share-2.30.2-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Install F15-Alpha-RC1 2. Login to gnome desktop
Same issue working from the test day live CD on a Samsung NC10 netbook (external USB DVD-RW): http://www.smolts.org/client/show/pub_6addbf83-d0f4-47c5-8219-d88d2c00e5aa Package: gnome-user-share-2.30.2-4.fc15 Latest Crash: Thu 24 Feb 2011 11:54:13 AM Command: /usr/libexec/gnome-user-share Reason: Process /usr/libexec/gnome-user-share was killed by signal 6 (SIGABRT) Comment: None Bug Reports: Unable to submit ABRT report from Live CD: "Reporting disabled because the backtrace is unusable". Did a copy / paste of output, looks similar to backtrace above but can attach if required.
Since installing the beta version of F15 released 19/04/2011, this issue appears to be fixed for me.
Thanks for letting us know, let's close this then.