Bug 5834

Summary:	I've had to double install webmin (service not in drakxservice)
Product:	Mageia	Reporter:	William Kenney <wilcal.int>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ennael1, pterjan
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	webmin-1.550-2.mga1.noarch.rpm	CVE:
Status comment:

Description William Kenney 2012-05-10 21:59:10 CEST

In both the 32-bit and 64-bit Mageia 2 RC you have
to double install webmin to get it to work. To
reproduce do a clean new install of M2RC and
after setting up the repos

MCC -> Software Management -> Install & Remove Software

Install webmin. Install will appear to go smoothly and
infact the webmin icon will appear in the tools menu
but will not open a browser and launch. Webmin will not
appear in:

MCC-> System -> Manage Systems services

Attemping to point a browser to http://localhost:10000
gets no response. Even a reboot at this point will
not work.

After reboot back into

MCC -> Software Management -> Install & Remove Software

delele webmin. When the delete is finished reinstall
webmin again and all is well including the line in

MCC-> System -> Manage Systems services

and accessing webmin in a browser with: http://localhost:10000
and the icon in the tools menu.

Comment 1 Manuel Hiebel 2012-05-10 22:05:56 CEST

seems it was never ported to systemd, 

(maybe we should drop it as it certainly contain CVE ...)

as a workaround you can use /etc/init.d/webmin start stop etc

CC: (none) => ennael1, pterjan
Summary: I've had to double install webmin in M2RC to get it to work => I've had to double install webmin (service not in drakxservice)

Comment 2 William Kenney 2012-05-10 23:25:53 CEST

I actually don't have a problem leaving it
as it is right now. Webmin is a very important
network tool so I would not recommend dropping
it. Lets think about it during the Mageia 3
Cauldron.

Thanks for the info.

Comment 3 Manuel Hiebel 2012-05-11 00:47:28 CEST

ok after a quick check seems there is no CVE so no worry :)
(I was thinking on that since there is no real maintainer)

Comment 4 William Kenney 2012-05-21 17:09:11 CEST

A new test install this morning tells
me that this is now fixed. I've changed
status to RESOLVED FIXED.

Thanks all.

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