Bug 1098807

Summary: gnome-shell sigsegv while openQA user_gui_login on PowerPC
Product: [openSUSE] openSUSE Tumbleweed Reporter: Michel Normand <normand>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dimstar, hector.oron, normand, okurz
Version: CurrentFlags: dimstar: needinfo? (normand)
Target Milestone: ---   
Hardware: PowerPC-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: user_gui_login-journalctl.log
user_gui_login-try_gdb_backtraces.log

Description Michel Normand 2018-06-22 12:34:15 UTC
Created attachment 775028 [details]
user_gui_login-journalctl.log

gnome-shell sigsegv while openQA user_gui_login on PowerPC

This is a transient failure in a local IBM openQA instance, not seen yet on o3.

extract of journalctl
===
Jun 20 11:30:41 susetest gnome-session[30356]: gnome-session-binary[30356]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jun 20 11:30:41 susetest gnome-session-binary[30356]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jun 20 11:30:41 susetest gnome-session-binary[30356]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jun 20 11:30:41 susetest org.gnome.Shell.desktop[30410]: (EE) failed to read Wayland events: Broken pipe
Jun 20 11:30:41 susetest polkitd[903]: Unregistered Authentication Agent for unix-session:6 (system bus name :1.165, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun 20 11:30:41 susetest gnome-software[30692]: plugin shell-extensions took 1.2 seconds to do setup
Jun 20 11:30:41 susetest at-spi-bus-launcher[30447]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jun 20 11:30:41 susetest at-spi-bus-launcher[30447]:       after 21 requests (21 known processed) with 0 events remaining.
Jun 20 11:30:41 susetest gdm-password][30335]: pam_unix(gdm-password:session): session closed for user bernhard
Jun 20 11:30:41 susetest gdm[1930]: GdmDisplay: display lasted 6.479209 seconds
Jun 20 11:30:41 susetest gsd-color[30205]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
Jun 20 11:30:42 susetest systemd-coredump[30808]: Process 30410 (gnome-shell) of user 1000 dumped core.
Jun 20 11:30:42 susetest systemd-logind[904]: Removed session 6.
===
Comment 1 Michel Normand 2018-06-22 13:32:56 UTC
Created attachment 775042 [details]
user_gui_login-try_gdb_backtraces.log

I saved externally the user_gui_login-problem_detection_logs.tar.xz file at
https://michelmno.fedorapeople.org/boo1098807/ 
as too big to be able to attached to this bug.
It contains the 
segmentation-faults-list.txt
segmentation-faults-info.txt
and related coredumps.

I was able to extract from them the backtraces of /usr/login and /bin/login and /usr/bin/gnome-shell saved in user_gui_login-try_gdb_backtraces.log attached to this bug.
* The /bin/login bt has identified source file/line
* The /usr/bin/gnome-shell bt has only one source file/line, I do not know why.
Comment 2 Oliver Kurz 2018-06-24 13:08:53 UTC
Could https://bugzilla.opensuse.org/show_bug.cgi?id=1091349 about "/bin/login dumped core" be related?
Comment 3 Michel Normand 2018-06-25 08:10:26 UTC
(In reply to Oliver Kurz from comment #2)
> Could https://bugzilla.opensuse.org/show_bug.cgi?id=1091349 about
> "/bin/login dumped core" be related?

would need more investigation with bug#1091349 data.
Comment 4 Michel Normand 2018-08-20 08:07:06 UTC
Note that  there is no failure if openQA is set with QEMUCPUS=1, QEMUTHREADS=1 
same as bypass bug https://bugzilla.suse.com/show_bug.cgi?id=1041747#c101
Comment 5 Dominique Leuenberger 2020-06-26 15:42:12 UTC
(In reply to Michel Normand from comment #4)
> Note that  there is no failure if openQA is set with QEMUCPUS=1,
> QEMUTHREADS=1 
> same as bypass bug https://bugzilla.suse.com/show_bug.cgi?id=1041747#c101

Does this bug still get masked with respective parameters, did the bug get resolved or is it just still there?
Comment 6 Héctor Orón Martínez 2020-10-16 06:29:27 UTC
Please reopen if you are still affected by this issue.