It does appear that the blkid command without any parameter is hung, and that blkid was invoked from gparted.
When you run GParted, has Ubuntu been running for a while, or did you immediately start up GParted as soon as Ubuntu booted?
The reason I ask is I have a hypothesis that internally blkid has to run at least once to build a cache of device information. If the cache has not yet been built, then calls blkid (without the -c /dev/null to bypass the cache) will have to wait until the cache of device information has been built.
Warren,
It does appear that the blkid command without any parameter is hung, and that blkid was invoked from gparted.
When you run GParted, has Ubuntu been running for a while, or did you immediately start up GParted as soon as Ubuntu booted?
The reason I ask is I have a hypothesis that internally blkid has to run at least once to build a cache of device information. If the cache has not yet been built, then calls blkid (without the -c /dev/null to bypass the cache) will have to wait until the cache of device information has been built.