Bug 1630899

Created attachment 1484751 [details]
File: backtrace

Created attachment 1484752 [details]
File: cgroup

Created attachment 1484753 [details]
File: core_backtrace

Created attachment 1484754 [details]
File: cpuinfo

Created attachment 1484755 [details]
File: dso_list

Created attachment 1484756 [details]
File: environ

Created attachment 1484757 [details]
File: limits

Created attachment 1484758 [details]
File: maps

Created attachment 1484759 [details]
File: mountinfo

Created attachment 1484760 [details]
File: open_fds

Created attachment 1484761 [details]
File: proc_pid_status

Created attachment 1484762 [details]
File: var_log_messages

Similar problem has been detected:

Tried to reproduce bug 1630899 on Wayland. Yes, it crashes also on Wayland, and takes the whole session with it, as usually.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
journald_cursor: s=1a38b5401d3c41189d87836b95e02866;i=19ba69;b=2a58ce89b3c84350a0afd1d52e27ccef;m=68007315;t=5763ae5ecd391;x=27fb41173c049384
kernel:         4.18.7-300.fc29.x86_64
package:        gnome-shell-3.30.0-3.fc29
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

This might be a violation of basic application functionality criterion (not sure), and also can be considered as a data loss scenario (you lose the whole session under wayland), so proposing for a blocker discussion.

trace shows an error "Function AsyncReadyCallback terminated with uncatchable exception"...

/var/log/messages has an interesting chunk:

Sep 19 15:44:22 phoenix gnome-shell[2134]: Function AsyncReadyCallback terminated with uncatchable exception
Sep 19 15:44:22 phoenix org.gnome.Shell.desktop[2134]: == Stack trace for context 0x55cb545951e0 ==
Sep 19 15:44:23 phoenix org.gnome.Shell.desktop[10340]: current session already has an ibus-daemon.
Sep 19 15:44:24 phoenix gnome-shell[10340]: g_dir_open_with_errno: assertion 'path != NULL' failed
Sep 19 15:44:24 phoenix gnome-shell[10340]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Sep 19 15:44:24 phoenix gnome-shell[10340]: g_dir_open_with_errno: assertion 'path != NULL' failed
Sep 19 15:44:24 phoenix gnome-shell[10340]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Sep 19 15:44:24 phoenix gnome-shell[10340]: Telepathy is not available, chat integration will be disabled.
Sep 19 15:44:24 phoenix gnome-shell[10340]: JS WARNING: [/home/kparal/.local/share/gnome-shell/extensions/no-title-bar.com/decoration.js 81]: reference to undefined property "screen"
Sep 19 15:44:24 phoenix gnome-shell[10340]: Extension "no-title-bar.com" had error: TypeError: global.screen is undefined
Sep 19 15:44:24 phoenix gnome-shell[10340]: JS WARNING: [/home/kparal/.local/share/gnome-shell/extensions/topIcons@gmail.com/extension.js 137]: reference to undefined property "screen"
Sep 19 15:44:24 phoenix gnome-shell[10340]: JS WARNING: [/home/kparal/.local/share/gnome-shell/extensions/topIcons@gmail.com/extension.js 137]: Too many arguments to method Shell.TrayManager.manage_screen: expected 1, got 2
Sep 19 15:44:24 phoenix gnome-shell[10340]: Extension "topIcons@gmail.com" had error: Error: Expected type object for Argument 'theme_widget' but got type 'undefined'
Sep 19 15:44:24 phoenix gnome-shell[10340]: Extension "workspaceNavigator" had error: SyntaxError: missing ( after for
Sep 19 15:44:24 phoenix gnome-shell[10340]: Some code called array.toString() on a Uint8Array instance. Previously this would have interpreted the bytes of the array as a string, but that is nonstandard. In the future this will return the bytes as comma-separated digits. For the time being, the old behavior has been preserved, but please fix your code anyway to explicitly call ByteArray.toString(array).
(Note that array.toString() may have been called implicitly.)
0 getCards() ["/home/kparal/.local/share/gnome-shell/extensions/shell-volume-mixer/utils.js":98]
1 _getCardDetails() ["/home/kparal/.local/share/gnome-shell/extensions/shell-volume-mixer/mixer.js":336]
2 wrapper() ["resource:///org/gnome/gjs/modules/_legacy.js":82]
3 _init() ["/home/kparal/.local/share/gnome-shell/extensions/shell-volume-mixer/mixer.js":49]
4 wrapper() ["resource:///org/gnome/gjs/modules/_legacy.js":82]
5 _Base.prototype._construct() ["resource:///org/gnome/gjs/modules/_legacy.js":18]
6 newClass() ["resource:///org/gnome/gjs/modules/_legacy.js":114]
7 enable() ["/home/kparal/.local/share/gnome-shell/extensions/shell-volume-mixer/extension.js":48]
8 enableExtension() ["resource:///org/gnome/shell/ui/extensionSystem.js":129]
9 loadExtension() ["resource:///org/gnome/shell/ui/extensionSystem.js":171]
10 _loadExtensions/<() ["resource:///org/gnome/shell/ui/extensionSystem.js":318]
11 _emit() ["resource:///org/gnome/gjs/modules/signals.js":128]
12 _loadExtension() ["resource:///org/gnome/shell/misc/extensionUtils.js":186]
13 wrapper() ["resource:///org/gnome/gjs/modules/_legacy.js":82]
14 scanExtensions/<() ["resource:///org/gnome/shell/misc/extensionUtils.js":192]
15 collectFromDatadirs() ["resource:///org/gnome/shell/misc/fileUtils.js":27]
16 scanExtensions() ["resource:///org/gnome/shell/misc/extensionUtils.js":191]
17 wrapper() ["resource:///org/gnome/gjs/modules/_legacy.js":82]
18 _loadExtensions() ["resource:///org/gnome/shell/ui/extensionSystem.js":320]
19 enableAllExtensions() ["resource:///org/gnome/shell/ui/extensionSystem.js":328]
20 _sessionUpdated() ["resource:///org/gnome/shell/ui/extensionSystem.js":359]
21 init() ["resource:///org/gnome/shell/ui/extensionSystem.js":367]
22 _initializeUI() ["resource:///org/gnome/shell/ui/main.js":229]
23 start() ["resource:///org/gnome/shell/ui/main.js":133]
24 <TOP LEVEL> ["<main>":1]

(In reply to Adam Williamson from comment #16)
> [/home/kparal/.local/share/gnome-shell/extensions/no-title-bar@franglais125.
> gmail.com/decoration.js 81]: reference to undefined property "screen"

Good call, I forgot to disable all my extensions. I tested again with all extensions disabled, and the crash still happens as described.

Do you have cleaner journal output from that try? It's a bit hard trying to unpick which messages may possibly be related and which might not.

Created attachment 1485489 [details]
journal without extensions (x11)

Created attachment 1485490 [details]
journal without extensions (wayland)

Discussed during the 2018-09-24 blocker review meeting: [1]

The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criteria:

"All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test".

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-09-24/f29-blocker-review.2018-09-24-16.05.txt

I see the same issue and also a very similar or identical stack trace with GNOME/Wayland and the TopIcons extension, but neither journalctl nor coredumpctl indicate any coredump. The session closes just as if it core dumped.

IRC comment from the other day when I brought this up in #gnome-shell:

21:11 < jadahl> fmuellner: kalev: could https://gitlab.gnome.org/GNOME/gnome-shell/issues/632 be related to the AsyncResult uncatchable error one? both have just as nice backtrace (none)

(Also adding jadahl to CC here.)

Been trying to reproduce by mounting and ejecting over and over again, but nothing crashes on my system. Could anyone who reproduces the crash provide a full backtrace of the crash with the debug symbols of "gvfs-client" installed?

I'm also no longer able to reproduce the crash. Previously I was able to crash it in 10 seconds consistently. Now I tried mounting and unmounting for several minutes, both on my desktop with updates-testing enabled, and in a VM with updates-testing disabled. No crash. Some update must have fixed this recently. I propose we close this, unless there's someone who can reproduce the crash with up-to-date packages.

Discussed during the 2018-10-15 blocker review meeting: [1]

The decision to classify this bug as a "RejectedBlocker" was made as this no longer seems to be reliably reproducible. We are not sure that it is fixed, but it at least no longer seems to have sufficient impact to be a blocker bug.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-10-15/f29-blocker-review.2018-10-15-16.00.txt

Tried again today, still can't reproduce it. It really seems like fixed, or the frequency of occurring went down by a few orders of a magnitude. Closing.

*** Bug 1640265 has been marked as a duplicate of this bug. ***

*** Bug 1641377 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Running Fedora 29 Gnome Wayland on a Quad display setup with radeon cards.
X11 applications (GTK2-based) do not respond to mouse clicks on primary display.
Screen Lock button from menu does not work, have to use Super-L.
Gnome Shell crashed after screen had been locked for a bit.
Can't run in Gnome Xorg mode, system crashes.

reporter:       libreport-2.9.6
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
journald_cursor: s=3bc9304ee7814efcae1d1b75f0a0a527;i=246a;b=8634806719f541328d93cfe70681cba5;m=2b4841e0c;t=57977d382c977;x=be553b7d9e188195
kernel:         4.18.16-300.fc29.x86_64
package:        gnome-shell-3.30.1-2.fc29
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1644745 has been marked as a duplicate of this bug. ***

*** Bug 1646162 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

i ran the random-background extension manually to load a new background. i'm not sure if this caused it, Chrome and Fritzing were also open at that moment.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
journald_cursor: s=942321f9610b4fa5bba21a7d3b2a8213;i=18eca;b=b641951675274c3e888368049a25e2e2;m=4049610315;t=57c4a23b01ca5;x=a16de09806a04e62
kernel:         4.19.4-300.fc29.x86_64
package:        gnome-shell-3.30.2-1.fc29
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            5008

Created attachment 1511858 [details]
File: backtrace

*** Bug 1657177 has been marked as a duplicate of this bug. ***

Reopening as per comment #33.

*** Bug 1672928 has been marked as a duplicate of this bug. ***

*** Bug 1674202 has been marked as a duplicate of this bug. ***

*** Bug 1677629 has been marked as a duplicate of this bug. ***

*** Bug 1684180 has been marked as a duplicate of this bug. ***

*** Bug 1687156 has been marked as a duplicate of this bug. ***

*** Bug 1691570 has been marked as a duplicate of this bug. ***

*** Bug 1692956 has been marked as a duplicate of this bug. ***

*** Bug 1693368 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.