[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-15 Thread spi
I added a systemd unit to stop autofs before going into suspend and start autofs again after resume. I haven't had any freezes with gdm3 anymore. But there is still a difference between Ethernet and Wifi. When connected to Wifi, it takes some seconds longer to unlock the user session. It seems

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-13 Thread spi
S2 instead of S3 didn't resolve the freezing too - took some time for the freezing to occur again. I stumbled across autofs and quick tests suggest with autofs turned off the freezing is gone. Is anybody else who is facing the freezing using autofs (or systemd's automount feature)? -- You

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-08 Thread spi
Still weird. The only Gnome extensions active are the follwoing ones from the Ubuntu repository: gnome-shell-extension-disconnect-wifi gnome-shell-extension-top-icons-plus gnome-shell-extension-ubuntu-dock I am still facing the freezing issues, but only if my Dell XPS13 notebook goes into S3

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-06 Thread spi
Ok, very weird. Removing just GSConnect (**) didn't help after all. I also had to remove: gnome-shell-extension-multi-monitors (*) No topleft hot corner (**) * these ones I installed from the Debian repository ** these ones are installed from https://extensions.gnome.org directly -- You

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-05 Thread spi
It seems it's the Gnome extension GSConnect (https://extensions.gnome.org/extension/1319/gsconnect/) in my case. Removed that and had no freezes since. Will examine further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-04 Thread spi
I had the following gnome extensions installed: GSConnect gnome-shell-extension-multi-monitors gnome-shell-extension-system-monitor gnome-shell-extension-caffeine gnome-shell-extension-disconnect-wifi gnome-shell-extension-shortcuts gnome-shell-extension-top-icons-plus

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-03 Thread spi
Have the same issue for quite some time. Couldn't find any pattern yet. Also have the impression gdm is waiting for something. It happens for me when I am on Ethnernet as well when on wifi. Have Dell XPS13 with Ubuntu 18.04.2, kernel 4.18.0-25-generic. Found today dozens in syslog:

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-05-20 Thread Ufos92
`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp` `sudo apt install nvidia-driver-` (check in GUI "Additional Drivers", mine is `430`) everything works. Even the screen layout wasn't broken. Thx to Dmitrii! -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-05-20 Thread Ufos92
Dell Precision 5520 freeze cuz of Nvidia confirmed. `sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-16 Thread Dmitrii Shcherbakov
Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot. If you see nvidia modules loaded, make sure that you select an xorg session on the login screen (not wayland) if you this control

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-16 Thread Dmitrii Shcherbakov
nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session:

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-06 Thread GrzesiekC
Also I did a lot of docking and unlocking (I've got 3 screen setup - built-in and two external monitors) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-06 Thread GrzesiekC
Hi all, can you cross check if you have any of these Gnome Shell plug-ins installed ? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813248/comments/10 I had both. First I uninstalled gnome-shell-extension-multi-monitors, did not help. Next, I uninstalled

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-15 Thread Diego Bersanetti
I have integrated graphics Intel HD4600 (Haswell) and discrete Nvidia GTX750M as well, which is managed by the Nvidia binary blob (the nouveau module is blacklisted) but usually disabled. I also have an external monitor always plugged in while at home, and nothing elsewhere. Unfortunately the bug

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-15 Thread Alex Garel
*-display description: VGA compatible controller produit: Skylake GT2 [HD Graphics 520] fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 07 bits: 64 bits

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-14 Thread GrzesiekC
Intel HD Graphics 520 - Internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 To manage notifications

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-14 Thread Pavlushka
Is all the affected one's have external graphics card and made any switch from external to integrated or from external to integrated then back or any kind of switch between external and integrated Graphics Cards? -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-06 Thread GrzesiekC
Thanks Diego. A similar situation here today. The whole Christmas season at home no issues at all - many suspends (lid close), with and without power supply. Coming today to the office, boom, unlock screen freeze after providing the password. One more hint - I've got the same SSID at home and my

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-04 Thread Alex Garel
Thanks Diego for the information, I also got the feeling that the bug is linked to logind waiting for something from the network or usb (not sure). I also wanted to add that this bug cause another annoyance : while I plug a USB storage key in, the system is blocked for a while : I can move the

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-01-04 Thread Diego Bersanetti
I have some new information: the bug is still happening as before, today I resumed my session and the login screen got stuck as usual; I left it there for a couple of minutes, then I unplugged and replugged the ethernet cable and, as soon as the network was up again, the session was unlocked!

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-11-27 Thread Alex Garel
I got the issue, today while using sudo (to use bindfs), just after I typed my password, whole gnome got blocked (the mouse cursor moving but without changing shape and being unable to type, neither have any action on any window or program), but I could log in a new tty console. Note also that

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-11-01 Thread Alex Garel
@grzesiekC, on my side, I quite frequently do the same (connecting / reconnecting), I will try to pay attention, to see if it's correlated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-31 Thread GrzesiekC
Well you can disregard #14, happened again. However, I notice one more thing, which my be helpful to troubleshoot the issue. In may case, it usually happens when I switch IP networks (wireless>wireless, wireless>wire, wire>wireless, etc). Here is an example: I can stay the whole weekend in my

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread Alex Garel
@grzesiekc thanks for the comment, on my side I have no such specific content. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread GrzesiekC
Hello again all, In my #10 comment, I forgot to mention that my system it is upgraded from ubuntu 16.04.4. As it is, on Thursday (25-10-2018), two major things happened: 1. The kernel was updated to - Linux E7470 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-25 Thread Alex Garel
** Attachment added: "tignasse-syslog2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5205390/+files/tignasse-syslog2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-25 Thread Alex Garel
** Attachment added: "tignasse-syslog1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5205389/+files/tignasse-syslog1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-25 Thread Alex Garel
I have the same bug here, and it's been quite a long time. It comes from time to time. After a while logins happens, but sometimes it's after a really long time ! I'm not sure but it seems uptime is generally high on my side. $ uptime 15:10:50 up 8 days, 19:07, 2 users, load average: 1,47,

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-23 Thread GrzesiekC
Hi all, You can add another person to the list Ubuntu 18.04.1 + all updates + meas 18.2.3 Dell 7470 using internal Intel(R) Core(TM) i5-6300U No Wayland. There are many more people like us: https://askubuntu.com/questions/1038723/slow-recovering-from-lock-screen-ubuntu-18-04

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-09-21 Thread Diego Bersanetti
This bug happened to me a number of times as well, on a fresh install of Ubuntu 18.04.1 on a Clevo W230ST (Intel Haswell, nvidia Optimus); it never happened after a lock screen but only after a suspend/resume; the nvidia proprietary drivers 396 are installed but not loaded, as I am using the Intel

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-09-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title:

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-08-10 Thread Po-Hsu Lin
I tried to reproduce this today on 4.15 with only one successful attempt, however I haven't figure what's the correct combination to make this fail. Now I'm running this laptop with 4.18rc8 for daily work, will keep an eye on this issue to see if it can be reproduced. Also I will try to find a

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-08-09 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-08-08 Thread Po-Hsu Lin
This just happened again, with the same HW config. When this happens, I have zombie processes (was testing ssh-agent) related to gnome-session, not sure if this will be the cause. USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND sam 1590 0.0 0.0 0 0 ?

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-08-08 Thread Po-Hsu Lin
Hello Daniel, thanks for the reply, but I don't have any other USB device connected to this laptop except this Microsoft mouse (connected directly without any hub in between). ~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST

[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-08-08 Thread Daniel van Vugt
I think 13:69 is /dev/input/event5, which is your: Aug 8 10:45:02 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event5 - PixArt Microsoft USB Optical Mouse: device removed However I wouldn't think it's a problem with the mouse. More likely the kernel has detected a USB hub disconnect, which