Bug 18398

Summary:	sta1 classic iso install of GNOME unstable over periods of an hour or less
Product:	Mageia	Reporter:	Len Lawrence <tarazed25>
Component:	Release (media or process)	Assignee:	GNOME maintainers <gnome>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	marja11, sysadmin-bugs
Version:	Cauldron	Keywords:	6sta1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	dmesg saved after crash journal file from boot to crash

Description Len Lawrence 2016-05-07 19:44:32 CEST

Description of problem:
GNOME installed from sta1 classic iso on laptop with CSM boot.  The desktop appears to function normally; no regressions noted but after periods left unattended the desktop crashes.  Shows tty2.  AltCtlF2 recalls the X display but without a window/desktop manager; missing window decorations.  Focus tends to be retained by last application used so firefox for instance can still respond to different URLs.  Two kernels were tried:
4.6.0-desktop-0.rc6.1.mga5
4.6.0-desktop-0.rc5.2.mga6
and journal and dmesg from the first are attached.

Version-Release number of selected component (if applicable):
Mageia-6-sta1-x86_64-DVD

How reproducible:
It appears to happen consistently within an hour of booting.

Steps to Reproduce:
1. Install GNOME from the iso for the component on a Legacy boot system
2. Make sure the desktop is functioning normally
3. Wait a while for the console to appear and type CtrlAltF2 to show the desktop

Comment 1 Len Lawrence 2016-05-07 19:47:50 CEST

Created attachment 7759 [details]
dmesg saved after crash

Comment 2 Len Lawrence 2016-05-07 19:48:48 CEST

Created attachment 7760 [details]
journal file from boot to crash

Marja Van Waes 2016-05-08 10:50:40 CEST

Keywords: (none) => 6sta1
CC: (none) => marja11
Assignee: bugsquad => olav

Comment 3 Len Lawrence 2016-05-09 17:04:38 CEST

No longer consistent.  Suspending OK after an hour and returning on pressing power button.  GNOME has been running on this laptop now for something like 36 hours.

Comment 4 Olav Vitters 2016-09-19 10:15:57 CEST

Interesting log entries:

May 07 11:46:55 canopus gnome-settings-daemon.desktop[3197]: (gnome-settings-daemon:3197): color-plugin-WARNING **: failed to create profile from EDID data: Error creating directory: Permission denied

May 07 11:46:55 canopus nautilus-autostart.desktop[3378]: (nautilus:3378): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist


May 07 11:51:51 canopus kernel: traps: gnome-shell[3161] trap int3 ip:7f1693aaf84b sp:7ffd8db95420 error:0



1. There was an old bug whereby a colour profile directory would be owned by root (IIRC). Does it happen under a new user as well? Please also check the GDM user account & home directory.

2. Theme shouldn't be affected by this, but still weird to get it.

3. gnome-shell is crashing. It would still be good to get a stack trace.

Assignee: olav => gnome

Comment 5 Len Lawrence 2016-09-19 11:04:47 CEST

Umm.  It is a bit late now.  No longer have that system installed.  RC replaced sta1 and did not show this bug AFAICR.  Better to wait for sta2 and see if it appears there.

As a matter of information, referring to point 3 in comment 4; how to provide a stack trace if gnome-shell crashes?

Comment 6 Len Lawrence 2017-03-15 10:37:59 CET

In several 6sta2 GNOME installs this bug is absent.
Not sure how to close this.  Using WONTFIX.
RESOLVED or OLD?

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

Comment 7 Samuel Verschelde 2017-03-15 10:38:45 CET

There was a bug, there's no bug now, I'd say FIXED

Resolution: WONTFIX => FIXED