Bug 489153 – systemsettings (kcm_screensaver) crash (segfault)

Bug 489153 - systemsettings (kcm_screensaver) crash (segfault)

Summary:	systemsettings (kcm_screensaver) crash (segfault)

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kdebase-workspace (Show other bugs)
Sub Component:
Version:	10
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ngo Than
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-08 05:27 EDT by vikram goyal
Modified:	2009-03-08 06:21 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-03-08 06:21:27 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
kcrash output (3.07 KB, text/plain) 2009-03-08 05:27 EDT, vikram goyal	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description vikram goyal 2009-03-08 05:27:32 EDT

Created attachment 334431 [details]
kcrash output

Description of problem:
system settings crash

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


How reproducible:


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


Expected results:


Additional info:
Playing with wall papers, screen savers and its diff options, on clicking ok it crashed

Comment 1 Kevin Kofler 2009-03-08 05:37:40 EDT

System Settings is part of kdebase-workspace, not kde-settings. The kde-settings package contains default settings, not the tools to change them.

You also left important portions blank, e.g. the detailed steps to reproduce the bug. Unfortunately, your "Additional info" is too vague to do anything with it.

Comment 2 Kevin Kofler 2009-03-08 05:43:09 EDT

The backtrace tells us it crashes somewhere in kcm_screensaver (no idea where because there's no debugging information, it just says "??") when processing a K3Process::processExited() signal (that may give us some idea about where it is, but nothing precise).

Comment 3 vikram goyal 2009-03-08 06:21:27 EDT

I suspected that the info I was providing was not enough, but I thought maybe whatever is there may prove useful. Sorry for the trouble. Closing it.

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