Thanks for the strace. So the main hald process does not do any disk access during that time. So let's do a more fine-grained testing: Let's kill the addons one by one and check which one is the culprit:
ps axo pid,cmd |grep hald-addon
This will show you a list of running hald helpers with their process ID number in front of it. Please use 'sudo kill <process ID>' to kill one after another and check in between whether the repeated disk access still happens. If it stops after killing a particular addon, please tell me its name. If it didn't stop, and the only processes left in
ps aux|grep hal
are 'hald' and 'hald-runner', then the culprit must be some other program (probably some that listens to hal via dbus) and we have to dig deeper.
Thanks for the strace. So the main hald process does not do any disk access during that time. So let's do a more fine-grained testing: Let's kill the addons one by one and check which one is the culprit:
ps axo pid,cmd |grep hald-addon
This will show you a list of running hald helpers with their process ID number in front of it. Please use 'sudo kill <process ID>' to kill one after another and check in between whether the repeated disk access still happens. If it stops after killing a particular addon, please tell me its name. If it didn't stop, and the only processes left in
ps aux|grep hal
are 'hald' and 'hald-runner', then the culprit must be some other program (probably some that listens to hal via dbus) and we have to dig deeper.
Thank you!