[Touch-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-12-01 Thread Alan Robertson
Please delete the words "needing to" from comment #8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1623969 Title: Cannot log in to kubuntu after update (Intel graphics +

[Touch-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-12-01 Thread Alan Robertson
@moontan - that sounds like a completely different bug. This bug is a graphics driver bug, and yours appears to be something to do with needing to ecryptfs key management. I wasn't using ecryptfs at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-11-16 Thread Alan Robertson
Sorry I didn't update this, but somewhere along the line, the problem went away - after another set of updates. I'm not sure which one(s). But it is definitely working again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-09-15 Thread Alan Robertson
Hi Christopher M. Penalver (@penalvch), I have tons of old kernels to choose from. What one would you like for me to try? Here are the choices: vmlinuz-3.19.0-28-generic vmlinuz-3.19.0-41-generic vmlinuz-4.2.0-36-generic vmlinuz-3.19.0-30-generic vmlinuz-3.19.0-42-generic

[Touch-packages] [Bug 1623969] [NEW] Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-09-15 Thread Alan Robertson
Public bug reported: 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: