Bug 489153 - systemsettings (kcm_screensaver) crash (segfault)
Summary: systemsettings (kcm_screensaver) crash (segfault)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 10
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-08 09:27 UTC by vikram goyal
Modified: 2009-03-08 10:21 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-08 10:21:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
kcrash output (3.07 KB, text/plain)
2009-03-08 09:27 UTC, vikram goyal
no flags Details

Description vikram goyal 2009-03-08 09:27:32 UTC
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 09:37:40 UTC
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 09:43:09 UTC
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 10:21:27 UTC
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.