After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789040 - SIGSEGV at meta_logical_monitor_get_scale
SIGSEGV at meta_logical_monitor_get_scale
Status: RESOLVED DUPLICATE of bug 788764
Product: mutter
Classification: Core
Component: general
3.26.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2017-10-16 06:00 UTC by Anatol Pomozov
Modified: 2017-10-16 09:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.25/3.26


Description Anatol Pomozov 2017-10-16 06:00:09 UTC 
It is a followup for https://bugzilla.gnome.org/show_bug.cgi?id=730551

After recent Arch Linux updates (gnome shell 3.26.1+3+g43ec5280b, mutter 3.26.1+12+gd6e3193c2) I see a SIGSEGV crash when monitor goes out of sleep mode. I can easy to reproduce it locally. Here is the crash stack, is there any other info that can be helpful to you?

Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 238066

  • #0 meta_logical_monitor_get_scale
    at backends/meta-logical-monitor.c line 181
  • #0 meta_logical_monitor_get_scale
    at backends/meta-logical-monitor.c line 181
  • #1 get_window_geometry_scale_for_logical_monitor
    at wayland/meta-window-wayland.c line 73
  • #2 meta_window_wayland_get_geometry_scale
    at wayland/meta-window-wayland.c line 637
  • #3 meta_window_wayland_move_resize_internal
  • #4 meta_window_move_resize_internal
  • #5 meta_window_move_resize_now
    at core/window.c line 4205
  • #6 idle_move_resize
    at core/window.c line 4240
  • #7 call_idle_later
    at core/util.c line 866
  • #8 g_main_context_dispatch
  • #9 0x00007f3cc941df69 in
  • #10 g_main_loop_run
  • #11 meta_run
    at core/main.c line 648
  • #12 0x0000564930e9fe8c in
  • #13 __libc_start_main
  • #14 0x0000564930e9ffba in 






Comment 1


Jonas Ådahl





          2017-10-16 09:07:36 UTC
        



Thanks for reporting, however, the backtrace looks like the one in bug 788764 so closing this as dup.

*** This bug has been marked as a duplicate of bug 788764 ***