Can't Delete Cabin from Land

Hi - I am a noobie, and I just bought a parcel of land on Kulla. I am brand new to building. Clueless, I added the cabin object to my property and tried making some edits. Now, I am unable to delete the cabin.

When I mouse over the cabin, I see
(no name)
Owner: Retrieving...
For Sale: Retrieving...

But I've been trying to figure out how to delete this for a couple hours now and it continues to say the above info. Selecting delete from the "pie" menu doesn't do any good. Selecting return from the "pie" menu also doesn't do any good.

What am I doing wrong? I had the same problem with a "tree" that I added from the building create menu.

If I move certain other objects to my property, I can delete them okay. I've tried selecting About Land from the pie menu and changing the restrictions to my land just in case that affects my (the owner's) rights as well as others, but nothing I try is working.

Suggestions? I'm getting pretty frustrated. Thanks!

Fleenie

Your cabin has "ghosted." It's a term we use to refer to an object that's been deleted (the server knows it's deleted) but for any one of a variety of reasons, the server never told the client on your system that the object was deleted.

So, you can still see it, because your client thinks it's still there. The info you see when you mouse over it is a result of your client asking the server for ownership information about the object. The server knows that it doesn't really exist, so it just ignores the request, and never sends back an answer.

You can either log off and log back on, and it'll be gone, or you can go for a long flying trip through about 3 sims or so to flush those objects out of your client cache. When you come back, they'll be gone.

Grim - You rule! Thanks very much for the quick reply and help. Logging off and back on did the trick. I'm thwapping my head saying "duhh" for not thinking of trying that two hours ago. My thanks again!

Fleenie

And THAT would be a perfect spot for the Lindens to enter in some "check" code... if the client thinks a prim is in a location, and the server says, "No, it was deleted," then the client should refresh and dump the prims, thus ENDING the ghosting problem.

A more unsavory poster might have said "log back on tomorrow, by then I'll have hacked your account and taken care of it for you" but I'm glad no one did.

And I can't believe ghosting is caused by end-user packet loss ONLY, as the Lindens seem to think for their bug report responses, since for small groups of people, everyone who was there at the time of the deletion sees the ghost.