Bug 723232

Summary: [abrt] gvfs-1.6.6-1.fc14: apply_journal_to_builder: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Leonard J. Umina <lenumina>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alexl, bnocera, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:5252894f8dda8510b42db34578505c0e6b46f2db
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 16:57:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Leonard J. Umina 2011-07-19 13:28:38 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 13464 bytes
cmdline: /usr/libexec/gvfsd-metadata
comment: The problem may be related to Google Chrome.  When I went back to my original X session the google chrome sessions I had attempted to start under the second X session were all there and running.  They had been started, just in the wrong session.  The crash report happened in the second session.
component: gvfs
Attached file: coredump, 589824 bytes
crash_function: apply_journal_to_builder
executable: /usr/libexec/gvfsd-metadata
kernel: 2.6.35.13-92.fc14.i686.PAE
package: gvfs-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1311077900
uid: 500

How to reproduce
-----
1. I was running a standard gnome session and decided to log in again under the same account and
    start another X session.
2. After doing so (cntrl-alt-F3, login, startx -- :2), I attempted to start google chrome
3. Google chrome started an additional session in my first X session, not the one it was started from

Comment 1 Leonard J. Umina 2011-07-19 13:28:40 UTC
Created attachment 513796 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 16:57:39 UTC
Backtrace analysis found this bug to be similar to bug #690984, closing as duplicate.

Bugs which were found to be similar to this bug: bug #594970, bug #608748, bug #613202, bug #645357, bug #659058, bug #690984

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 690984 ***