Bug 28950

Summary:	I was updating the system
Product:	Mageia	Reporter:	Jean-Claude Désinor <jean.claude.desinor>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, ouaurelien
Version:	8
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakconf-13.27-1.mga8	CVE:
Status comment:

Description Jean-Claude Désinor 2021-05-20 06:38:09 CEST

Theme name: Adwaita
Kernel version = 5.10.37-desktop-2.mga8
Distribution=Mageia release 8 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

Comment 1 Morgan Leijström 2021-05-20 07:45:50 CEST

Thank you for reporting.

How did you update?

What happened / did not work?

Can you provide a log?

CC: (none) => fri

Comment 2 Aurelien Oudelet 2021-05-21 02:57:11 CEST

Is this even reproducible?

When the system is updating with drakconf or mgaapplet, what did you do that trigger this Bug report? Did you try to "close" Mageia Control Centre?

Status: NEW => NEEDINFO
CC: (none) => ouaurelien

Comment 3 Jean-Claude Désinor 2021-05-21 03:06:17 CEST

I was just proceeding with a regular system update. There were many packages being updated, so I left momentarily. When I came back, I had a crash reported, but I wrongly assumed the logs would be collected automatically.
Should there be a log collected in the machine? Where should I look?

Comment 4 Aurelien Oudelet 2021-05-21 03:18:04 CEST

(In reply to Jean-Claude Désinor from comment #3)
> I was just proceeding with a regular system update. There were many packages
> being updated, so I left momentarily. When I came back, I had a crash
> reported, but I wrongly assumed the logs would be collected automatically.
> Should there be a log collected in the machine? Where should I look?

You should take the system log when there was the crash.
You have to remember the date and hour you left your computer and the hour you discovered the crash.

e.g.: if crash occurred 2021-05-19 19:00:00
Command (as root user in a Terminal):

journalctl --since "2021-05-19 18:00:00" --until "2021-05-19 22:00:00"

Add the output in an attached text file, please.

Comment 5 Aurelien Oudelet 2021-07-13 23:13:42 CEST

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.

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