Bug 19485 - Cauldron makes random reboots when you open a Terminal to check for updates
Summary: Cauldron makes random reboots when you open a Terminal to check for updates
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-09-29 02:05 CEST by Kristoffer Grundström
Modified: 2016-10-13 15:34 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
dmesg (72.79 KB, text/plain)
2016-09-29 02:06 CEST, Kristoffer Grundström 		Details
Xorg.log (35.66 KB, text/plain)
2016-09-29 02:07 CEST, Kristoffer Grundström 		Details
boot.log (12.13 KB, text/plain)
2016-09-29 02:08 CEST, Kristoffer Grundström 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2016-09-29 02:05:55 CEST 
Description of problem: I installed Mageia 6 (Cauldron) in my laptop [ASUS N550JK] and a couple of 4.7.5-desktop-1.mga6 kernel boots later as I opened the Terminal to check for updates the computer just blacks out and reboots. I have Plasma5, GNOME, MATE and Cinnamon installed. I can't reproduce this issue in Ubuntu 16.04 that I've installed next to Mageia 6 (Cauldron). If this was a hardware failure I think Ubuntu would also be affected by this issue no matter what kernel I'd be using.

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

How reproducible: 3 times and counting.

Steps to Reproduce:
1. Install Mageia 6 (Cauldron) using the nonfree net install iso.
2. Install Plasma5, GNOME, MATE and Cinnamon as DE's.
3. Login to Plasma5.
4. Open a Terminal window.
5. Start typing urpmi.update and voila, the computer goes black and reboots.
6. The same thing will happen again when you login the next time.
Comment 1 Kristoffer Grundström 2016-09-29 02:06:37 CEST 
Created attachment 8464 [details]
dmesg
Kristoffer Grundström 2016-09-29 02:06:47 CEST

CC: (none) => hamnisdude

Comment 2 Kristoffer Grundström 2016-09-29 02:07:11 CEST 
Created attachment 8465 [details]
Xorg.log
Comment 3 Kristoffer Grundström 2016-09-29 02:08:42 CEST 
Created attachment 8466 [details]
boot.log
Comment 4 Kristoffer Grundström 2016-09-29 02:09:43 CEST 
Any other log file I'm missing?
Marja Van Waes 2016-09-30 17:49:42 CEST

CC: (none) => marja11
Attachment 8465 mime type: text/x-log => text/plain

Marja Van Waes 2016-09-30 17:50:39 CEST

Attachment 8466 mime type: text/x-log => text/plain

Comment 5 Marja Van Waes 2016-09-30 17:57:35 CEST 
(In reply to Kristoffer Grundström from comment #4)
> Any other log file I'm missing?

immediately after an unwanted reboot, please run, as root:

   journalctl -ab -1 > journal.txt

and run journal.txt to this bug report.

The ~/.xsession-errors of the user to whom this happened would be useful, too.

Could you login with a different user, after this happens, and then fetch the .xsession-errors from the affected user from there?

Does this only happen in Plasma5? The terminal you're talking about, is that the KDE/Plasma5 konsole?
Comment 6 Marja Van Waes 2016-09-30 17:58:45 CEST 
s/run journal.txt to this bug report/attach journal.txt to this bug report/
Comment 7 Marja Van Waes 2016-10-09 10:34:20 CEST 
(In reply to Marja van Waes from comment #5)
> (In reply to Kristoffer Grundström from comment #4)
> > Any other log file I'm missing?
> 
> immediately after an unwanted reboot, please run, as root:
> 
>    journalctl -ab -1 > journal.txt
> 


Ping?

Please attach that file, Kristoffer :-)

Btw, _which_ terminal window did you use? xterm, konsole, gnome-terminal.... ?

Can you reproduce this in a text tty or in a different terminal emulator?
Marja Van Waes 2016-10-09 10:34:41 CEST

Keywords: (none) => NEEDINFO

Comment 8 Kristoffer Grundström 2016-10-11 23:48:48 CEST 
I cannot reproduce it right now, but I'll try to reproduce it with a VM of Cauldron.
Comment 9 Marja Van Waes 2016-10-13 15:34:49 CEST 
(In reply to Kristoffer Grundström from comment #8)
> I cannot reproduce it right now, but I'll try to reproduce it with a VM of
> Cauldron.

Closing as worksforme, for now.

Please reopen and supply all the requested information if you hit this again.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.