Bug#874621: screen lock cannot be unlocked in vnc session

2017-10-20 Thread Michael Biebl 
Control: severity -1 important

On Fri, 8 Sep 2017 12:22:37 +0530 Pirate Praveen  wrote:
> package: gnome-shell
> version: 3.22.3-3
> severity: grave
> justification: makes it unusable and it is a regression

Downgrading to important as this certainly doesn't make gnome-shell
unusable.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#874621: screen lock cannot be unlocked in vnc session

2017-09-08 Thread Pirate Praveen 
On 09/08/2017 01:39 PM, Simon McVittie wrote:
> You might also be able to use loginctl to list sessions, then something
> like "loginctl unlock-session 42" to unlock your session.
no, that did not work after I got locked in for the 3rd time. I was able
to lock and unlock manually, but the problem comes when it gets locked
after some idle time.

see logs attched


pravi@nishumbha:~$ loginctl list-sessions 
   SESSIONUID USER SEAT TTY 
12   1001 srud seat0/dev/tty2   
  2554   1000 pravi 
c1117 Debian-gdm   seat0/dev/tty1   

3 sessions listed.
pravi@nishumbha:~$ loginctl unlock-session 2554
pravi@nishumbha:~$ sudo loginctl unlock-session 2554
pravi@nishumbha:~$ loginctl session-status 2554
2554 - pravi (1000)
   Since: Fri 2017-09-08 22:22:50 IST; 4min 30s ago
  Leader: 13493 (sshd)
  Remote: 192.168.2.100
 Service: sshd; type tty; class user
   State: active
Unit: session-2554.scope
  ├─13493 sshd: pravi [priv]
  ├─13512 sshd: pravi@pts/4
  ├─13513 -bash
  ├─13803 loginctl session-status 2554
  └─13804 pager


signature.asc
Description: OpenPGP digital signature

Bug#874621: screen lock cannot be unlocked in vnc session

2017-09-08 Thread Pirate Praveen 
On 09/08/2017 01:46 PM, Simon McVittie wrote:
> On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
>> package: gnome-shell
>> version: 3.22.3-3
>>
>> This broke after a dist upgrade in sid yesterday.
> What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell
> hasn't been updated in sid since April, so unless your sid installation
> was previously extremely outdated, it wasn't a gnome-shell upgrade that
> triggered this.
attaching the dist-upgrade log
>
> After upgrading whatever packages triggered this, did you reboot, or
> log out and back in, or neither? If you didn't do either, the old
> gnome-shell will have continued to run with the old libraries, in which
> case we'd need to know which gnome-shell version and relevant libraries
> (clutter, mutter, gtk, gdk-pixbuf) were installed at the time you
> started the VNC session.
I rebooted.

tigervnc-standalone-server 1.7.0+dfsg-7

updated vnc libs: libgvnc-1.0-0:amd64 (0.6.0-3, 0.7.1-1),
libgtk-vnc-2.0-0:amd64 (0.6.0-3, 0.7.1-1),

attaching .vnc/xstartup

>
> Are there any relevant messages in syslog, the systemd Journal,
> ~/.cache/gdm/session.log (if you use gdm), or ~/.xsession-errors?
I use gdm, but there is no ~/.cache/gdm folder. Nothing in

~/.xsession-errors

> (Also, in future please use reportbug, which would have listed all the
> relevant packages after your upgrade already.)


Start-Date: 2017-09-07  12:29:08
Commandline: apt-get dist-upgrade
Requested-By: pravi (1000)
Install: fdisk:amd64 (2.29.2-4, automatic), libx265-130:amd64 (2.5-2, automatic), libgcc-7-dev:amd64 (7.2.0-4, automatic), libpython3.6-minimal:amd64 (3.6.2-5, automatic), libfyba0:amd64 (4.1.1-3, automatic), gir1.2-nm-1.0:amd64 (1.8.2-1, automatic), libvulkan1:amd64 (1.0.54.0+dfsg1-1, automatic), gnupg1-l10n:amd64 (1.4.22-1, automatic), gnupg-utils:amd64 (2.2.0-1, automatic), gedit-plugin-dashboard:amd64 (3.22.0-2, automatic), python3-olefile:amd64 (0.44-1, automatic), python-configparser:amd64 (3.5.0-1, automatic), gpg-wks-client:amd64 (2.2.0-1, automatic), libegl1:amd64 (0.2.999+git20170802-3, automatic), libblockdev-swap2:amd64 (2.12-2, automatic), libmaven-resolver-java:amd64 (1.0.3-2, automatic), udftools:amd64 (1.3-1, automatic), sntp:amd64 (1:4.2.8p10+dfsg-5, automatic), gir1.2-gepub-0.5:amd64 (0.5.2-1, automatic), libdw1:amd64 (0.168-1, automatic), gnome-user-docs:amd64 (3.25.90-2, automatic), libegl-mesa0:amd64 (17.2.0-2, automatic), libcommons-compress-java:amd64 (1.13-1, automatic), libarchive-cpio-perl:amd64 (0.10-1, automatic), libraw16:amd64 (0.18.2-2, automatic), libgslcblas0:amd64 (2.4+dfsg-6, automatic), gnupg1-curl:amd64 (1.4.22-1, automatic), libgl1:amd64 (0.2.999+git20170802-3, automatic), mdadm:amd64 (4.0-1, automatic), fonts-smc-karumbi:amd64 (1.0-1, automatic), cpp-7:amd64 (7.2.0-4, automatic), python-future:amd64 (0.15.2-4, automatic), python-automat:amd64 (0.6.0-1, automatic), libpython3.6-stdlib:amd64 (3.6.2-5, automatic), python3-asn1crypto:amd64 (0.22.0-1, automatic), libemf1:amd64 (1.0.9+git.10.3231442-1, automatic), fonts-smc-chilanka:amd64 (1.2.0-1, automatic), perl-modules-5.26:amd64 (5.26.0-7, automatic), libmaven-shared-utils-java:amd64 (3.1.0-1, automatic), libdap25:amd64 (3.19.0-1, automatic), gedit-plugin-multi-edit:amd64 (3.22.0-2, automatic), gpg-wks-server:amd64 (2.2.0-1, automatic), python3.6:amd64 (3.6.2-5, automatic), plymouth-label:amd64 (0.9.2-5, automatic), gpg:amd64 (2.2.0-1, automatic), libblockdev-crypto2:amd64 (2.12-2, automatic), fonts-smc-meera:amd64 (7.0-1, automatic), libsub-quote-perl:amd64 (2.004000-1, automatic), python-certifi:amd64 (2017.4.17-2, automatic), gedit-plugin-bracket-completion:amd64 (3.22.0-2, automatic), fonts-smc-raghumalayalamsans:amd64 (2.1.1-1, automatic), libnotmuch5:amd64 (0.25-6, automatic), libasan4:amd64 (7.2.0-4, automatic), libgles2:amd64 (0.2.999+git20170802-3, automatic), libblockdev-loop2:amd64 (2.12-2, automatic), libsnappy-jni:amd64 (1.1.4-1, automatic), libvoikko1:amd64 (4.1.1-1, automatic), libblockdev-fs2:amd64 (2.12-2, automatic), bubblewrap:amd64 (0.1.8-3, automatic), libntfs-3g872:amd64 (1:2016.2.22AR.2-2, automatic), libblockdev-part2:amd64 (2.12-2, automatic), fonts-smc-keraleeyam:amd64 (2.0-1, automatic), fonts-smc-suruma:amd64 (3.2.1-1, automatic), gedit-plugin-zeitgeist:amd64 (3.22.0-2, automatic), python3-unidiff:amd64 (0.5.4-1, automatic), libgsl23:amd64 (2.4+dfsg-6, automatic), libxmlsec1-nss:amd64 (1.2.24-4, automatic), chromium-common:amd64 (60.0.3112.78-1, automatic), libjim0.77:amd64 (0.77-2, automatic), golang-1.8-src:amd64 (1.8.3-2, automatic), libperl5.26:amd64 (5.26.0-7, automatic), python3.6-minimal:amd64 (3.6.2-5, automatic), libgmime-3.0-0:amd64 (3.0.1-4, automatic), gedit-plugin-draw-spaces:amd64 (3.22.0-2, automatic), binutils-x86-64-linux-gnu:amd64 (2.29-9, automatic), libstdc++-7-dev:amd64 (7.2.0-4, automatic), evolution-plugin-bogofilter:amd64 (3.24.5-3, automatic), libllvm5.0:amd64 (1:5.0-1, automatic), libglib2.0-dev-bin:amd64 (2.53.6-1,

Bug#874621: screen lock cannot be unlocked in vnc session

2017-09-08 Thread Simon McVittie 
On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
> package: gnome-shell
> version: 3.22.3-3
> 
> This broke after a dist upgrade in sid yesterday.

What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell
hasn't been updated in sid since April, so unless your sid installation
was previously extremely outdated, it wasn't a gnome-shell upgrade that
triggered this.

After upgrading whatever packages triggered this, did you reboot, or
log out and back in, or neither? If you didn't do either, the old
gnome-shell will have continued to run with the old libraries, in which
case we'd need to know which gnome-shell version and relevant libraries
(clutter, mutter, gtk, gdk-pixbuf) were installed at the time you
started the VNC session.

Are there any relevant messages in syslog, the systemd Journal,
~/.cache/gdm/session.log (if you use gdm), or ~/.xsession-errors?

(Also, in future please use reportbug, which would have listed all the
relevant packages after your upgrade already.)

Bug#874621: screen lock cannot be unlocked in vnc session

2017-09-08 Thread Simon McVittie 
On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
> Now I have to kill gnome-shell and use metacity to not lose the session
> or kill vncserver and restart session.

You might also be able to use loginctl to list sessions, then something
like "loginctl unlock-session 42" to unlock your session.

I'm somewhat surprised GNOME Shell works over VNC at all, given its
reliance on GL. Please describe your VNC session setup?

S

Bug#874621: screen lock cannot be unlocked in vnc session

2017-09-07 Thread Pirate Praveen 
package: gnome-shell
version: 3.22.3-3
severity: grave
justification: makes it unusable and it is a regression

This broke after a dist upgrade in sid yesterday. It was working
earlier. The password screen automatically gets submitted before
completion of password entry every few seconds. I initially thought it
was a problem with enter key of keyboard. But the keyborad is working fine.

This happened twice and I don't think it is a one off exception.

Now I have to kill gnome-shell and use metacity to not lose the session
or kill vncserver and restart session.



signature.asc
Description: OpenPGP digital signature