Bug 18451

Summary:	System freeze after launching harddrake
Product:	Mageia	Reporter:	Daniel Tartavel <contact>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	contact, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	harddrake-ui-17.30	CVE:
Status comment:
Attachments:	lshw log lspci log lsusb log

Description Daniel Tartavel 2016-05-13 00:51:46 CEST

Description of problem:
When launching harddrake, system freeze after few seconds ( 2 or 3)

Version-Release number of selected component (if applicable):
draktools version17.30

How reproducible:
launch harddrake

Comment 1 Daniel Tartavel 2016-05-13 00:53:30 CEST

Created attachment 7788 [details]
lshw log

CC: (none) => contact

Comment 2 Daniel Tartavel 2016-05-13 00:54:22 CEST

Created attachment 7789 [details]
lspci log

Comment 3 Daniel Tartavel 2016-05-13 00:55:03 CEST

Created attachment 7790 [details]
lsusb log

Comment 4 Thierry Vignaud 2016-05-13 11:07:15 CEST

I assume you're talking about the GUI, aren't you?

Have you tried pinging this maching from another box?
Does it work?
If yes, can you ssh in it?
Also, can you look at harddrake references in "journalctl -b" output (to be run as root)

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Source RPM: harddrake => harddrake-ui-17.30

Comment 5 Daniel Tartavel 2016-05-13 11:16:00 CEST

yes this is the GUI, now the problem is passed, i found some libraries with 0 Bytes, so i reinstalled this libraries with --replacepkgs, this did not run until i reboot. 
So now working.

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

Comment 6 Thierry Vignaud 2016-05-13 11:23:01 CEST

Changing resolution as OS was damaged

Resolution: FIXED => INVALID