I've opened a new bug report: Bug #1874178
I'll mark myself as not affected by this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing session often requires
Thank you for this extra information. This allowed to narrow down the
bug you experienced to a simplified, shorter bug scenario.
I was suspecting that this may not be the same bug.
> It's not necessary to actually log in as the other user.
The bug discussed here only happens when the user is
The default value was 0 minutes. I set it to one minute and it made no
difference.
Incidentally, it seems that clicking on the "Switch user" button is
enough to trigger the problem. I did this because I couldn't remember
whether or not I'd added another user (I hadn't at that point). It's not
Hi Jane @irihapeti.
Thank you for reporting.
The settings
"delay locking after screensaver for..."
that was in
"Power Manager" settings,
tab "Security"
may correspond to what exists in 20.04 in
"Screensaver" settings,
tab "Lock Screen", and renamed to
"Lock the screen after the screen
A fresh install on an external USB3 drive is showing exactly the same
behaviour. Not a VM problem, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing
@Stéphane: Sorry, I didn't see this sooner. I must have forgotten to
subscribe. (oops)
In Xubuntu Final (iso 20200420.1), there is no Security tab in the Power
Manager. Only a "security" checkbox which controls "Lock screen when
system is going to sleep". I had a look in the configuration editor
Thank You Jane @irihapeti for your message.
Can you be more specific about the sequence of events and symptom
observed?
Also, can you tell:
(1) the parameters mentioned on comment #11
and (2) whether following the workaround on comment #14 works for you?
This may be very helpful to fix the bug
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1776475
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This seems to have reappeared recently in Xubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing session often requires several attempts.
To manage
## Thanks @vdrok
> automatically lock the session - when the screensaver is activated
> delay locking after screensaver for - 5 seconds
> lock screen when system is going to sleep - checked
Hmm, on my system the delay was set to something small (perhaps even 0).
## Thanks @mag3sh
> From
I had the exact same issue. In my case, I upgraded xubuntu 16.04 to 18.04 and
this issue started showing up. Pulseaudio was also not working.
>From further investigation, I noticed that chrome-remote-desktop was starting
>Xsession and this was causing issues. I removed that package and it fixed
Hey gouri, here is the info you requested:
automatically lock the session - when the screensaver is activated
delay locking after screensaver for - 5 seconds
lock screen when system is going to sleep - checked
marked the bug as affecting me
as I said I'm using archlinux, it's just the place I
I have a question for people experiencing this bug (yes, you included
:-).
Please:
* open xfce4-settings-manager,
* click icon "power manager",
* click tab "security",
* report what settings are there for when to "automatically lock the session",
"delay locking after screensaver for...", "lock
Using lightdm 1.26.0 in arch with xfce, and experiencing the same
behaviour as described in comment #7, with no errors in the logs. In my
case the delay between "session is locked" message and actual greeter
appearance is around 10 seconds.
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (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/1776475
Title:
So far, the logs basically show that lightdm does its job, and just does
it again when bug happens.
I have the feeling that the actual reason of the bug does not appear in
the log.
Perhaps something triggers a lock behavior, causing lightdm to just do
what it's supposed to do.
The problem might
Sometimes a variant of the bug happens: after typing password, the
expected session does not happen. Instead, a black screen with a white
message on center, saying that session is locked and I have to wait for
a moment. About 20 seconds later, a lightdm login greeter appears and
only after typing
Summary: twice, bug happened when service org.gtk.vfs.Daemon is
activating *after* org.a11y.atspi.Registry is activated.
Details below.
Bug just happened again on unlocking session (versus switching users).
I compared the output of journalctl.
## Around unlock time: nothing to see
Around
In order to investigate this bug, I started to write down each time I
switch user and whether it works.
The time information allowed to obtain time-bounded log extracts that
focus on relevant parts using journalctl --since ... --until ... .
After 3 "work" and one "fail" case, I observed a
** Attachment added: "Example log when things fail (bug happens)."
Bug still regularly observed.
This is not the same bug as #1656399 though it share some
characteristics.
In particular, the fact that both bugs do not always occur (but somehow
randomly) suggests that both are linked to a race condition somewhere in
lightdm logic.
--
You received this bug
As seen in attached files, this is Xubuntu 18.04, where lightdm is
default, no significant local customization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing
22 matches
Mail list logo
