Bug 1038890

Summary: [abrt] virtuoso-opensource-6.1.6-1.fc18: gpf_notice: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: vikram goyal <vikigoyal>
Component: virtuoso-opensourceAssignee: Rex Dieter <rdieter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: ltinkl, pingou, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/91ef2aaa4b533047bb5c9d2ef8405a3592b4b186
Whiteboard: abrt_hash:f19a53587ca49a702801e4737a7644ee68e6777c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:34:57 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description vikram goyal 2013-12-06 04:26:25 UTC 
Description of problem:
It could be due to my home drive becoming 100% full as I had locked the KDE session & left the system for night downloading some files.

Thanks.


Version-Release number of selected component:
virtuoso-opensource-6.1.6-1.fc18

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_kn2126.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.11.9-100.fc18.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 gpf_notice at Dkutil.c:84
 #1 buf_disk_write at disk.c:1953
 #2 cpt_write_registry at regist.c:144
 #3 dbs_write_registry at regist.c:508
 #4 dbs_checkpoint at neodisk.c:1967
 #5 sf_makecp at sqlsrv.c:2713
 #6 sf_make_auto_cp at sqlsrv.c:2673
Comment 1 vikram goyal 2013-12-06 04:26:37 UTC 
Created attachment 833404 [details]
File: backtrace
Comment 2 vikram goyal 2013-12-06 04:26:41 UTC 
Created attachment 833405 [details]
File: cgroup
Comment 3 vikram goyal 2013-12-06 04:26:47 UTC 
Created attachment 833406 [details]
File: core_backtrace
Comment 4 vikram goyal 2013-12-06 04:26:51 UTC 
Created attachment 833407 [details]
File: dso_list
Comment 5 vikram goyal 2013-12-06 04:26:55 UTC 
Created attachment 833408 [details]
File: environ
Comment 6 vikram goyal 2013-12-06 04:26:59 UTC 
Created attachment 833409 [details]
File: exploitable
Comment 7 vikram goyal 2013-12-06 04:27:03 UTC 
Created attachment 833410 [details]
File: limits
Comment 8 vikram goyal 2013-12-06 04:27:10 UTC 
Created attachment 833411 [details]
File: maps
Comment 9 vikram goyal 2013-12-06 04:27:14 UTC 
Created attachment 833412 [details]
File: open_fds
Comment 10 vikram goyal 2013-12-06 04:27:19 UTC 
Created attachment 833413 [details]
File: proc_pid_status
Comment 11 vikram goyal 2013-12-06 04:27:23 UTC 
Created attachment 833414 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2013-12-21 14:48:17 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2014-02-05 22:34:57 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.