Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1825626
Title:
nvLock: client timed out, taking the lock
To manage notifications about this bug go to:
No, but this event seems to happen most often when I go in/out of
fullscreen mode in celluloid (gnome-mpv) while playing a video with
subtitles:
feb. 16 10:00:12 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer
event7 debounce: scheduled expiry is in the past (-34ms), your system
This sounds like the Nvidia driver not being patient enough to cope with
gnome-shell's slowness. We have the same kind of issue with libinput
too. But it is improving with each gnome-shell release...
Can anyone identify a particular app that causes the problem more often
than others?
--
You
I can also report this bug
Feb 2 23:36:46 abriosi-laptop /usr/lib/gdm3/gdm-x-session[2407]:
nvLock: client timed out, taking the lock
kernel: 5.3.0-28-generic
nvidia: 430.50
ubuntu 18.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Tags removed: disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1825626
Title:
nvLock: client timed out, taking the lock
To manage notifications about this bug go to:
This has been happening for a bit on a work computer that went through
the built in update process to 19.10.
I seem to have gotten some relief by purging the nvidia drivers and
reinstalling. YMMV
1979 sudo apt purge nvidia-prime
1980 cat /var/log/prime-supported.log
1981 cat
This has been happening for a bit on a work computer that went through
the built in update process to 19.10.
I seem to have gotten some relief by purging the nvidia drivers and
reinstalling. YMMV
1979 sudo apt purge nvidia-prime
1980 cat /var/log/prime-supported.log
1981 cat
** Also affects: nvidia-graphics-drivers-430 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
To add on my previous comment: after moving to 19.10 (which I think also
comes with its pre-bundled nvidia driver, in any case I'm on 430 now),
the issue seems to be greatly mitigated compared with what I was having
on ubuntu 19.04... like I'm getting it once a day at most (no consistent
repro
Hello Everyone,
Any progress on this? I have the same problem here, and I had to deactivate my
Nvidia graphical card to be able to use my computer...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
After upgrading to ubuntu 19.10 (and mutter 3.34.1), I cannot
consistently reproduce it as I used to before (vscode tab drag or chrome
bookmark drag) but I still managed to get it randomly while upgrading
some gnome extension
--
You received this bug notification because you are a member of
Happy to try and make this happen.. I believe I can make it happen
pretty reliably on my system. Perhaps I can do something while profiling
gnome?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I guess we need to reproduce the mutter freeze that the Nvidia driver is
telling us about and with some luck force a stack trace or core dump
while it is happening.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Scrolling back I can't see why I was thinking that in comment #29.
** Tags added: eoan
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I am seeing this in 19.10 (POP_OS). Nvidia 1060. Mutter is indeed at
3.34.
Basically any time I alt-tab or otherwise switch between windows it
freezes and I get this syslog message.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Sounds like maybe a fix/workaround went into mutter 3.34. Does anyone
see this problem in Ubuntu 19.10?
** Tags added: bionic
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
same problem here
Ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1825626
Title:
nvLock: client timed out, taking the lock
To manage notifications about this bug go
Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ?
It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1202
A discussion at https://forum.manjaro.org/t/desktop-gnome-frequently-
get-frozen-few-seconds-and-works-again/81603/29 for manjaro seems to
nail down:
* It looks related to mutter (a gnome desktop component), since some guys
report that the freeze disappears when updating mutter.
* It does not
21 matches
Mail list logo
