Bug 8798

Summary:	e17 complains of configuration hiccup when first started
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	trem <tremyfr>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ennael1, marja11, nic
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	5beta3 5rc
Source RPM:		CVE:
Status comment:
Attachments:	screenshot

Description claire robinson 2013-01-23 19:50:40 CET

Installed pre-3beta2 DVD 64 with Other Desktops as DE choice

On first starting e17 it takes you through the configuration steps but when it starts the desktop shows an apology for the configuration hiccup message.

Not sure if this is just because there is no existing configuration and whether this can be worked around but worthy of a bug report.

See screenshot

Comment 1 claire robinson 2013-01-23 19:51:17 CET

Created attachment 3428 [details]
screenshot

claire robinson 2013-01-23 19:51:49 CET

Whiteboard: (none) => 3beta2
CC: (none) => ennael1

Manuel Hiebel 2013-01-25 23:50:15 CET

Assignee: bugsquad => tremyfr

Comment 2 Nic Baxter 2015-02-25 05:08:59 CET

Still current with e18. After the first hiccup I is OK. Possibly the configuration wizard is expecting a file which is not created until later?

CC: (none) => nic

Nic Baxter 2015-02-25 05:09:47 CET

Whiteboard: 3beta2 => 3beta2, 5beta3

Marja Van Waes 2015-03-28 21:17:22 CET

CC: (none) => marja11
Whiteboard: 3beta2, 5beta3 => 5beta3

Comment 3 Nic Baxter 2015-03-29 03:35:17 CEST

Anything needed? Or not worth bothering with?

Comment 4 Marja Van Waes 2015-04-14 20:55:11 CEST

is this still valid for 5RC?

Comment 5 claire robinson 2015-04-15 09:54:28 CEST

It was valid in February as reported by Nic. It is no longer carried on the ISOs so unlikely anything will have changed.

Samuel Verschelde 2015-05-15 17:49:01 CEST

Whiteboard: 5beta3 => 5beta3 5rc

Comment 6 sturmvogel 2022-06-19 11:24:20 CEST

Mageia 4 was the last version where e17 was shipped. It is no longer available in Mageia, so closing FIXED.

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