tom arnall wrote:
If it's just a single-user box (and you're the single user), I'd just "sudo rm /tmp/kde-klorovwp0rg" and "sudo rm /tmp/ksocket-root" and "sudo rm /tmp/kde-root".i just tried to do an upgrade and got the following messages: ----snip--- Reading changelogs... Done Error: "/tmp/kde-klorovwp0rg" is owned by uid 1000 instead of uid 0. Link points to "/tmp/kde-root" Error: "/tmp/ksocket-klorobxLJlU" is owned by uid 1000 instead of uid 0. Link points to "/tmp/ksocket-root" and now the process is hung. what should i do? thanks, tom arnall
Or reboot (which will delete the contents of /tmp).I'd also keep in the back of my mind that this is slightly suspicious, but if it's just a personal workstation, I wouldn't think much more about it until and unless it happens again. Then I think I'd start doing a bit of forensics.
-- Kent