Bug 185427 - screen saver Desktop Settings discarding changes SIGSEGV
Summary: screen saver Desktop Settings discarding changes SIGSEGV
Status: RESOLVED DUPLICATE of bug 178761
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_screensaver (show other bugs)
Version: 4.1
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-24 11:37 UTC by Greg John Goodsir
Modified: 2009-02-24 23:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screensaver systemsettings.kcrash backtrace. (3.94 KB, text/plain)
2009-02-24 11:42 UTC, Greg John Goodsir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Greg John Goodsir 2009-02-24 11:37:14 UTC
Version:            (using KDE 4.1.3)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Mandriva RPMs

Crash occurred running sceensavar test and exiting Desktop Settings discarding changes.
1. I opened "configure your desktop" from the panel
2. Doubleclicked on Desktop then "screen saver" in the left panel.
3. Clicked on one of the screen savers.
4. Clicked on test button then clicked mouse to stop the test.
5. Clicked on the window "x" to exit.
Result, box popped up to ask if I wanted to save or discard. I clicked discard
Result was signal 11 SIGSEGV.
It is reproduceable every time. 
It will also happen if I click on any screen saver then click "Setup" and exit discarding changes.
It wont happen if I click on "Start automatically" then exit discarding changes.It wont happen also if I test on "random" screen saver if I go through "Setup" or "Test".
The version of KDE is: 4.1.3
Kernel is: 2.6.27.14-desktop586-1mnb.
Comment 1 Greg John Goodsir 2009-02-24 11:42:58 UTC
Created attachment 31597 [details]
screensaver systemsettings.kcrash backtrace.
Comment 2 Dario Andres 2009-02-24 23:19:10 UTC
Fixed in KDE4.2.1 and 4.3 :)

*** This bug has been marked as a duplicate of bug 178761 ***