Version-Release number of selected component: nepomuk-core-4.9.5-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.7.7-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QHashData::detach_helper2 at tools/qhash.cpp:233 #1 QHash<QString, Nepomuk2::ServiceController*>::detach_helper at /usr/include/QtCore/qhash.h:584 #2 detach at /usr/include/QtCore/qhash.h:303 #3 begin at /usr/include/QtCore/qhash.h:464 #4 Nepomuk2::ServiceManager::runningServices at /usr/src/debug/nepomuk-core-4.9.5/server/servicemanager.cpp:402 #5 Nepomuk2::Server::quit at /usr/src/debug/nepomuk-core-4.9.5/server/nepomukserver.cpp:158 #7 do_lookup_x at dl-lookup.c:123 #8 _dl_lookup_symbol_x at dl-lookup.c:738 #9 _dl_fixup at ../elf/dl-runtime.c:118 #10 _dl_runtime_resolve at ../sysdeps/x86_64/dl-trampoline.S:45 Potential duplicate: bug 868454
Created attachment 698638 [details] File: backtrace
Created attachment 698639 [details] File: cgroup
Created attachment 698640 [details] File: core_backtrace
Created attachment 698641 [details] File: environ
Created attachment 698642 [details] File: limits
Created attachment 698643 [details] File: maps
Created attachment 698644 [details] File: open_fds
Created attachment 698645 [details] File: proc_pid_status
Logged out, then logged back in, after several hours of use. That's all. backtrace_rating: 4 Package: nepomuk-core-4.10.1-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
após a tentativa de instalação do driver de video da nvidia "NVIDIA-Linux-x86_64-310.40" atualizei kernel, e mesmo depois disso não consegui instalar o driver, pois sempre que tento inicia o sisstema com esse driver, retorna o erro de no screen found backtrace_rating: 4 Package: nepomuk-core-4.10.1-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Login at the KDE Desktop. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.8.4-202.fc18.x86_64 package: nepomuk-core-4.10.1-1.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors:
Booted laptop. Started KDE. Nepomuk crashed. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.8.5-201.fc18.x86_64 package: nepomuk-core-4.10.1-1.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 431 ureports_counter: 2
I restarted to computer after a total freeze i.e. both keyboard and mouse were unresponsive, and this crash appeared on start-up. backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.8.8-202.fc18.x86_64 package: nepomuk-core-4.10.2-2.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors:
(In reply to comment #13) > I restarted to computer after a total freeze i.e. both keyboard and mouse > were unresponsive, and this crash appeared on start-up. > > backtrace_rating: 4 > cmdline: /usr/bin/nepomukserver > crash_function: QHashData::detach_helper2 > executable: /usr/bin/nepomukserver > kernel: 3.8.8-202.fc18.x86_64 > package: nepomuk-core-4.10.2-2.fc18 > reason: Process /usr/bin/nepomukserver was killed by signal 11 > (SIGSEGV) > uid: 1000 > ureports_counter: 1 > xsession_errors: Sorry, scratch that I was thinking of this afternoons other bug occurrence. I actually logged out and back in as requested after installing some new updates.
Logging in. Immediate crash pop-up. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.9.6-200.fc18.x86_64 package: nepomuk-core-4.10.4-1.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
As soon as I logged on I got this message. I hadnt started any other application. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.10.9-100.fc18.x86_64 package: nepomuk-core-4.10.5-1.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
Logging in. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/nepomukserver crash_function: QHashData::detach_helper2 executable: /usr/bin/nepomukserver kernel: 3.10.9-100.fc18.x86_64 package: nepomuk-core-4.10.5-1.fc18 reason: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
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.