Bug 232341 - kdeartwork-kscreensaver crashes on preview
Summary: kdeartwork-kscreensaver crashes on preview
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: screensavers (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-27 12:56 UTC by kailash.kain
Modified: 2015-01-26 07:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Output of glxinfo (16.88 KB, text/plain)
2010-03-27 16:36 UTC, kailash.kain 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kailash.kain 2010-03-27 12:56:11 UTC 
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Fedora RPMs

When selecting OpenGL Screen-savers for preview, some of screen-savers cause crash. Problem is reproducible each time for some of them, KPendulam for instance.
Comment 1 kailash.kain 2010-03-27 12:58:06 UTC 
Addditional info and trace is available at following URL:
https://bugzilla.redhat.com/show_bug.cgi?id=568953
Comment 2 Christoph Feck 2010-03-27 16:23:03 UTC 
Please attach the output of "glxinfo". It looks like you either miss OpenGL libraries, or they are not complete. The crash happens because the screen saver tries to call the "glGetIntegerv" function.
Comment 3 kailash.kain 2010-03-27 16:36:42 UTC 
Created attachment 42294 [details]
Output of glxinfo
Comment 4 Christoph Feck 2010-03-27 16:44:56 UTC 
Thanks for the information.
Comment 5 Martin Flöser 2015-01-26 07:35:08 UTC 
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.