As I mentioned in comment #2, this can be worked around. The issue is
that GDM3 assumes that it can get an inotify watch and degrades
ungracefully when it can't.
** Summary changed:
- After a period of locked inactivity, gdm3 no longer lets me unlock my session
["No space left on device"]
+ gdm
Dan,
I agree in an ideal world all software, at least core software like
gdm3, should handle such errors more gracefully and keep working.
However finding the time and expertise to make that a reality means it's
probably not realistic any time soon.
A more realistic fix is to find what's using up
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1726996
** Tags added: unlock
** Summary changed:
- After a period of locked inactivity, gdm3 no longer lets me unlock my session
+ After a period of locked inactivity, gdm3 no longer lets me unlock my session
["No space left on device"]
--
You received this bug notification because you are a member o
(It's also worth noting that I couldn't get to a PTY at all, so I had to
restart my machine to be able to fix this.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1726996
Title:
Afte
This can be worked around by following the instructions at
https://support.code42.com/CrashPlan/4/Troubleshooting/Linux_real-
time_file_watching_errors, but it seems to me that GDM should handle
this gracefully somehow.
--
You received this bug notification because you are a member of Ubuntu
Desk
