Tons of "log_kioremote: RemoteDirNotify::FilesChanged" errors in ~/.xsession-errors

Bug #1595588 reported by Dmitry
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Running KUbuntu 16.04 under VmWare Workstation 12.

$ grep "log_kioremote: RemoteDirNotify::FilesChanged" .xsession-errors | wc -l
273216

After few minutes:

$ grep "log_kioremote: RemoteDirNotify::FilesChanged" .xsession-errors | wc -l
517520

$ tail .xsession-errors
()
()
log_kioremote: RemoteDirNotify::FilesChanged
()
()
()
log_kioremote: RemoteDirNotify::FilesChanged
()
()
()

$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1848744k,nr_inodes=205555,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=373308k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd,nsroot=/)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct,nsroot=/)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices,nsroot=/)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids,nsroot=/)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio,nsroot=/)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio,nsroot=/)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,nsroot=/)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,nsroot=/)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory,nsroot=/)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,nsroot=/)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer,nsroot=/)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
vmhgfs-fuse on /mnt/hgfs type fuse.vmhgfs-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=373308k,mode=700,uid=1000,gid=1000)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: kde-runtime 4:15.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: KDE
Date: Thu Jun 23 18:00:08 2016
InstallationDate: Installed on 2016-04-26 (58 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
SourcePackage: kde-runtime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dmitry (dmitrymq) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-runtime (Ubuntu):
status: New → Confirmed
Changed in kde-runtime (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Kubuntu Kjar (kubuntu-q) wrote :
Download full text (11.2 KiB)

I'd suggest bumping this up.. It's definitely the kded5 [kdeinit5] process, and it's written 36 GB of those messages in just the time it's taken me to create an account and log this comment, and eventually kded dies, taking title bars and borders with it. Hardly usable.

This install is i386 also, but bare metal on a Dell E6500. It was a 14.04->16.04 online upgrade.

==snip==

user1@kubuntu:/proc/5164$ cat cmdline ; cat io; ls -l fd
kded5 [kdeinit5]rchar: 40202083
wchar: 38370100152
syscr: 6534768
syscw: 36874857
read_bytes: 8192
write_bytes: 126373888
cancelled_write_bytes: 212992
total 0
lr-x------ 1 user1 user1 64 Jul 25 18:41 0 -> pipe:[45266]
l-wx------ 1 user1 user1 64 Jul 25 18:41 1 -> /home/user1/.xsession-errors
lr-x------ 1 user1 user1 64 Jul 25 18:41 10 -> /usr/share/mime/mime.cache
lrwx------ 1 user1 user1 64 Jul 25 18:41 11 -> /home/user1/.config/libaccounts-glib/accounts.db
lrwx------ 1 user1 user1 64 Jul 25 18:41 12 -> socket:[45293]
lrwx------ 1 user1 user1 64 Jul 25 18:41 13 -> anon_inode:[eventfd]
lrwx------ 1 user1 user1 64 Jul 25 18:41 14 -> anon_inode:[eventfd]
lr-x------ 1 user1 user1 64 Jul 25 18:41 15 -> /dev/urandom
lrwx------ 1 user1 user1 64 Jul 25 18:41 16 -> socket:[44517]
lrwx------ 1 user1 user1 64 Jul 25 18:41 17 -> socket:[44523]
lrwx------ 1 user1 user1 64 Jul 25 18:41 18 -> socket:[44524]
lrwx------ 1 user1 user1 64 Jul 25 18:41 19 -> anon_inode:[eventfd]
l-wx------ 1 user1 user1 64 Jul 25 18:41 2 -> /home/user1/.xsession-errors
lrwx------ 1 user1 user1 64 Jul 25 18:41 20 -> anon_inode:[eventfd]
lrwx------ 1 user1 user1 64 Jul 25 18:41 21 -> socket:[45373]
lr-x------ 1 user1 user1 64 Jul 25 18:41 22 -> anon_inode:inotify
lr-x------ 1 user1 user1 64 Jul 25 18:41 23 -> /proc/5164/mounts
lrwx------ 1 user1 user1 64 Jul 25 18:41 24 -> socket:[44810]
lr-x------ 1 user1 user1 64 Jul 25 18:41 25 -> /dev/rfkill
lrwx------ 1 user1 user1 64 Jul 25 18:41 26 -> anon_inode:[eventfd]
lrwx------ 1 user1 user1 64 Jul 25 18:41 27 -> socket:[45681]
lr-x------ 1 user1 user1 64 Jul 25 18:41 28 -> /var/lib/dpkg/status
lr-x------ 1 user1 user1 64 Jul 25 18:41 29 -> /var/cache/apt-xapian-index/index.2/record.DB
lrwx------ 1 user1 user1 64 Jul 25 18:41 3 -> socket:[45284]
lrwx------ 1 user1 user1 64 Jul 25 18:41 30 -> /dev/ptmx
lrwx------ 1 user1 user1 64 Jul 25 18:41 31 -> /dev/pts/1
lrwx------ 1 user1 user1 64 Jul 25 18:41 32 -> socket:[45691]
lrwx------ 1 user1 user1 64 Jul 25 18:41 33 -> socket:[45690]
lr-x------ 1 user1 user1 64 Jul 25 18:41 34 -> /dev/urandom
lrwx------ 1 user1 user1 64 Jul 25 18:41 35 -> socket:[45777]
lr-x------ 1 user1 user1 64 Jul 25 18:41 36 -> /var/cache/apt-xapian-index/index.2/spelling.DB
l-wx------ 1 user1 user1 64 Jul 25 18:41 37 -> /run/systemd/inhibit/7.ref|
lr-x------ 1 user1 user1 64 Jul 25 18:41 38 -> /var/cache/apt-xapian-index/index.2/synonym.DB
lr-x------ 1 user1 user1 64 Jul 25 18:41 39 -> /var/cache/apt-xapian-index/index.2/termlist.DB
lrwx------ 1 user1 user1 64 Jul 25 18:41 4 -> anon_inode:[eventfd]
lr-x------ 1 user1 user1 64 Jul 25 18:41 40 -> /var/cache/apt-xapian-index/index.2/postlist.DB
lr-x------ 1 user1 user1 64 Jul 25 18:41 41 -> /var/lib/apt/lists/archive.canonical.com_ubuntu...

Revision history for this message
Bob Tracy (rct) wrote :

Affects me too. Upgraded from trusty LTS to xenial LTS (i386) on a Dell D630 when the fun started. Per information posted elsewhere, a temporary workaround to stop the extreme CPU utilization and the spew into ~/.xsession-errors is to run "balooctl disable", then kill the running "baloo_file" process (which should take care of the "baloo_file_extractor" child process as well).

Revision history for this message
Leon (fellows) wrote :

Affects me too.
uname -a gives:
Linux kubuntu-acer 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:59 UTC 2016 i686 i686 i686 GNU/Linux

in my ~/.xsession-errors there are just two files, that apparently have changed.
But as stated above they are mentioned a lot!! and it does not stop (although they do not change).

("/home/leon/file1.log", "/home/leon/data/file1.csv")
()
log_kioremote: RemoteDirNotify::FilesChanged
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/file1.log") )
log_kioremote: result => KUrl()
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/data/file1.csv") )
log_kioremote: result => KUrl()
()
("/home/leon/file1.log", "/home/leon/data/file1.csv")
()
log_kioremote: RemoteDirNotify::FilesChanged
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/file1.log") )
log_kioremote: result => KUrl()
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/data/file1.csv") )
log_kioremote: result => KUrl()
()
("/home/leon/file1.log", "/home/leon/data/file1.csv")
()
log_kioremote: RemoteDirNotify::FilesChanged
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/file1.log") )
log_kioremote: result => KUrl()
log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/leon/data/file1.csv") )
log_kioremote: result => KUrl()
()
("/home/leon/file1.log", "/home/leon/data/file1.csv")
()

Thanks bob for the "workaround"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.