Bug 20097

Summary:	freeze and crash after a moment
Product:	Mageia	Reporter:	thierry rouillon <thierry.rouillon>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	5	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mageia 5.1 x86 64	CVE:
Status comment:

Description thierry rouillon 2017-01-10 22:44:45 CET

Description of problem:
Freeze and black screen before automatic reboot

Version-Release number of selected component (if applicable):


How reproducible:
permanently

Steps to Reproduce:
at first: the PC start.
It run ~ 10'
It freeze.
The TTY3 is filled with message. 
it looks like https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963

Comment 1 Marja Van Waes 2017-01-11 22:20:52 CET

Hi Thierry,

Please give more information.

You chose the component "Installer", did you install Mageia 5.1 from a classical iso (so _not_ from a Live iso)?

And does the problem occur 10 minutes after booting into the newly installed system?

If you installed from a classical iso, then please fetch 

   /root/drakx/report.bug.xz

from the root partition you installed to, and attach it to this bug report.

Please do also attach

  /var/log/Xorg.0.log.old

that you fetch after an automatic reboot

And also attach journal.txt that is the result of running, as root

    journalctl -ab -1 > journal.txt

also from after an automatic reboot.

Thanks :-)

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Marja Van Waes 2017-01-15 12:17:44 CET

@ Thierry, 

If you don't now how to supply the requested information, then please ask in the forum for help http://www.mageialinux-online.org/forum/

Thanks :-)

Comment 3 Marja Van Waes 2017-02-06 11:41:50 CET

@ Thierry

If you cannot supply the requested information because I _misunderstood_ your description of this bug, then please say so!

Comment 4 Marja Van Waes 2017-02-10 18:45:48 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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