Bug 693521 - [abrt] gpsdrive-2.11-1.fc14: loadmap: Process /usr/bin/gpsdrive was killed by signal 11 (SIGSEGV)
Summary: [abrt] gpsdrive-2.11-1.fc14: loadmap: Process /usr/bin/gpsdrive was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 699064
Alias: None
Product: Fedora
Classification: Fedora
Component: gpsdrive
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6c251d5b47896a2e81c8389c79b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 21:13 UTC by kuijstej
Modified: 2012-03-20 16:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:46:15 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (34.88 KB, text/plain)
2011-04-04 21:13 UTC, kuijstej
no flags Details

Description kuijstej 2011-04-04 21:13:09 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 35715 bytes
cmdline: gpsdrive
component: gpsdrive
Attached file: coredump, 72118272 bytes
crash_function: loadmap
executable: /usr/bin/gpsdrive
kernel: 2.6.35.11-83.fc14.i686
package: gpsdrive-2.11-1.fc14
rating: 4
reason: Process /usr/bin/gpsdrive was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301950820
uid: 500

How to reproduce
-----
1.by starting GpsDrive it starts and after one or two seconds it disappear.

2.this report  was given
3.

Comment 1 kuijstej 2011-04-04 21:13:11 UTC
Created attachment 489859 [details]
File: backtrace

Comment 2 Kevin Fenzi 2011-04-06 14:37:53 UTC
Have you run gpsdrive ok in the past? 

If you 'mv .gpsdrive .gpsdrive.sav' and start it does it work ok?

Comment 3 abrt-bot 2012-03-20 16:46:15 UTC
Backtrace analysis found this bug to be similar to bug #699064, closing as duplicate.

Bugs which were found to be similar to this bug: bug #699064, bug #702871

This comment is automatically generated.

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


Note You need to log in before you can comment on or make changes to this bug.