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
Created attachment 840831 [details] File: backtrace
Created attachment 840832 [details] File: cgroup
Created attachment 840833 [details] File: core_backtrace
Created attachment 840834 [details] File: dso_list
Created attachment 840835 [details] File: environ
Created attachment 840836 [details] File: exploitable
Created attachment 840837 [details] File: limits
Created attachment 840838 [details] File: maps
Created attachment 840839 [details] File: open_fds
Created attachment 840840 [details] File: proc_pid_status
Created attachment 840841 [details] File: var_log_messages
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
things keep working, cannot reproduce the crash anymore (having an updated system)
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
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
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 #12 includes a workaround (to recover from a corrupted database)
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.
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.