Control: clone 789118 -2
Control: retitle 789118 Cannot unlock screen after upgrading: Type of message,
'(sssb)', does not match expected type '(sssbb)'
Control: retitle -2 Cannot unlock screen after upgrading: Error: can't convert
this._frame to an integer
Control: reassign -2
On Wed, 25 Jan 2017 at 12:52:13 +, Simon McVittie wrote:
> With that incompatibility out of the way, there's another one:
>
> Jan 25 12:28:31 host gdm-session-worker.really[11355]:
> pam_unix(gdm-password:auth): conversation failed
> Jan 25 12:28:31 host
On Sun, 11 Oct 2015 at 15:48:10 -0700, Josh Triplett wrote:
> I just encountered this problem again, and in addition to the repeated
> authentication failure messages, I also saw a message on the lock screen
> matching this one I later found in logs:
>
> gnome-session[551]: (gnome-shell:956):
Package: gnome-shell
Version: 3.18.3-2
Followup-For: Bug #789118
Dear Maintainer,
Pretty close to this bug, although it's not dependant on upgrading Gnome. The
last few upgrades of SID have surfaced a similiar bug.
On setting my power settings via Gnome-Settings for 15 minutes, upon attempting
Package: gnome-shell
Version: 3.16.3-2+b1
Followup-For: Bug #789118
I just encountered this problem again, and in addition to the repeated
authentication failure messages, I also saw a message on the lock screen
matching this one I later found in logs:
gnome-session[551]: (gnome-shell:956):
Package: gnome-shell
Version: 3.16.2-4
Severity: grave
[Filing this on gnome-shell because it shows the lock/unlock screen, but
the bug might lie in another component.]
I just upgraded this system to GNOME 3.16 in unstable; I've included the full
list of
upgraded packages from the aptitude log
6 matches
Mail list logo
