[Bug 1138455] New: GDM does not start properly on aarch64
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455 Bug ID: 1138455 Summary: GDM does not start properly on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/961187/modules/first _boot/steps/22 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: guillaume.gardet@arm.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installation of GNOME in openQA, GDM seems to not start properly as there is only a black screen, for both X11 and Wayland. This may be related to last gdm update: https://build.opensuse.org/request/show/708281 -- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-create_hdd_gnome@aarch64 fails in [first_boot](https://openqa.opensuse.org/tests/961187/modules/first_boot/steps/22) ## Test suite description image creation job used as parent for other jobs testing based on existing installation. GUI-Installation and selecting the gnome desktop during installation. ## Reproducible Fails since (at least) Build [20190614](https://openqa.opensuse.org/tests/961170) ## Expected result Last good: [20190607](https://openqa.opensuse.org/tests/954690) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=Tumbleweed&flavor=DVD&test=create_hdd_gnome&arch=aarch64&distri=opensuse&machine=aarch64) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c1
--- Comment #1 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c2
--- Comment #2 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c3
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c5
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c10
--- Comment #10 from xiaoguang wang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
xiaoguang wang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c11
Guillaume GARDET
We can find 'Application 'org.gnome.Shell.desktop' killed by signal 11' from journal log. Signal 11 is segment fault, so I need the gnome-shell backtrace to find where happens segment fault.
Where could I find it? It seems to be missing from 'journalctl'. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c12
xiaoguang wang
(In reply to xiaoguang wang from comment #10)
We can find 'Application 'org.gnome.Shell.desktop' killed by signal 11' from journal log. Signal 11 is segment fault, so I need the gnome-shell backtrace to find where happens segment fault.
Where could I find it? It seems to be missing from 'journalctl'.
First you need to enable system coredump. When gnome-shell was killed by signal 11, system will create a coredump of gnome-shell. You can use command 'coredumpctl list' to list the coredump. Use command 'coredumpctl gdb xxx' to attach the coredump, and use command 'thread apply all bt full' to collect backtrace. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c13
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c14
--- Comment #14 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c15
--- Comment #15 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c16
--- Comment #16 from xiaoguang wang
Created attachment 809425 [details] gdb 'thread apply all bt full'
Could you install these packages first: libmozjs-60-debuginfo libgjs0-debuginfo gnome-shell-debuginfo libmutter-4-0-debuginfo glibc-devel-debuginfo Then attach to coredump by 'coredumpctl gdb', collect information by: thread apply all bt full call gjs_dumpstack() -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c17
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c18
--- Comment #18 from Guillaume GARDET
(In reply to Guillaume GARDET from comment #14)
Created attachment 809425 [details] gdb 'thread apply all bt full'
Could you install these packages first: libmozjs-60-debuginfo libgjs0-debuginfo gnome-shell-debuginfo libmutter-4-0-debuginfo glibc-devel-debuginfo
Then attach to coredump by 'coredumpctl gdb', collect information by: thread apply all bt full
Done in new attachment.
call gjs_dumpstack()
returns "You can't do that without a process to debug." -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c19
--- Comment #19 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c20
--- Comment #20 from xiaoguang wang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c21
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c22
--- Comment #22 from xiaoguang wang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c24
--- Comment #24 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c25
--- Comment #25 from xiaoguang wang
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c26
--- Comment #26 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455
http://bugzilla.opensuse.org/show_bug.cgi?id=1138455#c27
Guillaume GARDET
I already did a rebuild of gjs some times ago. I triggered a rebuild of mozjs60 now.
Let's see how it goes.
Ok, I installed mozjs60 rpms from openSUSE:Factory:ARM with: osc get binaries openSUSE:Factory:ARM mozjs60 standard aarch64 on a broken qemu image from 20190705, and after a reboot, gnome is started properly! So, next openQA snapshot should show this bug as fixed. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com