Switching users in Ubuntu/Ubuntu Gnome freezes graphics

Bug #1652644 reported by Vidar Hoel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

This bug was present in Ubuntu Gnome 16.04 LTS with GDM, but did a clean install of Ubutnu 16.04 LTS with Unity and LightDM, and the bug is still present.

How to reproduce:
1. Boot the system, wait for LightDM to start and show the Ubuntu Unity greeter.
2. Log in as a user.
3. From the power menu (top right), choose an other user
4. In the password-promt (greeter) for the user, type in the correct password

At this point, one of three thing might happen:
a- The desktop, desktop icons, Unity-launcher and main menu for the user is loaded. The user can use the system as expected!
b- The desktop, desktop icons and Unity-launcher the user is loaded. However, just before the main-menu-bar at the tops loads, the the graphics freezes. I can move the cursor, but that's it. It is not possible to click or do anything with the mouse-cursor.
c- Same as (b), but during this process the screen goes complete blank (black), with only the cursor showing (and moving).

When (b) or (c), pressing ALT+F1-F6 does not help, the screen just stays the same (except the cursor dispersers). Pressing ALT+F7 afterwards does not bring the cursor back.

The system has not frozen. I can SSH to the box and it lives as nothing has happened. It's only effecting the display/graphics.

This bug happens about 1/3 of the times I switch the user. Sometimes I can switch to and from users several times (2-5) before this bug comes to life.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-57-generic 4.4.0-57.78
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sitron 1903 F.... pulseaudio
Date: Mon Dec 26 16:58:42 2016
HibernationDevice: RESUME=UUID=9d82d48a-107c-4d15-844d-c4ba62a3d320
InstallationDate: Installed on 2016-12-18 (8 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
Lsusb:
 Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=2a82deba-0eba-4358-b17c-65be40fe066f ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-57-generic N/A
 linux-backports-modules-4.4.0-57-generic N/A
 linux-firmware 1.157.6
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: Intel Corp.
dmi.bios.version: GKPPT10H.86A.0060.2016.1021.1324
dmi.board.name: DCP847SKE
dmi.board.vendor: Intel Corporation
dmi.board.version: G80890-105
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0060.2016.1021.1324:bd10/21/2016:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-105:cvn:ct3:cvr:

Revision history for this message
Vidar Hoel (vidar-hoel) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Vidar Hoel (vidar-hoel) wrote :
Revision history for this message
Vidar Hoel (vidar-hoel) wrote :
Download full text (4.0 KiB)

I was tailing /var/log/kern.log when I switch to a new user, and then back to mine user again - then the screen goes blank. Here is the tail:

Dec 26 17:35:25 nuc gnome-session-binary[3980]: Entering running state
Dec 26 17:36:36 nuc kernel: [ 2890.006683] ------------[ cut here ]------------
Dec 26 17:36:36 nuc kernel: [ 2890.006725] WARNING: CPU: 1 PID: 1037 at /build/linux-7x12eW/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
Dec 26 17:36:36 nuc kernel: [ 2890.006728] vblank wait timed out on crtc 0
Dec 26 17:36:36 nuc kernel: [ 2890.006730] Modules linked in: cfg80211 snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep intel_rapl snd_pcm x86_pkg_temp_thermal intel_powerclamp corete
mp kvm_intel snd_seq_midi snd_seq_midi_event kvm snd_rawmidi irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd snd_seq joydev snd_seq_device input_leds snd_timer snd mei_me lpc_ich mei so
undcore mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid i915 e1000e i2c_algo_bit drm_kms_helper ahci syscopyarea libahci sysfillrect sysimgblt fb_sys_
fops drm ptp pps_core video fjes
Dec 26 17:36:36 nuc kernel: [ 2890.006795] CPU: 1 PID: 1037 Comm: Xorg Not tainted 4.4.0-57-generic #78-Ubuntu
Dec 26 17:36:36 nuc kernel: [ 2890.006798] Hardware name: /DCP847SKE, BIOS GKPPT10H.86A.0060.2016.1021.1324 10/21/2016
Dec 26 17:36:36 nuc kernel: [ 2890.006801] 0000000000000286 000000003f24334e ffff8802117abb08 ffffffff813f6f33
Dec 26 17:36:36 nuc kernel: [ 2890.006806] ffff8802117abb50 ffffffffc0067b38 ffff8802117abb40 ffffffff810812d2
Dec 26 17:36:36 nuc kernel: [ 2890.006811] ffff880035667800 0000000000000000 0000000000000000 000000000002a4a0
Dec 26 17:36:36 nuc kernel: [ 2890.006816] Call Trace:
Dec 26 17:36:36 nuc kernel: [ 2890.006825] [<ffffffff813f6f33>] dump_stack+0x63/0x90
Dec 26 17:36:36 nuc kernel: [ 2890.006831] [<ffffffff810812d2>] warn_slowpath_common+0x82/0xc0
Dec 26 17:36:36 nuc kernel: [ 2890.006836] [<ffffffff8108136c>] warn_slowpath_fmt+0x5c/0x80
Dec 26 17:36:36 nuc kernel: [ 2890.006842] [<ffffffff810c3da5>] ? finish_wait+0x55/0x70
Dec 26 17:36:36 nuc kernel: [ 2890.006864] [<ffffffffc00372e5>] drm_wait_one_vblank+0x1b5/0x1c0 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.006870] [<ffffffff810c4240>] ? wake_atomic_t_function+0x60/0x60
Dec 26 17:36:36 nuc kernel: [ 2890.006923] [<ffffffffc01dbe1a>] intel_atomic_commit+0x43a/0x6f0 [i915]
Dec 26 17:36:36 nuc kernel: [ 2890.006953] [<ffffffffc005000f>] ? drm_atomic_set_crtc_for_connector+0x6f/0xe0 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.006981] [<ffffffffc0051017>] drm_atomic_commit+0x37/0x60 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.006998] [<ffffffffc00e6dc6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
Dec 26 17:36:36 nuc kernel: [ 2890.007024] [<ffffffffc003fe42>] drm_mode_set_config_internal+0x62/0x100 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.007050] [<ffffffffc004449c>] drm_mode_setcrtc+0x3cc/0x4f0 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.007071] [<ffffffffc0035752>] drm_ioctl+0x152/0x540 [drm]
Dec 26 17:36:36 nuc kernel: [ 2890.007096] [<ffffffffc004...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Vidar Hoel, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

tags: added: bios-outdated-0061
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Vidar Hoel (vidar-hoel) wrote :

I have now tested the new kernel for two days, and unfortunately, after several user switches I got a blank screen again :-( However, the kernel does not output any errors. So it seems this bug is not kernel related.

Here is a log from lightdm, which is the only log I could find with an error:
[+2816.49s] DEBUG: Seat seat0: Switching to user erling
[+2816.49s] DEBUG: Seat seat0: Creating user session
[+2816.49s] DEBUG: Session pid=3701: Started with service 'lightdm', username 'erling'
[+2816.50s] DEBUG: Session pid=3701: Authentication complete with return value 7: Authentication failure
[+2816.50s] DEBUG: Session pid=3701: Sending SIGTERM
[+2816.50s] DEBUG: Seat seat0: Starting greeter to authenticate session
[+2816.50s] DEBUG: Seat seat0: Creating greeter session
[+2816.51s] DEBUG: Seat seat0: Creating display server of type x
[+2816.51s] DEBUG: Using VT 9
[+2816.51s] DEBUG: Seat seat0: Starting local X display on VT 9
[+2816.51s] DEBUG: DisplayServer x-2: Logging to /var/log/lightdm/x-2.log
[+2816.51s] DEBUG: DisplayServer x-2: Writing X server authority to /var/run/lightdm/root/:2
[+2816.51s] DEBUG: DisplayServer x-2: Launching X Server
[+2816.51s] DEBUG: Launching process 3702: /usr/bin/X -core :2 -seat seat0 -auth /var/run/lightdm/root/:2 -nolisten tcp vt9 -novtswitch
[+2816.51s] DEBUG: DisplayServer x-2: Waiting for ready signal from X server :2
[+2816.51s] DEBUG: Session pid=3701: Exited with return value 1
[+2816.51s] DEBUG: Seat seat0: Session stopped
[+2816.66s] DEBUG: Seat seat0 changes active session to
[+2816.92s] DEBUG: Got signal 10 from process 3702
[+2816.92s] DEBUG: DisplayServer x-2: Got signal from X server :2
[+2816.92s] DEBUG: DisplayServer x-2: Connecting to XServer :2
[+2816.92s] DEBUG: DisplayServer x-2: Error connecting to XServer :2
[+2817.20s] DEBUG: Got signal 10 from process 3702
[+2817.49s] DEBUG: Got signal 10 from process 3702

(Last three lines pops up when I tried to switch user and the bug appeared).

I assume this is an X/lightdm bug?

Revision history for this message
Vidar Hoel (vidar-hoel) wrote :

The tested kernel was: linux-image-4.10.0-041000rc2-generic

Revision history for this message
penalvch (penalvch) wrote :

Vidar Hoel, it appears you may be hitting multiple bugs simultaneously. Given the call trace no longer appears, it would either be the latest mainline kernel fixes this one issue, or doesn't manifests the bug anymore. I'll mark this Confirmed given that the originally scoped issue isn't resolved.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.