Bug 705098 - [abrt] geoclue-0.12.0-3.fc14: Process /usr/libexec/geoclue-master was killed by signal 6 (SIGABRT)
Summary: [abrt] geoclue-0.12.0-3.fc14: Process /usr/libexec/geoclue-master was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 670128
Alias: None
Product: Fedora
Classification: Fedora
Component: geoclue
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a24f78f21160d89a43ef9c249f1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 15:49 UTC by Sailor Ripley
Modified: 2012-03-21 17:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:55:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.02 KB, text/plain)
2011-05-16 15:50 UTC, Sailor Ripley 		no flags Details
View All

Description Sailor Ripley 2011-05-16 15:49:57 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 16408 bytes
cmdline: /usr/libexec/geoclue-master
component: geoclue
Attached file: coredump, 9920512 bytes
crash_function: gc_master_provider_initialize_interfaces
executable: /usr/libexec/geoclue-master
kernel: 2.6.35.13-91.fc14.x86_64
package: geoclue-0.12.0-3.fc14
rating: 4
reason: Process /usr/libexec/geoclue-master was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1305560663
uid: 500

How to reproduce
-----
1. I was enabling and disabling wireless networks...
2.
3.
Comment 1 Sailor Ripley 2011-05-16 15:50:01 UTC 
Created attachment 499194 [details]
File: backtrace
Comment 2 Sailor Ripley 2011-05-16 15:51:01 UTC 
Package: geoclue-0.12.0-3.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I was enabling and disabling wireless networks...
2.
3.
Comment 3 abrt-bot 2012-03-21 17:55:45 UTC 
Backtrace analysis found this bug to be similar to bug #670128, closing as duplicate.

Bugs which were found to be similar to this bug: bug #579910, bug #640048, bug #647523, bug #670128

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 670128 ***
Note You need to log in before you can comment on or make changes to this bug.