Bug 872032 - [abrt] nepomuk-core-4.9.2-5.fc17: Private: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Summary: [abrt] nepomuk-core-4.9.2-5.fc17: Private: Process /usr/bin/nepomukservicestu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nepomuk-core
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:31c78e5481d059776ff86d01a3e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-01 03:56 UTC by vikram goyal
Modified: 2013-08-01 01:41 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 01:40:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: core_backtrace (1.20 KB, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: environ (1.83 KB, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: backtrace (26.44 KB, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: limits (1.29 KB, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: cgroup (130 bytes, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: smolt_data (2.96 KB, text/plain)
2012-11-01 03:56 UTC, vikram goyal
no flags Details
File: xsession_errors (2.34 KB, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details
File: dso_list (7.75 KB, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details
File: maps (40.89 KB, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details
File: proc_pid_status (929 bytes, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details
File: var_log_messages (650 bytes, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details
File: open_fds (270 bytes, text/plain)
2012-11-01 03:57 UTC, vikram goyal
no flags Details

Description vikram goyal 2012-11-01 03:56:40 UTC
Description of problem:

I logged into KDE & the crash icon was there so I don't know when it happened, like whether it happened at the time of logging in or before.

Otherwise the machine was running idle with sendmail running in the background & the desktop was logged out for the night.


Version-Release number of selected component:
nepomuk-core-4.9.2-5.fc17

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        /usr/bin/nepomukservicestub nepomukfileindexer
crash_function: Private
kernel:         3.6.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 Private at kernel/qvariant.h:356
: #1 QVariant::QVariant at kernel/qvariant.cpp:1411
: #2 QDBusPendingReplyData::argumentAt at qdbuspendingreply.cpp:270
: #3 argumentAt<0> at /usr/include/QtDBus/qdbuspendingreply.h:176
: #4 operator QDBusPendingReplyTypes::Select<0, bool, void, void, void, void, void, void, void>::Type at /usr/include/QtDBus/qdbuspendingreply.h:186
: #5 Solid::PowerManagement::appShouldConserveResources at /usr/src/debug/kdelibs-4.9.2/solid/solid/powermanagement.cpp:77
: #6 Nepomuk2::EventMonitor::EventMonitor at /usr/src/debug/nepomuk-core-4.9.2/services/fileindexer/eventmonitor.cpp:84
: #7 Nepomuk2::FileIndexer::FileIndexer at /usr/src/debug/nepomuk-core-4.9.2/services/fileindexer/fileindexer.cpp:57
: #8 KPluginFactory::createInstance<Nepomuk2::FileIndexer, QObject> at /usr/include/kde4/kpluginfactory.h:477
: #9 KPluginFactory::create at /usr/src/debug/kdelibs-4.9.2/kdecore/util/kpluginfactory.cpp:203

Comment 1 vikram goyal 2012-11-01 03:56:43 UTC
Created attachment 636429 [details]
File: core_backtrace

Comment 2 vikram goyal 2012-11-01 03:56:46 UTC
Created attachment 636430 [details]
File: environ

Comment 3 vikram goyal 2012-11-01 03:56:51 UTC
Created attachment 636431 [details]
File: backtrace

Comment 4 vikram goyal 2012-11-01 03:56:53 UTC
Created attachment 636432 [details]
File: limits

Comment 5 vikram goyal 2012-11-01 03:56:55 UTC
Created attachment 636433 [details]
File: cgroup

Comment 6 vikram goyal 2012-11-01 03:56:57 UTC
Created attachment 636434 [details]
File: smolt_data

Comment 7 vikram goyal 2012-11-01 03:57:00 UTC
Created attachment 636435 [details]
File: xsession_errors

Comment 8 vikram goyal 2012-11-01 03:57:03 UTC
Created attachment 636436 [details]
File: dso_list

Comment 9 vikram goyal 2012-11-01 03:57:06 UTC
Created attachment 636437 [details]
File: maps

Comment 10 vikram goyal 2012-11-01 03:57:08 UTC
Created attachment 636438 [details]
File: proc_pid_status

Comment 11 vikram goyal 2012-11-01 03:57:11 UTC
Created attachment 636439 [details]
File: var_log_messages

Comment 12 vikram goyal 2012-11-01 03:57:15 UTC
Created attachment 636440 [details]
File: open_fds

Comment 13 Fedora End Of Life 2013-07-03 23:12:48 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 14 Fedora End Of Life 2013-08-01 01:41:02 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.