Since it seems this bug manifests itself only after certain 'apt upgrade' runs that call ureadahead triggers, would backporting the fix from Vivid ureadahead package ver. 0.100.0-19 be an option to resolve it? I'm thinking of the fix for https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/777224 and the non-systemd change done to http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ureadahead/vivid/revision/32#debian/rules
Since it seems this bug manifests itself only after certain 'apt upgrade' runs that call ureadahead triggers, would backporting the fix from Vivid ureadahead package ver. 0.100.0-19 be an option to resolve it? /bugs.launchpad .net/ubuntu/ +source/ ureadahead/ +bug/777224 and the non-systemd change done to http:// bazaar. launchpad. net/~ubuntu- branches/ ubuntu/ vivid/ureadahea d/vivid/ revision/ 32#debian/ rules
I'm thinking of the fix for https:/