Bug 636585

Summary:	Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
Product:	[Fedora] Fedora	Reporter:	Magnus Tuominen <magnus.tuominen>
Component:	kdebase-workspace	Assignee:	Than Ngo <than>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	awilliam, fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than, thomasj
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-04 16:35:49 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:

Description Magnus Tuominen 2010-09-22 16:02:11 UTC

Description of problem:

Nepomuk crashed

Version-Release number of selected component (if applicable):

Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35.4-28.fc14.x86_64 x86_64
How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
no crash.

Additional info:

track implementation of upstream report into f14 final.
https://bugs.kde.org/show_bug.cgi?id=252061

Comment 1 Adam Williamson 2010-09-22 16:08:44 UTC

we need this bug to exist in Fedora Bugzilla as it blocks F14 release, and we can't mark a KDE bug as blocking our release.

"In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) "

(abrt should be read as KDE's bug reporting tool in this case :>)



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Rex Dieter 2010-10-01 16:11:59 UTC

I wouldn't consider this a blocker, without more information.

What this on a fresh install or upgrade?  Fresh user or pre-exising home?

Comment 3 Rex Dieter 2010-10-01 17:30:56 UTC

At least one comment in irc,

[12:35] <adamw> i hit it on a reboot after install from live iirc

(I did a x86_64 install myself, and didn't see it).

Comment 4 Adam Williamson 2010-10-01 17:31:14 UTC

I hit this on first boot of a freshly installed system from Beta live image.

Comment 5 Magnus Tuominen 2010-10-01 20:47:23 UTC

I did a fresh install using the x86_64 beta kde livecd, and I have not seen this happening again since reporting the bug.

Comment 6 Than Ngo 2010-10-04 16:35:49 UTC

We can not reproduce this issue anymore. Feel free to reopen it again if this issue still shows up. thanks

Comment 7 Adam Williamson 2010-10-04 19:56:52 UTC

Ngo, please don't un-mark bugs as blockers when closing them in future. As long as the bug is closed, it won't actually be considered to be blocking the release, but if it turns out it's not fixed and it gets re-opened it *will* be blocking the release, which is what we want. It would be bad if this issue turned out not to be fixed, so it was re-opened, but because you had removed the Blocks: field it was no longer marked as a release blocker and we lost it for release.