gnome-shell crashes ending session upon DP monitor switch-away

Bug #1801110 reported by John
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

I have a DisplayPort switching arrangement consisting of a 4way DP switch that switches 2, daisy-chained DP monitors.

Many times, but not always, when switching the displays away from this host, gnome-shell crashes. Later, switching back, I'm presented with the gdm login screen, previous session is gone.

journal trace.

Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.735610:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.828123:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.829899:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.844313:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Oct 31 14:26:19 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142619.936305:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999619 s, l
Oct 31 14:26:20 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142620.866151:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00119 s, la
Oct 31 14:26:21 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142621.876094:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00083 s, la
Oct 31 14:26:22 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142622.866910:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00015 s, la
Oct 31 14:26:23 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142623.866649:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999805 s, l
Oct 31 14:26:24 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142624.866857:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00075 s, la
Oct 31 14:26:25 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142625.867939:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00054 s, la
Oct 31 14:26:26 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142626.867620:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999784 s, l
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Backtrace:
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x561135c42c39]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fd818e74e1f]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 2: /usr/bin/Xwayland (present_extension_init+0xce6) [0x561135bab416]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 3: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x390) [0x561135aed380]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 4: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x533) [0x561135aed6f3]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 5: /usr/bin/Xwayland (TimerSet+0x180) [0x561135c3c4b0]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 6: /usr/bin/Xwayland (TimerSet+0x1f8) [0x561135c3c578]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 7: /usr/bin/Xwayland (WaitForSomething+0x277) [0x561135c3c657]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 8: /usr/bin/Xwayland (SendErrorToClient+0x10c) [0x561135c0c95c]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 9: /usr/bin/Xwayland (InitFonts+0x3b6) [0x561135c10b36]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fd818c9c09b]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 11: /usr/bin/Xwayland (_start+0x2a) [0x561135ae21ea]
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Segmentation fault at address 0x0
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE)
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: Fatal server error:
Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Caught signal 11 (Segmentation fault). Server aborting

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
John (john-e-francis) wrote :

No crash file is produced in /var/crash at the time the crash occurs. There are plenty of whoopsie reports under my ID, but none from close to the time of the crash.

Since I see a segmentation fault, it seems a crash did occur.

Perhaps I need to enable more aggressive crash capturing somehow?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
John (john-e-francis) wrote :

bump

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

> Perhaps I need to enable more aggressive crash capturing somehow?

Yes, please follow step 3 in comment 1 to do that.

Changed in gnome-shell (Ubuntu):
status: Expired → Incomplete
Revision history for this message
John (john-e-francis) wrote :

...following step 3 in comment 1....
...rewiring monitors...

Please see newly filed bug 1811008

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. Moving to bug 1811008...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.