Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

Bug #1727320 reported by Luca
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Gnome-shell crash and restart after the login and the screen flicker 1 time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470 laptop.

If I go in display settings I notice a second monitor Synaptics Inc 24'' which doesn't exist in reality. In Wayland after the screen stop flickering I don't have any other problem and that monitor is not present there.

xrandr | grep -i ' connected'
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have anything connected to this port

With Fedora 26 I don't have this problem but I'm not yet able to find what package is the culprit.
I believe this problem is related to Displayport 1.2, I don't have any dock nor I need to connect more than 1 monitor and would be satisfied just having one interface.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Oct 25 11:46:16 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-19 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Luca (zapduke) wrote :
affects: gnome-shell (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1505409, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Marvin Schlegel (marvinschlegel) wrote :

the exact same is happening to me, also on a latitude e7470, but with arch linux, 4.14.6 kernel.

I can also reproduce this behaviour including the not-in-reality-existing monitor showing up in xrandr in Ubuntu 17.10 live ISO. Latest Fedora 28 live also affected. As this problem doesn't go away with booting LTS kernels, I suppose it's not a kernel related bug, nor related to video drivers.

I'm also not sure if this is really a duplicate of bug #1505409, as this is new behavior and nothing a bug from 2015 could be. Ubuntu 16.04/10 not affected for example.

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Dima Ryazanov (dima-gmail) wrote :

I'm running into the exact same bug in Fedora 27 - but what's really bizarre is that I'm using the same hardware, Dell Latitude e7470.

Just filed a Gnome bug here: https://bugzilla.gnome.org/show_bug.cgi?id=791962

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1727320

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Luca (zapduke) wrote :

This bug is not a duplicate of bug #1505409, unfortunately I don't have the laptop anymore and I cannot say it's kernel related, but it may be a combination of kernel/graphics stack that shows an additional display due to the Displayport 1.2 capability.

Revision history for this message
Marvin Schlegel (marvinschlegel) wrote :

this bug seems fixed for me since updating E7470 BIOS to v1.18.5, which was released 12/22/17 here:

http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=ND42N&lwp=rt

as this leaves us with 0 affected users, I think this bug can be closed.

Luca (zapduke)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Fix Released
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Dima Ryazanov (dima-gmail) wrote :

Actually, I've upgraded to the 1.18.5 BIOS, but still seeing the bug.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does this happen to older Ubuntu releases, say 17.04?

Revision history for this message
Dima Ryazanov (dima-gmail) wrote :

(Note: I'm using Fedora, not Ubuntu - but figured, this info will still be useful to anyone affected by the bug.)

I've upgraded from Fedora 27 to 28, and the bug went away. My best guess is that updating Gnome from 3.26 to 3.28 is what fixed it. (The kernel versions don't seem to have any effect.)

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.