Bug 7694 - Mga3 alpha2 DVD i586 LXDE - munch screensaver error
Summary: Mga3 alpha2 DVD i586 LXDE - munch screensaver error
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 3alpha2
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-03 19:02 CEST by claire robinson
Modified: 2015-04-14 20:19 CEST (History)
2 users (show)

See Also:
Source RPM: xscreensaver
CVE:
Status comment:


Attachments

Description claire robinson 2012-10-03 19:02:54 CEST
munch screensaver gives error when previewed

correct syntax is: 
munch word_list_file affix_file
xscreensaver exited abnormally: signal 0: etc
claire robinson 2012-10-03 19:04:20 CEST

CC: (none) => oliver.bgr
Whiteboard: (none) => 3alpha2

Comment 1 Derek Jennings 2012-10-25 01:23:10 CEST
This problem is caused because the default configuration of xscreensaver contains a list of all the screensavers but only the ones actually installed are shown in the list of available screensavers.

By default only the Themed screensaver is installed with Mageia, all the others are in additional packages.

However the package hunspell has a binary /usr/bin/munch which has the same name as one of the (not installed) screensavers and xscreensaver tries to treat it as a valid screensaver.

If the real munch screensaver is installed from the xscreensavers-base package then the preview works correctly

I suspect the easiest way to resolve this bug is to just not worry about it :-)

CC: (none) => derekjenn

Manuel Hiebel 2012-10-26 22:48:33 CEST

Source RPM: (none) => xscreensaver
Severity: normal => minor

Comment 2 Marja Van Waes 2015-04-14 20:19:24 CEST
No action since over 2 yrs ago and still assigned to Bug Squad

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
Resolution: (none) => OLD


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