Created attachment 371054 [details] output from emerge --info When I start LXDE, I see the pcmanfm process at almost 100% CPU usage. This issue could be resolved with the new version (see #502134). However, I'm adding this bug for completeness and will close if it indeed works properly with the new version.
I can't reproduce it. I am using pcmanfm with LXDE and with openbox and it works as expected. Having said that, 1.2.0 is in the tree so update to that one if it fixes your problem
Strange. I have a similar setup (LXDE/Openbox) Still not working with pcmanfm 1.2.0 (output from top): 3068 tdalman 20 0 526300 14584 11900 R 98.6 0.1 169:17.61 pcmanfm When I kill pcmanfm and then start it in a shell I get the same result. Plus these warnings, though I suspect they are unrelated: ** (pcmanfm:32392): WARNING **: XDG_TEMPLATES_DIR is set to invalid path, ignoring it ** (pcmanfm:32392): WARNING **: modules directory is not accessible Any ideas ?
Oh, and this is what strace returns: poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily unavailable) where this is what /proc/<pid>/fd looks like for pcmanfm: tdalman@tarantula:/proc/538/fd> l total 0 lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 0 -> /dev/pts/1 lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 1 -> /dev/pts/1 lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 10 -> anon_inode:[eventfd] lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 11 -> anon_inode:inotify lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 12 -> anon_inode:[eventfd] lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 13 -> /proc/538/mounts lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 14 -> socket:[182511] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 15 -> anon_inode:[eventfd] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 18 -> socket:[159682] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 19 -> anon_inode:[eventfd] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 2 -> /dev/pts/1 lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 22 -> pipe:[180291] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 3 -> socket:[174953] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 4 -> anon_inode:[eventfd] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 5 -> socket:[182505] lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 6 -> pipe:[182507] l-wx------ 1 tdalman tdalman 64 Mar 9 10:34 7 -> pipe:[182507] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 8 -> socket:[182508] lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 9 -> anon_inode:[eventfd]
(In reply to Tolga Dalman from comment #3) > Oh, and this is what strace returns: > > poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, > events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, > {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) > recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily > unavailable) > poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, > events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, > {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) > recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily > unavailable) > poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, > events=POLLIN|POLLPRI}, {fd=6, events=POLLIN|POLLPRI}, {fd=13, events=0}, > {fd=22, events=POLLIN}], 6, 4294967295) = 1 ([{fd=22, revents=POLLHUP}]) > recvmsg(3, 0x7fff84a98980, 0) = -1 EAGAIN (Resource temporarily > unavailable) > > where this is what /proc/<pid>/fd looks like for pcmanfm: > tdalman@tarantula:/proc/538/fd> l > total 0 > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 0 -> /dev/pts/1 > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 1 -> /dev/pts/1 > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 10 -> anon_inode:[eventfd] > lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 11 -> anon_inode:inotify > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 12 -> anon_inode:[eventfd] > lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 13 -> /proc/538/mounts > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 14 -> socket:[182511] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 15 -> anon_inode:[eventfd] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 18 -> socket:[159682] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 19 -> anon_inode:[eventfd] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 2 -> /dev/pts/1 > lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 22 -> pipe:[180291] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 3 -> socket:[174953] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 4 -> anon_inode:[eventfd] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 5 -> socket:[182505] > lr-x------ 1 tdalman tdalman 64 Mar 9 10:34 6 -> pipe:[182507] > l-wx------ 1 tdalman tdalman 64 Mar 9 10:34 7 -> pipe:[182507] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 8 -> socket:[182508] > lrwx------ 1 tdalman tdalman 64 Mar 9 10:34 9 -> anon_inode:[eventfd] Could you report this upstream? We don't patch the pcmanfm code so whatever this is, is a general upstream bug.
Greetings, Since I got bit by this from my recent world update, I found a good workaround on this one from the Debian forums: 1.) Open PCManFM on the desktop. 2.) Go to Edit > Preferences > Volume Management. 3.) Uncheck all 3 Auto-mount options. 4.) Close PCManFM. 5.) Reboot (if necessary, or just restart the desktop). This worked for me where installing gvfs, as recommended in some of our forum threads, had no real change. The folks at Debian were pretty certain it stems from PCManFM trying to do all the listed mounts in /etc/fstab, but there was speculation whether this was being caused by CD/DVD entries or other Removable Media and/or external drive entries. On my system, I have both DVD and external drive entries, both with "noauto" options, in the fstab. I hope this helps others.
1.1.2 has been removed so I am marking this as obsolete