[Bug 1674765] Re: libvirt-qemu should be a system account

2017-08-15 Thread GrzesiekC
*** This bug is a duplicate of bug 1667113 *** https://bugs.launchpad.net/bugs/1667113 Hi all, There is another solution here https://askubuntu.com/questions/897026 /why-do-i-have-a-libvirt-qemu-account-in-lock-switch-account-options-in- ubuntu (Apr 14 at 11:11): "... For whatever reason

[Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-11 Thread GrzesiekC
The same here: Linux E7470 4.13.0-33-generic #36~16.04.1-Ubuntu SMP Wed Feb 7 23:32:33 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748812 Title: cannot

[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

2018-10-15 Thread GrzesiekC
Hi all, according to this site https://developer.mozilla.org/en- US/docs/Mozilla/Calendar/Calendar_Versions#Development_Snapshots - TB 60.2.1 requires 6.2.2.1 version of Lightning Also. I found this info: "... If you are using Linux and installed Thunderbird and/or Lightning by using the

[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-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-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

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-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-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-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 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-11-09 Thread GrzesiekC
The proposed package is unusable, the GUI is broken: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic Here is an output when run from terminal [7719, Main Thread] WARNING: failed to open shm:

[Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-11-18 Thread GrzesiekC
Hi Olivier, First of all, thank you for your support. I also forgot to mention that my current setup is an upgrade of 16.04.x. On the other hand, I've got a secondary laptop (working a semi server ATM) where I did a fresh 18.04.x a while ago. No issues with TB 68.2.1 there. Nevertheless, here

[Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-11-23 Thread GrzesiekC
Than you Olivier, I removed the apparmor profile by following this guide: https://help.ubuntu.com/community/AppArmor For the last couple of days no major issues. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

2019-11-18 Thread GrzesiekC
I've check the other laptop, no Apparmor profile there. $ sudo apparmor_status | grep thunderbird $ Strange, I cannot recall enabling it on my current laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.