Bug 1063871 - HDMI causes gnome-shell crash
Summary: HDMI causes gnome-shell crash
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-17 17:12 UTC by jean-christophe baptiste
Modified: 2017-10-20 16:02 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jean-christophe baptiste 2017-10-17 17:12:09 UTC 
Crashes are very easy to reproduce since today's snapshot (zypper dup):

Steps:

1. Open a gnome-shell session (wayland)

2. Open a few windows

3. Plug in/out an HDMI secondary display 2 or 3 times

4. gnome-shell crashes severely to log-in screen

Core dumps here:

https://my.pcloud.com/publink/show?code=VZDHjX7ZUlKhUc7xJGYPI9ayLJzHVyroyvty
Comment 1 Dominique Leuenberger 2017-10-17 18:28:20 UTC 
Please extract a backtrace, don't provide coredumps (TW is so fast living and most devs won't have the same set of packages installed, hence it is close to impossible to get the right debug info set together... best chance is on your machine)
Comment 2 jean-christophe baptiste 2017-10-18 16:53:31 UTC 
Sure, sorry.

Yesterday's backtraces are identical:

#0  0x00007f328593e0d0 in raise () at /lib64/libc.so.6
#1  0x00007f328593f6b1 in abort () at /lib64/libc.so.6
#2  0x00007f3287a8d96d in g_assertion_message () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f3287a8d9fa in g_assertion_message_expr () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f3285f4f07e in meta_monitor_manager_get_logical_monitor_from_number () at /usr/lib64/libmutter-1.so.0
#5  0x00007f3285f9cf96 in meta_workspace_get_work_area_for_monitor () at /usr/lib64/libmutter-1.so.0
#6  0x00007f32819776bd in  () at /usr/lib64/libffi.so.7
#7  0x00007f3281976bcf in  () at /usr/lib64/libffi.so.7
#8  0x00007f3286a1e378 in  () at /usr/lib64/libgjs.so.0
#9  0x00007f3286a1fb54 in  () at /usr/lib64/libgjs.so.0
#10 0x00002e83e200b0c0 in  ()
#11 0x00007fff48d72b80 in  ()
#12 0x00007fff48d72530 in  ()
#13 0x0000000000000000 in  ()

And I got an incomplete backtrace today:

#0  0x00007f93c2bf19c1 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd398412b0
Comment 3 jean-christophe baptiste 2017-10-18 17:22:59 UTC 
Again, in a few minutes (I am just surfing, checking emails):

% coredumpctl list
Wed 2017-10-18 19:13:00 CEST   3958  1000   100   6 none      /usr/bin/gnome-shell
Wed 2017-10-18 19:19:32 CEST   4724  1000   100   5 none      /usr/bin/gnome-shell

New versions of mutter/gnome-shell are buggy as hell (had no big issue for months before).
Comment 4 Michael Gorse 2017-10-20 15:25:21 UTC 
This might be https://bugzilla.gnome.org/show_bug.cgi?id=788607
I've applied the upstream patches to mutter and gnome-shell. Updated packages are in GNOME:Factory, but Tumbleweed doesn't have the updates just yet.
Comment 5 Bernhard Wiedemann 2017-10-20 16:02:57 UTC 
This is an autogenerated message for OBS integration:
This bug (1063871) was mentioned in
https://build.opensuse.org/request/show/535494 Factory / mutter