Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
I just took some updates to a number of graphic libraries on 16.04, and now I can't login to kubuntu. The symptom is that it takes my password on the greeter screen, but never updates the screen after that.
The messages include these possibly related kernel messages:
kernel: [ 701.564034] [drm:intel_
kernel: [ 701.564054] [drm:intel_
I'm currently running kernel 4.4.0-36.
Here are my most recent updates. The problem started after I rebooted. Of course that was the next time I logged in too...
Start-Date: 2016-09-07 08:46:04
Commandline: /usr/bin/
Remove: libcdaudio1:amd64 (0.99.12p2-14), linux-image-
End-Date: 2016-09-07 08:48:13
Start-Date: 2016-09-07 16:42:27
Install: libgnome-
Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-
End-Date: 2016-09-07 16:44:34
Start-Date: 2016-09-12 14:31:39
Commandline: /usr/sbin/synaptic
Requested-By: alanr (1000)
Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-
End-Date: 2016-09-12 14:32:17
It was after rebooting after updates that this occurred. My workaround is "rm -fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can log in...
If I try to log in again without doing this, the problem recurs. This happens even if I just log in and log back out, and try to log in again.
However, I may just found a better workaround - press ALT-CTRL-F1 then ALT-CTRL-F7, and then the next chunk of the login sequence occurs.
This makes it consistent with an issue reported in AskUbuntu http://
And it's possibly related to bug https:/
In fact, each time I do this, I get a little further in the login sequence. It appears that the trigger for this bug is likely the prompts to provide passwords for my various ssh private keys (I have four). This also includes prompts from the KDE wallet manager for me to use the KDE wallet - and I don't use that feature.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for `/apps/
Date: Thu Sep 15 07:53:07 2016
DistUpgraded: 2016-05-25 14:07:14,644 DEBUG Running PostInstallScript: './xorg_
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2014-07-12 (795 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
MachineType: ASUS All Series
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-05-25 (112 days ago)
dmi.bios.date: 01/16/2014
dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed from AMI)
dmi.bios.version: 1707
dmi.board.
dmi.board.name: P9D WS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnASUSTeKC
dmi.product.name: All Series
dmi.product.
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Thu Sep 15 07:51:50 2016
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 9393
vendor ACI
xserver.version: 2:1.18.3-1ubuntu2.3
Alan Robertson, thank you for reporting this and helping make Ubuntu better.
To clarify, if you boot into the kernel prior to the update, does this issue go away?