Description of problem: After reboot, the crash was recorded. I run kmail. Version-Release number of selected component: virtuoso-opensource-6.1.6-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_hX1221.ini +wait crash_function: gpf_notice executable: /usr/bin/virtuoso-t kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gpf_notice at Dkutil.c:84 #1 itc_fix_back_link at gate.c:757 #2 itc_landed_down_transit at gate.c:979 #3 itc_search at search.c:1701 #4 itc_next at search.c:1800 #5 table_source_input at sqlrun.c:1501 #6 qr_resume_pending_nodes at sqlintrp.c:809 #7 subq_next at sqlintrp.c:848 #8 subq_node_input at sort.c:474 #9 qr_resume_pending_nodes at sqlintrp.c:809
Created attachment 688097 [details] File: backtrace
Created attachment 688098 [details] File: cgroup
Created attachment 688099 [details] File: core_backtrace
Created attachment 688100 [details] File: dso_list
Created attachment 688101 [details] File: environ
Created attachment 688102 [details] File: limits
Created attachment 688103 [details] File: maps
Created attachment 688104 [details] File: open_fds
Created attachment 688105 [details] File: proc_pid_status
Created attachment 688106 [details] File: smolt_data
Created attachment 688107 [details] File: var_log_messages
This crash persisted until I deleted all of .kde/share/apps/nepomuk/repository/main/data/virtuosobackend . Now the crash cannot be reproduced. I have no idea how the database got corrupted. Since so much depends on this process running, it would be nice to see a bit more robustness added to virtuoso-opensource.
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.
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.