Bug 678500

Summary: [abrt] gnome-phone-manager-0.65-15.fc15: do_pre_parse_initialization: Process /usr/bin/gnome-phone-manager was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Elad Alfassa <elad>
Component: gnome-phone-managerAssignee: Linus Walleij <triad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bnocera, triad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a69cdfee891da37e0bc2c1190aa1b8a1df55affc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 15:20:33 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 Elad Alfassa 2011-02-18 09:24:38 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 12221 bytes
cmdline: gnome-phone-manager
component: gnome-phone-manager
Attached file: coredump, 2211840 bytes
crash_function: do_pre_parse_initialization
executable: /usr/bin/gnome-phone-manager
kernel: 2.6.38-0.rc4.git0.2.fc15.x86_64
package: gnome-phone-manager-0.65-15.fc15
rating: 4
reason: Process /usr/bin/gnome-phone-manager was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1297757699
uid: 500

How to reproduce
-----
1.start gnome-phone-manager
2.
3.

Comment 1 Elad Alfassa 2011-02-18 09:24:42 UTC
Created attachment 479470 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 15:20:33 UTC
Backtrace analysis found this bug to be similar to bug #700190, closing as duplicate.

Bugs which were found to be similar to this bug: bug #697475, bug #700190, bug #718775, bug #756112, bug #756894, bug #757531, bug #758147, bug #759670, bug #759772, bug #759864, bug #766318

This comment is automatically generated.

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