** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop. Repeat
We can close this bug report at this point. But I do appreciate the
follow up!
It turns out that there were two problems. The first was that 18.04 had
misconfigured the cryptoswap so that was not working at all. I reported
this separately before the release of bionic and I believe that this bug
I'm a little rusty and lost now. Can you please reword the bug title to
better describe the problem, if any?
** Changed in: gdm3 (Ubuntu)
Status: Expired => New
** Summary changed:
- Greeter/lockscreen fails to authenicate in an endless loop
+ Greeter/lockscreen fails to authenicate in an
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Tit
I can confirm the default swapfile behaviour in 18.04 looks weird, but I
don't know what the intention there is. Please log a separate bug for
that if you think it's a problem that needs fixing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've been studying the swap mess. It seems that the installer made a
swapfile called /swapfile and entered the line in /etc/crypttab as:
cryptswap1 /target/swapfile /dev/urandom swap,offset=1024,cipher=aes-
xts-plain64
which is the wrong, non-existent filename. So that seems to be an issue with
Thanks. Your comments led me to look at swap. There is no swap!
I installed from iso image several weeks ago (I am traveling and had a
bad ecryptfs corruption, not sure how this happened, and needed to
reinstall, and had this on my memory stick for testing).
I selected encrypted and had an prex
Come to think of it, some code might be returning ENOSPC ("No space left
on device") for a RAM-based operation.
So please also check how much RAM your system has before and after the
problem (run 'free -m'), and check 'ps' to see if any process is
unusually large.
** Changed in: gdm3 (Ubuntu)
"No space left on device" is coming up way too often in your log. I
can't explain that but it is still possibly relevant since a lot of
things are failing with that message.
Please monitor your disk usage carefully, before and after the problem
occurs again. And when it occurs again, please send u
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
I saw that. But the disk is far from full. Don't know what's up with
the /snap loopback devices. The hard drive itself is at 35%. Here's
the df output:
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 767M 1
Your log is showing "No space left on device"
So one of your disks is full, which may be the problem. Please check by
running:
df -h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
I'm still getting failures. This is with a fixed variety and no gnome-
shell extensions other than the default ubuntu extensions.
I don't see but reports similar to this, so I gather that others are not
generally plagued by this problem. Nonetheless, I appreciate any advice
or comment you have o
Thanks. That variety script was from an old version of variety, it
seems. I removed that and checked that the current scripts in
/usr/share/variety/scripts do not have that bug (looked like an
operation on a shell variable that may not exist). I did notice a few
variety crashes, but they do not
Thanks. I can see two recurring issues that might be the cause:
1. Something called 'variety' is failing:
Mar 17 08:16:14 magpie variety.desktop[1860]:
/home/weinberg/.config/variety/scripts/set_wallpaper: line 121: [: ==:
unary operator expected
Try fixing your script, or try uninstalling 'vari
Daniel,
I took a few days, but it did again fail with the same issue. I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested. Had to
reboot afterwards, to be able to log on to the desktop.
Hope this helps you spot the
Martin,
Can you please reproduce the problem with Wayland and then:
journalctl -b0 > todays-journal.txt
and attach the resulting file here?
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop
To manage notifications about this bug go to
Also a problem with the Wayland session. Not a big surprise. For now,
I've turn off the screen lock.
Not sure what else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greete
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred. I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
20 matches
Mail list logo
