Bug 1046084

Summary: [abrt] virtuoso-opensource: gpf_notice(): virtuoso-t killed by SIGSEGV
Product: [Fedora] Fedora Reporter: matthias.rambausek
Component: virtuoso-opensourceAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: franck.bailliet, ltinkl, marwalk, phob0ss13, pingou, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/befe37098f068c19807104a41d5e4569c46d50e4
Whiteboard: abrt_hash:7cccc4e20af0b34ff222a4fc1ff2d396ed31dfb3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:45:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 matthias.rambausek 2013-12-23 15:14:32 UTC 
Description of problem:
This happens on every startup (KDE only) and also when trying to restart the desktop-search services via the corresponding kcm module.
I already deleted the directory ~/.kde/share/apps/nepomuk (to repopulate the database from scratch) but this did not fix the problem.


Probably the same bug as
* Bug 1020499 or
* Bug 1033977

(I don't know if abrt found any duplicates)

Version-Release number of selected component:
virtuoso-opensource-6.1.6-5.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_ik2348.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gpf_notice at Dkutil.c:84
 #1 pg_make_map at insert.c:151
 #2 buf_disk_read at disk.c:1838
 #3 page_wait_access at gate.c:191
 #4 itc_dive_transit at gate.c:898
 #5 itc_down_transit at gate.c:997
 #6 itc_sample_1 at search.c:3464
 #7 itc_local_sample at search.c:3633
 #8 itc_sample at search.c:3678
 #9 sqlo_inx_sample_1 at sqlcost.c:1359

Potential duplicate: bug 836188
Comment 1 matthias.rambausek 2013-12-23 15:14:39 UTC 
Created attachment 840831 [details]
File: backtrace
Comment 2 matthias.rambausek 2013-12-23 15:14:41 UTC 
Created attachment 840832 [details]
File: cgroup
Comment 3 matthias.rambausek 2013-12-23 15:14:44 UTC 
Created attachment 840833 [details]
File: core_backtrace
Comment 4 matthias.rambausek 2013-12-23 15:14:46 UTC 
Created attachment 840834 [details]
File: dso_list
Comment 5 matthias.rambausek 2013-12-23 15:14:48 UTC 
Created attachment 840835 [details]
File: environ
Comment 6 matthias.rambausek 2013-12-23 15:14:51 UTC 
Created attachment 840836 [details]
File: exploitable
Comment 7 matthias.rambausek 2013-12-23 15:14:53 UTC 
Created attachment 840837 [details]
File: limits
Comment 8 matthias.rambausek 2013-12-23 15:14:56 UTC 
Created attachment 840838 [details]
File: maps
Comment 9 matthias.rambausek 2013-12-23 15:14:58 UTC 
Created attachment 840839 [details]
File: open_fds
Comment 10 matthias.rambausek 2013-12-23 15:15:00 UTC 
Created attachment 840840 [details]
File: proc_pid_status
Comment 11 matthias.rambausek 2013-12-23 15:15:02 UTC 
Created attachment 840841 [details]
File: var_log_messages
Comment 12 matthias.rambausek 2013-12-25 18:23:10 UTC 
today at least email-indexing is working after 
1. stopping all nepomuk services via the desktop-search kcm module
2. erasing the folder ~/.kde/share/apps/nepomuk
3. restarting the nepomuk services via the desktop-search kcm

I have tried above steps before without success, but not so today. I hope nepomuk/virtuose keep working after reboot

merry christmas
Comment 13 matthias.rambausek 2013-12-29 00:27:18 UTC 
things keep working, cannot reproduce the crash anymore (having an updated system)
Comment 14 franck.bailliet 2014-06-06 19:09:56 UTC 
Another user experienced a similar problem:

The incident appears every nex restart of my machine.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_ik1637.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.13.6-200.fc20.x86_64
package:        virtuoso-opensource-6.1.6-5.fc20
reason:         virtuoso-t killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 franck.bailliet 2014-06-07 05:43:19 UTC 
Another user experienced a similar problem:

The incident appears every new restart of my machine.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_ik1637.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.13.6-200.fc20.x86_64
package:        virtuoso-opensource-6.1.6-5.fc20
reason:         virtuoso-t killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 franck.bailliet 2014-06-07 23:38:00 UTC 
Another user experienced a similar problem:

This incident occures every time i start my system.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_ik1720.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.13.9-200.fc20.x86_64
package:        virtuoso-opensource-6.1.6-5.fc20
reason:         virtuoso-t killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Rex Dieter 2014-06-08 17:29:43 UTC 
comment #12 includes a workaround (to recover from a corrupted database)
Comment 18 Fedora End Of Life 2015-05-29 10:08:01 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 19 Fedora End Of Life 2015-06-29 13:45:46 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.