[Bug 1718573] Re: Cannot unlock lock screen

2017-10-09 Thread jeremy-list
I can no longer replicate this bug with the 4.13.0-12-generic kernel.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718573

Title:
  Cannot unlock lock screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1718573] Re: Cannot unlock lock screen

2017-10-08 Thread Daniel van Vugt
Your GUI is hanging

Sep 21 14:30:43 hostname org.gnome.Shell.desktop[2881]: Window manager
warning: last_user_time (850630) is greater than comparison timestamp
(850629).  This most likely represents a buggy client sending inaccurate
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work
around...

for apparently the same reasons as the kernel:

Sep 21 15:25:24 hostname kernel: [drm:intel_pipe_update_end [i915]]
*ERROR* Atomic update failure on pipe A (start=56315 end=56316) time 495
us, min 763, max 767, scanline start 762, end 786

which is a hardware/firmware bug (!?):

Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST: CPU0: -1008111239 
force to 0
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -1008111239 CPU1: 0
Sep 21 14:16:41 hostname kernel:  #2
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -1008111239 CPU2: 0
Sep 21 14:16:41 hostname kernel:  #3
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -1008111239 CPU3: 0

I've never seen this happen before but have encountered plenty of code
over the years where such bugs were expected and had to be handled. It
sounds like you may need a different kernel, different BIOS, or new
firmware from Intel. It's certainly not gnome-shell's fault that it
might hang in such a volatile environment.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718573

Title:
  Cannot unlock lock screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1718573] Re: Cannot unlock lock screen

2017-10-06 Thread Sebastien Bacher
the log has errors about the stored configuration and the intel driver,
unsure which one is to blame

** Package changed: gnome-settings-daemon (Ubuntu) => gnome-shell
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718573

Title:
  Cannot unlock lock screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs