Attachment 137017 Details for Bug 100745 – gnome-shell coredump after amdgpu displayport link status failed

gnome-shell coredump after amdgpu displayport link status failed

gnomeshell_crash.txt (text/plain), 1.45 KB, created by Dimitrios Liappis on 2018-01-29 11:07:40 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dimitrios Liappis

Created: 2018-01-29 11:07:40 UTC

Size: 1.45 KB

patch

obsolete

>systemd-coredump[19219]: Process 19048 (gnome-shell) of user 1000 dumped core.
>Stack trace of thread 19048:
> #0  0x00007ffb976e3e4c meta_window_move_resize_request (libmutter-1.so.0)
> #1  0x00007ffb976e4d03 meta_window_x11_configure_request (libmutter-1.so.0)
> #2  0x00007ffb976d9acd handle_other_xevent (libmutter-1.so.0)
> #3  0x00007ffb976da9fb xevent_filter (libmutter-1.so.0)
> #4  0x00007ffb96929a7f gdk_event_apply_filters (libgdk-3.so.0)
> #5  0x00007ffb96929d69 _gdk_x11_display_queue_events (libgdk-3.so.0)
> #6  0x00007ffb968f3820 gdk_display_get_event (libgdk-3.so.0)
> #7  0x00007ffb96929b12 gdk_event_source_dispatch (libgdk-3.so.0)
> #8  0x00007ffb991a5b77 g_main_context_dispatch (libglib-2.0.so.0)
> #9  0x00007ffb991a5f20 g_main_context_iterate.isra.23 (libglib-2.0.so.0)
> #10 0x00007ffb991a6232 g_main_loop_run (libglib-2.0.so.0)
> #11 0x00007ffb976ba7bc meta_run (libmutter-1.so.0)
> #12 0x0000559e7105042c main (gnome-shell)
> #13 0x00007ffb9703500a __libc_start_main (libc.so.6)
> #14 0x0000559e7105056a _start (gnome-shell)
>
>Stack trace of thread 19057:
> #0  0x00007ffb9711f3db __poll (libc.so.6)
> #1  0x00007ffb991a5e99 g_main_context_iterate.isra.23 (libglib-2.0.so.0)
> #2  0x00007ffb991a5fac g_main_context_iteration (libglib-2.0.so.0)
> #3  0x00007ffb83d0e42d dconf_gdbus_worker_thread (libdconfsettings.so)
> #4  0x00007ffb991cd486 g_thread_proxy (libglib-2.0.so.0)
> #5  0x00007ffb973fe61b start_thread (libpthread.so.0)
> #6  0x00007ffb9712b98f __clone (libc.so.6)

Actions: View

Attachments on bug 100745: 130957 | 135668 | 137017

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.