Log in not available after lock screen with multi-monitor

Bug #1315369 reported by Jane Silber on 2014-05-02
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
xf86-video-intel
Invalid
Medium
linux (Ubuntu)
High
Maarten Lankhorst
Trusty
High
Unassigned
unity (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Unassigned

Bug Description

After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo.

Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all.

I can't reproduce this if I select "lock screen" from the UI, but it happens reliably if it locks due to inactivity.

Other info:
- I am running a fresh install of 14.04
- I have it set to lock after 5 min of inactivity, and require login after lock
- I have an external monitor, configured to be on the left side of the laptop screen
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jane 2184 F.... pulseaudio
 /dev/snd/controlC0: jane 2184 F.... pulseaudio
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec
InstallationDate: Installed on 2014-05-01 (20 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: Dell Inc. Dell System XPS L321X
Package: unity 7.2.0+14.04.20140416-0ubuntu1
PackageArchitecture: i386
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
Tags: trusty trusty
Uname: Linux 3.13.0-24-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/09/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 085X6F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L321X
dmi.sys.vendor: Dell Inc.

tags: added: lockscreen

What happens if you move the mouse on the external monitor?
Does the login prompt appear?
Or, are you able to just type (without seeing anything) and hit enter to get in?

The blank screen thing doesn't seem an unity issue, though. Since if you can see the ubuntu logo on the laptop screen, then it means that unity is not blanking the screen anymore, but it looks like that a lower level component (unity-settings-daemon's power module?) didn't turn that monitor on.

Changed in unity (Ubuntu):
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Jane Silber (silbs) wrote :

I can't get the mouse over to the external monitor. I can move it around in the laptop screen, but can't escape the boundaries of that screen when this is happening.

I tried typing the password (without being able to see anything), but that didn't work.

One more check to figure out where the problem might be:
 - Ctrl + Alt + F1
 - Login there and run:
     COMPIZ_CONFIG_PROFILE=ubuntu DISPLAY=:0 compiz --replace

At this point, go back with Ctrl+Alt+F7, and there unity should reload. If it resumes your session properly then it seems an unity's fault.

You can also just run "unity" from tty1, but that will relock your session. If compiz doesn't seem to reload try with a "killall -9 compiz" before.

PS: if you want to lower the idle delay needed to blank and lock the screen for testing purposes you can use
  gsettings set org.gnome.desktop.session idle-delay 1 # means 1 second

Use this to reset the default values instead:
  gsettings reset org.gnome.desktop.session idle-delay

Jane Silber (silbs) wrote :

Thanks Marco. I'm on the road for the next 10 days - will try this and give fedback when I'm back at my desk.

Jane Silber (silbs) wrote :

Hi Marco. I tried the steps from comment #3, but no luck. After Ctrl + Alt + F1 I can see the login prompt, but am not able to login as neither the laptop keyboard nor an external keyboard seem to be recognised (nothing happens - no letters, no error, no feedback). And since the keyboard isn't recognised, I can't even Ctrl + Alt + F7 to get back to Unity.

This is really strange... Because it's weird that the keyboard works once to go to tty1 and then it stops to send events...

Anyway I would say at this point that unity doesn't seem to be the guilty here.
Just another way, to make sure this is the case, enable the OSK (this would fallback to the old gnome-screensaver):
  gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true

Then give it another try, if you still get this problem, this is definitely not an unity issue.

Use this command to reset the on-screen-keyboard setting afterwards
  gsettings reset org.gnome.desktop.a11y.applications screen-keyboard-enabled

Jane Silber (silbs) wrote :

Marco - if you don't think it's unity, can you reassign to wherever you think is more appropriate? Thanks

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1315369

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

apport information

tags: added: apport-collected trusty
description: updated

apport information

Jane Silber (silbs) wrote : CRDA.txt

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-key
Changed in linux (Ubuntu Trusty):
importance: Undecided → High
status: New → Confirmed
Maarten Lankhorst (mlankhorst) wrote :

Can you get the syslog while booting with drm.debug=6 added to the kernel command line? That should get more information about the modeset failure.

Changed in linux (Ubuntu):
assignee: nobody → Maarten Lankhorst (mlankhorst)
status: Confirmed → Incomplete
Jane Silber (silbs) wrote :

Hi Maarten - happy to do that, but I need more explicit instructions.

Also, I've now seen this happen twice under slightly different circumstances. When I first reported this, I was referring to a situation in which my screen automatically locks after inactivity. To avoid that, I have now changed it so that it doesn't lock, but it does turn off after inactivity and am getting the same behaviour (i.e,. external monitor black, can't do anything on laptop, unplugging monitor makes both go black). I've now had to change to neither lock nor turn off after inactivity in order to maintain a functional system, but obviously this isn't an ideal config.

Maarten Lankhorst (mlankhorst) wrote :

ok, press e during boot in grub, you'll see a line with 'linux /boot/vmlinuz-*', add drm.debug=6 to the end, then boot normally with ctrl-x or f10 and force the bad things to happen. attach the resulting /var/log/dmesg to the bug :)

Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu Trusty):
status: New → Confirmed
Andy Whitcroft (apw) wrote :

To be explicit. We would like to obtain a system log with graphics debugging enabled, after reproducing the problem. We believe the following steps should achieve that:

1) reboot, interrupt grub, and add "drm.debug=6" to the kernel command line. There is a good guide on how to do this at the URL below, see the section "Temporarily Add a Kernel Boot Parameter for Testing":

   https://wiki.ubuntu.com/Kernel/KernelBootParameters

2) reproduce the issue

3) hit ctrl-alt-F1 to get the text login, and then hit the power button which should trigger a clean reboot.

4) boot normally, login and attach the files /var/log/dmesg, /var/log/dmesg.0 and /var/log/syslog.

Hope that makes sense.

Jane Silber (silbs) wrote :

Weirdly, this isn't happening as reliably as it used to. It still happens, but not 100% of the time, so I've hard trouble capturing it. I've applied some updates since I first reported it, so that may be changing the behaviour somewhat. I'm definitely still seeing it - just not every time.

And I'm seeing new things too. The dmesg.0 and syslog file I'm attaching today were captured after a similar issue (but not exactly the same). After the screen dimmed and locked, when I moved the mouse the monitor was blacked out and laptop screen on (as originally reported) but this time the login screen was on the laptop. However, I still couldn't log into it - no keyboard actions recognised, except ctrl-alt-F1 which blacked out the screen (but no console log in). I then had no option but to press power button.

I'll continue to try to capture logs with the orig symptoms, but hopefully these will help too.

Jane Silber (silbs) wrote :
Jane Silber (silbs) wrote :
  • syslog Edit (905.9 KiB, application/octet-stream)
Maarten Lankhorst (mlankhorst) wrote :

Seems to be a bug in intel modesetting alright, I'll contact the intel graphics devs and see if they can do anything with it.

Changed in unity (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in unity:
status: Incomplete → Invalid
Gregory (skygreg) wrote :

It's not related to Intel, I didn't have an Intel card. I have both an AMD and a Nvidia card, and this bug happens with both of them. I can't do an "apport-collect" as this bug is closed, please re-open it.

It's really annoying.

David Baucum (maxolasersquad) wrote :

I would just like to chime in that unlike silbs, this has become more frequent for me. I have already rebooted my machine three times today.

Today I turned off allowing my machine to automatically lock or turn off the screen. Hopefully that will stave off the problem until a fix is issued.

Gregory and David, in order to make sure weather your problem is related to unity or not, please follow the steps I wrote above to double check.

Thanks.

Jane Silber (silbs) wrote :

I've had to stop using my external monitor completely to avoid the problem. I tried turning off screen locking and screen dimming to avoid it, but that didn't help. The only thing I have found that leaves me in a reliable working state is to not use the external monitor.

David Baucum (maxolasersquad) wrote :

In my setup I have two monitor plugged into my laptop's base station. The graphics card will not support three monitors, so I only have the two external monitors activated. When I came in this morning the computer did not auto-lock or turn off the monitors and all was fine.

@3v1n0: There are many steps, do you mean the kernel arguments at grub? I will enter those the next time I reboot.

David Baucum (maxolasersquad) wrote :

I meant to add that my symptoms are 100% exactly like silbs, except that my left monitor exhibits the behavior of her external monitor and my right monitor exhibits the behavior of her laptop's screen.

Rodrigo Vivi (rodrigo-vivi-y) wrote :

Could you please attach your /var/log/Xorg.0.log?

David Baucum (maxolasersquad) wrote :

Added.

I added the kernel options and turned back on locking and turning off the monitor. Hopefully when I come back from lunch the problem will show. If so I will upload a new Xorg.0.log file.

Rodrigo Vivi (rodrigo-vivi-y) wrote :

Thanks.

Could you please test with a different kernel? It would help us to verify if there is already a patch for this issue available.

If possible test with our development branch drm-intel-nightly from http://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-nightly

jchysk (jchysk) wrote :

I have a 4-monitor set up and idling out to the lock screen seems to black screen freeze it about 25% of the time since 14.04 update. I'm able to restart lightdm via SSH in order to bring the screen back, but I still have to logout in order to get full access to all 4 monitors again after it happens.

I've attached my Xorg log

I'll try to run through the debugging a little bit later to attach the dmesg and syslog

David Baucum (maxolasersquad) wrote :

@rodrigo-vivi-y: Can you point me to instructions on what to do to boot from a nightly kernel?

David: No I meant the ones I've pointed out in the previous comments... #6 and #3 in particular.

David Baucum (maxolasersquad) wrote :

Here is my xorg logs during a crash while using the drm.debug=6 kernel option.

David Baucum (maxolasersquad) wrote :

Here is the dmesg log.

Chris J Arges (arges) wrote :

This looks like a similar bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935
There is a workaround identified here as adding the following to the kernel cmdline: linemodeset=0 video.allow_duplicates=1
In addition it seems like v3.9 and older kernels could potentially work meaning this could be a regression.

Jane Silber (silbs) wrote :

I tried the drm-intel-nightly kernel (from 18 June) and still experience the same problems as originally reported. I followed the steps in comment #31 to attach logs - those logs attached. The failure with these logs was slightly different though - behaviour was that I could see the login prompt, but no keyboard input was recognised - i.e., the same thing that I saw in comment #32. So sometimes failure is that I can't get to a screen with the login prompt and sometimes the failure is that the login prompt is there but I can't actually log in because keyboard input not recognised/processed.

Jane Silber (silbs) wrote :
Jane Silber (silbs) wrote :
Jane Silber (silbs) wrote :

I also tried the suggested workaround from comment #50 (with the Trusty kernel) and ran into the same problem. This time after screen locked, I had black external monitor, working laptop screen but without the login prompt, and no recognised keyboard input - I.e,. I couldn't event ctrl-alt-F1 to get to login prompt. I'll attach the logs below just in case they help.

Jane Silber (silbs) wrote :
Jane Silber (silbs) wrote :
Rodrigo Vivi (rodrigo-vivi-y) wrote :

Jane, could you please file a bug on bugs.freedesktop.org with this -nightly information?
There we definitely have a bug. That is similar/duplicated of 1324935 as Chris pointed out

Copied from launchpad.

After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo.

Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all.

I can't reproduce this if I select "lock screen" from the UI, but it happens reliably if it locks due to inactivity.

Other info:
- I am running a fresh install of 14.04
- I have it set to lock after 5 min of inactivity, and require login after lock
- I have an external monitor, configured to be on the left side of the laptop screen

Created attachment 101671
dmesg with WARN_ON's triggering

Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
status: Unknown → Confirmed
Yingying Zhao (yingying-zhao) wrote :

Would you please try this branch http://cgit.freedesktop.org/~pzanoni/linux/?h=bdw-pc8-fixes , Intel QA has verified an issue (which we think is same as this one) on this appointed branch.

I can't reproduce it on my desktop. i will try it on a laptop.

One of the strange things about this bug is the excessive amount of times the following message appears:
[drm:drm_dp_i2c_do_msg] native defer

If you have the available resources, can you reproduce this bug with a different monitor and/or a different DP cable?

Hi Maarten,

Our QA couldn't reproduce the issue here, Paulo couldn't reproduce the issue as well. I tried with IVB, eDP+HDMI and couldn't reproduce.

Then I went to our lab and got a SNB with LVDS and DP, installed a fresh 14.04, configured the external monitor to the left side and waited 5 minutes and also couldn't reproduce the issue. after 5 minutes it is lock and black and after I move the mouse everything just light up and I can normally log in.

On launchpad bugzillas I've seem people reporting the issue with non intel gpu.
or with hibrid using fglrx.

Please provide more info here. Can you double check if this happens even without hibrid and without the fglrx driver and provide the logs?

Thanks,
Rodrigo.

Link training fails -> black screen. Everything else is a red herring and are minor irrelevant issues.

Jane Silber (silbs) wrote :

I switched from a VGA to an HDMI cable. I have not encountered the problem again since that switch.

(In reply to comment #0)
> Copied from launchpad.

What's the launchpad bug?

(In reply to comment #6)
> (In reply to comment #0)
> > Copied from launchpad.
>
> What's the launchpad bug?

Sorry, saw that now in the see also.

Any idea if an adapter was used? One reporter at launchpad says the problem is not present after switching from VGA to HDMI:

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1315369/comments/63

Changed in xserver-xorg-video-intel:
status: Confirmed → Incomplete
tags: removed: kernel-key

I guess this one is either fixed or dead.

Changed in xserver-xorg-video-intel:
status: Incomplete → Invalid
Stephen Rasku (ubuntu-srasku) wrote :

I had this problem when I came back from lunch today. I am running a desktop with two DisplayPort monitors. I was able to move the cursor from monitor to monitor but no prompt appeared to allow me to enter my password. I had to go into a text console to reboot. I had a VM running which got aborted so this is very annoying.

AntoineM (antoine-merle) wrote :

This bug is still present for me with a fresh install of xenial.
I have a dual-monitor setting with DVI and HDMI.

As noted before, the behaviour is erratic, it does not happen every day or after each locked screen.
I am mostly unable to log in (unresponsive log-in screen or black screen) after relatively long periods of inactivity such as when I come back to the office in the morning.

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

Other bug subscribers

Remote bug watches

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