Red Hat Bugzilla – Bug 1265550
User applet not showing users
Last modified: 2017-08-15 05:26:35 EDT
Created attachment 1076120 [details]
Description of problem:
User applet not showing users
$ rpm -qa | grep control
I can't reproduce it with the same version of the control-center. How did you upgrade to F23? Does it happen with live system?
Do you see some errors when you run the control-center from command line?
What is output of the following command?
dbus-send --system --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers
$ gnome-control-center user-accounts
(gnome-control-center:4832): AccountsService-WARNING **: Failed to monitor logind session changes: No space left on device
$ dbus-send --system --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers
method return time=1443649196.822658 sender=:1.3 -> destination=:1.177 serial=267 reply_serial=2
object path "/org/freedesktop/Accounts/User1000"
$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 734M 15G 5% /dev/shm
tmpfs 16G 1,9M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/sda1 59G 19G 38G 33% /
tmpfs 16G 96M 16G 1% /tmp
/dev/sda3 500M 8,5M 492M 2% /boot/efi
/dev/sdb1 3,7T 3,5T 210G 95% /home
tmpfs 3,1G 12K 3,1G 1% /run/user/42
tmpfs 3,1G 80K 3,1G 1% /run/user/1000
/dev/sdd1 1,4G 1,4G 0 100% /run/media/mikhail/20150810-fedlet-i686
/dev/sdc1 1,5G 1,5G 0 100% /run/media/mikhail/Fedora-Live-WS-x86_64-23_B-T4
Created attachment 1078963 [details]
that means you're out of inotify watches and glib is failing to fall back to polling. Probably you have some automated backup software, or anti-virus software, or indexing software that's using up all your inotify watches.
You can work around the problem by putting
fs.inotify.max_queued_events = 65535
fs.inotify.max_user_instances = 65535
fs.inotify.max_user_watches = 65535
in /etc/sysctl.d/00-local.conf . Or if you can identify the software that's using up all your inotify watches, you can see if it has some configuration that limits its resource usage.
> Probably you have some automated backup software, or anti-virus software, or indexing software that's using up all your inotify watches.
I am not using backup and antivirus software. For indexing gnome-shell used tracker.
In my case a lot of i/o operations created google-chrome with a lot of tabs.
How I can sure of it?
i don't actually think there's a good way to enumerate the currently in use inotify watches at present, unfortunately. There's no lsof equivalent. There might be some way to run a systemtap script in the background while your session is running to keep a tally as they come and go, but that's probably tricky to set up.
Anyway, if you're getting that error message you're definitely out of inotify watches. I'd try the workaround and see if the problem goes away. if you suspect tracker, you could try killing it and see if the problem recovers.
(In reply to Ray Strode [halfline] from comment #8)
> Anyway, if you're getting that error message you're definitely out of
> inotify watches. I'd try the workaround and see if the problem goes away.
> if you suspect tracker, you could try killing it and see if the problem
Very strange, but killing tracker helps.
Created attachment 1079461 [details]
Somebody to deal with a this problem?
VSCode not works too because of this issue.
Created attachment 1117414 [details]
$ rpm -q glib2
problem still here
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.