Bug 969670

Summary: [abrt] nepomuk-core-4.10.3-1.fc18: QGlobalStaticDeleter<QMutex>::~QGlobalStaticDeleter: Process /usr/bin/nepomukserver was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Eduardo Medina <edu.rm.85>
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:96954515cb61b85b893b3fb06e8b48cbf7f7519b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:37:23 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Eduardo Medina 2013-06-01 17:29:21 UTC 
Description of problem:
Everytime I log in with my personal user Nepomuk crashes.

Version-Release number of selected component:
nepomuk-core-4.10.3-1.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 3
cmdline:        /usr/bin/nepomukserver
crash_function: QGlobalStaticDeleter<QMutex>::~QGlobalStaticDeleter
executable:     /usr/bin/nepomukserver
kernel:         3.9.4-200.fc18.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (5 frames)
 #8 QGlobalStaticDeleter<QMutex>::~QGlobalStaticDeleter at ../../src/corelib/global/qglobal.h:1948
 #9 __cxa_finalize at cxa_finalize.c:55
 #10 __do_global_dtors_aux at /lib64/libQtCore.so.4
 #11 ??
 #12 _dl_fini at dl-fini.c:253
Comment 1 Eduardo Medina 2013-06-01 17:29:26 UTC 
Created attachment 755573 [details]
File: backtrace
Comment 2 Eduardo Medina 2013-06-01 17:29:30 UTC 
Created attachment 755574 [details]
File: cgroup
Comment 3 Eduardo Medina 2013-06-01 17:29:33 UTC 
Created attachment 755575 [details]
File: core_backtrace
Comment 4 Eduardo Medina 2013-06-01 17:29:37 UTC 
Created attachment 755576 [details]
File: dso_list
Comment 5 Eduardo Medina 2013-06-01 17:29:41 UTC 
Created attachment 755577 [details]
File: environ
Comment 6 Eduardo Medina 2013-06-01 17:29:45 UTC 
Created attachment 755578 [details]
File: limits
Comment 7 Eduardo Medina 2013-06-01 17:29:49 UTC 
Created attachment 755579 [details]
File: maps
Comment 8 Eduardo Medina 2013-06-01 17:29:52 UTC 
Created attachment 755580 [details]
File: open_fds
Comment 9 Eduardo Medina 2013-06-01 17:29:56 UTC 
Created attachment 755581 [details]
File: proc_pid_status
Comment 10 Eduardo Medina 2013-06-01 17:30:00 UTC 
Created attachment 755582 [details]
File: var_log_messages
Comment 11 Eduardo Medina 2013-06-01 17:52:15 UTC 
I solved the bug erasing the files from $HOME/.kde/share finding the files related with Nepomuk.

The problem was that Nepomuk was taking the configuration from a old version that used Strigi.

Sorry.
Comment 12 Fedora End Of Life 2013-12-21 13:48:54 UTC 
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.
Comment 13 Fedora End Of Life 2014-02-05 21:37:23 UTC 
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.