![]() |
2011-05-19
, 07:09
|
|
Posts: 1,411 |
Thanked: 1,330 times |
Joined on Jan 2010
@ Tatooine
|
#2
|
![]() |
2011-05-19
, 08:53
|
Posts: 169 |
Thanked: 56 times |
Joined on Jan 2010
@ Italia
|
#3
|
I'm sure this has come up before - try something like http://www.google.com/search?q=site%...20thumbnailerd
![]() |
2011-05-19
, 09:17
|
|
Posts: 1,411 |
Thanked: 1,330 times |
Joined on Jan 2010
@ Tatooine
|
#4
|
You should find who is asking hildon-thumbnail to work.
You can run dbus-monitor in a console and check who is asking new thumbnails. Check if you find a D-Bus message like this:
method call sender=:1.106 -> dest=org.freedesktop.thumbnailer serial=14 path=/org/freedesktop/thumbnailer/Generic; interface=org.freedesktop.thumbnailer.Generic; member=Queue
If so, you know that ":1.106" is asking the thumbnail. You can find the pid of ":1.106" with the following command:
dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID string::1.106
Maybe there is not a lot of thumbnail requests but only one thumbnail request which is stuck using 100% of CPU? You can check with the command "ls -l /proc/1442/fd" where 1442 is the pid of hildon-thumbnailerd. If the same photo is open for a long time, it may be a problem.
In any case, killing it should not be a problem (except that the thumbnails currently created will fail of course): it is restarted automatically (by D-Bus activation, see /usr/share/dbus-1/services/org.freedesktop.thumbnailer.service) when a process request a new thumbnail.
The Following User Says Thank You to jedi For This Useful Post: | ||
![]() |
2011-05-19
, 09:34
|
|
Posts: 1,079 |
Thanked: 1,019 times |
Joined on Mar 2010
|
#5
|
The Following User Says Thank You to stickymick For This Useful Post: | ||
![]() |
2011-05-19
, 09:58
|
Posts: 169 |
Thanked: 56 times |
Joined on Jan 2010
@ Italia
|
#6
|
Also, have you tried tweaking tracker.cfg ?
![]() |
2011-05-19
, 10:01
|
Posts: 169 |
Thanked: 56 times |
Joined on Jan 2010
@ Italia
|
#7
|
The Following User Says Thank You to cipper For This Useful Post: | ||
![]() |
2011-05-19
, 10:06
|
|
Posts: 1,411 |
Thanked: 1,330 times |
Joined on Jan 2010
@ Tatooine
|
#8
|
yes, I had disabled battery index but not initial battery indexing. It is possible to completely disable watching and indexing only when needed (when I open the image viewer)?
![]() |
2011-05-19
, 10:36
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#9
|
![]() |
2011-05-19
, 10:57
|
|
Posts: 1,079 |
Thanked: 1,019 times |
Joined on Mar 2010
|
#10
|
in fact I have noticed a black thumbnail of a photo I have shot yesterday, but the image viewer opened it correctly so I wasn't sure about that. But maybe the thumbnailerd uses a different engine with respect to the viewer. I deleted that image and up to now all seems fine. Anyway this thumbnailerd is really annoying...
I also tried to rebuild the database and restart the tracker, without success.
How to know which file is hanging the thumbnailerd?
thank yoy guys.