Red Hat Bugzilla – Bug 1013705
[abrt] virtuoso-opensource-6.1.6-3.fc19: gpf_notice: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 12:25:23 EST
Version-Release number of selected component:
cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_Vs2200.ini +wait
runlevel: N 5
Thread no. 1 (10 frames)
#0 gpf_notice at Dkutil.c:84
#1 itc_bm_insert_in_row at bitmap.c:693
#2 key_bm_insert at bitmap.c:932
#3 key_insert at row.c:2632
#4 insert_node_run at sqlrun.c:1650
#5 insert_node_input at sqlrun.c:1674
#6 ins_qnode at sqlintrp.c:1403
#7 code_vec_run_1 at sqlintrp.c:1908
#8 qn_input at sqlrun.c:680
#9 qr_subq_exec at sqlrun.c:3544
Potential duplicate: bug 728523
Created attachment 805304 [details]
Created attachment 805305 [details]
Created attachment 805306 [details]
Created attachment 805307 [details]
Created attachment 805308 [details]
Created attachment 805309 [details]
Created attachment 805310 [details]
Created attachment 805311 [details]
Created attachment 805312 [details]
Created attachment 805313 [details]
Created attachment 805314 [details]
I had been seeing this on my Fedora 20 box with the KDE 4.11.9x series and also 4.12,
However since clearing /tmp and stopping nepomuk and removing
$HOME/.kde/share/apps/nepomuk and enabling nepomuk again the crash has stopped. Not ideal but maybe something was corrupted somehow. Virtuoso has not crashed for a few days.
Another data point:
* Had these crashes several times a day (fully up-to-date F20, KDE-4.12.5)
* Tested proposed workaround from comment #12 few days ago
* Crashes stopped completely
Another user experienced a similar problem:
Started happening after a recent update of system from Fedora repos. Keeps happening over and over.
cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_Z24893.ini +wait
reason: virtuoso-t killed by SIGSEGV
runlevel: N 5
*** Bug 1103291 has been marked as a duplicate of this bug. ***
*** Bug 1111363 has been marked as a duplicate of this bug. ***
We have reports of this at least up to virtuoso-opensource-6.1.6-5.fc20 in the dupe. retrace server indicates this is a very commonly-hit crash, FWIW. Upstream report https://bugs.kde.org/show_bug.cgi?id=325189 has a similar subject but the traces in the report look different; not sure what's going on there.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.